Legal
Privacy policy
Last updated: 19 September 2026
Who we are
RevealWhy is operated by Soulution Insights LDA, a company established in Portugal (European Union), based in Cascais, Lisbon, Portugal, NIF 518116794 (registered address in the legal notice). For the analytics data our customers collect on their websites, the customer is the controller and Soulution Insights LDA is the processor acting on the customer's instructions (see the data processing agreement). For the accounts of people who sign in to the RevealWhy dashboard, and for RevealWhy's own analytics of this website and the dashboard (below), Soulution Insights LDA is the controller.
What the tracking script collects on a customer's website
- Page views and navigation (paths, page titles, referrer), clicks, scrolling, viewport size, device class, browser and operating system.
- A session replay of the page structure. Form inputs are always masked. Customers can mark elements to be masked (
data-rw-mask) or not recorded at all (data-rw-block), and exclude whole routes. - A random visitor identifier stored in the browser, and — only when the customer calls
identify()— a one-way hash of the customer's user id. - An approximate location (country, city, time zone) derived from the IP address at the moment of collection.
What we do to minimise it
- IP addresses are truncated before storage (IPv4 to /24, IPv6 to /48). The full address is used in memory only to derive the approximate location.
- Personal data patterns are removed from text before it is stored — e-mail addresses, phone numbers, payment card numbers, IBANs, passport-like identifiers, access tokens and keys are replaced by placeholders such as
[email]. This runs in the browser and again on our servers. - URLs are cleaned: query parameters are dropped except campaign parameters (
utm_*,gclid,ref), fragments are dropped, and customers can declare path patterns (for example/share/:token) whose secret segments are replaced. - Browser Do Not Track and Global Privacy Control signals are honoured, and customers can require consent before anything is recorded.
- Language models only receive the cleaned text and URLs described above.
RevealWhy's own analytics on revealwhy.com and app.revealwhy.com
We use RevealWhy to understand how our own website and dashboard are used, and Soulution Insights LDA is the controller for that data. It runs only with your consent: until you choose "Allow" in the banner, the tracking script is not loaded and nothing is stored or sent. You can change your choice at any time under Privacy choices (in the site footer and the dashboard's account menu). Withdrawing stops recording immediately and clears the script's browser storage. The legal basis is your consent (Art. 6(1)(a) GDPR).
- What is collected: pages visited, clicks, scrolling, device class, browser and a session replay of the page structure, with the protections described above (masked form inputs, removal of personal data patterns, cleaned URLs, truncated IP addresses).
- Dashboard text is masked: all text in the dashboard is masked in the replay and in click data. On the marketing site, our own published page text can appear in the replay; form inputs are always masked.
- Dashboard pages that show our customers' data — session lists and replays, page snapshots and heatmaps, eye-tracking views, study participants — are never recorded, nor are the pages study participants use.
- When you are signed in, we attach a one-way hash of your account id and your plan to the session; never your name or e-mail address.
- Your choice is stored in a first-party cookie (
rw_self_analytics) for six months, after which we ask again. - This data follows the same retention and deletion rules as any RevealWhy project. Contact support@revealwhy.com to access or delete it.
Retention
| Data | Kept for |
|---|---|
| Sessions, events, replays, heatmaps | The retention period of the customer's plan, then deleted automatically |
| Derived behavioural records (the analysis "spine") | Deleted with their sessions and never kept longer than 180 days |
| Attention predictions (page images analysed by our model) | Superseded versions deleted after 60 days |
| Erasure audit records | Kept as proof of erasure; the erased identifier is stored only as a one-way hash |
Your rights
If you visited a website that uses RevealWhy, please contact that website's operator — they are the controller and can ask us to delete your data. Customers can erase a single visitor, a signed-in user (by the hashed id), or an entire project through the API; erasure runs asynchronously and is recorded in an audit log. Dashboard users can contact us at support@revealwhy.com for access, correction or deletion of their account data. You may also complain to your data-protection authority.
Where data is processed
Our infrastructure runs on Google Cloud in the United States. The providers we use are listed on the subprocessors page. Transfers outside the EU rely on the safeguards set out in the data processing agreement.
Security
Data is encrypted in transit (HTTPS) and at rest (Google-managed encryption keys). Browser (publishable) keys can only send data; reading or managing data requires a signed-in user or a secret API key with explicit scopes. Browser keys only work from the website domains the customer has allowed.