Data protection
How we meet UK GDPR when we handle your organisation's data: the data processing terms, our sub-processors, transfers and security.
Last updated 18 November 2026
Who is responsible for what
UK data protection law (the UK GDPR and the Data Protection Act 2018) splits responsibility between a controller, who decides why and how personal data is used, and a processor, who handles it for them.
- Your organisation's content. You're the controller of the personal data you put into 53°, such as your contacts and the people you send proposals to. That includes the emails sent from and received at any email addresses you connect. We're your processor. The terms below apply.
- Your account and our own records. We're the controller of the data we use to run our business: your account, billing, support and analytics. The privacy policy covers that.
- Company
- 53 Degrees App LTD
- Company number
- 16727854
- ICO registration
- ZC077341
- support@53degrees.app
Data processing terms
These terms are part of our terms of service. They apply whenever we process personal data for your organisation, and they're the contract the UK GDPR requires between a controller and its processor. You don't need to sign anything separately.
What we process
| Aspect | Details |
|---|---|
| Subject matter | Storing and processing your organisation's content so that you can use 53°. |
| Duration | For as long as your organisation exists in the app, then until its content is deleted. |
| Nature and purpose | Hosting, organising, displaying, sending and deleting content as you and your members direct through the app, including sending and receiving email at the addresses you connect. |
| Types of personal data | Names, contact details, job roles, notes and messages, files, deal and proposal details, signatures, and whatever else you choose to add. If you connect your own email addresses: the emails sent from and received at them, with their attachments, the names and addresses of the people they're from and to, their subject and time, and whether each was delivered, opened, clicked, bounced or marked as spam. If you send marketing email: who is on your lists, and the record of how each person came to be, with the IP address and browser of anyone who signed up, confirmed or unsubscribed themselves. |
| Whose data | Your contacts, customers and suppliers, the people you send proposals to, the people you exchange email with, and your members and guests. |
The app isn't built for special category data, such as health records, or for data about criminal convictions. Please don't add it.
Email from your own addresses
If you connect your own email addresses, we send email from them for you, receive what's sent to them, and keep both in your inbox in the app. We store each email's content and attachments, who it's from and to, its subject and time, and whether it was delivered, opened, clicked, bounced or marked as spam. We also hold your domain name, its DNS records and whether they've been verified.
The people you write to, and who write to you, are your contacts. You're the controller of these emails and we handle them on your instructions, like the rest of your content.
You can track opens and clicks. With tracking on, emails sent from your addresses carry a tracking pixel and rewritten links, so you can see when they're opened and clicked. Tracking is off unless an owner or admin turns it on under Organisation settings → Integrations → Email.
We count how many of your emails bounce or are marked as spam, and pause sending from your addresses if too many do. Your addresses still receive email while sending is paused.
Marketing email
If you send marketing email, the people on your lists are your contacts and you're the controller. We send to a contact only while there's a record of how they came to be on your list, and we keep that record for you: each change, when it happened, and on whose word. For a sign-up on one of your forms it holds the wording the person agreed to, the privacy policy it linked to, and their IP address and browser. For someone a member of your team adds, or a file you import, it holds who did it and the reason they gave.
A form that opts people in to marketing email can only be live while it asks them to agree to your privacy policy, and you've given us a link to one. You can also ask new subscribers to confirm their email address first.
Every marketing email carries a link to unsubscribe and your postal address, and neither can be removed. Unsubscribing takes effect at once, applies to all of your marketing email, and is recorded with the person's IP address and browser. A member of your team can't opt that person back in unless they've asked to be.
A consent record is kept for as long as you keep the contact, and for three years after you delete them, so you can still answer a question about an email you sent. Deleting your organisation deletes its consent records.
We keep one list of addresses that no organisation can send marketing email to: those where email bounced, and those whose owner marked an email as spam. All marketing email leaves through the same service, so an address that fails or objects for one organisation is blocked for all of them. We're the controller of that list. It holds the address, the reason and the date, and it isn't deleted with your organisation. A contact at a blocked address stays in your contacts and can't be opted in.
What we commit to
We will:
- process your data only on your documented instructions, which are these terms and what you and your members do in the app, unless UK law requires otherwise, in which case we'll tell you first if we're allowed to
- tell you if we think an instruction breaks data protection law
- make sure everyone we let handle your data is bound to keep it confidential
- keep the security measures described on this page in place
- use sub-processors only as described below, under contracts that protect your data to the same standard, and stay responsible for what they do
- help you answer requests from individuals exercising their rights
- help you with security, breach notification, impact assessments and consulting the regulator, as far as they relate to our processing
- delete or return your data when the service ends, as described below
- give you the information you need to show these terms are being met, and allow an audit, as described below
If you need to audit us, we'll first answer your questions in writing and share what evidence we have. If that isn't enough, you can audit our processing once a year, with 30 days' notice, in working hours, at your own cost and under a confidentiality agreement.
What you commit to
- You have a lawful basis for the personal data you add, and you've told the people it's about what they need to know.
- That covers the emails you send and receive through your own addresses, and the record of opens and clicks while tracking is on. Telling the people you write to, and having a lawful basis for tracking, is yours to do.
- You'll send marketing email only to people who have agreed to it, or whom the law otherwise lets you write to, and the reason you give when you add someone by hand or from a file is true.
- The privacy policy your forms link to is yours, is accurate, and says how you use what people give you.
- Your instructions to us are lawful.
- You'll choose who joins your organisation with care and keep their roles up to date.
Sub-processors
You agree to us using the providers below to help run the app. Each is bound by a contract that protects your data.
| Provider | What it does | Data involved | Where |
|---|---|---|---|
| Convex | Hosts the app's database and server code | Accounts, organisations and all the content you add | United States |
| Vercel | Hosts and delivers the web app | IP addresses and request logs | United States, with servers worldwide |
| Cloudflare | Checks that a sign-up comes from a person, not a bot | IP address and browser details when you create an account | United States, with servers worldwide |
| UploadThing | Stores uploaded files | Files, profile pictures and logos | United States |
| Stripe | Takes payments and issues invoices | Billing contact, billing address, tax ID and payment card | Ireland and United States |
| Resend | Sends the app's email, sends and receives email at the addresses your organisation connects, and sends your organisation's marketing email | Names, email addresses, message content and attachments, your domain name, and whether an email was delivered, opened, clicked, bounced or marked as spam | United States |
| Bouncer | Checks that an email address can receive email before marketing email goes to it | The email addresses your organisation sends marketing email to | European Union |
| PostHog | Product analytics, session replay, error reports and logs | Usage events, device details and, with consent, your name and email | European Union |
| Productlane | Help centre, support messages and feedback | Name, email address and what you send us | European Union |
| Linear | Our record of customer organisations, for support and planning | Organisation name and plan | United States |
| incident.io | Alerts us to faults and runs the status page | Technical fault details, and your email address if you subscribe to status updates | United Kingdom and United States |
Before we add or replace a sub-processor, we'll update this page and email your organisation's owner at least 14 days ahead. If you object on reasonable data protection grounds and we can't resolve it, you can cancel and we'll refund any fees paid for time after you leave.
These services only receive data when you or a member choose to use them. They act under their own terms, not as our sub-processors.
| Provider | What it does | Data involved | Where |
|---|---|---|---|
| Sign-in, Calendar, Drive and Contacts, when you connect them | Your Google profile, and the calendar events, files or contacts the connection covers | United States, with servers worldwide | |
| Microsoft | Sign-in, Outlook Calendar, OneDrive and Outlook Contacts, when you connect them | Your Microsoft profile, and the calendar events, files or contacts the connection covers | United States, with servers worldwide |
| Sign-in, when you choose it | Your LinkedIn name, email address and profile picture | United States | |
| Giphy | GIF search in chat | What you search for, and your IP address when a GIF loads | United States |
International transfers
Several of our sub-processors store data outside the UK. We only transfer personal data where the law allows it:
- to countries the UK has found adequate, which includes the European Union
- to US companies certified under the UK-US data bridge
- otherwise under the International Data Transfer Agreement, or the UK Addendum to the EU's standard contractual clauses, after assessing the risk
Security
These are the measures we keep in place.
- Encryption. Data is encrypted in transit with TLS, and at rest by our hosting providers.
- Sign-in. Every password sign-in needs a second step, by emailed code or authenticator app. Passkeys are supported, new accounts must verify their email address, and sign-in attempts are rate limited. Signing up with Google, Microsoft or LinkedIn only works when the provider confirms the email address.
- Sessions. Members can see every device they're signed in on and revoke any of them.
- Access by role. Each member's role decides what they can see and change, and the app checks it on every request. Only a role that may change members' roles can invite an admin.
- Separation. Each organisation's data is kept apart from every other's.
- Files. Private files are served through signed links that expire. What a file is, how big it is and whose it is are taken from our storage provider, never from the browser.
- Our staff. Access to customer data is limited by staff role and ends when someone leaves our team. What staff do, including signing in as a customer to help them, is recorded in an audit log.
- Browser protections. Other websites can't show the app inside their own pages, apart from the forms built to be embedded.
- Analytics. Session replays never show what anyone types.
- Backups. The database is backed up every day.
- Monitoring. Automated checks watch the app and alert us to faults.
Requests from individuals
If someone asks to see, correct or delete the data you hold about them, you can do most of it in the app: find the contact, edit or delete it, or export your contacts to a file. If you need more, email us and we'll help.
If someone contacts us directly about data in your organisation, we'll pass the request to you and won't answer it ourselves unless the law requires us to.
Data breaches
If we become aware of a breach affecting your organisation's personal data, we'll tell the organisation's owner without undue delay, with what we know about what happened, what data is involved and what we're doing about it, so you can meet your own duty to report it.
Deleting and returning data
- You can export your contacts, and download your files, at any time.
- Deleting something in the app removes it from the app. Deleting the organisation removes all of its content, and the clear-out finishes in the background.
- Emails sent from and received at your own addresses are kept until you delete them. We don't delete them on a timer. Deleting a conversation removes its emails, and their attachments unless you've filed one with another record. A conversation about a form response or a proposal is deleted with that response or proposal. Removing your domain keeps the conversations you've already had.
- A copy of each email we send for you is held for 45 days after it's delivered, bounces or fails, so that delivery, opens and clicks can be matched to it, and never for more than 90 days after it was sent. It's deleted on that schedule, not when you delete the conversation or the organisation.
- The record of how a contact came to be on your marketing list is kept for three years after you delete the contact, then deleted. Deleting your organisation deletes these records with everything else.
- The list of addresses that can't be sent marketing email is ours, not yours, and stays when your organisation is deleted.
- An organisation that goes a year without a plan is deleted, after we email the owner and wait 14 days.
- Copies in our providers' backups are overwritten on their normal cycle.
- We keep invoices and payment records for as long as tax law requires.
Contact us
We aren't required to appoint a data protection officer. Data protection questions go to support@53degrees.app.