How Specwarden protects your data
Specwarden is built for design, manufacturing, and quality engineering teams who share sensitive DFMEA data. These are the ten commitments we make about how we handle your information — written for a quality engineer, not a lawyer.
Your files never sit on our servers
We parse your spreadsheet inside the request that uploaded it, then immediately throw away the file. No disk writes, no S3 bucket holding your IP.
We log counts, never your content
Our database stores how many rows you reviewed and how many findings came back — not the cells themselves, never the failure modes or supplier names.
Findings live only in your browser tab
Close the tab and the review is gone. We use the browser's session storage, which clears the moment your tab closes. We don't sync findings to our servers.
Free tier shows 5 findings, paid unlocks all
We never re-charge you on upgrade. The full review runs once. Upgrading just unlocks what was already computed.
Deterministic rules always run, even when AI fails
If our AI reviewer times out or hits an error, you still get every rule-based finding plus a banner explaining what happened. No error page.
AI degradation has a guaranteed floor
Seven deterministic checks (rating ranges, RPN math, required fields, etc.) run before any AI call. Even in the worst Anthropic outage, you get those.
Every request gets an end-to-end ID
If something looks wrong, share the request ID from your error message — we can trace it from your browser through to Anthropic and back.
Quota gates protect you from surprises
We check your plan and quotas before any paid work runs. You'll see a clear upgrade dialog if a file exceeds your tier's row cap — not a surprise bill.
Stripe webhooks can't double-charge
Stripe sometimes replays the same event. Our handler deduplicates by event ID, so a network hiccup never bills you twice.
Secrets never enter our git history
API keys for Anthropic, Clerk, Stripe and Supabase live only in our deployment environment. They're not in our codebase and can't leak through a public repo.
Last reviewed: 2026-05-16