About AKRIBBA.

• Read-only by default. We ingest a copy of payout events; your systems of record stay untouched.
• Minimal PII by design. We work in integer minor-units and pseudonymous IDs; personal data is optional and best kept inside your perimeter.
• We never see raw data. Verification runs on sealed inputs and emits proofs — not the underlying sensitive values.
• Raw mirrors aren’t retained. Event copies used for a window aren’t kept by default; only the transcript and digest persist.
• Purpose-limited. Data is used only to compute outcomes, generate transcripts, and produce audit artifacts under your policy.
• Differential privacy option. Where aggregates are shared, noise protects any single record — even if every other value is known.

• Encrypted everywhere. AES-256 at rest, TLS 1.3 in transit, mTLS between services.
• Signed & sealed. JWS (ES256) over payloads; content-addressed transcripts with a digest that must replay exactly.
• Keys & secrets. KMS-managed keys, scheduled rotation, short-lived scoped tokens; customer-managed keys (BYOK) optional.
• Least privilege. SSO/SAML, MFA and role-based access; every administrative action is logged.
• Tamper-evident records. Immutable, append-only audit logs; WORM object-lock for transcripts.
• PII isolation. Any personal data lives in separate encrypted stores under a separate key hierarchy.
• Configurable retention. Transcript retention is yours to set — typically 6–24 months.
• Erasure built in. Customer-initiated erasure is supported per principal or per window.

Request data erasure →

• GDPR. Minimal PII by design; where used, differential privacy provides the “appropriate safeguards” contemplated by Article 89.
• CCPA. The proofs we emit don’t constitute personal information.
• DPA & SCCs. You are the Controller; AKRIBBA is a read-only Processor. A Data Processing Addendum with Standard Contractual Clauses is available.
• Data residency. US/EU regions by default, with in-country or self-hosted options; no cross-region movement without your consent.
• Subprocessors. Kept in a living DPA appendix, each evaluated for security posture and least-data scope, with change notices.
• SOC 2 & ISO. SOC-Lite at pilot, then SOC 2 Type 1 and Type 2 on a published roadmap; ISO 27001 planned.
• PCI alignment. We store and process no card numbers (PANs); PCI intersections are documented.
• Incident response. Initial notice within 24 hours; a written post-mortem within five business days.