PactBoost

Privacy Policy

Last updated 2 October 2026

This explains what personal data PactBoost handles, why, who helps us, how long we keep it and what your rights are under UK data protection law (the UK GDPR and the Data Protection Act 2018) and, where it applies, the EU GDPR.

1. Who is responsible

  • We are the controller for the data we need to run our business: accounts and sign-in, billing, security, support and our website. “We” means PactBoost Ltd, a company registered in England and Wales.
  • Your organisation is the controller for what its team puts into its workspace — prompts, uploads, generated media, boards, notes, and what its clients write on review links. For that content we act as a processor: we handle it only to provide PactBoost, on your organisation’s instructions, under our Data Processing Agreement.
  • If you are a client reviewing work on a review link, the workspace that sent you the link decides about what you write there; ask them first. You can also contact us.
  • Questions or requests: the contact details in the app.

2. What we collect

  • Account details: name, email address, your role, and a securely hashed password (we never store the password itself).
  • Workspace details: the workspace’s name, branding and settings, the people in it, invitations, and the names of the clients and brands it works for.
  • Billing details (Studio): the billing email and the workspace and contact name we give Stripe, our Stripe references, invoices and payment status. Your card details go straight to Stripe — we never see or store card numbers.
  • Content: prompts, uploads, generated pictures, videos and audio, boards, designs, notes, chats with the PactBoost assistant, brand kits, and the descriptions PactBoost’s AI writes of your files (when someone asks it to) so you and the assistant can find them.
  • Review feedback: what reviewers choose on a review link (keep or reject), what they write, and the marks they draw. We don’t ask reviewers for their name or email, and we don’t store their IP address.
  • Aggregator keys: the API keys you add, stored encrypted; only the last four characters are ever shown.
  • Activity: the workspace activity log admins can see (for example who invited whom, changed a setting or downloaded a file), when each person was last active, and a record of each generation (who ran it, the model, the prompt, its status and estimated cost).
  • Technical data: your IP address is used briefly to protect sign-in and other forms from abuse and is not stored, except in the record of actions taken by our own staff. Our server keeps short-lived error logs.
  • Messages: what you send us — by email or through the app.

3. Why we use it, and our legal basis

  • To provide PactBoost — accounts, workspaces, generations, storage, reviews, the assistant (performing our contract with you or your organisation).
  • To bill Studio workspaces and keep accounting records (contract; legal obligation for tax records).
  • To keep PactBoost secure — preventing fraud and abuse, investigating problems, keeping logs (our legitimate interests in a safe, working service).
  • To support you and tell you about important changes to the service or these policies (contract; legitimate interests).
  • To improve PactBoost using counts of how features are used (legitimate interests). We don’t use your content to train AI models, and we don’t sell personal data or use advertising trackers.
  • To comply with the law when we must (legal obligation).

4. How PactBoost uses AI

  • When you or a teammate generate something, or ask the PactBoost assistant for help, the prompt and the pictures, videos or audio involved are sent to the AI aggregator (kie.ai) and on to the model chosen. Nothing is sent to an AI model unless someone in your workspace starts it.
  • Some helpers run as part of a step you take: describing files when you or the assistant ask, learning from a result marked as approved so later prompts in the workspace follow what worked, and checking edited pictures during a review run. Each uses only that workspace’s own content, on the workspace’s key.
  • PactBoost doesn’t make decisions about people that have legal or similarly significant effects. AI results can be wrong; a person in your workspace decides what to use.
  • The aggregator’s and model providers’ own terms apply to the processing they do.

5. Who helps us

These companies process personal data for us:

  • DigitalOcean, LLC — Hosting: the server, the database, backups and stored files (Spaces).
  • Stripe — Payments, invoices and subscriptions for Studio workspaces.
  • kie.ai — The AI aggregator that runs generations and PactBoost’s AI helpers (the assistant, describing pictures, brand kits) and passes them to the AI model chosen — for example models from Google, OpenAI, Anthropic, Kuaishou (Kling) or ByteDance (Seedance).

A few more are used only when a feature is switched on. The full list, with what each receives and where, is on our Sub-processors page; we update it before adding a new one. If you connect Claude to PactBoost, or use the PactBoost desktop app’s “My Claude”, what Claude does is governed by your own agreement with Anthropic.

6. Transfers outside the UK

Some of these companies process data outside the UK, including in the United States. When they do, we rely on UK adequacy regulations (such as the UK–US data bridge) or the UK International Data Transfer Agreement or Addendum, or another safeguard the law allows. PactBoost’s own server and stored files are hosted in the DigitalOcean region named on our Sub-processors page.

7. How long we keep it

  • Your account: while you’re a member of a workspace. You can delete your account at any time in Settings → Account; it is anonymised straight away. If you’re removed from your last workspace, your account is anonymised 30 days later.
  • Content: until your team deletes it or the workspace is closed. Deleted files, folders and projects wait in the Trash for 30 days, where they can be restored, and are then permanently deleted. A file that other work in the workspace was made from (for example a reference picture) is the exception: it stays, hidden from the Library, as part of that work’s recipe until that work is deleted too — unless someone chooses “Delete forever”, which deletes it at once. The record of how each file was made (the model, prompt, settings and which files it used) stays in the workspace’s history until the workspace is closed.
  • When someone leaves a workspace: the files they made stay with the workspace, as they belong to the organisation.
  • After a Studio plan ends: the workspace stays read-only so you can download your files. If it stays without a plan for 12 months, we may close it, telling its admins at least 30 days before.
  • Closed workspaces: everything in them is permanently deleted 90 days after closing (until then, we can reopen it if you ask). We keep only a minimal record that the workspace existed, and the billing records below.
  • Sign-ups that were never paid for: deleted after 30 days.
  • Backups: every backup copy expires within 35 days, so deleted data leaves our backups within 35 days of being deleted.
  • Billing records: 6 years, as UK tax law requires.
  • Logs: the workspace activity log 12 months; records of our staff’s actions and support access 24 months; server error logs are rotated and kept only briefly.
  • Invitations and reset links: cleared 30 days after they expire or are used.
  • On your own devices: see our Cookie Policy for what PactBoost keeps in your browser and the desktop app.

8. Your rights

You can ask us for a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, or to receive it in a portable format. Where we rely on consent, you can withdraw it at any time. You can correct your name and delete your account yourself in Settings → Account, and download your workspace’s files from the Library. For anything else write to the contact details in the app; we’ll answer within one month.

If your request is about content in an organisation’s workspace, we may pass it to that organisation’s admin, as they decide about that content, and we’ll help them answer it.

You can also complain to the Information Commissioner’s Office (ico.org.uk), though we’d appreciate the chance to help first.

9. Security

  • Connections are encrypted (HTTPS). Passwords are hashed with a slow, salted algorithm; aggregator keys are encrypted; sign-in, reset and access tokens are stored only as fingerprints.
  • Every workspace’s data is kept apart from every other workspace’s, and the server checks the workspace on every request.
  • You can sign out of every device at once in Settings → Account; changing your password does the same.
  • Our staff look at a workspace’s content only to help it or keep PactBoost safe. Doing so needs a stated reason, is limited to an hour at a time, and is recorded in a log the workspace’s admins can see.
  • Review links can be opened by anyone who has the link, until the workspace closes it. Share them only with the people who should see the work.

10. Cookies and your devices

PactBoost uses only the cookies it needs to keep you signed in and protect sensitive actions — no advertising or analytics cookies. It also keeps some things in your browser, such as your preferences and a safety copy of the board you’re working on. The Cookie Policy lists them.

11. Children

PactBoost is for businesses and isn’t meant for anyone under 18.

12. Changes

We’ll update this policy when what we do changes, and tell workspace admins about significant changes before they take effect. See also our Terms of Service.