Aampe Data Management
Data definitions
Enduser data: This includes contact_ids, behavior event data and attribute information on your end users.
More information in our data model documentation
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.
PII present is removed or anonymized during this stage, ensuring compliance and security.
Once transformed, enduser Data is stored in our BigQuery warehouse as a separate, tenant-specific dataset.
Every tenant has their own dedicated message queues. These queues handle everything from SMS to push notifications and emails.
Physical Data Location
We are able to co-locate BigQuery instances into any Google Cloud location to satisfy any compliance requirements on data storage location.
Aampe Agent Learning
Each tenant’s agents learn the user preferences based only on their own data. These models are stored securely within the tenant’s dataset.
Aampe agent learning based on users message interactions is stored into the same tenant-specific dataset in BigQuery. This data includes end users label(message content), timing and channel preference.
Aampe message data embedded with enduser level learning can be exported directly to your data warehouse. More information here.
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.
Updated 22 days ago