The safest data is data we never hold.
Last updated 22 September 2026
ROSA's security starts with a design decision: the check runs on the minimum data that can support its findings, and nothing more. That restraint is deliberate, and it is the strongest control we have. This page sets out how we treat the data we do hold.
Minimal by design
- No names, no identities. No name, full date of birth, address or contact detail appears on the tapes we receive. Loans are identified from facts fixed at origination about the borrower, the property and the debt, and the check is designed so that we cannot identify the person behind any loan.
- No access to your estate. No system access, no credentials, no software installed on your side, no integration with your pipelines. Each party sends us a file, and nothing else of yours is touched.
Separate, private channels
Each party's tape reaches ROSA in its own channel: a funder's copy comes from the funder or, where the funder agrees, from the lender on its behalf. No party ever sees another party's feed. Reports return the same way: one report per party, delivered to that party's own private folder and nowhere else.
Reports scoped to their recipient
ROSA will not share one funder's loan details or reports with another. A funder's report covers that funder's own funding line. Where a finding involves another funder, the other party's identity is withheld from the page itself unless the parties have agreed otherwise. The scoping happens when the report is built, so the document each recipient holds contains only what that recipient is entitled to see. There is no shared portal to misconfigure.
Verifiable, reproducible evidence
Every tape is hashed with SHA-256 when it arrives, and every report carries its own report id, the engine version and the evidence hash on the page. Underlying evidence is archived rather than bundled into the report. Any report can be checked against the archive, and any cycle can be reproduced from what each party submitted. You can see this on the specimen report.
Sign-in, storage and certifications
Portal sign-in needs a second factor for every user, and automated transfers use SFTP with a credential issued to each institution. ROSA's own operator access sits behind multi-factor sign-in and takes no customer traffic. Loan tapes, findings and reports are stored in London, and the evidence archive's recovery copy is in Ireland. The infrastructure is certified by its suppliers: the file exchange to SOC 2 Type II, and AWS to ISO 27001 and SOC 2. ROSA itself has Cyber Essentials on its roadmap.
If something goes wrong
We tell every affected customer within 24 hours of confirming a security incident that affects its data, and follow with a written account within 72 hours: what happened, what was affected and what is being done. Professional indemnity and cyber insurance stand behind the service, with certificates on request.
This website
rosaverified.com is a set of static pages served over HTTPS. It has no accounts, no database, no cookies and no tracking scripts. See the privacy notice.
An honest note
ROSA is a young firm. This page describes what is true today and claims no certification we do not hold. If your due diligence needs more depth than this page gives you, ask us directly: hello@rosaverified.com.