7 Moments Where Your Platform Is Losing Revenue
Read the article
Technical Documentation

Security, Privacy & Compliance

inncivio is built for regulated financial platforms. Data is anonymized before it leaves the user's browser, encrypted twice in transit, and stored in a database instance and under an encryption key that belong to one client only. inncivio is SOC 2 Type II certified.

Anonymized at source

  • What inncivio receives: anonymized footprints and journeys, such as click paths, views, hovers, help opens, order-ticket steps and idle time.
  • What inncivio never receives: names, e-mail addresses, identifiers, typed values, quantities, prices or account numbers.
  • Re-identification stays with you: only you can link a journey back to a user, in your own environment. inncivio never holds that link.
  • Signals that need account data, such as exposure mismatch, are resolved on your side.

Encryption

Protection layerStandard
Requests in transitAES-256-GCM, with a unique per-request key wrapped with RSA-2048 (OAEP, SHA-256)
Responses in transitAES-256-GCM, same per-request key, fresh IV
TransportHTTPS / TLS 1.2+ with HSTS
Server-to-server APIHTTPS / TLS 1.2+ with token authentication, expiry and rotation
Data at restAES-256 via AWS KMS, one dedicated key per client
Console accessBcrypt-hashed passwords, signed time-limited tokens (HMAC-SHA256), 2FA available

The capture script uses the browser's native Web Crypto API and holds only a public key. If encryption fails, nothing is sent.

Tenant isolation

  • Each client runs on a dedicated database instance on AWS, with VPC isolation and IAM-controlled access.
  • Each client's data is encrypted under its own AWS KMS key, which also covers backups, snapshots and replicas.
  • No raw client data crosses tenant boundaries. Only aggregated, anonymized learning signals improve inncivio's models.

Proprietary, self-hosted AI

All models, including the language model, are trained and hosted in inncivio's own AWS infrastructure. No journey data, signal or action is sent to a third-party AI service.

A non-invasive layer

The in-app layer runs client-side only and overlays interventions without modifying your application code or backend logic. It is compatible with strict Content Security Policies that allow *.inncivio.com only.

Auditability

  • Every action stores its decision trace: the signals, the rules applied, and any override or suppression with its reason.
  • Signals dropped by validation are logged with the rule that dropped them.
  • Human review before activation keeps you in control of what reaches your users.
  • Security event logging, anomaly detection and automated alerting.

Compliance and standards

  • SOC 2 Type II certified: security, access and key-management controls are independently audited. View our Trust Center.
  • GDPR: anonymized processing, data minimization, and re-identification kept exclusively with the data controller.
  • Financial conduct: no recommendation, forecast, suitability assessment or urgency language, enforced in code on every action.
  • Aligned with OWASP Top 10, NIST SP 800-38D (AES-GCM) and NIST SP 800-56B (RSA-OAEP).
  • Regular penetration testing and code audits, with automated patch management.

The full inncivio Data Security & Encryption Overview is available on request.

Ready to See inncivio in Action?

Let us show you how our AI-driven, fintech-focused approach delivers more than just adoption - it drives measurable growth.