Privacy

Who runs Fama

Fama is run by [the operator's legal name], [its address]. We decide what is collected and why. Write to [a contact email] about anything on this page, including a request to see, correct or delete what we hold.

What we hold, and why

Your account

Your email address and name, to sign you in. Your password is never stored, only a scrypt hash of it.

Your session

One cookie, ap_session, holding a random token for 30 days. We keep only a SHA-256 hash of the token. Fama sets no analytics, advertising or third-party cookies.

Ad accounts you connect

The Meta ad account ID, its name, currency and time zone, the name of the Meta user who connected it, and the access token, encrypted with AES-256-GCM. The token carries ads_read to read performance and delivery, ads_management to make the changes you, your AI tools or your autopilot rules ask for, and business_management to list your ad accounts. For a Facebook sign-in we also keep the permissions Meta granted and Meta’s app-scoped ID for you, so that removing the app in Facebook deletes the connection.

Conversations

Your questions, the agent’s answers, and the account data its tools read to answer them (ad names, budgets, spend and results), so you can come back to them.

Changes and the activity log

Every change made or asked for in the account: who asked (you, the chat, an AI tool or an autopilot rule), the exact change, the limits it was checked against, whether it was made, waited for you or was refused, and what Meta reported afterwards.

Autopilot rules

The rules you or your AI tools save, and a record of each check: what each rule matched, the figures that matched, and what it did. Checks are kept 90 days.

Keys for AI tools

For each key: its name, the ad account it reaches, what it may do, its first ten characters, when it was made and last used. The key itself is never stored, only a SHA-256 hash of it.

Usage

For each agent run: the model, the effort level, token counts, the number of tool calls and any error, to enforce plan limits and keep costs visible.

The waitlist

Your email address and the plan you chose, to tell you when it opens.

Abuse limits

Your IP address, and the email you sign in with, in counters that stop repeated sign-in, sign-up and waitlist attempts.

Who else sees it

Anthropic. When you ask the agent something, your question, the conversation so far and the ad account data the agent reads are sent to Anthropic’s API, which runs Claude, the model that writes the answer. Your email address and name are not sent. Anthropic’s commercial terms say it does not train its models on API inputs and outputs; see Anthropic’s privacy policy.

Meta. Reads go to Meta’s Marketing API with your token. A change goes to Meta when you, your AI tool or a rule you switched to live asks for it, and only inside the limits you set; a change over a limit goes only once you confirm it. Copies of ad sets are always created paused. Meta handles your ad data under its own terms.

AI tools you connect. If you make a key under Settings, AI tools, the tool you connect it to (for example Claude Code, Cursor or claude.ai) receives what its questions read from that ad account, under that tool’s own terms. A key that may act can make changes inside your limits; no key can confirm a change that is over one. Revoke the key to stop it at once.

Hosting. The service and its database run with [the hosting providers].

Nobody else. We do not sell what we hold, share it for advertising or use it to train any model.

How long we keep it

• Your account, connections, conversations, changes, autopilot rules and keys: until you delete them, or your account. Disconnecting an ad account deletes its keys, rules and their history.
• Usage records: until you delete your account. They stay when you delete a conversation, without its content, because plan limits count runs per month.
• The audit log: 30 days on Free, 180 on Pro and 365 on Agency. Older events are deleted automatically.
• A session: 30 days, or until you sign out.
• Abuse counters: deleted within a day of their window ending. No window is longer than an hour.
• A waitlist entry: until the plan opens and we have told you, until you ask us to remove it, or until you delete your account.

Your choices

• Disconnect an ad account in Settings and its stored token is deleted. You can also remove Fama under Business Integrations in your Meta settings: Meta tells us, and every connection you made by signing in with Facebook is deleted at once. A data deletion request made through Meta works the same way and gives you a code to check on the data deletion page.
• Delete any conversation, whenever you like: open it and press Delete. Its questions, answers and the data read for them go with it; changes it made stay in your activity log.
• Delete your account in Settings. It removes your account, workspace, connections and tokens, conversations, changes, autopilot rules, activity log, waitlist entry and sign-in counter, at once.
• Ask [a contact email] for a copy of what we hold about you, or to correct it.
• You can also complain to the data protection authority where you live, or where we are based.

How it is protected

Access tokens are encrypted at rest with AES-256-GCM. Passwords are stored as scrypt hashes and session tokens as SHA-256 hashes, so a copy of the database cannot be used to sign in. Keys for AI tools are stored the same way, as SHA-256 hashes. Sign-in, sign-up, the waitlist and AI tool requests are rate limited. Every change, whoever asks for it, is checked in the code that talks to Meta against the limits you set: over a limit it waits for you, past your daily cap it is refused.

Children

Fama is a tool for running advertising and is not meant for anyone under 18.

Changes to this page

The date at the top shows when this page last changed.