Privacy, in plain language

Browsing does not require an account

You can browse Home, Explore, Workflows, Learn, Useful reads, and public Community pages without creating an AI Human Community account. Ordinary browsing is designed not to create a Supabase Auth session.

The current invite build does not include an advertising network or a third-party behavioral analytics product. The services that host and operate the site may still produce ordinary infrastructure and security logs as part of running the product.

Save and “I tried this” create anonymous local identity

The first time you Save a Workflow or mark one as Tried, the site creates an anonymous Supabase Auth user so those choices belong to one browser identity instead of being public or shared between everyone.

For each Workflow interaction, the current product stores:

• the Workflow identifier;
• whether it is Saved;
• whether it is marked Tried;
• timestamps used to keep the state current.

An anonymous interaction does not create a public profile or public Community identity.

Old anonymous accounts are eligible for cleanup

The current cleanup job only removes an anonymous account when all of these conditions are true: the account is at least 90 days old, there has been no Auth session refresh in 30 days, and there has been no Workflow interaction update in 30 days. Permanent accounts are excluded from that stale-anonymous cleanup.

Email return is for an account that already exists

My Stuff can send a one-time email sign-in link to an existing permanent account. The current flow deliberately does not create a new account from an unknown email address, and the same neutral message is shown whether or not an account exists so the form does not reveal account membership.

If you started with anonymous Saved/Tried state on the same browser, the product can merge that state into your permanent account after you return through the email link.

Community participation is intentionally more identifiable

Reading Community does not require a public identity. Posting, replying, contributing a Workflow, or remixing one requires a claimed permanent account and public profile.

Depending on what you choose to do, the product may store your display name, discussions, replies, private contribution drafts, review status, and approved published Workflows. Public Community posts and approved published Workflows are visible to other people. Private draft/review records are not intended as public browsing data.

Share only what the job actually needs

Do not put passwords, authentication secrets, government identifiers, full financial credentials, or unrelated private data into Community posts, contributions, reports, or AI prompts just because a field will accept text.

Other people’s information deserves the same care. Remove unnecessary names, account numbers, addresses, children’s information, workplace data, or other identifying details when the task works without them.

Your choices and requests

• You can browse without creating an account.
• Turning both Saved and Tried off removes that Workflow interaction row for the current identity.
• Signing out uses local-device scope.
• You can ask for a privacy/data review, correction, or removal through the site’s concern-reporting path.