Privacy Policy

1.Who we are

[COMPANY] operates sentryq Cloud. For the account data described in this policy we are the controller. For everything inside your workspace — your fans, your chatters, your conversations — you are the controller and we are your processor, under the Data Processing Agreement.

Questions about this policy, or any request under it, go to the address published on our site.

2.What we collect about your agency

When you create a workspace we collect: the agency name, the subdomain you chose, the email address and password of the account owner (stored only as an argon2id hash, never in readable form), the timezone you selected, and how many models you expect to run.

When you connect Fanvue we store the identifier of the Fanvue account that granted access, the access and refresh tokens for it (encrypted with AES-256-GCM before they touch a disk), and the list of creators that account manages with whether each holds a licence.

As you use the hub we record operational events: sign-ins, provisioning steps, settings changes, administrative actions and errors. Where an action is worth evidencing we also store a salted hash of the IP address it came from. We do not store the address itself.

3.What we do not collect

We do not collect payment card details. Billing happens inside Fanvue, and no card number, bank detail or billing address reaches us.

We do not read the contents of your workspace for our own purposes. We do not use your conversations, fans or media to train models, to build a profile of your business, or to inform anything we sell to anyone else.

This website carries no advertising pixels and no cross-site trackers. If page analytics are enabled, they are self-hosted, cookieless, and record a page path and a referrer — never an identity.

4.Why we are allowed to hold it

Account data is processed to perform our contract with you: we cannot provide a workspace without knowing who owns it and where it lives.

Operational and security logs are processed under our legitimate interest in keeping the service secure, available and auditable, balanced against the fact that they contain an identifier and an action, not the content of anybody's work.

Where we email you about the service — a provisioning result, a security notice, a change to these documents — that is contractual, not marketing. We do not send marketing email to your account address without asking first.

5.Cookies

The hub sets one cookie: a signed, httpOnly session cookie that keeps you logged in for twelve hours. It carries your user identifier, your role and your agency, and it is signed so it cannot be edited.

During the Fanvue connection flow a second, short-lived cookie holds the OAuth state and verifier. It is deleted as soon as the connection completes.

Neither is used for tracking, and neither is shared with anyone.

6.Who else sees it

We use a small number of service providers, each listed on our subprocessors page with what it does and where it runs. That page is the authoritative list; it changes when the list changes.

We disclose data outside that list only where the law requires it. Where we are legally able to tell you about such a request, we will.

We do not sell personal data and we have never done so.

7.Where it is held

Your workspace, its database and its media are hosted in Germany. The hub is hosted in Germany.

Two providers on our subprocessors page operate outside the EU. They receive only what is described there — an email address for transactional mail, DNS queries for your subdomain — and never the contents of your workspace.

8.How long we keep it

Account records are kept while your workspace exists, and for 30 days after it is closed so that an accidental cancellation can be undone.

Webhook delivery records are kept for 7 days. Subscription events are kept for 30 days. Audit records of administrative actions are kept for two years, because they are the evidence of who did what to an account.

Backups are retained for 30 days and rotate out after that.

9.Your rights

You can ask us for a copy of the account data we hold about you, ask us to correct it, ask us to delete it, ask us to restrict how we use it, or object to processing we do under legitimate interest. You can also ask for it in a portable form.

Write to the address on our site. We will answer within 30 days. We will ask you to confirm you control the account before we act, because a deletion request that turns out to be somebody else's is not recoverable.

If you are unhappy with how we have handled a request you can complain to a data protection authority in your country.

10.Requests about someone in your workspace

If a fan or a chatter asks about data held inside your workspace, that request is yours to answer: you are the controller for it. We will help you find, export or delete what you need, and we will not act on such a request without your instruction.

The Data Processing Agreement sets out how we assist and how quickly.

11.Security

Every workspace has its own database, its own storage and its own credentials. Secrets we hold on your behalf — Fanvue tokens, database URLs, storage keys — are encrypted at rest with AES-256-GCM and decrypted only in the process that needs them.

Passwords are hashed with argon2id and are never recoverable, by us or by anyone. Access to production infrastructure is limited to named operators.

If a breach affects your data we will tell you without undue delay, and in any case within 72 hours of becoming aware, with what we know and what we are doing.

12.Changes

We will update this policy when what we do changes. The version is stamped at the top, and a material change is notified by email to your account address at least 30 days in advance.