Stamplay security

Stamplay takes the security of your data and our infrastructure very seriously.
We are committed to providing a secure and reliable platform that is safe, secure, and available to all of our customers.

Overview

Stamplay is firmly committed to the privacy of our customers and the data which they store on the Stamplay cloud platform. You can read more about the privacy of your account information and data in our Privacy Policy.

In addition to the security of your account information, we also treat the data you store on our services with the utmost sensitivity.

Data storage and processing locations

Data is stored and processed within the Ireland (eu-west-1) AWS region.

Initial connections with API endpoints leverage worlwide coverage of AWS Cloudfront.

Data processing information
Examples of end-user personal data processed by Stamplay

Some Stamplay services process your end users' personal data to provide their service.
The chart below has examples of how various Stamplay services use and handle end-user personal data.

Stamplay Service Personal Data How data helps provide the service
Auth Email addresses
Passwords
Third party service informations
How it helps: Stamplay Auth uses the data to enable end-user authentication, and facilitate end-user management.
Retention: Stamplay Auth retains authentication information until the Stamplay customer initiates deletion of the associated user, after which data is removed from live and backup systems within 180 days.
Object Sent data
Uploaded files
How it helps: Allow users the store specific types of data so that they can be exposed via API.
Retention: Stamplay Object retains data information until the Stamplay customer initiates deletion of the associated object, after which data is removed from live and backup systems within 180 days.
Flows Request body
Request query parameters
Third party significant request headers
Response body
Third party significant response headers
Files
How it helps: Flow logs empower customers to debug flows easily (authentication credentials are stripped before logging).
Retention: Flow logs are retained for a period of 30 days, after which data is removed from live and backup systems within 180 days.
Code Block Request body
Response body
How it helps: Code Block logs empower customers to debug Code Block easily.
Retention: Code Block logs are retained for a period of 14 days, after which data is removed from live and backup systems within 180 days.

Key concepts

Automate your business now

Streamline operations and improve productivity by 10X