Security
Your invoices reveal your supply chain. We guard them that way.
Commercial invoices, carrier contracts and container flows are competitive information. ATAHSKIA isolates, encrypts and never reuses them.
SOC 2
Type II report
AES-256
Encryption at rest
TLS 1.3
In transit
0
Models trained on customer data
Controls
How the platform is protected.
Isolation
Tenant-isolated financial data
Each customer's invoices and evidence live in a logically isolated tenant with per-tenant encryption context. Cross-tenant queries are blocked at the data layer.
Encryption
256-bit AES at rest, TLS 1.3 in transit
Storage, backups and file uploads are encrypted with AES-256. Keys are managed in a cloud KMS with rotation.
Access
SSO, MFA and role-based access
SAML SSO, enforced MFA and RBAC down to dispute approval rights. Every access and action is logged.
Data use
Zero trade data sharing
No pooling, reselling or model training on customer data. The public Billing Accuracy Index is aggregated and blinded.
Resilience
US hosting with failover
AWS us-east-1 (N. Virginia) with us-west-2 (Oregon) failover. 99.9% uptime SLA on Enterprise plans.
Responsible disclosure
Found something? Tell us.
Report vulnerabilities to security@atahskia.si. Our security.txt is published at /.well-known/security.txt. We acknowledge reports within one business day.
Security FAQ
Where is our data stored?
In AWS us-east-1 (N. Virginia) with us-west-2 (Oregon) failover. Customer invoice data is not stored outside the United States.
Do you train models on our invoices?
No. Customer invoices, container data and dispute history are never used to train models, never pooled across customers, and never sold or shared.
Can we get the SOC 2 report?
Yes, under NDA through the trust center or from security@atahskia.si.
See also subprocessors and the DPA.
Don't let your 30-day dispute window expire.
Send your recent D&D invoices for a free audit. We report what is recoverable within 48 hours.