Skip to main content

Data retention policy and server infrastructure

Talon.One's server infrastructure is where the data you send to Talon.One is stored and how we ensure the Campaign Manager is always available, while our data retention policy refers to how long we keep different types of data available in the Campaign Manager.

Data retention policy​

Data is archived automatically depending on the type. The retention time is stated in your contract and can be modified to suit your needs. To discuss a data retention plan specific for your account, contact your Customer Success Manager.

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 7 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:

  • Belgium (europe-west1)
  • London (europe-west2)
  • North Virginia (us-east4)
  • Los Angeles (us-west2)
  • Singapore (asia-southeast1)
  • Sydney (australia-southeast1)

Next steps​

See the Getting started page to set up your deployment.