​
Definitions

Enduser data: This includes contact_ids, behavior event data and attribute information on your end users. See our data model documentation for more information. System data: This includes information such as server logs and error reports. Aampe customer records: Usernames, billing related information

​
Data Storage Location

Each customer has a dedicated pipeline that reads enduser data from their sources and transforms it into Aampe’s data model. Any PII present is removed or anonymized, ensuring compliance and security. Once transformed, enduser data is stored in our cloud warehouse as a separate, tenant-specific dataset.
We are able to co-locate BigQuery instances into any Google Cloud location to satisfy any needs on data storage location.
Every tenant has their own message queues. These queues handle messages across all channels.

​
Agentic Learning

Your agents learn based only on your data. While your agents may share information amongst themselves, they cannot share information with agents from other Aampe customers. Agentic learning based on users message interactions is stored into the same tenant-specific dataset. This data includes prefernces over labels, timing, and channels for each user. Aampe data on users and content decisions can be exported directly to your data warehouse. See here for information on receiving data from Aampe.

​
Data Retention

Data is retained by Aampe throughout the contract period.

​
Additional Information

All data is encrypted at rest and in transit. Access to data is restricted to authorized personnel only. Regular security audits are conducted to ensure the security of data.