LEGAL
Privacy Policy
1. Overview
Sentiqra ("we", "us", "our") operates a semantic-analysis API platform at sentiqra.tech, providing structured text analysis for safety, security, risk, market, and customer workflows. This privacy policy explains what data we collect, how we use it, and the choices you have.
We are committed to GDPR and CCPA compliance. We do not sell your data. We do not use your content for model training.
2. Data We Collect
2.1 Account Data
- Name, email, password - required to create an account
- Organization details - optional, for billing and invoicing
- Payment information - processed by Stripe and PayPal; we do not store card numbers
2.2 API Usage Data
- API request metadata - request ID, timestamp, response status, latency, API key ID, analyzer(s) called, configuration ID, and source IP address (security/audit signal). Retained on the fixed audit-log schedule (see Section 4)
- Detection results - we return detection results to you; individual signal results are not stored. Only aggregate counters are derived from them before the response is sent, apart from the bounded idempotency replay copy and webhook delivery payloads described in Section 4
- Content you submit - processed in memory on our EU-hosted infrastructure and not persisted. To perform the analysis it is transmitted to our US processing subprocessor solely for that computation; the text is not used for any other purpose (see Sections 8 and 9)
2.3 Analytics Data
- Page views and CTA clicks - tracked via our first-party analytics on the marketing site
- Session identifier - a random, per-session ID; no third-party cookies
- User agent hash - classification fingerprint of User-Agent string; the raw string is not stored
- Evaluation milestones - for signed-in accounts, we record the first time evidence-backed activation steps complete (email verified, first real API request, configuration pinned, receipt verified, evaluation completed, production integration). These records contain only the stage name and timestamp - never submitted text, API secrets, case identifiers, or per-signal results. Optional feedback you submit about evaluation barriers is stored with your account
Analytics tracking only occurs after you accept our cookie consent banner. You can decline analytics tracking at any time.
3. How We Use Your Data
- To provide and improve the Sentiqra API service
- To process payments and issue invoices
- To send service notifications (security alerts, billing notices)
- To understand how visitors use our marketing site (analytics)
- To comply with legal obligations
We do not:
- Sell your data to third parties
- Use your submitted content for model training - see the commitment and the controls that enforce it
- Share your data with advertising networks
4. Data Retention
Sentiqra distinguishes the data classes below. Submitted content and individual signal results are processed in memory and are not persisted. Only aggregate counters and operational metadata are stored.
- Account data - retained while your account is active; deleted within 30 days of account closure. Request metadata associated with a closed account is deleted on the same 30-day schedule regardless of plan tier
| 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.
5. Data Security
- API keys are stored as HMAC hashes; the plaintext key is shown once at creation
- All API traffic is encrypted via TLS 1.2+
- Database connections use TLS
- Access to production data is restricted and logged
- Regular security audits and dependency scanning
6. Your Rights
6.1 GDPR (EU/EEA/UK)
- Right to access your personal data
- Right to rectification of inaccurate data
- Right to erasure ("right to be forgotten")
- Right to data portability
- Right to object to processing
- Right to withdraw consent at any time
6.2 CCPA (California)
- Right to know what personal information we collect
- Right to delete your personal information
- Right to opt-out of the sale of personal information (we do not sell data)
- Right to non-discrimination for exercising your rights
6.3 Breach notification (GDPR Art. 33)
When acting as a processor, Sentiqra will notify the customer (as controller) without undue delay after becoming aware of a personal-data breach affecting processing performed on the customer's behalf. This is our obligation under GDPR Article 33(2) - the separate 72-hour provision in Article 33(1) governs the controller's notification to the supervisory authority and is not our notification window. Further information will be provided as it becomes available. Our internal target is a preliminary notice within 24 hours of confirmed awareness - that target exists to support your own notification duties, not as permission to wait. Because submitted content is not persisted, breach exposure is limited to the retained metadata classes in Section 4 rather than a stored content corpus.
6.4 Data Processing Agreement
The published Data Processing Agreement (v2.0) applies to every customer relationship in which Sentiqra acts as a processor - no separate signature or Enterprise plan is required. Acceptance is recorded at signup with the applicable version. Customers needing a countersigned copy for procurement can request one at legal@sentiqra.tech. EU/EEA transfers rely on EU Standard Contractual Clauses; UK transfers use the UK Addendum or IDTA as applicable (see Section 9).
To exercise any of these rights, contact us at privacy@sentiqra.tech.
7. Cookies & consent
We use only first-party, essential cookies for session management and authentication (__Host-sentiqra-session, XSRF-TOKEN). Analytics uses no cookies at all - it sends events via the Beacon API with an ephemeral, in-memory session identifier that is discarded when the page closes. Your consent choice itself is stored in localStorage (sq_cookie_consent) so we can honor it. The full storage inventory is on the Cookie Policy.
Controlling analytics: the consent banner offers Accept analytics, Reject analytics, and Manage preferences. To withdraw at any time, open Cookie Settings in the site footer and choose Reject - analytics stops immediately, no events are sent after withdrawal, and your login session and other essential storage are not affected. You do not need to clear browser storage manually.
Server-side security telemetry (rate-limit and abuse-detection counters) is separate from analytics, is not governed by the consent banner, and exists solely to protect the service - see Section 4.
8. Third-Party Services
- Contabo - dedicated hosting (all compute, database, cache) in Germany (privacy policy)
- Third-party inference provider - receives the text you submit for transient processing only, during the request, never your account data; vendor identity and terms are disclosed under NDA in the security package (contact privacy@sentiqra.tech)
- Amazon Web Services (S3) - encrypted object storage for backups, eu-central-1 (privacy policy)
- Stripe - payment processing (privacy policy)
- PayPal - payment processing (privacy policy)
- Google - optional sign-in with Google (account identity on authentication) and delivery of contact-form email (privacy policy)
- GitHub - optional sign-in with GitHub (account identity on authentication) (privacy policy)
We do not share your submitted content with these services beyond what is necessary to process your API request. The canonical list - with each provider's region, data categories, retention, and transfer mechanism - is on the Subprocessors page (also mirrored in the Trust Center).
9. International Transfers
Your account data is hosted on our EU infrastructure (Germany) - this is hosting location, not a claim of EU-only processing. Submitted text is transmitted to our US inference subprocessor for transient processing during the request; encrypted backups are stored on AWS S3 (eu-central-1); payment processors and optional OAuth sign-in providers are global US entities. Transfers from the EU/EEA rely on EU Standard Contractual Clauses (SCCs, 2021/914) or an adequacy decision; UK transfers are covered by the UK Addendum to the EU SCCs or the IDTA as applicable - EU SCCs alone are not assumed to cover UK transfers. An EU data residency option covering submitted-content processing is on our roadmap - see the Trust Center.
10. Contact
For privacy questions or requests, contact privacy@sentiqra.tech.
11. Changes to This Policy
We may update this policy from time to time. We will notify you of material changes via email or a notice on our website. The "Last updated" date above reflects the most recent revision.