Privacy Policy — DataHide Chrome Extension
Last updated: March 27, 2026
This privacy policy explains how the DataHide Chrome extension ("the Extension") collects, uses, and protects your data. The Extension is published by TISSY (SARL), the company behind DataHide.
1. What the Extension does
The DataHide Chrome extension is a companion tool for DataHide users. It provides:
- A popup dashboard showing your ad campaign metrics (spend, revenue, ROAS)
- Overlay badges on Meta Ads Manager and Google Ads showing DataHide metrics next to your campaigns, ad sets, and ads
- A UTM link builder
- A pixel debugger for verifying your DataHide tracking pixel
2. Data collected
2.1 Authentication data
When you log in to the Extension, we store your session tokens (JWT) in chrome.storage.local so you stay authenticated between browser sessions. We also read authentication cookies from datahide.fr to detect existing sessions. This data stays on your device and is never shared with third parties.
2.2 Campaign entity names
The Extension stores campaign, ad set, and ad names (fetched from the DataHide API) in chrome.storage.local to match them against what you see on Meta Ads Manager and Google Ads. This data is used solely to display overlay badges and is never transmitted elsewhere.
2.3 What we do NOT collect
- We do not read or intercept your network requests
- We do not collect browsing history, form data, or personal information from pages you visit
- We do not inject tracking scripts into any page
- We do not collect data from pages other than Meta Ads Manager and Google Ads
- We do not sell or share any data with third parties
3. External connections
The Extension communicates with the following servers:
| Server | Purpose | Data sent |
|---|---|---|
api.datahide.fr | Fetch dashboard metrics, campaign data, overlay metrics | Authentication token, organization ID |
ybstwfsmvyrcirsylwas.supabase.co | Authentication (login, token refresh) | Email, password (on login), refresh token |
No data is sent to any other server. The Extension does not include any analytics, advertising, or tracking SDK.
4. Permissions explained
| Permission | Why it is needed |
|---|---|
storage | Store session tokens, cached metrics, theme preference, and entity names locally on your device |
cookies | Read authentication cookies from datahide.fr to detect an existing DataHide session (single sign-on) |
activeTab | Run the pixel debugger on the currently active tab when you click the debugger button |
scripting | Inject the pixel debugger script into the active tab to detect the DataHide tracking pixel |
alarms | Periodically refresh authentication tokens in the background (every 30 minutes) |
Host: adsmanager.facebook.com, business.facebook.com | Inject overlay badges showing DataHide metrics next to your Meta Ads campaigns |
Host: ads.google.com | Inject overlay badges showing DataHide metrics next to your Google Ads campaigns |
Host: datahide.fr, api.datahide.fr | Read authentication cookies and communicate with the DataHide API |
5. Data storage and retention
- Session tokens: Stored in
chrome.storage.localuntil you log out or they expire - Cached metrics: Stored locally with a 5-minute TTL, automatically cleared on expiration or manual refresh
- Entity names: Stored locally and refreshed from the API periodically. Cleared when you switch organization or log out
All data is stored locally on your device using Chrome's built-in storage APIs. No data is persisted on our servers beyond what is already stored in your DataHide account.
6. Data security
- All communications use HTTPS/TLS encryption
- Authentication tokens are stored in Chrome's sandboxed extension storage, inaccessible to websites
- Content scripts run in Chrome's isolated world, separated from page scripts
- The Extension does not execute remote code — all JavaScript is bundled in the extension package
7. Your rights
You can at any time:
- Log out from the Extension to clear all stored session data
- Uninstall the Extension to remove all locally stored data
- Request data deletion from your DataHide account by contacting dpo@datahide.fr
For full GDPR rights (access, rectification, erasure, portability, objection), see our main privacy policy.
8. Changes to this policy
We may update this policy when the Extension evolves. Significant changes will be communicated through the Extension or by email. The date at the top of this page indicates the last update.
9. Contact
- Data Protection Officer: Quentin Barroche
- Email: dpo@datahide.fr
- Address: TISSY - DPO, 128 rue La Boetie, 75008 Paris, France