Privacy
Last updated 6 November 2026
hush is a CRM. Almost everything in it belongs to the business using it rather than to us, and this page is mostly about what that means in practice: where the data sits, who can reach it, and what we will not do with it.
Who we are
hush is made and run by Sonic Blue Tech Ltd, a company registered in England and Wales, number 12789740, at The Old Dairy, 1 Whitebushes, Redhill, Surrey, RH1 5LN.
Two different jobs
We handle two kinds of information and the law treats them differently, so it is worth being clear which is which.
- Your customers' details, put into hush by you. Here you are the controller and we are your processor. It is your book. We hold it, we do what your account asks us to do with it, and we do nothing else with it.
- Your own account. Your name, your sign in details, what you pay and when. Here we are the controller, because it is our relationship with you rather than yours with your customers.
Where it lives
In Frankfurt. The application and the database both run in the European Union on infrastructure provided by Render. We chose Frankfurt on purpose, because hush can hold sensitive details such as your customers' health details.
Five of the companies listed under "Who else touches it" can handle data in the United States: Render, Anthropic, Twilio SendGrid, Stripe and Sentry. Google Fonts may too, but Google does not say where. When personal data goes from the UK to the United States, the law requires a safeguard: an agreed set of rules that protects it. For each of the five, the table names the safeguard that its contract with us relies on. For Anthropic, this can include notes, emails or files with sensitive details about your customers.
Backups are taken daily and kept in the same region.
What we hold
- The records you create or import: people, companies, bookings, jobs, invoices, notes and the history of what changed.
- Whatever you connect hush to, and only what that connection is scoped to read.
- Messages hush has sent on your behalf, so you can see what went out and when.
- An audit log of who did what inside your account.
Your mailbox
When you connect Outlook or Gmail to send, hush asks for permission to
send and for nothing else. The scopes are
Mail.Send and gmail.send.
Reading your mail is a separate choice, made with its own button. If you
connect Outlook reading, hush asks for Mail.Read
only: it can read, and cannot send, move, change or delete anything. It reads
your Inbox, your Sent Items and only the other folders you choose. It files an
email only against people and work already in your hush account, keeps nothing
from an email it does not file beyond a count, and never creates a contact from
your mail.
hush has no permission to read Gmail. Mail you forward to hush yourself is filed the same way.
You can revoke it at any time from Microsoft or Google directly, without asking us.
Who else touches it
We use as few outside companies as we can. The first five in the table are bound by a contract to use your data only as we instruct. Google Fonts and the OpenStreetMap Foundation have no contract with us.
| Who | What for | What they see | Where | Safeguard |
|---|---|---|---|---|
| Render | Hosting and the database | Everything hush stores | Frankfurt, Germany. Render is a US company, and its contract allows the data to be sent to the United States | The UK Extension to the EU-US Data Privacy Framework. If the framework stops applying, the UK's International Data Transfer Addendum to the EU Commission Standard Contractual Clauses applies instead |
| Anthropic | Answering questions you ask in hush, reading files you upload, and suggesting when a piece of work has moved on | The question and the figures needed to answer it; the file; or the recent notes and emails on the piece of work concerned | The United States, and other countries where Anthropic runs its service | The UK's International Data Transfer Addendum to the EU Commission Standard Contractual Clauses |
| Twilio SendGrid | Sending email, when you have not connected your own mailbox | The message and who it is addressed to | The United States | The UK Extension to the EU-US Data Privacy Framework. If the framework stops applying, the UK's International Data Transfer Agreement applies instead |
| Stripe | Taking payment for hush | Your billing details. We never see your card | The United States, and other countries where Stripe runs its service | The UK Extension to the EU-US Data Privacy Framework. If the framework stops applying, the UK's International Data Transfer Addendum to the EU Commission Standard Contractual Clauses applies instead |
| Sentry | Telling us when something in hush goes wrong, so that we can fix it | The error, the page it happened on and which business it affected. Form contents, cookies and your account details are removed first, but an error message can include part of a record | The United States, and other countries where Sentry runs its service | The UK Extension to the EU-US Data Privacy Framework. If the framework stops applying, the UK's International Data Transfer Addendum to the EU Commission Standard Contractual Clauses applies instead |
| Google Fonts | The typefaces on these pages | Your IP address and browser details, when a page loads. Google says it does not set cookies or use this to build profiles | Google's servers. Google does not say where | Google does not name a safeguard for Google Fonts |
| OpenStreetMap Foundation | Finding where a town or city is, so that hush can show its weather forecast. This happens only when you add a place without its latitude and longitude | The name or address of the place you typed. The request comes from hush's server, so they do not see your IP address. They keep a log of searches | The United Kingdom and the Netherlands | None is needed, because the data stays in the UK and the EU |
Systems you choose to connect, such as HubSpot, QuickFile or your own mailbox, are not our subprocessors. They are yours, you connect them yourself, and you can disconnect them the same way.
What we do not do
- We do not sell anything to anybody.
- We do not advertise to you or to your customers.
- We do not track you across the internet. There is no analytics script on the app and no advertising pixel anywhere.
- Email hush sends for you carries no open tracking and no click tracking. A reminder about money should not arrive full of links to a domain your customer does not recognise.
- We do not use your book to train anything.
Cookies
One. It says you are signed in, and it exists so that you do not have to type your password on every screen. It is not shared with anyone and there is nothing else to consent to, which is why hush has never shown you a banner.
How long we keep it
Your records stay until you delete them or close your account. When an account closes we delete the data within 30 days, and you can export everything before that. Financial records that we are legally required to retain, such as our own invoices to you, are kept for six years.
Your rights
If you are a customer of a business using hush, that business decides what happens to your details. Ask them first, and we will help them answer you.
If you hold a hush account, you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to the address below and we will answer within a month. If you think we have got it wrong you can complain to the Information Commissioner's Office at ico.org.uk.
If something goes wrong
If there is a breach affecting your data we will tell you, and we will tell you what we actually know rather than waiting until the story is tidy.
Asking us anything
privacy@hushcrm.com, or by post to the registered address above.