We are currently building something exciting and will be launching soon. Registration is temporarily closed. Launching soon — registration temporarily closed.

Trust Center

Security & Compliance

Our commitment to protecting submitted content. Transparency about our practices, subprocessors, and compliance roadmap.

Compliance Status

GDPR

Self-assessed compliant

Self-assessed via internal legal review. Our status: an Art. 28 DPA published and accepted at signup, a published subprocessor list with transfer mechanisms, a retention schedule, and the security controls below. GDPR certification mechanisms exist under Art. 42/43 - we have not pursued certification. Independent assurance for the control environment is in progress under the SOC 2 Type II program.

Scope: Account data and submitted-content processing across the Sentiqra API and portal

Basis: Internal legal review. DPA under Art. 28 available on request; EU/EEA/UK transfers use Standard Contractual Clauses.

Last reviewed: September 2026

CCPA

Self-assessed compliant

Self-assessed via internal legal review - the verifiable evidence is the published privacy policy, data-rights process, retention schedule, and subprocessor list on this page and the legal hub.

Scope: California-resident personal information handled by the Sentiqra API and portal

Basis: Internal legal review. We do not sell or share personal information for cross-context behavioral advertising.

Last reviewed: September 2026

SOC 2 Type II

In Progress

SOC 2 Type II program in progress - not yet audited. We removed the previous target date rather than keep a stale promise on the page; contact us for the current program status and available attestations.

Last reviewed: September 2026

ISO 27001

Planned

In gap analysis - not yet audited. No committed certification date until the gap analysis completes.

Last reviewed: September 2026

Every claim on this page carries a review date. If any look stale, ask us - we'd rather tell you the real status than leave an expired promise up.

Security Practices

Encryption in transit

TLS 1.2+

All API and portal traffic encrypted in transit.

Encryption at rest

AES-256

Database and storage encrypted at rest.

API key storage

HMAC hashed

Keys stored as one-way hashes; plaintext shown once.

Audit logging

All admin actions

Administrative actions logged for review.

Dependency scanning

Continuous

Automated vulnerability scanning in CI.

Abuse & extraction monitoring

Continuous

We monitor automated abuse and attempts to replicate service functionality. Depending on the circumstances, controls may restrict, throttle, or suspend access. Customers can contact support to resolve legitimate evaluation or capacity issues.

Access Control

RBAC + scoped MFA

Role-based access control with owner, admin, developer, billing, and read-only roles. Self-service two-factor enrollment with recovery codes, optional organization-enforced MFA, and mandatory 2FA for privileged staff access.

Data Handling

Content Storage

Sentiqra distinguishes content (your submitted text and the analytical signals returned to you) from operational metadata (data needed to run the service, bill accurately, and maintain security). Submitted content is processed in memory and not persisted; individual signal results are not stored outside the bounded exceptions below — the 24-hour idempotency replay record and webhook delivery payloads redacted within 7 days of terminal delivery. The response fingerprint is returned in the receipt and is never indexed or stored as a queryable operational field; its only server-side copy lives inside the bounded idempotency replay record when a key is supplied. Only aggregate counters and operational metadata are stored beyond that window. This policy covers the analysis API processing path; account details, support correspondence, billing records, and consented feedback are stored deliberately under separate retention schedules.

No Training on Submitted Content

We do not use submitted API content to train or improve detection models. Our processing and retention controls are designed to enforce this commitment. The data-handling policy describes retained metadata, subprocessors, and available assurance evidence.

Retention Policy

Data class Retention period Purpose
Submitted content Not retained —
Signal-level results Not retained Not written to operational stores — the only copies are the bounded exceptions in this schedule: the 24-hour idempotency replay response and webhook delivery payloads you configure
Analysis result fingerprint Not retained as a queryable field Returned in the response receipt for your own verification — never indexed or stored as an operational field. A stored unkeyed result digest would allow candidate-output inference against common results. The only server-side copy is inside the bounded 24-hour idempotency replay record when you supply an Idempotency-Key (see that class); verification itself is a read-only recomputation.
Webhook delivery payloads Until delivery ends, then ≤7 days Delivered to customer-configured endpoints only; the derived-output payload (signals/indicators) is redacted after the delivery lifecycle while the delivery record is kept
Request & operational metadata 30-90 days Billing, abuse prevention, security, reliability, receipt verification. Per-request usage metadata is swept at 90 days; the security request-audit log is swept at 30 days. Longer windows may be agreed contractually
Abuse-detection telemetry 48 hours Anti-extraction & automated-abuse prevention. Non-content request fingerprints, response-code counters, connection signals - never submitted text
Idempotency records 24 hours Safe-retry deduplication. Holds the key, a keyed request hash, per-analyzer outcomes, and the stored response for identical replays - submitted text is never included
Aggregated analytics 12 months Usage analytics, Detection Insights, capacity planning
Audit events 24 months Security, compliance, investigations
Support tickets & correspondence 24 months Support history, dispute resolution, abuse investigation. Stored in the portal (not the analysis path) - keep secrets and customer-submitted text out of ticket bodies
Billing records & invoices 7 years Tax compliance (finance/legal)
Compute-metering metadata 13 months Per-run infrastructure cost metering (key id, analyzer, outcome, latency, configuration alias — never submitted content). Finance reconciliation and capacity planning

Request metadata never includes submitted text or individual signal results — it is the operational envelope around the request: the fields needed to verify a receipt, reconcile usage, or investigate an incident. Retention bounds are the same on every plan: the request audit log is swept at 30 days and per-request usage metadata at 90 days. Longer metadata windows are agreed contractually (Enterprise) and recorded in the customer's agreement.

Data Deletion

Account data deleted within 30 days of account closure. Contact privacy@sentiqra.tech for data deletion requests.

Controls & Evidence

Each published control statement has an internal owner and evidence security can produce during a review.

Submitted API content is not used to train or improve detection models

Owner: Backend engineering · Evidence: Request-path data-flow documentation, dataset provenance records, code review of the analysis path

Submitted text is not persisted after the response completes

Owner: Backend engineering · Evidence: Automated retention tests, storage-schema review (no content columns), logging configuration

Only operational metadata is retained, on a published schedule

Owner: Security · Evidence: Retention schedule in the API contract registry, scheduled cleanup jobs, access-permission review

Subprocessors receive only what is needed to process the request

Owner: Legal · Evidence: Subprocessor terms (DPA/SCCs) and the published subprocessor list below

Public Policies & Verification

Verify Reproducible Output Data Handling Policy No-Training Commitment & Controls

Subprocessors

EU application hosting is not EU-only processing - submitted text is processed transiently in the US, backups stay in the EU, and payment/OAuth/support involve their respective providers. Full detail on the subprocessors page.

Legal entity Purpose Region Data categories Transfer mechanism Privacy Policy
Contabo GmbH Dedicated infrastructure - application compute, database, and cache hosting Germany (EU) Account data, operational metadata, support correspondence, billing records - whatever the hosted systems store None required - processing stays in the EU View
Third-party inference provider (disclosed under NDA) Submitted-text analysis - transient computation during the request only United States Submitted text only - during the request; no account, billing, or payment data EU SCCs (2021/914); UK transfers covered by the UK Addendum or IDTA as applicable View
Amazon Web Services (S3) Encrypted object storage for backups - disaster recovery only, not live processing eu-central-1 (Germany, EU) Encrypted backups of portal and API databases - may include account and billing records EU storage region; EU SCCs cover any third-country support access View
Stripe Payment processing - card payments, invoices, billing lifecycle Global (US entity) Billing data - payer name, email, payment method tokenization, transaction records EU SCCs (2021/914); UK Addendum/IDTA as applicable View
PayPal Payment processing - PayPal payments and billing lifecycle Global (US entity) Billing data - payer name, email, transaction records EU SCCs (2021/914); UK Addendum/IDTA as applicable View
Google Sign-in with Google (optional OAuth) and delivery of contact-form/support email (Google Workspace) Global (US entity) Account identity (name, email, avatar) when you choose Google sign-in; contact-form submissions (name, email, message) EU SCCs (2021/914); UK Addendum/IDTA as applicable View
GitHub Sign in with GitHub (optional OAuth) Global (US entity) Account identity (name, email, avatar) when you choose GitHub sign-in EU SCCs (2021/914); UK Addendum/IDTA as applicable View

Compliance Roadmap

Completed

  • Public status page
  • Unified REST API contract
  • Webhook signature verification
  • Verification receipts for every classification

In progress

  • SOC 2 Type II program
  • ISO 27001 gap analysis
  • EU data residency option

Planned

  • ISO 27001 certification
  • Batch API
  • SCIM provisioning

More Resources

Privacy Policy

How we handle personal data

Legal Disclaimer

Benchmark methodology & claims

Benchmark Results

Per-language Top-3 Hit Rate

vs LLM Moderation

Sentiqra vs Perspective, GPT-4o

Pricing

From Free to Enterprise

Quickstart Guide

First API call in under 5 minutes

API Reference

Full endpoint, parameter, and response docs

Contact

Talk to Solutions Engineering

Need a DPA or security review?

For data processing agreements, security questionnaires, or enterprise security reviews, contact our team.

Independent-review scopes, dates, and limitations: /security/assurance.

security@sentiqra.tech