HridaSpro Docs

Privacy

Data Handling

What Spro collects, what it stores, and what it never does — in plain terms.

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:

FieldPurpose
TimestampAudit and debugging
Model & providerUsage tracking
Token countsBilling and cost analytics
LatencyPerformance monitoring
HTTP status codeReliability and debugging
Guardrail violation metadataSecurity 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:

ControlEffect
Zero Data RetentionRequest/response content is not retained — see ZDR
Anonymize LogsPII, PHI, and other sensitive values masked before logs are stored — masking is irreversible
Use for Model TrainingOff by default. When enabled, anonymized interaction data may improve Spro's detection models
Log RequestsOff to disable request history entirely

Security Standards

StageStandard
Data in transitTLS 1.2 minimum, TLS 1.3 preferred
Data at restAES-256 encryption
API keys and secretsEncrypted at rest, never logged in plain text
Internal accessLogged 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