Security & trust
Formeze remembers the information you choose to save, so it’s built to treat that information as sensitive at every step: encrypted on disk, protected in transit, and never used in ways you didn’t ask for.
Three commitments shape every security decision behind Formeze.
Encrypt by default
Field values aren't stored in plain text. Each one is encrypted with AES-256-GCM — authenticated encryption that also detects tampering — before it's written to storage.
Keep you in control
Autofill is a review loop, not an autopilot. You see what was matched and what needs a second look, and you can export saved account data or delete the account at any time.
Stay in-house
Every part of our AI — from semantic matching to optional AI-assisted formatting — runs on independent models on our own servers. Your saved values are never sent to an outside AI provider, and we never sell or resell your personal data.
The practices
The specifics behind the promise — the encryption, hashing, and access controls that protect your account and your saved data.
Saved field values are encrypted with AES-256-GCM. Every record gets a fresh random initialization vector and an authentication tag, so stored data can't be silently altered.
All traffic between your browser or extension and our servers travels over TLS. Your data is protected on the wire as well as on disk.
Passwords are hashed with bcrypt at cost factor 12 — never stored in plain text. Sign-in uses constant-time checks so attackers can't probe which emails have accounts.
Email verification and password resets use cryptographically random tokens that are single-use and expire after one hour, limiting the window for misuse.
Both semantic matching and optional AI-assisted formatting run on independent models hosted on our own infrastructure. Your saved values are never sent to outside AI providers, and we never sell your data.
Confidence states mark uncertain matches so you can verify them before anything leaves the page, and known sensitive fields — passwords, one-time codes, card numbers — are excluded from capture and fill outright rather than flagged. Formeze fills — you decide what to submit.
Export or delete your account data from settings. Account deletion removes primary database records and queues cleanup for embeddings linked to known stored fields; historical provider-only embeddings fall outside the current automated guarantee.
The encryption key lives apart from the database, and the encrypted format is versioned so keys can be rotated without losing access to existing data.
Questions?
If you have a security question or want to report a vulnerability, we want to hear from you.