Security for a journal app isn't a feature list; it's a posture. Here is ours, plainly.
Encryption
All traffic between you and SandDune runs over HTTPS (TLS), and your data is stored with industry-standard encryption at rest by our infrastructure providers.
Per-user isolation
Your notes are isolated to your account at the database layer — access policies are enforced per-user on every table, not just in application code. Files in storage are keyed to your account with unique, unguessable identifiers, and AI processing records live in private storage that is never publicly accessible.
Your account is the front door
SandDune's protections all sit behind your login, which makes your password the part we can't do for you:
- Use a password manager and a unique password (the 8+/upper/lower/number/symbol requirement is a floor, not a target).
- Your email account can reset your SandDune password — securing that email account (ideally with two-factor authentication) effectively secures your journal.
- On shared devices, log out; sessions persist on a device once logged in.
The rest of the posture
- Payments: processed entirely by our payment processor — full payment details never touch our servers.
- Rate limiting protects the service (and your quota) from abuse.
- Minimal surface: no public profiles, no sharing links to notes, no third-party app integrations — a small attack surface is a quiet security feature of its own.
Reporting a vulnerability
If you believe you've found a security issue, please email support@sanddune.ai with details. We read every report and respond to genuine findings.