Built to be trusted.
By design.
At Activation Studio, security, privacy, and reliability are core design principles β not afterthoughts. This page outlines how we protect your data and maintain compliance.
Security
Data Security
- βTLS encryption for data in transit
- βAES-256 encryption for data at rest
- βMonthly and recurring data protection audits
- βExplicit customer consent before any temporary access to logging or database data
- βUser and role management with access disabled by default
Application Security
- βOWASP ZAP testing
- βSQL injection protection
- βCross-site scripting (XSS) protection
- βUnauthorized access and authorization testing
Incident Response
- βAutomated logging and audit trails
- βRegional incident identification and reporting
- βRemediation and mitigation processes
- βAdmin user notification on incidents
Privacy
Privacy Policy
Review our full privacy practices for a comprehensive overview of how we collect, use, and protect your data.
Read Privacy Policy βData Usage
We use customer data to:
- βValidate login requests
- βCollect and process web behavior data
GDPR & CCPA compliance via:
- βRegional hosting on request
- βDedicated security officer
- βRegular privacy impact assessments
- βDocumented and enforced privacy policies
- βEmployee training and awareness
- βOngoing GDPR and CCPA audit monitoring
Data Retention & Deletion
Compliance
Certifications
System Availability
Security Best Practices
We recommend the following for your SFMC environment:
- βEnforce MFA in Marketing Cloud
- βDon’t share user accounts in Marketing Cloud
- βRotate Marketing Cloud passwords frequently
Support & Contact
Support Channels
Security Contact
For questions or concerns about trust, security, or privacy β please reach out directly. We aim to respond within one business day.
Email security team βSecurity questions.
How is communication between business applications secured? +
Encryption in Transit:
- βTLS 1.2 / TLS 1.3 for all communications, ensuring data confidentiality and integrity
- βHTTPS with HSTS (HTTP Strict Transport Security) enforced to prevent downgrade attacks
Secure Front-End & Back-End Communication:
- βAPI communications secured with OAuth 2.0 and JWT tokens for authentication
Are data leakage prevention (DLP) solutions applied? +
DLP measures on the hosting environment:
- βAt Rest: Data stored in Amazon RDS is encrypted
- βIn Transit: AWS Beanstalk environments configured to use HTTPS (TLS/SSL)
- βApplication Secrets stored in AWS Secrets Manager
Access Controls & Logging:
- βRole-Based Access Control (RBAC) for confidential data
- βAudit logs tracking data access and modifications
- βRestricted database access via security groups
Encryption & Tokenization:
- βAES-256 encryption protects stored data
Are backups performed and tested regularly? +
- βCritical systems and databases backed up daily; cloud backups configured for continuous data protection (CDP)
- βBackups are AES-256 encrypted to prevent unauthorized access
- βOff-site backups via AWS S3 ensure redundancy
- βBackups tested periodically; disaster recovery drills validate restoration effectiveness
Are patch management processes in place? +
- βSecurity patches and software updates monitored and applied regularly via GitHub Dependabot
- βAWS Beanstalk automatically manages infrastructure patches
- βSecurity updates prioritised based on threat intelligence and CVE databases
- βSoftware Bill of Materials (SBOM) tracks third-party libraries for vulnerabilities
Questions about security
or compliance?
We’re happy to answer procurement questions, share our ISO certificate, or walk through our security setup with your team.