Legal
Privacy Policy
Last updated: 31 October 2026
Who we are
Deckr is operated by Brobots Ltd, a company registered in England and Wales. Deckr turns a survey data file into a PowerPoint deck. This policy explains what we store, for how long, who else handles it and what you can control. It covers your rights under UK GDPR and the Data Protection Act 2018.
For the survey data you upload, your organisation decides what is processed and why, and we process it on your behalf. For your account details, we decide how they are used, as described below.
Questions? Contact us at hello@getdeckr.com.
In short
Your uploaded data file is saved on our server while your deck is built, then deleted when the build finishes or fails.
Finished decks are kept in your account until you delete them, or until your organisation's retention window (90 days unless you change it) has passed and our retention process removes them.
A new organisation starts with open-ended answers kept away from the AI model, and with charts-only decks, which make no call to write analysis.
We keep an account for each person who signs in, and nightly database backups for 14 days.
What we store, and for how long
| What | What it contains | How long |
|---|---|---|
| Your uploaded files | The survey data file, plus any template, logo, crosstab, previous-wave or per-market file sent with it. Saved on our server's storage so the build survives a restart. | Deleted when the build finishes or fails. A build that never starts is failed and its files deleted after 3 hours. A file that makes the build crash is tried at most three times, then failed and deleted. |
| Finished decks | The PowerPoint file, plus any ZIP of several decks or Excel tables export. | Until you delete the deck, or your organisation's retention window has passed and our retention process removes it (see section 04). They are not included in backups. |
| Deck records | The status of each build; the brief you typed (study name, audience, objectives, notes and settings) so the deck can be run again; the data file's column names, question wording and declared answer labels, and the order of the deck's charts, so a re-run on your next wave keeps that order and says what changed (never an answer, a count or a figure); the outline of any written analysis, with its numbers removed; the slide count, file size and where the deck is stored. Never the data file itself. | As the deck they belong to. |
| Open-end coding cache | Only when your organisation has turned on respondent free text: for each theme, a count, a sentiment split and one example answer from a respondent. | As your decks: your retention window, an organisation erase, or deleting the decks. |
| Your organisation's settings files | Templates, logos, brand fonts and reference decks you upload to teach Deckr your house style. A finished client deck used as a reference can itself contain survey results and quotes. | Until you replace them or your organisation's data is erased. The retention window does not remove them. One working copy of a reference deck, made when you build on it as your template, is not yet removed by an erase. Nor is a separate cache of the house style Deckr reads from each reference deck, which can hold short pieces of the deck's text. |
| Accounts | For each user: email address, a hashed password (or a Google sign-in), role, and sign-in security fields. For each organisation: its name (with Google sign-up, your Google name is used to start with), branding and analysis settings, plan, and Stripe customer and subscription identifiers if you pay by card. API keys are stored hashed. | While the account exists. A sign-up whose email is not verified within 24 hours is deleted. |
| Usage and security records | For each build: time taken, study type, slide count, the study name, and the AI usage and its cost. Product events (for example "signed up", "deck created") carrying coarse categories only. A security log of sign-ins, role and plan changes, API-key changes, admin downloads and deck deletions. | While the account exists. Removed by an organisation erase. |
| Database backups | A nightly copy of our database: accounts, records and settings. Deck files are not in it. | Each backup is set to be deleted 14 days after it is made. A record you delete stays in the backups made before you deleted it until those backups are deleted. |
| Server logs | Our server's own log lines, held by our hosting provider. They can include email addresses, organisation names, column names from an uploaded file, and occasionally text quoted in an error message. | Set by our hosting provider, not by Deckr. |
| Error reports | If error reporting is switched on: the type of error, where in our code it happened and which page was requested. Error messages, log text, web addresses, request contents, cookies and sign-in headers are removed before a report is sent. | Set by Sentry (see section 07). |
| Applications | What you enter on the application form (name, role, email, agency, country and your answers). An example deck or sample data file you attach is emailed to our inbox, not stored on our server. | Kept until we delete them. They are not covered by the retention window. |
| Onboarding sessions | When we run a scoping session with you: your answers, the summary we compile, and any sample data file and reference deck you upload. | The two files are deleted when the summary is compiled, or 14 days after your last answer if the session is never finished. The answers and summary are kept. |
Retention and deletion
Your retention window
Each organisation has a retention window for its decks, their records and its open-end coding cache. It is 90 days unless an Owner or Admin sets another number under Settings, from 1 day to 3,650 days. Setting it to 0 keeps them indefinitely.
When a deck is older than the window, it becomes due for deletion and is removed when our retention process runs. Until that process has run on your organisation, an older deck may still be in your account. You can always delete it yourself.
Deleting a deck yourself
The Delete button on your Decks page removes the deck file and its records straight away. The deck file is gone for good. Its records stay in database backups until those backups are deleted (see section 03).
Erasing an organisation's data
Email us to ask for your organisation's data to be erased. An erase removes every deck and its records, the files of any build still running, your templates, logos, fonts and reference decks, your open-end coding cache, onboarding sessions recorded as being about your organisation, and your usage and security records.
An erase does not close your account. Your sign-in, your team list and your billing link stay until you ask us to close the account as well. Things an erase does not reach today:
- database backups, until each backup is deleted;
- the working copy of a reference deck, and the cache of the house style read from your reference decks, both described in section 03;
- an application, or an onboarding session held before your organisation existed on Deckr;
- server logs, error reports, and data held by the providers in section 07, which follow their own retention.
Download links
Each download link is made when you ask for it and expires after one hour. Until it expires, anyone who has the link can download the deck, so please do not forward it.
What reaches the AI model, and what never does
Deckr computes every figure itself, in its own code. It uses Anthropic's Claude models for language tasks. What we send depends on how your organisation and each deck are set up.
On any deck, these can be sent
- Column names and question wording (including the items of a grid or tick-box question), with each question's type and how many people answered, so the model can propose an analysis plan and identify key questions.
- Short variable codes (for example
q3_purchase_intent), so the model can turn them into readable titles.
Only when a deck includes written analysis
- The brief you typed, and summary figures for each slide: percentages, averages, base sizes and answer labels. A charts-only deck makes no call to write analysis.
Only when your organisation has turned on respondent free text
- Every open-ended answer that can be coded, each cut to 300 characters and sent in batches, to be grouped into themes with sentiment.
- A few short example answers, included when the model writes the analysis.
- Nothing removes personal details that a respondent wrote inside an answer, such as a name or an email address, before it is sent.
Never sent
- Your uploaded file itself, or any respondent's row of answers.
- Columns Deckr detects as personal details, such as names, email addresses, phone numbers and respondent identifiers. These are also never charted.
One limit to know about: with free text turned off, a "please specify" column with only a few different answers can still be charted as a list of answers. Those answers then reach the model as chart labels, like any other.
Templates and reference decks are read by our own code, not by the model. We have an option to analyse reference-deck images with the model, which is switched off.
We use Anthropic's API under its commercial terms. Anthropic states that it does not train its models on API inputs or outputs, and that by default it deletes them after 7 days. See Anthropic's privacy policy. Deckr does not train or fine-tune any model on your data.
Controls for your organisation
- Respondent free text. Decides whether open-ended answers can reach the model (section 05). A new organisation starts with it off. An Owner or Admin can change it under Settings → Analysis policy. If your organisation was set up before October 2026, please check this setting: it may be on.
- Charts only. A new organisation starts with charts-only decks: charts titled with their questions, with no written analysis and no call to write any. Written analysis can be added to a deck on the upload page.
- Retention window. How long decks, their records and the open-end coding cache are kept (section 04).
- Team roles and projects. Owners and Admins decide who can see, create and delete decks, and who can reach each project.
Who else handles your data
We do not sell, rent or trade your data. We use these providers to run Deckr:
| Provider | What for | What they handle |
|---|---|---|
| Railway | Hosting | Our servers and their storage: the database, your uploaded files during a build, and decks when cloud storage is not in use. Server logs. |
| Cloudflare R2 | File storage | Finished decks, your settings files, and the nightly database backups. |
| Anthropic | AI model | What section 05 describes. |
| Stripe | Billing, if you subscribe | Your email address, plan and payment details. Card details are entered on Stripe's own page and never reach Deckr. No survey data. |
| Sentry | Error reports, when switched on | What section 03 describes under "Error reports". No survey data. |
| Our email provider | Sending email | Recipient addresses and the message: sign-up verification, password resets and team invites. When you tick "email me when ready", your finished deck is attached. Application form messages, with any files you attached, are sent to our inbox. |
| "Sign in with Google", if you use it | Your email address, name and whether Google has verified the email. No survey data. | |
| Google Fonts | Web fonts | Your browser loads our fonts from Google, so Google receives your IP address and the page request. No survey data. |
Where your data is held
Finished decks, settings files and database backups are stored with Cloudflare R2 in its EU jurisdiction, which keeps those files in the EU.
Our servers, database and your uploaded file during a build are hosted by Railway. Anthropic, Stripe, Sentry and Google are based in the United States, so data sent to them may be processed outside the UK and the EU.
How we use your data
- To build your decks and keep them available to you
- To run your account: sign-in, team invites, password resets and billing
- To keep the service secure, and to find and fix errors
- To count usage, which we do ourselves, without third-party analytics
We do not use your data for advertising, profiling, or any automated decision-making that produces legal or similarly significant effects.
Cookies and browser storage
Deckr sets two cookies, both only to keep you signed in safely:
- a session cookie, which holds your sign-in and a security token and ends when you close your browser;
- a "remember me" cookie, which keeps you signed in for up to 30 days.
Your browser's local storage remembers whether you chose the light or dark theme. We use no advertising cookies, tracking pixels or third-party analytics. Stripe's and Google's own pages, if you visit them to pay or sign in, are covered by their own policies.
Your rights under UK GDPR
As a data subject you have the right to: be informed, access your data, rectification, erasure, restriction of processing, data portability, and to object to processing.
To exercise any right, email hello@getdeckr.com and we will respond within 30 days. If you are a respondent in a survey a Deckr customer ran, please contact the organisation that ran the survey; we will help them answer your request.
Contact and complaints
Contact Brobots Ltd at hello@getdeckr.com for any privacy-related queries.
If you are unsatisfied with our response, you have the right to lodge a complaint with the UK Information Commissioner's Office at ico.org.uk.
Brobots Ltd, registered in England and Wales.