Privacy Policy
The short version
Your case material never reaches us. Documents, video, audio and images are opened, analysed and redacted entirely on your own computers. Nothing derived from them — no text, no transcripts, no detections, no thumbnails, not even file names — is transmitted to Safe Redact.
What we do hold is the information needed to run a licence: who your people are, which computers they have authorised, and what they are entitled to use. This policy explains that, and nothing about it is buried.
1. Who we are
Safe Redact is operated by [Registered company name], a company registered in [Country] under number [Company number], with its registered office at [Registered address]. In this policy “we”, “us” and “Safe Redact” mean that company.
For questions about this policy or about your personal data, contact admin@saferedact.io, or write to us at the address above marked for the attention of [Data protection contact].
2. Two systems, and why the difference matters
Safe Redact is built so that the part of the product handling sensitive material and the part connected to the internet are separate. It is worth understanding the split, because it determines what we could disclose even if we were compelled to.
The desktop application
Runs on your computers. Opens your files, detects faces, speech, text and other identifiers, applies redactions and writes the output. All of this happens locally, including the machine-learning models. Signing in when it opens needs a network connection; the work itself does not.
We have no access to anything it processes, and no ability to obtain it.
The Admin Panel
Runs on our servers. Records which organisations hold licences, which people hold seats, which computers are authorised, and what administrators have done. It is the only part that communicates with us.
Everything in this policy concerns this side alone.
3. What we collect
3.1 Account information
- Your work email address, which identifies your licence
- Your name, as recorded by you or your administrator
- The organisation you belong to, and your role within it
- Account status, and the time you last signed in
3.2 Device information
When you authorise a computer to run Safe Redact, we record:
- A device identifier derived from that computer's hardware and operating system
- The computer's name and operating system version
- When it was first authorised and when it was last seen
This exists to enforce the limit on how many computers one licence may run on. It is not location data, and it does not tell us what the computer is used for.
3.3 Administrative records
We keep an append-only record of actions taken in the Admin Panel — licences granted or revoked, devices released, roles changed, and occasions when Safe Redact staff viewed customer identities. These records exist so that changes affecting access can be accounted for afterwards, including by you.
3.4 Technical information
Our servers log the ordinary details of a web request, including IP address, browser type and the time of the request, and retain them for [retention period] for security and diagnostics.
3.5 What we never collect
To be explicit, because on a product like this the omissions matter more than the inclusions. We do not receive, store or have any means of obtaining:
- Documents, video, audio or images you open in Safe Redact
- Text, transcripts, detections, redaction regions or thumbnails derived from them
- File names, folder paths or project contents
- Any record of which files you have worked on, or when
- Your Safe Redact password (see section 5)
4. Why we process it, and on what basis
| Purpose | Data | Lawful basis |
|---|---|---|
| Providing and enforcing the licence you have bought | Account and device information | Performance of a contract |
| Authenticating you and keeping the account secure | Account information, technical logs | Performance of a contract; legitimate interests in security |
| Accounting for administrative changes | Administrative records | Legitimate interests in accountability; legal obligation where applicable |
| Sending service email — invitations, password resets, notices | Email address, name | Performance of a contract |
| Meeting legal, tax and regulatory obligations | Account and billing records | Legal obligation |
We do not use your information for advertising, we do not profile you, and we do not sell or share it for anyone else's marketing.
5. Passwords and sign-in
Safe Redact never sees your password. Authentication is handled by a dedicated identity service we operate, which stores only a cryptographic hash and is the only place your password is ever entered. When you change or reset it, you do so on that service — the Admin Panel cannot display, retrieve or set it, by design rather than by policy.
6. Cookies
The Admin Panel sets a single cookie, which keeps you signed in, along with a token that protects forms against cross-site request forgery. Both are strictly necessary for the service to function.
There are no advertising cookies, no analytics cookies and no third-party trackers of any kind. Nothing on these pages is loaded from an external service that could observe you.
7. Who else is involved
We keep the list of third parties short on purpose. Those who process personal data on our behalf are bound by contract to use it only on our instructions:
- [Hosting provider] — servers on which the Admin Panel runs, located in [Country / region]
- [Email provider] — delivery of service email such as invitations and password resets
We may also disclose information where we are legally required to. If we receive a demand for customer data, we will tell the affected customer unless prohibited by law from doing so. Note that such a demand cannot reach case material, because we do not hold any.
8. Where your data is held
Personal data is stored in [Country / region]. Where information is transferred outside [applicable region], we rely on [transfer mechanism, e.g. standard contractual clauses]. Customers with data-residency requirements should raise them before purchase, as they may affect which deployment is appropriate.
9. How long we keep it
- Account and device information — while the licence is active, then [period] after it ends
- Administrative records — [period], because their value is in being available long after the event
- Technical logs — [period]
- Billing records — as required by tax and company law
10. Your rights
Subject to the law that applies to you, you may ask us to give you a copy of your personal data, correct it, delete it, restrict or object to how we use it, or provide it in a portable form. To exercise any of these, contact admin@saferedact.io. We will respond within [period].
If your account was created by your employer, some requests are best directed to them first: they decide who holds a seat and what role you have. We will tell you if that is the case rather than simply refusing.
You also have the right to complain to a data protection authority — in [Country], [Authority name and contact].
11. Security
Connections are encrypted in transit. Backups are encrypted at rest. Access to production systems is restricted to named individuals and recorded. Licences are issued as cryptographically signed tokens, so a licence cannot be forged or altered without the signing key, which is held separately from the application.
If a breach affects your personal data and is likely to result in a risk to you, we will notify you and the relevant authority within the time limits the law sets.
12. Changes
If we change this policy in a way that materially affects you, we will tell account holders by email before it takes effect rather than relying on you to notice the date at the top of this page.