Privacy Policy (draft) — CCPA/CPRA

This draft describes how Humans.Army (Santa Monica, California) intends to handle personal information. It is written for California residents under the CCPA/CPRA. It is not a finished notice and has not been reviewed by privacy counsel.

1. Categories we collect

• Identifiers: name, email, phone, city, account IDs.
• Commercial / campaign data: briefs, scripts, brand assets, deposits (via Stripe — we do not store full card numbers).
• Professional information (operators): bio, skills, languages, availability, mission history, ratings.
• Geolocation: a one-time GPS coordinate at mission check-in (not continuous tracking). Approximate accuracy may be stored.
• User content: proof photos, interaction logs, feedback notes, dispute text.
• Inferences / reports: AI-generated campaign summaries from field notes.

2. Purposes

Operate the marketplace (accounts, campaigns, assignments, training, check-in, proof review, payout tracking); FTC disclosure records; security and fraud; compliance with law; product improvement. We do not sell personal information and we do not share it for cross-context behavioral advertising in this product (no ad pixels ship in the app).

3. Location data limits

Check-in location is used only to confirm the operator is within the mission radius. It is shown to the assigned operator, the admin, and (in aggregate / live dashboard form) the buyer of that campaign. It is not used to track operators off-mission. Precise geolocation may be “sensitive personal information” under CPRA; we intend to limit use to the check-in purpose.

4. Operator PII vs buyer view

Buyers see first name + last initial + rating for assigned operators, not full identity, phone, or exact address. Campaign reports summarize field notes and may include paraphrased customer comments operators typed — operators should not log unrelated third-party personal data.

5. Processors

Depending on configuration: Neon (database), an S3-compatible object-storage provider (uploaded brand assets and mission proofs), Stripe (payments), Anthropic (script/quiz/report generation), Mapbox (maps), and email/OAuth providers if enabled. Each is used only when the corresponding key is set. Accounts and sessions are handled in-app rather than by a third-party identity provider, except where you sign in with Google or GitHub.

6. Retention

Account data for the life of the account; campaign, proof, location, and acknowledgement records for the campaign plus a period needed for disputes and legal holds (to be set with counsel — not automated in v1). You may request deletion subject to legal exceptions.

7. California privacy rights

You may request to know, access, correct, or delete personal information, and to opt out of sale/sharing (we do not sell/share today). We will not discriminate for exercising CPRA rights. Authorized-agent requests will follow CPRA rules once a production process exists. Contact the operator of humans.army in Santa Monica, CA. A “Do Not Sell or Share My Personal Information” link will be required if sale/share ever begins.

8. Children

The service is for adults. We do not knowingly collect information from anyone under 18.

9. Security

Access is role-gated with row-level security in Postgres. No security measure is perfect.

10. Early-access list and site measurement

Early-access (pre-signup) list. If you join the list we collect your email, whether you are a brand, a business with staff, or an individual, and anything optional you add (name, business name, city, a note). Individuals confirm they are 18 or older. We use it to contact you about early access and to decide where to launch. We send other product updates only if you tick that box, and you can unsubscribe at any time. We do not ask for date of birth, background or criminal history, work authorization, or tax information on the list. Only Humans.Army administrators can see it, and we will delete your entry on request. Each entry gets a random invite code; if someone joins through your invite link, we record that they came from your code so we can credit you. The code contains nothing about you, and nobody else can look up who owns it.

Homepage measurement. The homepage rotates between a few messages and counts, anonymously, how many visits saw each one and how many joined the list. A view record holds only the message shown and a timestamp — no IP address, device ID, or account. A first-party cookie (ha_hv, 30 days) remembers which message you saw so the page stays consistent. No third-party analytics or advertising pixels are used.