UPDATED 29 SEPTEMBER 2026

Privacy notice

What we collect

For early access, we record your email, request source, consent choices and delivery status. For accounts, we use your email, authentication records, profile fields, optional avatar, preferences, terms acceptance and access permissions. If you have private-app access, your goals, check-ins, life events and connection records belong to your private workspace. Community records include topics, replies, reports, previous edit text, moderation actions and optional in-app reply alerts.

Why we use it

We use these records to operate accounts, send requested confirmations and security emails, display your chosen profile, enforce access permissions and handle support. Optional waitlist updates use the consent given on the early-access form and offer an unsubscribe link. Essential account confirmation and password recovery emails are separate.

Who can see it

Other eligible members can receive your display name, handle, bio and avatar when your community profile is visible. They cannot receive your email, preferences or private-app records from that profile. Owners can manage account email, status, staff roles and app grants. Owner status does not grant access to another member’s private app records through the application. Authorized infrastructure administrators can access stored data to operate the service.

Mobile Today and private story drafts

When enabled, the mobile app saves your chosen daily priorities, completion choices and one private recipient-name and story-question draft. These records are available to your account, including when you use another device. Other members and application owners cannot read them through the application. Saving a question does not contact its recipient or send an invitation. Your device stores its sign-in session using operating-system protection; unsaved text stays in memory and can be lost when the app closes.

You can export or erase these mobile records in the app. Erasure removes their saved content and earlier request fingerprints; a revision and limited request metadata remain to prevent an old save from restoring erased content. This does not close your account, erase other HUMANOS records or remove copies from existing backups. Normal provider backup retention still applies. If you choose to save or share an export, that copy is outside HUMANOS's controls. Authorized infrastructure administrators can access stored records to operate the service.

Community visibility and alerts

Active verified members can read visible discussions. A hidden profile is shown as “Member” without its name, handle or avatar, but posts retain an account identifier for ownership and moderation. This is not anonymous posting. Reports, earlier edit text and hidden content are available to moderators and owners, not ordinary members.

If you enable reply notifications in My account, HUMANOS creates in-app alerts for replies to topics you start and replies addressed to you. Turning the preference off stops new alerts. Existing alerts remain in your inbox. This feature sends no community emails and does not subscribe you to marketing.

Publications and ballots · single-choice-v1

Published announcements and proposals are visible to active verified members; drafts are owner-only. We store your current choice, account identifier, vote revision, timestamps and voting-rules acceptance. The application shows you your own ballot and shows aggregate results only after closing, including to owners. It does not expose a list of individual ballots to members or app owners. Authorized infrastructure administrators can access stored records to operate the service.

A vote cast while eligible stays counted after suspension. Account deletion removes that account’s ballot and can change historical totals. Owner drafts, publication changes and audit evidence are retained for operational review. Archiving does not erase them. This release has no automatic publication or ballot deletion schedule. Contact the operator about removal requests. The voting form asks you to accept these rules and this data handling before submitting a ballot.

Contributions · support-v1

We store your account reference, verified email at checkout, accepted recipient and refund policy, USD amount, provider references, payment/refund/dispute status and timestamps. Your payment history and receipt links are available to you and authorized owners. Other members cannot view them. Owners can request refunds, with an internal reason and audit record. Stripe receives the payment information needed to process contributions and receipts.

Financial records, including the checkout email, policy snapshots and audit history, can remain after account deletion for reconciliation and operational review. This release has no automatic financial-record deletion schedule. Contact the operator with a retention or removal request.

Referrals and rewards · rewards-v1

If you choose to save a referral link, a browser cookie retains a random referral token for up to 30 days. You can instead choose registration without a referral. A short-lived signup ticket binds the chosen referral to your signup email; confirmation on another device does not change a referral already saved at account creation. Existing accounts cannot be re-attributed through profile edits or a referral URL.

We record program acceptance, attribution, verified referral counts, award evidence, policy versions, amounts, hold and review dates, funding references and ledger changes. Your inviter sees aggregate verified referral counts and their own reward history, not your email, identity or payment details through Rewards. Authorized owners can inspect recipient account IDs, award evidence, linked payment records and funding history. Creator evidence and review reasons are visible to the award recipient, so owners should not include unrelated private information.

Expired capture and signup-ticket records are removed when owners run the reward candidate check. Durable attribution remains while the referred account exists. Financial award, funding and audit records may remain after account deletion for reconciliation; they have no automatic deletion schedule in this release. Contact the operator about retention or removal. Program participation does not subscribe you to marketing.

Payout accounts and verification · payouts-v1

Stripe collects identity documents, bank details and verification information within its secure components. HUMANOS stores your account reference, signup email used for account setup, country, provider account ID, eligibility and requirement status, payout terms acceptance, policy snapshot, award reservation, transfer and payout identifiers, verified statuses, recovery amounts and audit history. It does not store full bank account numbers or identity documents.

Your payout records are available to you and authorized owners. Secure provider account-management sessions are issued only for the signed-in account holder. Owners review eligibility, funding, provider operations and recovery; ordinary members cannot access another person's payout history. Operational payout records can remain after account deletion and have no automatic deletion schedule in this release. Contact the operator about retention or removal requests.

Service providers

Supabase provides authentication, database and private image storage. Vercel hosts the application. Resend delivers application messages and, when configured as the Supabase mail provider, account emails. These providers process relevant information to deliver those services. Stripe processes enabled support contributions and payment receipts. Card details are entered in Stripe’s embedded payment component; HUMANOS does not store full card numbers.

Cookies, logs and security

Essential cookies maintain your sign-in session. The application uses short-lived, keyed request identifiers for rate limiting; infrastructure providers may process IP addresses and technical logs. Access and staff changes are recorded in an administrative audit log. Confirmation and invitation tokens are not intended to be shared publicly.

Retention and choices

Account and app records are retained while needed to provide the service. Delivery, suppression and audit records may remain for security and operational purposes. Community posts, edit history, reports and moderation evidence remain until an authorized operator reviews a removal request; this release has no automatic retention cleanup. There is no automated account-deletion workflow in this release. Contact the operator to request access to, correction of or deletion of your information; the operator will explain the handling and any records that must be retained. You can edit your profile, hide its community visibility and change saved notification preferences in your account.

Contact

Operator: HumanOS. support@tryhumanos.com