Sub-processors

Why this list exists

No system this size runs alone. Data protection law requires the customer to know who else the data reaches, and this is the complete list of services the operator of this installation uses in this installation.

In a self-hosted install the list is shorter: each service below only comes into play when its key is configured, and anything unconfigured receives no data at all.

Infrastructure

• Application hosting — runs the code and serves the pages. Sees the traffic, does not hold the database.
• Database and file storage — holds contacts, conversations, deals and media. This is where the data actually lives.
• Cache and rate limiting — holds short-lived counters. Receives no message content.

Messaging and communication

• Messaging platform — delivers and receives the conversations of the connected channel. Handles phone numbers and message content, under the platform's own terms.
• Transactional email delivery — sends sign-up confirmations, password resets and notices. Handles name and email address.

Artificial intelligence

The models that answer in a person's place receive the slice of conversation needed to reply, plus the knowledge you uploaded. These vendors' business terms do not allow training models on what goes through the programming interface — which is precisely why access happens that way, and not through the consumer interface.

Payment and monitoring

• Payment processor — handles card details. The card number NEVER passes through Atenza and is never stored in it; the browser talks to the processor directly.
• Error monitoring — receives the technical report of a failure. The report is sanitised before it leaves: personal data and secrets are stripped.

Changes to this list

A new sub-processor is announced a reasonable time before it starts processing data. Anyone who disagrees may cancel without penalty, by the route described in the Refund Policy.