​
Data Classification & Storage

Antei classifies all incoming data across integrations, uploads, and APIs into structured categories. This enables consistent handling, secure storage, and proper routing across internal services.

​
Data Classification Model

Each field in the platform is tagged with metadata to guide its treatment across ingestion, mapping, validation, and downstream usage.

ClassificationDescription
Core IdentifierFields required to uniquely identify entities (e.g. contact_id, txn_id)
JurisdictionalFields that impact region-specific logic (e.g. country, state, tax_id)
FinancialMonetary fields like amount, tax, currency, exchange_rate
DerivedComputed or post-processed fields (e.g. reverse_charge_applied)
SensitivePersonally identifiable or regulatory-sensitive (e.g. email, ip_address)
Audit MetadataSync metadata such as source, sync_time, extracted_id, mapping_tag

Each record (invoice, transaction, product, contact) is processed using these classifications.

​
Storage Architecture

Antei uses a layered storage model based on data sensitivity and processing stage:

LayerDescription
Ingestion LayerTemporary staging of raw integration payloads (used during transformation)
Validation LayerIntermediate storage for normalized and enriched records
Primary DatabaseSystem-of-record for validated data, powered by Xano
Document StoreFile storage (e.g. invoices, registrations) managed via Cloudflare R2
Logs & MetadataProcess logs and metadata maintained through Railway and Render

📌 Sensitive documents (e.g. tax notices) are never stored in plaintext. Access is scoped and logged.

​
Regional Data Residency

PII and jurisdictional data is stored based on the customer’s region:

Client RegionData Residency LocationScope of Application
EU CustomersEU serversAll sensitive fields + Vault + logs
India CustomersIND serversPII, transaction metadata, file uploads
Other ClientsUS (Global server)Default server unless region-specific setup exists
  • PII is regionally hosted; generalized data (e.g. classification metadata) may reside in USA
  • All traffic is encrypted and scoped with access controls
  • Region assignment is configurable at org level

​
Encryption & Access Control

LayerProtection Applied
At RestAES-256 / Cloud provider encryption (PostgreSQL, R2)
In TransitHTTPS (TLS 1.2+) with forced SSL enforcement
Access ControlToken-based access, scoped per user and org, with audit logs
Field-levelSensitive fields excluded from logs and stored encrypted if required

​
Field Metadata Example

Every mapped field carries classification and sync metadata. For example:

{
  "field": "invoice_total_amount",
  "source": "stripe_invoice.total",
  "extracted_id": "abc123",
  "isSensitive": false,
  "classification": "financial",
  "mappingVersion": "v1.3"
}

​
Retention Defaults

Data TypeRetention PeriodNotes
Core Transaction DataPersistentStored indefinitely for audit and compliance
Validation Logs90 daysAuto-deleted unless marked as critical
Uploaded Files12 monthsCleaned periodically unless retained manually
Audit Logs180 daysVisible under Org Settings → Audit Trail

Retention can be customized for enterprise clients upon request.

​
Next Steps

​
Questions?

Need help with data classification and storage?
Email support@antei.com