Security

Our commitment to protecting your data

Overview

SchemaShield is designed to minimize data exposure by default. We ensure valid, schema‑conformant outputs while keeping your prompts and outputs ephemeral unless you explicitly opt in to persistence.

Data Handling

• Zero‑Persistence (default): We process prompts/outputs in memory and do not write them to disk by default.
• Optional persist=true: When enabled for debugging, we store minimal request/response artifacts; default retention is 30 days, after which logs are deleted.
• BYO Provider Keys: API keys are provided per request and are not stored by default. Keys are used only to service the request and then discarded.
• PII‑scrub Logs: If logging is enabled, redaction rules sanitize common PII patterns before storage.

Transport & Storage Security

• TLS for all network communication; HSTS enabled.
• Least‑privilege access and audit for production systems.
• Secrets managed via environment variables and access‑controlled CI/CD.

Infrastructure

We host on Vercel and compatible cloud providers. Payments are processed by Stripe. Transactional email is sent via Resend.

Sub‑processors

• Vercel (hosting, web analytics)
• Stripe (billing)
• Resend (email)
• LLM providers you choose (e.g., OpenAI, Anthropic)

Availability & DR

We monitor performance and error rates and roll out changes via staged deploys. Critical configuration is version‑controlled. Optional persisted logs and entitlements are backed by provider‑managed durability guarantees.

Responsible Disclosure

If you believe you’ve found a vulnerability, please email security@schemashield.ai. We operate a good‑faith safe‑harbor policy: do not access or modify data that is not yours, avoid service disruption, and give us reasonable time to remediate before public disclosure.

Compliance

We follow industry best practices appropriate for an early‑stage service. Formal certifications (e.g., SOC 2) are on our roadmap. Contact us for security questionnaires.