Skip to content
English - United States
Submit a Support Ticket
See our API Documentation
  • There are no suggestions because the search field is empty.

How does Catena store, secure, and dispose of my fleet's telematics data?

An overview of how Catena Clearing stores, encrypts, retains, and disposes of TSP data, and how carrier credentials are secured.

How and where is data stored?

Telematics data is stored in Amazon Web Services (AWS) in the United States. Catena operates cloud-natively with no on-premises systems or physical media. Operational data lives in a managed Amazon Aurora PostgreSQL database, with a durable copy stored in Amazon S3 and loaded into Snowflake for analytics. All data is encrypted at rest using AES-256 via AWS KMS (customer-managed key, automatic rotation) and in transit using TLS 1.3+.

How are carrier/TSP credentials handled and secured?

Credentials are established through Connect, Catena's onboarding flow. A fleet receives an invitation from a Catena customer and securely shares its telematics provider credentials through the Catena web application, granting Catena programmatic access to retrieve data on the fleet's behalf. Each credential is validated against the provider before storage, and credentials are encrypted at the application layer (AES) before storage - only ciphertext is ever persisted. The encryption key is held in AWS Secrets Manager under least-privilege access. OAuth and session tokens refresh automatically, and all provider communication occurs over HTTPS.

What is the retention period, and how is data disposed of?

Operational data in the primary database is retained for approximately 120 days, then automatically and permanently removed via scheduled partition deletion (not soft-deletion). A durable analytics copy persists in S3/Snowflake indefinitely. Because the fleet owns its data, Catena honors verified deletion requests from the fleet, including GDPR erasure rights. Automated database backups are kept for disaster recovery for up to 30 days.

Is data transferred elsewhere, and is it anonymized?

Catena operates on a permission-granted-only basis. a customer can only access data a fleet has explicitly shared with them via Connect. Deliveries to authorizing customers (via API or designated endpoints) are governed by explicit share agreements and record-level filters, and are authenticated/integrity-protected with HMAC-SHA256 signing over HTTPS. Data shared with an authorizing customer is the fleet's own identifiable data, delivered in identifiable form for operational use. Any external aggregation Catena performs across fleets is anonymized. Infrastructure/analytics sub-processors (AWS, Snowflake) operate under data processing agreements.

Full data lifecycle summary

  1. Acquisition: a fleet is invited by a Catena customer and shares credentials via Connect
  2. Ingestion: data is pulled over HTTPS, deduplicated, written to encrypted Aurora, copied to S3/Snowflake → Storage: held in AWS (US), encrypted at rest with rotating KMS keys → Use: the authorizing customer accesses only what's been shared, via REST API or webhook
  3. Disposal: operational data ages out at ~120 days; the fleet's data is deleted on verified request (incl. GDPR). The fleet remains the data owner throughout.