Security and data handling

What data does SafePrompt store?

• Safe prompts: on the free plan, excluded from the intelligence collector. Request metadata and enabled session records are separate. On a paid plan the published intelligence-text retention window is 24 hours while Intelligence Sharing is switched on, which is how an account starts; switch it off in Settings, Privacy and Data Controls to stop intelligence contribution. Session tracking is off, so a session token stores nothing. Request metadata follows its own retention policy.
• Blocked prompts: prompt text and the client IP are collected for network defence under the published 24-hour retention policy.
• Request metadata: timestamp, account id, verdict, threat categories, processing time.
• Account data: email and a hashed password. Billing runs through Stripe and we never store card numbers.
• Attack pattern hashes: cryptographic hashes, pseudonymous rather than anonymous, retained under the 90-day record policy.

How long does SafePrompt keep your data?

An hourly job enforces every window in this table.

Two categories sit outside this table: billing records, kept for seven years because tax law requires it, and usage metrics, which the same hourly job deletes at 90 days. The privacy page carries the full table.

Who else processes your prompts?

SafePrompt pins provider routing in code and versions it in git, so a change is a reviewable code change rather than a silent configuration switch. Since 17 August 2026 your prompt reaches only the companies below. Before that date, routing fallbacks were enabled and a small fraction of requests may have reached other inference providers available through OpenRouter. The privacy page carries the same list plus the email and analytics processors, and records that history too.

• OpenRouter: routing gateway.
• Groq, Crusoe, CoreWeave, Cloudflare, Together AI, DeepInfra: inference providers.
• TypeSafe: an additional safety check, reached through OpenRouter.
• Supabase: database, hosted on AWS.
• Cloudflare Workers: API hosting.
• Cloudflare Pages: frontend delivery.
• Stripe: payments. Stripe never receives prompt content.

Inference providers operate globally and the region for a given request is not pinned. If you need a fixed inference region, tell us before you integrate.

How are your API keys protected?

• Your API key is stored as a hash, so nobody can read it back, including us.
• API traffic runs over TLS; always call the https:// endpoint.
• The database is encrypted at rest with AES-256.
• Every read is scoped to your API key, so one account's records are not reachable from another's. That scoping is enforced in the API and in database row-level security, and it is on the list for the first external test.
• Provider tokens and database credentials are platform-managed secrets and never reach source control. A secret scanner in the deploy pipeline blocks live-format keys before anything ships.

Your data stays yours

• Export: Use dashboard/API export for supported account records; it excludes retained hash records and has record limits. Contact privacy@safeprompt.dev for an access request concerning additional personal data.
• Deletion: Dashboard/API deletion supports selected account records and samples that still hold prompt text or raw IPs. Dashboard/API deletion does not remove retained hash records separately. These records remain pseudonymous personal data under our 90-day retention policy. For a request concerning them, contact privacy@safeprompt.dev. Applicable erasure and objection rights remain subject to legal conditions and exceptions.
• Data Processing Agreement: on request from privacy@safeprompt.dev.
• We never sell your personal information and we never share it for cross-context advertising. The free plan does trade blocked prompts for the service, and the privacy page sets out what that exchange is worth and how to leave it.
• Network intelligence: paid plans can switch off pattern sharing.

How do you report a vulnerability?

Send a security issue to security@safeprompt.dev. We aim to acknowledge within two business days and to give you an initial assessment within ten, and we will credit you in the fix announcement if you want it. If we are going to miss that, we will tell you.

Safe harbour. If you follow the rules below, we will not bring or support legal action against you for your research, and we will say so in writing if anyone asks. Stay within them: test only against your own account and your own data, never another customer's; do not run denial-of-service, spam or social-engineering tests; do not access, copy, keep or publish anyone else's personal data, and stop and tell us the moment you encounter it; do not test our suppliers' systems, because we cannot speak for them; and give us 90 days to fix an issue before publishing, or agree a different date with us.

We cannot waive claims that belong to our customers, and we cannot bind law enforcement. What we can promise is our own conduct, and this is it.

Privacy and DPA requests: privacy@safeprompt.dev. General support: support@safeprompt.dev.

Where we are today

SafePrompt publishes its security posture as it stands, so you can size the risk before you integrate.

• Penetration testing: the first external test is planned once paid usage covers the cost, and no third-party test has run yet. Next review 1 October 2026.
• Compliance evidence: we publish the retention windows, the processors and the controls instead of a badge, and we will answer a security questionnaire directly. SOC 2 is not started, and we review that position quarterly. Next review 1 October 2026.
• Availability: your integration decides what to do when a check cannot complete, block or log and continue, and the API itself fails closed on internal errors. We publish no status page and make no availability commitment, so design your integration with an explicit fallback.
• Benchmark: Current aggregate measurements are published on SafePrompt; dated external per-case results are linked from the benchmarks page. Our own suite is separate from those external datasets. See what SafePrompt covers.
• Key management: provider tokens and database credentials are platform-managed secrets that never reach source control. We run no dedicated hardware security module or external key-management service.
• Access control: production access is limited to a small founding team, and every administrative change to the block and allow lists is logged. A formal periodic access review is not in place yet.