Privacy & Cookies
Effective: September 19, 2026. This notice describes how the Children of One People project handles personal information on this website. The project is designed to collect as little personal information as reasonably possible while still supporting secure participation, transparent deliberation, and contributor privacy choices.
What we do not do
We do not sell personal information. We do not use third-party advertising, behavioral advertising, cross-site advertising profiles, or commercial audience-building pixels. We do not use visitor information to decide political positions or to rank contributors by identity or viewpoint.
Information we may receive
Ordinary website use
Our hosting and security infrastructure may process ordinary technical information such as IP address, request time, requested page, browser or device information, and security signals. The application itself uses one-way hashes rather than plaintext IP addresses for several rate-limiting and verification records. Hosting providers may maintain ordinary server and security logs under their own operational retention practices.
Contributor accounts
If you request a contributor sign-in link, we process your email address, account timestamps, one-time authentication records, and security/rate-limit information. Sign-in is passwordless. Contributor browser sessions expire after four hours of inactivity and after twelve hours in all cases.
Feedback and consultation responses
If you submit feedback, we process the text you submit and the choices necessary to review it. Depending on what you choose to provide, that may also include an optional name, email address, self-described perspective or relevant experience, a suggested revision, an RFC target, and your publication and attribution choices.
Publication permission and attribution are separate choices. Choosing to keep a submission private means the submission itself and attribution to you will not be published, quoted, closely paraphrased, or used to identify you. A private submission may still influence independently authored project reasoning without identifying or reproducing your contribution.
Guest receipt codes
Guest submissions may receive a one-time receipt code. We store only a one-way hash of that code, not the original code. The code can be used to view the associated submission status and exercise the guest controls available for that submission.
Privacy requests
If you make a privacy request, we process the information needed to verify and handle that request, which can include a contact email, request type, request details, verification records, and an internal case history. Closed-account verification is designed so that a former plaintext account email does not remain in the closed contributor record.
Why we use this information
We use personal information only for purposes reasonably connected to operating and securing the site, authenticating contributors, receiving and reviewing consultation material, honoring publication and attribution choices, maintaining provenance and revision records, preventing abuse, communicating about a submission or privacy request when appropriate, and complying with applicable legal obligations.
Cookies and similar technologies
The site uses only functional and security-related browser state at present. This can include short-lived contributor, guest-receipt, and privacy-verification session cookies. Contributor sessions use secure cookie settings and expire as described above. Guest-receipt and closed-account privacy-verification sessions expire after twenty minutes.
Forms that need abuse protection use Cloudflare Turnstile. Turnstile is loaded only on pages that actually use the protected form. Cloudflare may process network, browser, device, and security signals and may use strictly necessary cookies or similar mechanisms to provide the service. See Cloudflare's privacy policy for its practices.
We currently do not use analytics or advertising cookies. Because we do not sell personal data or use it for targeted advertising, Global Privacy Control or another opt-out preference signal does not change current advertising or sale behavior: there is presently nothing of that kind to opt out of. If those practices ever change, the site must implement the legally required controls before beginning them.
Service providers and disclosures
We use service providers to operate the site, including website/database hosting, transactional email, and anti-abuse/security services. Current infrastructure includes DreamHost services and Cloudflare Turnstile. Providers receive only the information reasonably necessary to perform their service.
We may also disclose information when required by applicable law, valid legal process, or when reasonably necessary to protect the security and integrity of the site or the rights and safety of people. Public disclosure of contributor material is governed separately by the contributor's publication and attribution choices.
Retention
Different information has different retention needs. Used or expired magic-link and privacy-verification tokens are scheduled for deletion after 48 hours. Rate-limit and administrative login-attempt records are scheduled for deletion after 90 days. Short-lived browser sessions expire substantially sooner.
Submissions, privacy cases, provenance records, and privacy/audit events do not automatically expire solely because of age. They may be needed to preserve a reliable deliberative record, document privacy choices, or respond to later rights requests. That does not make them immune from correction, restriction, withdrawal, scrubbing, or erasure where appropriate.
Closing a contributor account removes the active account email and display name, revokes sign-in tokens, and leaves a pseudonymized recovery/provenance anchor so existing submissions and later verified privacy requests can still be handled safely. Closing an account is separate from withdrawing or erasing a submission.
Your choices and privacy requests
Depending on the information involved and applicable law, you may request access, correction, erasure, publication or attribution changes, withdrawal of a submission from future project use, or another privacy action. The project provides these controls even when a particular statutory threshold may not require every one of them.
Signed-in contributors can review account-linked submissions through the dashboard. A guest who retained a receipt code can use the submission lookup page. For broader privacy requests, including requests involving a closed account, use the privacy request process or email privacy@childrenofonepeople.org.
Children
This is a general-audience civic and constitutional project, not a service directed to children under 13. Account and contribution features are intended for people age 13 or older. If we learn that personal information from a child under 13 has been collected in circumstances requiring parental consent or deletion, we will restrict the information and take the steps required by applicable law.
Sensitive information
Please do not include unnecessary sensitive personal information in a submission. Optional perspective fields are self-described context, not identity verification or credentialing, and are not intended to infer protected characteristics that a contributor did not choose to provide.
Security
We use measures including secure session cookies, CSRF protection, single-use authentication tokens, hashed security identifiers, rate limiting, access controls, privacy review before publication, and restricted administrative tools. No security system can guarantee absolute protection, so data minimization remains part of the security model.
Changes to this notice
We will update this notice when our actual data practices materially change. New advertising, analytics, payment processing, sensitive-data processing, or materially different third-party data use must not begin without an appropriate privacy review and an updated notice.
Contact
Privacy questions and requests: privacy@childrenofonepeople.org.