Trust
Security
You are handing us your clients' names and home addresses. Here is exactly what protects them today, and what does not exist yet.
Last updated July 27, 2026
What protects your data today
Encryption everywhere. All traffic to LetterFi runs over TLS. Data is encrypted at rest in our database and file storage.
Row-level isolation. Every table in our database enforces PostgreSQL row-level security. Access is scoped to the authenticated account at the database layer, not merely hidden in the interface, so a query can only ever return your own rows. Your contacts, letters, and handwriting are invisible to other customers by construction.
Authentication. Accounts are managed by Supabase Auth. Passwords are salted and hashed; we never store or see them in plain text. Sessions are held in HTTP-only cookies and refreshed server-side on every request.
Least-privilege server access. Elevated database credentials are confined to server-side code and are never exposed to the browser. Privileged operations verify the signed-in user and confirm ownership of the records involved before they run.
No card data. We do not store payment card numbers anywhere.
U.S. infrastructure and production. Our application, our data, and our writing machines are all in the United States. Letters are produced in a controlled facility, and the production hardware is not exposed directly to the public internet.
Your handwriting stays yours. Handwriting samples are used only to produce your own letters. They are never shared with other customers, sold, licensed, or used to train models.
What we do not claim
We would rather tell you this up front than have you find out in a due-diligence questionnaire.
We do not hold a SOC 2 Type II report. No LetterFi materials should be read as asserting one. If your firm requires a SOC 2 report from vendors today, we are not yet a fit.
We are not a compliance or archiving system. We do not currently provide books-and-records retention, supervisory pre-approval workflows, or archive export designed to satisfy SEC Rule 17a-4, FINRA Rule 4511, or equivalent state rules. Your firm remains responsible for capturing and retaining its own correspondence records.
We do not review your letters. Nothing in LetterFi should be relied on as a supervisory control over the content you send.
On our roadmap
These are planned, not shipped. We will move each one into the section above only when it is genuinely in production, and we are not putting dates on them here.
- Retention and archive export: durable copies of every letter sent, exportable in a form your firm can hand to an examiner or feed into an existing archive.
- Supervisory approval workflows: routing letters to a designated principal for review before they are produced.
- Customer-visible audit logs: a readable history of who did what in your account.
- Hardened service authentication: continued tightening of authentication and rate limiting across every internal service endpoint, including those that drive production hardware.
- Role-based access for firms: multiple seats per firm with distinct permissions, plus single sign-on.
- Independent testing: third-party penetration testing and formal SOC 2 readiness work.
What we ask of you
- Use a strong, unique password for your LetterFi account.
- Upload only the recipient data you actually need in order to mail a letter.
- Remove contacts you no longer have a business reason to keep.
- Tell us immediately if you think your account has been accessed by someone else.
Reporting a vulnerability
If you find a security issue, email sales@letterfi.ai with enough detail to reproduce it. We will acknowledge your report, keep you updated while we investigate, and we will not pursue legal action against anyone who reports in good faith, avoids privacy violations and service disruption, and gives us reasonable time to fix the issue before disclosing it.
Related reading: our Privacy Policy covers what we collect and who we share it with.