Privacy Policy

AI4Everyone · Last updated 4 September 2026

Draft. This describes what the software currently does, written against the code rather than from a template. It has not been reviewed by a lawyer. Read it before relying on it, and have it reviewed before accepting real users' data.

This policy covers the AI4Everyone platform and the products built on it: Video, Social, and Product Reviewer. Each product also has its own policy covering the third-party services it connects to; where they differ, the product's own policy governs that product.

Who we are

AI4Everyone operates this platform. Contact us at support@ai4everyone.dev for any question about this policy, or to exercise any right described below.

What we collect, and why

Data	Why	Source
Your Google account identifier, email address, and name	To identify you when you sign in and to associate your work with your account	Google, when you choose to sign in
A session record: a hashed session token, expiry, and the browser and IP address that created it	To keep you signed in and to let you see and revoke active sessions	Created by us when you sign in
Workspace and membership records	To separate your data from every other customer's	Created by us
Content you create or upload within a product	To provide that product's function	You
Credentials for third-party accounts you connect	To act on your behalf on those services, only as you direct	That service, after you grant access

Signing in does not grant access to anything else

Signing in with Google requests only your identity — your name, email address, and a stable account identifier. It requests no access to YouTube, Gmail, Drive, or any other Google service. Connecting a service such as YouTube or Instagram is a separate, explicit step, asked for at the moment you need it, and you can decline it and still use the rest of the product.

How it is protected

• Third-party credentials are encrypted before storage. They are never written in plain text, and are decrypted only to perform an action you asked for.
• Session tokens are stored only as a hash. The value in your browser cannot be recovered from our database, so a copy of the database does not let anyone sign in as you.
• Isolation is enforced by the database, not only by application code. Every record carries the workspace that owns it, and the database refuses to return rows belonging to another workspace even if the application asks for them.
• Each product's data is held separately. Products do not share workspaces or records with each other.

No system is perfectly secure, and we do not claim otherwise. If you believe you have found a vulnerability, please write to support@ai4everyone.dev.

Who else sees it

We do not sell your data, and we do not use it to train models. We share it only with the infrastructure and service providers needed to run the platform — hosting, database, object storage, and the third-party services you explicitly connect — and only to the extent needed to provide the function you asked for. We disclose data to authorities only where the law requires it.

Where a product sends content to an AI model provider to do its work, it does so to produce the output you requested. The relevant product's own documentation names the providers it uses.

Where it is held

Data is processed and stored on infrastructure in the United States. If you are outside the United States, using the platform involves transferring your data there.

How long we keep it

• Account and workspace records: until you delete your account.
• Sessions: until they expire or you sign out.
• Connected-service credentials: until you disconnect that service, or you delete your account.
• Content you create: until you delete it, or you delete your account.

Deleting a connected service removes its stored credentials. Backups are retained for a limited period and are overwritten in the ordinary course.

Your choices

• See what we hold. Ask us and we will tell you.
• Correct it. Most of it you can edit directly; ask us for the rest.
• Delete it. Ask us to delete your account and we will remove your data.
• Disconnect a service at any time, from within the product.
• Revoke our access from the provider's side. For Google, use Google account permissions. Revoking there stops our access immediately, whatever we hold.

Children

The platform is not intended for anyone under 16, and we do not knowingly collect their data.

Changes

If this policy changes materially, we will say so here and update the date above before the change takes effect.