Squeezly

Privacy policy

Last updated:

This policy explains what personal data Squeezly handles, why, and what rights people have over it. Squeezly is a business service for Fanvue agencies and creators. In this policy, "we", "us" and "our" mean Squeezly.

1. Who is responsible for which data

Three kinds of data pass through Squeezly, and our role is not the same for each.

  • Workspace data. The business that holds a workspace (an agency, or a creator working alone; the "agency" in this policy) uses it to chat with fans and decides why and how the fan and creator data in it is used. For that data the agency is the controller and we act as its processor: we handle the data on the agency's instructions and under our terms of service.
  • Account data. For the account details of the agency's own team members who sign in to Squeezly, and for our own records of how the service is used, we are the controller.
  • Waitlist requests. For what a person tells us when they ask to join the waitlist on our website, we are the controller.

If you are a fan or a creator, the agency that runs the creator account is your first point of contact for anything in this policy.

2. What data we process

  • Account details of team members: name, email address, role in the workspace and sign-in credentials. A team member who signs in with Fanvue is identified by their Fanvue account.
  • Fanvue connection data: the OAuth tokens that Fanvue issues when an agency or creator authorises the connection, and the identifiers of the connected accounts. We never receive a Fanvue password.
  • Creator profile information: the profile and voice the AI should use, scripts, prices, and references to media in the creator's vault, as entered by the agency or by the creator through a set-up link.
  • Fan data read through Fanvue's API: fan identifiers such as the Fanvue user ID, handle and display name; the chat messages in the creator's conversations, including pictures a fan sends, which the service reads in order to write replies; and events such as a new follow, a new subscription, a purchase or a like on a post.
  • Usage and audit logs: what team members and the AI did in a workspace (for example switching the AI on or off, sending a message or freezing a chat), together with technical records such as times and errors.
  • Sign-up protection: when a workspace is created we keep a one-way digest of the network address the request came from, to limit how many workspaces can be created from one place. We do not keep the address itself.
  • Waitlist requests: the email address and the Telegram handle of the person asking and, if they give them, their name or their agency's and links to their Fanvue profiles; what they tell us about their business (how many creators they run, whether their subscribers are free or paid, their new subscribers and revenue over 30 days, what a subscriber is worth to them, who answers their chats today and what they write about them); and a one-way digest of the network address the request came from, to limit repeated requests. We do not keep the address itself.

Fans may share personal details in a conversation. We process them only to provide the service in that conversation, including the notes described in section 4. We do not receive fans' payment card details: payments are handled by Fanvue.

3. What we use it for

  • To provide the service to the agency: reading incoming messages and events, writing and sending replies in the creator's voice, following up, offering pay-per-view content, and showing the team its chats, sales and audit trail.
  • To keep conversations safe: recognising chats that must be frozen and handed to a person, and keeping a record of what happened.
  • To run accounts: creating sign-ins for team members, signing them in, and answering support requests.
  • To answer a request to join the waitlist: looking at whether the service fits, and writing to the person about it by email or Telegram.
  • To keep the service secure and working: finding faults, preventing misuse and measuring reliability.
  • To meet legal obligations and to deal with legal claims.

For the data we control, we rely on our contract with the agency, on our legitimate interest in running a secure and reliable service, and on legal obligations where they apply. For a waitlist request we rely on the steps the person asks us to take before a contract, and on our legitimate interest in knowing who asks to use the service. For workspace data, the agency decides the legal basis as controller. We do not sell personal data, and we do not use it for advertising of our own.

4. Webhook logs and what is kept from chats

Fanvue tells the service about new messages and other events through webhooks. The text of a fan's message is not kept in our webhook logs: the stored copy of an event keeps identifiers and times and leaves the message text out. Stored event payloads are pruned automatically on a schedule.

The service does not keep its own full copy of every conversation: it reads a chat from Fanvue when it needs to write in it. What it does keep in the workspace is what the AI needs to stay consistent and what the agency's team needs to supervise it: short notes about a fan drawn from the conversation (for example what they said about themselves and what they bought), a summary of the history with a long-standing customer, the drafts and messages the AI wrote, and the excerpts a team member rated or flagged.

5. Service providers

We use other companies as sub-processors to run the service. They handle data on our instructions. By category, they are:

  • Hosting: runs the application and its scheduled jobs.
  • Database, sign-in and file storage: stores workspace data, accounts and files.
  • Email delivery: sends a team member the link to choose a new password when they ask for one. It receives their email address.
  • AI model providers: receive the conversation context needed to write a reply, such as recent messages in the chat, a picture the fan has sent, the creator's profile and the relevant script, and return the text.
  • Voice provider (optional): used where an agency switches on voice notes. It receives what is needed to produce the audio, such as the text to be spoken.

The list of named providers is available on request. If an agency connects a tool of its own, such as a channel for alerts, the service sends information to that tool on the agency's instructions. Fanvue is not our sub-processor: the service reads from and writes to Fanvue through its official API, and Fanvue handles that data under its own privacy policy. We may also disclose data where the law requires it.

6. International transfers

Some of these providers may process data outside the country where you live, including outside the European Economic Area and the United Kingdom. Where that happens, we rely on a transfer mechanism that the law recognises, such as an adequacy decision or standard contractual clauses.

7. Retention and deletion

  • Workspace data is kept for as long as the workspace exists, except for event payloads, which are pruned as described in section 4.
  • A workspace admin can request deletion of the workspace and its data from Settings at any time. We act on the request promptly, and deletion removes the workspace's data, including the notes and messages kept from chats, profiles, scripts, stored tokens and the team's sign-ins.
  • A waitlist request is kept for up to 12 months and is deleted after that. We delete it sooner when the person who sent it asks us to.
  • Backups are kept for a limited time and age out on their normal schedule.
  • We may keep limited records for longer where the law requires it or where we need them to deal with a legal claim.

8. Security

  • Data is encrypted in transit.
  • Fanvue tokens are stored server-side only and are never sent to the browser.
  • Each workspace's data is isolated from every other workspace's, and the isolation is enforced in the database itself.
  • Our own staff have least-privilege access: no more than they need to run and support the service.

No system is free of risk. If we learn of a personal data breach that affects workspace data, we tell the agency concerned without undue delay.

9. Your rights

Under the GDPR and similar laws, you have the right to ask for access to your personal data, to have it corrected or deleted, to restrict or object to its use, and to receive it in a portable form. You also have the right to complain to the data protection authority where you live or work.

  • Fans and creators: please contact the agency that runs the creator account, because it is the controller of that data. We help agencies answer these requests, and if a request reaches us instead we pass it on to the agency concerned where we can identify it.
  • Team members of a workspace: ask a workspace admin, who can change or remove your account.
  • People on the waitlist: ask us, and we correct or delete your request.

We answer within the time the law allows.

10. Cookies

Squeezly uses only essential cookies: the session cookie that keeps you signed in, and a short-lived cookie that protects the step where you connect or sign in through Fanvue. We do not use advertising or analytics cookies. Your browser also remembers, on your device only, whether you chose the light or the dark look of the site.

11. Children

Squeezly is a service for business users. It is not directed at children, and it must not be used in connection with anyone under 18. A chat that shows signs of a minor is frozen and handed to a person at the agency.

12. Changes to this policy

We may update this policy. We will post the new version on this page with a new date and, where a change materially affects how personal data is handled, tell workspace admins by email or in the app.