Tetra runs fully on DigitalOcean, with servers hosted in London. As a cloud provider, DigitalOcean guarantees the physical and network security of Tetra servers and helps us ensure that our server software is always up-to-date.
Tetra maintains secure connections when accessing the services you have integrated with. All web-based data integrations use HTTPS, and we maintain a list of IP addresses that can be put on an accept list by the other service.
All web-based integrations that have OAuth available use it, and any that do not use the most secure form of authentication that the other service supports. Connections to databases are made through our secure VPC with private subnets.
All data in Tetra, these are encrypted in transit and at rest.
The most sensitive data that Tetra stores is the data that you process with Tetra (through uploading, integrating, creating, or otherwise pulling it into a workflow). We are extremely careful with that data, and it is our highest priority to ensure it is secure.
We make sure to only store the data that is required for running your Tetra workflows as long as it is needed. Data in a workflow is stored for a maximum of 14 days, or until the next time the workflow runs.
Backups are stored for a maximum of 30 days before being deleted.
If you would like to have all of your data deleted from the Tetra platform and our data subprocessors, please send your request to firstname.lastname@example.org.
Data sent to or from Tetra is encrypted in transit using 256-bit encryption. Our API and application endpoints use industry-standard SSL/TLS 1.2+ encryption.
Data stored by Tetra is encrypted at rest using an industry-standard AES-256 encryption algorithm.
We never store passwords in plaintext. All passwords are stored as an irreversible hash in our database.
Tetra does not sell any of your data.
Tetra collects customers' names and email addresses (during the sign-up process) to use in our analytics subprocessors. Usage data from the Tetra platform is also collected and sent to our analytics subprocessors.
However, data that is uploaded, created, integrated, or otherwise pulled into Tetra and displayed as the "results" of any step is not sent to any analytics subprocessors. This data is saved and used only to ensure the functioning of the workflows that you create and use on the Tetra platform.