Effective November 6, 2026

Privacy at DraftPeople.

DraftPeople, operated by DraftPeople, LLC, needs enough information to match voters with their districts and let communities invite people to serve. Private account, location, and on-device review information are separated from public profiles.

Information DraftPeople collects

Account information may include your email address, sign-in provider, and provider account identifier. A private district lookup collects your street address, city, state, and postal code. Activity information includes drafts you start, people you support, accounts you block, notification choices, identity claims, office-area concerns and responses, campaign-finance notice acknowledgements, and reports you submit.

If you create or claim a public person card, public information may include a name, general location, photo you choose to publish, biography, personal or professional website, contact-page link, a social-profile link you explicitly choose to publish, office status, affiliation, office-specific campaign website, aggregate supporter count, whether that count includes the person shown, and a public-safe office-area review status. Other supporter identities, blocked-account choices, office-area reporter identities, and office-area concern counts are not displayed.

Information submitted about another person

A user may submit a person’s name and suggest one or more public offices. The submitting user must reasonably believe the information is accurate, must not knowingly draft a person under 18, and must not submit private or sensitive information.

Before an unclaimed community draft is saved, DraftPeople converts the submitted name to a first name and last initial for the public server record. Public matches may also show the suggested office or voting area and an aggregate supporter count. DraftPeople does not store a Facebook URL, Facebook identifier, Facebook photo, or shared Facebook text in the public or private server record for that unclaimed draft.

How information is used

DraftPeople uses information to authenticate accounts, identify districts and relevant offices, display and rank matches, honor private account blocks, prevent duplicate identities, let people control claimed profiles, request one-time identity confirmation from an original drafter, ask drafters or claimed people to review possible office-area mismatches, answer support requests, investigate safety reports, and protect the service from misuse.

Stepping forward as considering or accepting records one expression of support on the person’s own profile when the office pairing is not unresolved or hidden as a mismatch. Declining removes that self-support, and a person may also withdraw it. An unconfirmed identity request does not move another user’s draft or support. Blocking an account withdraws your support from profiles connected to that account. A DraftPeople expression of support or office-area concern is not a petition signature, vote commitment, campaign contribution, ballot-access determination, or legal-eligibility ruling.

Location privacy

Your full voting address is never displayed on a public profile. It is used for district lookup and retained privately so you can review or update your districts. A claimed person may choose to display a district-derived city and state, state only, or no location. Editing a public profile or connecting Facebook does not change district information.

Information saved on your device

DraftPeople may temporarily save one unfinished draft in website storage on your device, including the proposed person’s name and selected offices. It expires after 30 days and is cleared when you submit it, discard it, or sign out. A draft begun while signed in is associated locally with that account so it is not restored for a different or signed-out session.

The iPhone share extension may receive a Facebook address and readable text that you deliberately share with DraftPeople. The app uses that information only on your device to help you confirm the intended person. DraftPeople does not automatically retrieve a Facebook name, photo, posts, friends, or other profile information. Continuing sends only the confirmed name, a random local review identifier, and office choices to DraftPeople’s website; it does not transmit the Facebook address or shared Facebook text. The server keeps only the abbreviated public name and office choices for an unclaimed draft.

After a successful draft that began in the iPhone app, the app may keep the shared Facebook address and the name the drafter confirmed in its encrypted on-device account vault for up to 30 days after submission. They are associated locally with the resulting DraftPeople person profile so the drafter can recognize the private shortcut, open the original profile, and deliberately share a draft announcement. The full confirmed name and Facebook address are not added to the unclaimed DraftPeople server record or supplied to another DraftPeople user. The user must write their own message and choose a destination in the iOS share sheet. Only after that explicit choice does the device give the message, Facebook address, and public DraftPeople link to the selected outside service, whose terms and privacy practices apply.

Each DraftPeople account uses a separate encrypted vault on the device. It may contain unfinished app reviews, private Facebook references, the account identifier, supported- and recent-draft shortcuts, public person and office details, DraftPeople profile paths, public website and owner-published social links, office-area review status, and synchronization times. The vault encryption key is kept in the Apple Keychain for this device and requires Face ID, Touch ID, or the device passcode when the vault is reopened. DraftPeople does not receive or store biometric information. Device authentication establishes access to the vault on that device; the separately authenticated DraftPeople account determines which account vault may be opened.

An owner-published social link is public server data rather than a private share-extension reference. A user can remove a private Facebook reference and its locally retained name without withdrawing support or deleting the public DraftPeople card. Private Facebook references expire after 30 days. When signing out, the user may keep that account’s vault encrypted and locked for later restoration by the same DraftPeople account, or permanently erase it from the device. Signing out from the website inside the app keeps the vault locked by default. A signed-out session or a different DraftPeople account cannot display the locked vault. Account deletion erases that account’s vault and key; uninstalling the app removes app data.

The mobile app’s dedicated DraftPeople browser may retain authentication cookies and ordinary website data on the device so a signed-in session can continue between visits. Signing out ends the DraftPeople account session and removes retained website data from the app.

The installable web app may cache public interface files, brand images, and an offline explanation so DraftPeople can open reliably. It does not intentionally cache authenticated account pages, your full voting address, or private database responses for offline use.

Identity and service providers

A verified DraftPeople email proves control of an account, not legal identity. If someone responds to an unclaimed community draft, they choose Decline, Consider, or Accept for a specific office. Consider and Accept create or update that person’s separate Step Forward profile immediately. The original community card and its supporters remain unchanged until the original drafter confirms that the responding account is the person intended. If the drafter does not confirm, the independent profile and the original community draft remain separate. A Decline request likewise does not hide or change the original card until the identity match is confirmed.

A person may optionally connect a Facebook account in their own name to strengthen the identity label on a DraftPeople profile they already control. A matching Facebook name alone does not transfer an unclaimed community card or let one account remove another user’s draft. After connecting Facebook, a profile owner may separately enter a Facebook profile address and explicitly choose to publish it. That owner-supplied address then appears on the public DraftPeople profile and may synchronize to app cards for people who support the profile. The owner can remove it later. If that profile was already linked to unclaimed cards as a possible duplicate, publishing the link may ask each original drafter to review both profiles and confirm or reject the match. No support moves unless the drafter confirms. DraftPeople does not treat the supplied address itself as proof that Meta verified the URL.

DraftPeople uses Supabase for authentication and database services, Cloudflare for hosting and security, and Geocodio for address geocoding and district lookup. Meta and Supabase process an optional Facebook connection; DraftPeople may privately retain the provider account identifier and may publish the verified account name on the person’s controlled DraftPeople profile. Provider identifiers are not displayed publicly and are not used to retrieve an unclaimed person’s Facebook profile. DraftPeople’s servers do not store a Facebook profile address received through the iPhone share extension. DraftPeople does not receive your Facebook password, post automatically or without your approval, or request your friends list.

Who can see information

Public profile information, including a social-profile link the profile owner explicitly publishes, and aggregate community activity can be seen by DraftPeople users. The drafted person may hide a claimed card. A private account block is visible only to the person who created it and authorized DraftPeople systems; the blocked account is not notified. Automated safeguards screen public submissions for clear threats, unsafe markup, and automated spam. Authorized support, moderation, and owner administrators can review private reports, hide content, and suspend or restore account activity through logged moderation actions. They do not need routine access to full voter addresses.

DraftPeople does not sell personal information. Information may be disclosed when required by law or when reasonably necessary to protect people, DraftPeople, or the integrity of the service.

Retention and choices

DraftPeople retains information while it is needed to operate the service, preserve legitimate moderation and draft history, resolve disputes, or meet legal obligations. Hiding a card removes it from ordinary public match results without necessarily deleting its history. You can update your district address, publish or remove an optional social-profile link, withdraw support, change notification choices, block or unblock an account, hide a claimed profile, or permanently delete your signed-in account. Direct deletion removes private account records, including block choices, and self-started public content; independently submitted community draft history may be retained only in a hidden, de-identified form.

Security and age

DraftPeople uses access controls and separates private information from public profile data, but no Internet service can promise absolute security. Do not submit passwords, government identification numbers, or sensitive private information in public fields. DraftPeople is intended for adults. Do not create an account if you are under 18, and do not knowingly draft a person under 18.

Questions or requests

Use the private support form for privacy questions, access problems, or corrections. A dedicated data-deletion page explains how to request deletion, including after using Facebook Login. This policy may change as the pilot develops; a new effective date will appear here when it does.