Source
Security / trust page — Whatagraph
Checked for Whatagraph on 1 Nov 2026
- Page
- https://whatagraph.com/security-policy
- Checked
- 1 Nov 2026, 09:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:528c633c9b0ea8e52da75aec935fd9a643cf2d431bc8fae51449cd9ca08299c8
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Encryption aes256 Report an error
“We encrypt data using AES-256 encryption.”
-
Tls Report an error
“All interactions with our services, including access to our web portal, account management system, and any transactions, are securely encrypted by default using standard cryptographic protocols (TLS 1.2 or higher).”
-
Providers Report an error
“Google Cloud Platform and Amazon Web Services are our providers of choice and both organizations have excellent compliance and regulatory audits including SOC 1/2-3, PCI-DSS, and ISO27001.”
-
Data residency Report an error
“Your data is processed in the European Union. Any transfer to a third country is guaranteed under GDPR rules.”
-
GDPR Report an error
“Whatagraph is compliant under the General Data Protection Regulation (GDPR).”
-
Password policy Report an error
“Each employee uses a unique password with a minimum of 8-10 symbols to log into their account, which is secured with 2-step verification. To ensure the highest level of data protection, passwords must be changed to a new one every 6 months.”
-
Data backups Report an error
“We obtain your data through third-party data integrations and create backup copies. These copies are retained for a specified period or until they are no longer relevant, after which they are deleted.”
-
Deletion right Report an error
“At all times you retain control over the data Whatagraph has access to and the transactions that occur and at any time can request a deletion of all personal data.”
-
Oauth tokens Report an error
“Whatagraph requires users to give access to read the data from data sources, e.g. Facebook Ads and Google Ads APIs. Where possible, we will make use of OAuth access tokens.”
-
Token storage Report an error
“We keep your user access tokens to enable data retrieval upon your request or according to your schedules.”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Data Analyst European sovereignty
- The Finance Controller European sovereignty
- The IT Administrator European sovereignty
- The Managing Director European sovereignty
- The SaaS Product Lead European sovereignty
- The Skeptic European sovereignty