Obscurly - Secure Data Processing

Welcome to SimSage (UK) Limited’s Secure Data Processing overview, specifically as it applies to how your data is handled by our Obscurly Document Redaction tool.

Obscurly is a product developed, owned and operated by SimSage (UK) Limited.

SimSage UK Limited (“we”), (“us”) or (“our”) respects your privacy and is committed to protecting your personal and business data.

This Secure Data Processing overview applies to your use of our Obscurly sites:

(“our sites”);

and sets out the basis on which any data we process for you through the Obscurly tool, or that you provide to us (as an individual acting on behalf of an organisation),

Your acceptance of this data security policy is deemed to occur upon your first use of our sites. If you do not accept and agree with this policy, you must stop using our sites immediately.

For SimSage (UK) Limited’s full Privacy Policy, please refer to https://simsage.ai/privacy-policy

SimSage (UK) Limited’s full Privacy Policy applies to:

communications with us (whether in person or online via the contact us page (or using the SimSage info@simsage.ai or info@simsage.co.uk addresses);
information you provide to us when you sign up to create an account on our sites; and
information you provide when you request software licences or services from us.

Changes to our Obscurly Data Security processing

Any changes we may make to the Obscurly Data Security Processing in the future will be posted on this page and, where appropriate, notified to you by e-mail.

Contacting us

If you have any questions, comments or requests regarding the Obscurly Data Security Processing, or SimSage (UK) Limited’s Privacy Policy or any issues or queries regarding any data processing, or you would like to make a complaint, please contact us via:

email at info@simsage.ai or info@simsage.co.uk,
by telephone on +44 (0) 7961 801095, or,
by post to SimSage, St John’s Innovation Centre, Cowley Road, Cambridge CB4 0WS, United Kingdom.

If you have any cause for complaint about our use of your data, please contact us using the details provided above and we will do our best to solve the problem for you. If we are unable to help, you also have the right to lodge a complaint with the UK’s supervisory authority, the Information Commissioner’s Office (www.ico.org.uk).

How your Obscurly-related data is handled by SimSage

Hosting

Obscurly runs on a dedicated virtual server (8 vCPU, 24 GB RAM, Ubuntu 24.04 LTS) with Contabo GmbH, a German hosting provider, in their EU region. Only Obscurly runs on it. A separate, identical test server is used for changes before they reach production.

What happens to your document

Your file is uploaded over an encrypted connection and held in the server's memory only. It is never written to disk.
While you review your file on the Obscurly site, the on-screen preview is rendered by a document viewer whose working cache lives on a memory-backed filesystem, and that copy is never copied to disk or any other storage media.
The moment you save the redacted copy or cancel, the document and its preview are discarded. If you do neither, they are discarded automatically after 30 minutes.
The only information retained afterwards is a count of how many saves your account made that day, used for subscription plan limits. No document content and no document names are retained.
Our server logs mask the identifier of your review session, so a log line cannot be tied back to a document.

Who holds your credentials and payment details

Sign-in is handled by Kinde, an independent secure-identity provider. https://www.kinde.com/ Obscurly never sees or stores your password.
Card payments are handled by Stripe https://stripe.com/ through integration with Kinde's billing service. Obscurly never sees card numbers or any other card details.
Nothing in Obscurly stores personal data beyond your account identifier and the daily save count.

Encryption and browser protections

HTTPS only, TLS 1.2 or 1.3. Older protocols are refused. Certificates come from Let's Encrypt and renew automatically.
HTTP Strict Transport Security is set for one year, so browsers refuse to talk to the site unencrypted.
A Content Security Policy restricts what the page can load and run to our own code and the analytics tag. Framing by other sites is blocked, content-type sniffing is disabled, and the referrer is not leaked to other sites.
The session cookie is Secure, HttpOnly, SameSite=Strict, scoped to the API path, and each review is bound to the browser that started it, so nobody else can reach your session even with its address.

Limits that protect against abuse

Requests are rate-limited per client at 40 per second with short bursts, and 20 concurrent API connections.
At most 20 open reviews per network address, 100 in total, and 300 MB of documents in memory at once, so the service degrades gracefully rather than falling over.
Uploads are capped at 50 MB, and a single redaction is given a fixed time budget.

Server hardening

Administrative access is by SSH key only. Password logins are disabled, and root cannot log in with a password.
A host firewall permits only web traffic (80 and 443) and SSH. Every other port is closed to the internet.
Fail2ban blocks addresses that repeatedly fail to log in.
The operating system installs security updates automatically.
The application runs in containers. The redaction service runs as an unprivileged user, and the containers are reachable only through the front web server on the local interface, never directly from the internet.

Testing and assurance

Every release passes an automated gate before it ships: unit tests, end-to-end tests in five browsers, and a vulnerability scan of the dependencies and the built container images. A release with a high or critical finding cannot be published.
The service was scanned dynamically with OWASP ZAP, both anonymously and as a signed-in user, and penetration tested in September 2026. No high-severity findings are outstanding.
This is a single server, not a clustered setup.