How Spro treats your data, in plain terms:
- We don't persist the content of your prompts or model outputs.
- We do keep a metadata log per request — timestamp, model, token counts, latency, HTTP status code — for billing, security, and debugging.
- We never sell your data.
For the complete legally-binding policy, see our Privacy Policy.
The Details
Prompt & Response Content
Spro's guardrail engine processes your request and response text in memory to perform detection and analysis. For most guardrails:
- Text is processed in an isolated, stateless pipeline
- No prompt content is written to disk during guardrail evaluation
- Results are returned in memory and only metadata is persisted
For ML-based guardrails (harassment, toxicity, hallucination detection), text is passed to Spro's inference models hosted on the same infrastructure. No third-party inference providers are used.
Metadata Logs
Per request, Spro keeps a metadata record:
| Field | Purpose |
|---|---|
| Timestamp | Audit and debugging |
| Model & provider | Usage tracking |
| Token counts | Billing and cost analytics |
| Latency | Performance monitoring |
| HTTP status code | Reliability and debugging |
| Guardrail violation metadata | Security monitoring |
What Spro Never Collects
- Your provider API keys in plain text — with BYOK, keys are encrypted at rest and only used to authenticate upstream requests
- User identity or authentication data from your application
- Any data outside your configured project endpoints
Optional Controls
Projects can enable additional data-handling controls under Settings → Data & Privacy — see Workspaces:
| Control | Effect |
|---|---|
| Zero Data Retention | Request/response content is not retained — see ZDR |
| Anonymize Logs | PII, PHI, and other sensitive values masked before logs are stored — masking is irreversible |
| Use for Model Training | Off by default. When enabled, anonymized interaction data may improve Spro's detection models |
| Log Requests | Off to disable request history entirely |
Security Standards
| Stage | Standard |
|---|---|
| Data in transit | TLS 1.2 minimum, TLS 1.3 preferred |
| Data at rest | AES-256 encryption |
| API keys and secrets | Encrypted at rest, never logged in plain text |
| Internal access | Logged and audited |
Spro's practices are designed to support GDPR and HIPAA compliance, with SOC 2 in progress.
Responsible Disclosure
If you discover a security vulnerability in Spro, report it to hello@hridaai.com. We take all reports seriously and respond promptly. Please do not publicly disclose vulnerabilities before giving us a reasonable opportunity to address them.
What's Next
- Zero Data Retention — Workspace-level ZDR
- BYOK — Your own provider keys
- Zero Data Retention — Content never stored
- FAQs — Common questions about data and security
