CAMPAIGN PREVIEW
Support should remain your choice.
How the proposed support campaign would record consent, confirm email, report support and handle withdrawal.
A proposal by AlphaBravo · Authority, funding and deployment remain open.
Start a conversation
Collection has not opened
This campaign is being reviewed inside the private website preview. It is not accepting real signatures, organizational endorsements or offers of expertise. The following describes the implemented workflow and proposed operating policy. Campaign owners, the monitored help contact, final retention periods and the initial government recipients must be named before activation.
Three separate purposes
A signature supports the exact statement version. An organizational endorsement is a separate request, reviewed for authority and exact public attribution. An expertise or pilot offer is an inquiry for staff follow-up. None grants private-resource access or is used as sales qualification. An optional organization on a personal signature is not an endorsement by that organization.
Information and consent
The signature flow requests a name, email, self-reported state or territory, and optional organization. The proposed first release is for adults aged 18 or older who live in a U.S. state, the District of Columbia or a U.S. territory. It records agreement to the displayed statement, eligibility acknowledgement and privacy version. No identity documents or full street addresses are requested.
Email confirmation establishes mailbox control; it does not establish citizenship, residency or one unique human. Email addresses are normalized to lowercase without removing plus tags or provider-specific dots.
Campaign updates are optional and unchecked by default. Update consent is activated only after email confirmation. Withdrawing support and unsubscribing from updates are independent choices. No updates are sent by this initial implementation.
What is shared
The proposed policy is aggregate support summaries and separately approved organizational endorsements only. Personal names and email addresses are not published, sent to government recipients, sold or reused for sales. Staff can export aggregates for recipient packets and a separate list of explicit campaign-update opt-ins for that purpose. New sharing terms cannot silently replace the policy people agreed to.
Counting and review
The count is calculated from current email-confirmed signatures for the displayed statement version. Pending, withdrawn and flagged records are excluded. Counts refresh on page load and show their retrieval time; unavailable counts are not displayed as zero. Test records must never be mixed with public counts.
One normalized email may have one active signature per version. Duplicate requests and repeated confirmation clicks cannot add another active signature. A material statement change requires fresh agreement to a new immutable version; repeated signers across versions are not represented as distinct people. A campaign count is not a representative poll.
Storage, email and abuse prevention
The implementation uses Cloudflare D1 for campaign records, Cloudflare Turnstile for abuse verification, and a configurable Resend integration for confirmation and management emails. Provider setup and the final notice are required before use. Cloudflare Access protects staff administration separately from resource collection grants.
Single-use links expire after one hour. The server stores token hashes. The link token stays in the URL fragment and is removed from browser history before review; it is then sent only to this site through a POST request. Review pages use no third-party analytics and suppress referrer information. Email scanners that merely open a link cannot confirm support.
Abuse counters use keyed hashes of the email and network address, scoped to an hour. Raw IP addresses are not stored in the campaign database. These short-lived counters expire after 24 hours and are removed by daily cleanup. They are not identities, duplicate-signature rules or reading-history profiles. Provider and hosting logs are separate; their retention and access must be reviewed before collection.
Provider acceptance is not proof of delivery to an inbox. Failed email jobs remain visible to staff and retry within the link’s lifetime, subject to limits. A request by itself never counts as a signature.
Withdrawal, unsubscribe and deletion
Request a private management link to withdraw, unsubscribe, or do both. A GET request makes no change; a deliberate submission consumes the link. Withdrawal removes support from the current count. Unsubscribe disables update consent independently.
The campaign data owner must approve and publish the retention periods for pending records, signatures, organization/expertise requests and operational events before launch. The implementation applies approved campaign retention through scheduled cleanup. Expired token jobs are deleted after a further day. A verified deletion request can remove a signature, its consent record and its associated email jobs through restricted staff administration.
The final notice must identify the responsible organization, a monitored privacy/help contact, provider handling details, retained audit information and how to make a deletion or correction request. Until then, collection remains disabled.