Account Safety and Compliance

Your creator accounts are your business. This page explains how to use Sufflera so that it protects them, keeps your data safe and keeps your agency within the rules of the platforms you work on.

Platform rules

Sufflera works next to OnlyFans, Fansly and Fanvue. It is not connected to, approved by or run together with any of them.

Each platform has its own rules about automation and account access, and they apply to you. They change over time and differ between platforms. Some forbid automated messages completely; others forbid only some kinds.

Before you turn on automatic sending for a creator account, check what that platform’s current rules allow. This is your decision as the account’s operator, and the responsibility is yours, not ours. Our Terms of Service §6 explains this in full.

In practice:

Work by hand (Manual) or with drafts only (Draft only) unless you have confirmed that automatic sending is fine for that platform and that account.
Keep the automation pace as it is. The default pace exists for a reason; do not treat it as an obstacle.
Have a person read the autopilot log every day.
Follow each platform’s rules on sharing accounts and team access.

Working responsibly

Sufflera gives you powerful tools. A few principles keep agencies out of trouble:

People, not volume. Every message goes to a real person who believes they are talking to your creator. Everything here is meant to make that conversation better, not fake.

Never automate distress. The stop on a possible crisis is on by default for every creator. Leave it on. A person in crisis needs a human, and no money matters more.

Never automate complaints or disputes. Automated answers make them worse. Sufflera holds them for a person; keep it that way.

Do not misrepresent what you sell. The draft check already stops promising content that is not attached or inventing a purchase, but your prices, delivery times and content descriptions are yours to keep honest.

Respect a “no”. If a fan says no to something, the chat history keeps it. Do not override it.

You are responsible for what goes out from your accounts. Every draft is checked before it reaches you, and every automatic send passes the safety checks in Reply Modes and Autonomy. The final responsibility for what is sent from your creator accounts is still yours as the operator. That is why the check, the reply modes and the autopilot log exist.

You are responsible for the content you upload, the accounts you run and the chats you hold. In particular:

everyone in content you upload must have agreed to it and be of legal age, and you must be able to prove it;
you must be allowed to run every creator account you connect;
your team must follow the law wherever they work.

Our Acceptable Use Policy (§9) lists what is forbidden. Breaking it can lead to suspension.

Protecting your account

Access

Give each team member their own login. Shared logins make it impossible to know who did what, and they are the most common cause of incidents nobody can explain later.
Keep chatters on assigned creators only, so a new creator is never shown to everyone.
Deactivate people who leave, on their last day. It works at once, everywhere, including the extension, and keeps the record of their work.
Give billing permissions only to people who really need them.

Passwords

Use a unique password for each account, ideally from a password manager.
Confirm the email on every account so password recovery works.

Checking activity

Read the activity log once a month: deletions, billing and subscription changes, automation stops.
Read the autopilot log every day while automation is running.

Your data

Separation. Your account’s data belongs to your account. Creators, fans, chats and content are never visible to another customer, and inside your account access is limited by role and assigned creators.

We never train on your data. Your chats, CRM records and personas are not used to train, fine-tune or test any AI model of ours. Our contract with our AI provider excludes using your content to train models. Our own quality tests run on a separate database of made-up test data, never on customer data.

How long data is kept. Chat history does not expire: it is kept until you delete it, because the assistant works from it.

Draft text is different: it is erased automatically after 180 days. The fan message that led to the draft, the draft and its translation are removed; the numbers stay, so quality statistics and ratings do not change. You do not need to do anything and it cannot be turned off. If you need the wording of an old draft for a dispute, export it before six months pass.

Export.

What	How
Your whole account, as JSON	Settings → Account → Export my data (Owner or Admin)
Your billing history	Settings → Billing
One fan’s record: messages, purchases, reminders, photos, drafts	Ask us

The account export is a full machine-readable copy of everything in your account. Use it to move elsewhere or for your own records.

Ask us for one fan’s record when a person asks you to hand over what you hold about them. It covers only that person, so you can answer without revealing anything about anyone else.

Deleting. Deleting a fan removes his messages, purchases, reminders, photos and drafts.

Deleting your account permanently removes your working data: CRM records, fan data, personas and drafts.

Two things are kept, only for legal reasons:

financial records (invoices, payment receipts, billing history) for up to seven years, because tax and accounting law requires it;
proof of acceptance: which version of our terms was accepted and when. The IP address and browser details recorded then are discarded.

Backups are overwritten on their normal cycle, usually within fourteen days. Export anything you need to keep before deleting.

Your data rights. You can use several rights right in the product: access and portability through the exports above, correction by editing any field, erasure by deleting a record or the account, and limiting automation by setting the reply mode to Manual or leaving autopilot off. For anything else, write to privacy@sufflera.com; we answer within 30 days.

Security. Passwords are hashed with Argon2id and never stored as plain text; dashboard sessions use short-lived tokens, the extension stays signed in until you sign out, and the server can end any session; access is checked on the server, not by hiding buttons; data is encrypted in transit; and payments run with protections against double charges. If a data breach is likely to be a risk, we notify the supervisory authority within 72 hours and affected customers without undue delay.

The details are in our Privacy Policy.

Your role under data protection law

For the chats and fan records in your account, you are the data controller and we are your processor. In practice:

you decide what is collected and how long it is kept;
you are responsible for having a legal basis to keep it;
you are responsible for answering requests from the people concerned;
we process it on your instructions and tell you exactly what we do with it.

Our Privacy Policy §3 explains the split in detail, and §7 explains exactly what is sent to the AI and what is kept.

If something goes wrong

If something looks wrong (unexpected messages, a chat that went badly, an account you do not recognise):

Press the emergency stop. It stops automatic sending for the creator at once, from Creator Studio or with Pause on the side panel’s Draft tab.
Stop autopilot in every tab where it runs: Stop is in the top row of the Autopilot tab.
Read the autopilot log to see exactly what was sent, to whom and when.
Check the activity log for account changes you did not expect.
Deactivate any user you are not sure about.
Contact support with the times.

Stopping costs nothing and can be undone at once. Use it early.