One People is designed around a privacy-first architecture: collect as little as possible, keep control close to the user, and avoid building systems that depend on surveillance to function.
This document is provided for informational purposes. Consult legal counsel before relying on it.
Last updated: March 2026
We aim to collect the minimum information needed to operate the public site and manage early access.
Today that primarily means waitlist information you choose to provide, such as your email address, and limited high-level site analytics if we enable them. We do not design our services around behavioral profiling.
We do not sell personal data. We do not run ad-tech style tracking across the web. We do not treat your activity as an asset to package and monetize.
Where local-first or no-trace modes are available, the goal is to keep your data on your own device or under your direct control.
Privacy-first architecture is a product differentiator for One People. We are not trying to collect everything first and add restrictions later.
We want the system itself to make restraint normal: minimal retention, minimal telemetry, open-source inspection, and infrastructure that can run locally when that is the right answer.
This page is written to be readable by normal people. It is meant to explain how we think about data and what commitments matter most.
It is not a substitute for legal review, and specific deployments or product features may require more detailed disclosures.
If you join the waitlist, we may store your email address and any limited signup details you submit so we can contact you about beta access, product updates, or onboarding.
If analytics are used, they should be basic, aggregate, and aimed at understanding site reliability and broad traffic patterns, not building personal dossiers.
We try to avoid non-essential cookies. If cookies are used, they should be minimal and tied to core functionality, security, or simple aggregate measurement rather than cross-site tracking.
We keep personal information only as long as needed for the purpose it was collected for, such as managing the waitlist, complying with legal obligations, or maintaining service security.
When the information is no longer needed, we aim to delete it or de-identify it.
If applicable under GDPR, CCPA, or similar laws, you can request a copy of the personal information we hold about you.
You can ask us to delete personal information we no longer need, subject to legal, security, or operational exceptions.
Where required, you can request that your data be provided in a portable format so you can move it elsewhere.
If you exercise privacy rights, we will not treat that as a reason to punish or degrade your access in ways prohibited by law.
The public website links to the One People Commons at commons.onepeople.cloud and to the public GitHub organization at github.com/OnePeople.
If you follow those links, your interaction with those services is governed by their own terms and privacy practices.
We do not currently embed third-party advertising trackers or social media surveillance pixels in this site.
If we use vendors for hosting, email delivery, analytics, or waitlist management, we expect them to process data only as needed to provide the service and not for unrelated profiling or resale.
As the platform evolves, this section should be updated to reflect any meaningful new processors, infrastructure providers, or user-facing integrations.
For access, deletion, or portability requests, publish and maintain a dedicated contact channel before relying on this page in production.
Placeholder contact: [[email protected]]
You can also direct community questions through the Commons at commons.onepeople.cloud.