Skip to main content

Data retention policy and server infrastructure

Learn how and where the data you send to Talon.One is stored and how our infrastructure ensures high availability. Also learn how long we retain the data you send to Talon.One.

Data retention policy​

Be default, we retain the data sent to Talon.One for the following periods:

Type of dataRetention period (days)
Events30
Customer sessions30
Effects30
Audit logs90
Integration API logs7
Webhook logs7
Rule failure reasons
(returned by the Update customer session endpoint)		7

Custom data retention plans are stated in your contract with Talon.One and can be modified further to suit your needs. To make changes, contact our support team.

Server infrastructure​

Our infrastructure is three-time redundant, self-checking, self-healing and distributed over several availability zones to ensure high availability.

We use a Kubernetes cluster, that:

  • Stretches over two different Google Cloud availability zones.
  • Runs every production deployment on at least one instance per zone.
  • Features a synchronized master in each zone.

Our cluster has automatic health checks on both hardware and software. This ensures an appropriate distribution of load across all healthy machines and automatic discovery, isolation, and replacement of faulty components resulting in excellent reliability.

Our active-active database servers have a standby copy in a second availability zone with automatic handover in the case of catastrophic failure. They also have a separate backup mechanism allowing us to go back to any point in time within the last seven days.

Each customer instance is stored in its own VPC.

Architecture of the platform.

Deployment locations​

When you integrate with Talon.One, you can select from the following available deployment locations:

  • St Ghislain, Belgium (europe-west1)
  • London, England (europe-west2)
  • Ashburn, Virginia, USA (us-east4)
  • The Dalles, Oregon, USA (us-west1)
  • Los Angeles, California, USA (us-west2)
  • Jurong West, Singapore (asia-southeast1)
  • Jakarta, Indonesia (asia-southeast2)
  • Sydney, Australia (australia-southeast1)

Next steps​

To set up your deployment, see Getting started.