GROUPHASE
🔑
Authentication
The platform authenticates to the Google Ads API using OAuth 2.0 with a developer token tied to our own manager account. Credentials are stored as secrets, never in source code, and are rotated periodically.
Security & data governance
How we secure access and handle advertising data
The GROUPHASE advertising platform connects to the Google Ads API only to manage our own App campaigns. Access is restricted to internal employees, data is encrypted, and we never share Google advertising data with third parties or use it to serve ads to anyone other than GROUPHASE.
👤
Access control
Only authorised GROUPHASE employees can use the platform. Access is role-based and limited to the marketing, analytics and engineering staff who operate our own campaigns. No external party is granted access.
🔒
Encryption
Data is encrypted in transit (TLS) between the platform and the Google Ads API, and at rest in our internal data store. Access to that store is logged and restricted.
🗂️
What we access
Through the API we read campaign, ad group and asset performance metrics, and write budget, campaign and asset changes — only for Google Ads accounts that GROUPHASE owns and operates.
⏳
Retention
Performance data is retained only as long as needed for internal reporting and optimisation, then deleted or aggregated. We do not build long-term profiles of individuals from this data.
🚫
Limited use
Google advertising data is used solely to operate our own campaigns. It is never sold, transferred to data brokers or advertising platforms, or used to serve ads to anyone other than GROUPHASE.
Compliance
Standards we align with
- ▹Google Ads API Terms of Service and the Google API Services User Data Policy, including its Limited Use requirements.
- ▹The Mauritius Data Protection Act 2017 and, where it applies, the EU General Data Protection Regulation (GDPR).
- ▹Internal access reviews so that only current employees who need the platform retain access.
For how we handle personal data more broadly, see our Privacy Policy.