Security
Built for the data you are trusted with.
A mortgage advisor holds some of the most sensitive information a family has. WealthLens was designed so that most of it never reaches us in the first place, and the rest is locked to the advisor who owns it.
How we protect it
Six things that are true today
No Social Security numbers. No dates of birth.
WealthLens does not ask for them and does not store them. The loan-file parser runs in your browser and never reads Social Security numbers, dates of birth, employer names or bank account numbers, so they never reach us. The contact details and financials you import are stored in your account.
Documents are scrubbed before any AI reads them.
When a document is read for you, identifiers such as Social Security numbers, emails, phone numbers, dates of birth and street addresses are removed from the extracted text before it reaches a model.
Your data never trains an AI model.
We use Anthropic and Google under commercial terms that exclude training on customer inputs. Each AI call is logged with a redacted copy of what was sent, so there is a record.
Each advisor sees only their own files.
Advisor-to-advisor isolation is enforced in the database with row-level security policies, not just in the app. The one exception is a narrow, read-only support view, described below.
Documents go straight to encrypted storage.
Uploads go from your browser straight to an encrypted bucket over a signed link that expires in five minutes.
Encrypted in transit and at rest.
Every connection uses HTTPS. The database and the document store encrypt data at rest. Card payments are handled by Stripe, so card numbers never touch WealthLens.
Independent assessment
Reviewed by an outside firm
In May and June 2026, Cyber Analytical Solutions, an independent cybersecurity firm, assessed the live WealthLens platform: API security testing against production, a review of every row-level security policy in the database, a read-only review of the source code and build pipeline, and a review of the cloud infrastructure. All testing was read-only and non-destructive.
We remediated its findings. A letter of attestation from the assessing firm is available on request.
Request the security briefInfrastructure
What WealthLens is built on
We do not run our own servers. Every layer sits on a provider whose controls are audited independently, and whose attestations are available directly from them.
| Provider | Role | Assurance |
|---|---|---|
| Supabase | Database, authentication, serverless functions | SOC 2 Type II |
| Amazon Web Services | Document storage, OCR, hosting (US East) | SOC 2 Type II |
| Stripe | Payments and card storage | PCI DSS Level 1 |
| Anthropic and Google | AI models | No training on customer data |
The SOC 2 and PCI attestations above belong to the providers named, and the AI line is a contract term. WealthLens itself has not completed a SOC 2 audit. If your organization requires one, tell us and we will say plainly where we are.
Plain answers
The questions a reviewer asks
Who at WealthLens can see my client files?
Support staff can open an advisor account in a read-only view to help with a problem. Nothing can be edited from that view. It exists for support and nothing else.
Can my client see anything beyond their own file?
No. A client link opens one file. It does not reveal your other clients, your pipeline or your account. You can turn any link off at any time.
Where is the data stored?
In the United States, on Supabase and Amazon Web Services infrastructure in the US East region.
Can I delete my data?
Yes. You can delete any client file yourself, and you can ask us to delete your account and your client files. A redacted log of AI calls is kept for 24 months.
What about passwords and sign-in?
The sign-up form requires at least twelve characters and scores every password with a strength meter. Sessions use short-lived tokens issued by Supabase Auth.
Is the MISMO import certified?
It is compatible with the MISMO 3.4 file format that every major loan origination system exports. We do not claim MISMO certification, and we do not need your LOS credentials to read a file.
Want the full picture?
The long-form Data Security and PII Protection page walks through the upload pipeline, the redaction layer and the AI call log step by step. It is written for the person on your team who has to sign off.
