Privacy and participant rights

Open reading and public records

You can read released pages and search public records without creating an account. Our hosting and security providers may process ordinary request metadata such as IP address, browser information, timestamps, and requested paths for delivery, abuse prevention, and reliability. We do not sell this data or use it to build political persuasion profiles.

Receipted Discord contributions

Ordinary Discord conversation is not automatically a formal contribution. When you explicitly confirm exact text, Campaign Core stores that contribution for campaign-only review under policy public-discord-input@2.

By confirming, I ask the Korey Streich Campaign Committee / AI for Wisconsin to store the exact text shown for campaign-only review for 30 days. This includes access-restricted encrypted recovery copies, which are scheduled for automatic pruning on the next 15-minute enforcement cycle after each snapshot reaches 30 days. Discord displays exact contribution text only through transient private responses, not persistent bot direct messages. A deletion removes the active copy promptly and creates a minimized tombstone that must be reapplied before any restored service starts; encrypted recovery blocks remain inaccessible until their bounded snapshot is pruned. I understand this is one individual, unweighted contribution—not a vote, publication permission, endorsement, adoption, or promised response. I do not grant public attribution, contact, cross-session memory, model-training, or organization-transfer permission. My receipt lets this same Discord account privately inspect, correct, withdraw, or delete the contribution during the retention period.

Campaign Core receives keyed one-way digests for the Discord participant, session, channel, and message—not the raw Discord identifiers. The separately protected digest key is retained so the same Discord account can exercise receipt rights. Unconfirmed text expires from a short-lived in-process challenge and is not committed as a contribution.

Inspection, correction, withdrawal, and deletion

Your receipt supports private inspection, a confirmed correction, withdrawal from further processing, and deletion—even when new intake is paused. Withdrawal stops active processing while the exact text remains under the accepted retention rule. Deletion erases the active exact text and source context and invalidates participant-level derivatives; a minimized nonidentifying audit commitment and restore tombstone remain to prove and reapply the governed action. Encrypted recovery snapshots are pruned on the next 15-minute enforcement cycle after reaching 30 days. A restored service must reapply the newest valid cumulative tombstone catalog before it starts. Expiry applies the same active content-erasure treatment after 30 days unless a precise legal hold requires deletion to pause.

Uses you do not grant

Confirmation does not grant public attribution, publication, contact, cross-session memory, advertising, model training, organization transfer, endorsement, vote meaning, or candidate adoption. A later request for any optional use requires a separate purpose and affirmative choice.

Separate services and accounts

KYN uses a separate pseudonymous browser key and independent operator/evidence boundary. Accountable campaign-role login uses self-hosted Keycloak and Campaign Core. Legacy Clerk, Google, Convex, score, and follower records are not imported into Campaign Core or KYN by default. Each surface provides its own notice before data collection.

Legacy Party Favors records and controls

The archived Party Favors experiment previously used account profile and email information supplied through Google or Clerk, limited security metadata such as IP address, browser, and timestamps, and—when a participant connected a platform or authorized an activity check—social engagement signals used to award and display favor balances. We did not receive Google passwords, sell Google user data, use it for credit or lending decisions, or use it to train AI models.

Restricted preservation copies may still contain legacy account, score, follower, and ledger records for continuity, security, dispute handling, and archival obligations. They remain outside Campaign Core and KYN and are not used as identity assurance, ballot eligibility, or vote weight. Service providers may process them only to host, secure, recover, or support that archive, or when disclosure is required by law.

You can revoke any remaining Google authorization from Google third-party access. To request a copy, correction, or deletion of legacy Party Favors data, email kc@uspartyparty.com. We will delete or irreversibly de-identify data within a reasonable period, typically within 30 days, unless a documented legal, security, or archival obligation requires limited retention; linked provider copies and caches follow their applicable deletion cycle.

Security, processors, and incidents

External traffic uses HTTPS. Authoritative campaign data is stored in private PostgreSQL on the campaign state host with narrow service identities, default-deny gateways, append-only events, frequent encrypted off-device backups, and tested recovery procedures. We may use infrastructure providers such as Vercel, Discord, Tailscale, and model providers only within the disclosed purpose and data-class boundary. We will investigate security incidents and provide legally required notice.

Age boundary

The current public Discord participation channel is limited to people who affirm they are 18 or older. We do not knowingly use the contribution workflow to collect personal information from children.