Effective Date: March 1, 2026 | Last Updated: March 18, 2026
Your documents never leave your device. This is not a feature — it is the architectural foundation of Arkova. Document fingerprinting (SHA-256) runs entirely in your browser using the Web Crypto API. We never receive, store, process, or have access to your original files.
Document fingerprints: A one-way cryptographic hash (SHA-256) of your file. This cannot be reversed to reconstruct the original document.
Account information: Email address, name, and organization name when you create an account.
Credential metadata: Issuer name, credential type, issue/expiry dates, and field labels — never raw document text or PII.
Usage data: Page views, feature usage, and API call counts for service improvement.
When AI-powered extraction is enabled, only PII-stripped structured metadata (credential type, issuer, dates, field labels) may be sent to our servers for processing. Client-side PII stripping removes all personally identifiable information before anything leaves your browser. Raw OCR text and document bytes are never transmitted.
All data is encrypted in transit (TLS 1.3) and at rest. Database access is enforced through Row Level Security (RLS) — every table has mandatory tenant isolation. API keys are hashed with HMAC-SHA256. Audit events are logged to an append-only, PII-scrubbed audit trail.
You may request deletion of your account and all associated data at any time. We support GDPR right-to-erasure, including anonymization of audit log entries. Contact hello@arkova.ai to exercise your rights.
Credential verification is public by design. Anyone with a verification link or QR code can confirm a document's status and timestamp. No account is required. Only the credential's public ID and non-sensitive metadata are exposed — never the document itself or the holder's personal information.
For privacy inquiries: hello@arkova.ai
Arkova Technologies, Inc.