RRevealyst

Privacy Policy

Last updated: 08 July 2026.

This Privacy Policy explains how Thalia Technologies Private Limited (“we”) handles personal data in Revealyst. Revealyst is designed to be EU-safe by default: it measures how teams adopt AI tools using only the behavioral signals the tool vendors already expose — never the content of prompts, completions, code, or messages.

1. Roles

For a customer’s workspace, the customer is the controllerof their workers’ personal data and we act as their processor, governed by our Data Processing Agreement (§8). For our own account and billing data, and for Personal (individual) accounts, we act as controller. Paddle is the Merchant of Record for payments and is an independent controller of the payment data it processes.

2. What we process

We never process prompt or completion content. There is no content field in our data model; the optional Revealyst Agent summarizes local tool logs on your machine and structurally cannot send content; and there is no browser extension or proxy. We do not process special-category data.

3. How we use it and our legal basis

We process usage data to provide the analytics you connect the Service to produce. For workplace data, the appropriate lawful basis is normally the customer’s legitimate interests(managing and getting value from their AI-tool investment), balanced by the privacy protections below. We do not rely on employee consent as a basis, in line with EDPB guidance on the employer–employee power imbalance.

4. Privacy protections built into the product

5. Security

Vendor credentials — the highest-value data we hold — are encrypted at rest with per-record AES-256-GCM envelope encryption under a versioned application-held key, and are used only to read your usage data (we perform no writes or administrative actions on your vendor accounts). Tenant isolation is enforced mechanically so one customer’s data cannot be read by another.

6. Retention

Raw vendor payloads are retained approximately 90 days to allow correction of normalization errors, then purged automatically; after that only the derived metrics and scores remain. Account data is retained for the life of the account and deleted on request in accordance with the DPA.

7. Sub-processors and transfers

We use a small set of sub-processors to run the Service, including Neon (database hosting), Cloudflare (application compute and delivery), AWS (Amazon Web Services, for email delivery infrastructure), and Paddle (payments, as Merchant of Record). The current list, locations, and any transfer safeguards (e.g. Standard Contractual Clauses) are maintained in the DPA.

8. Data Processing Agreement

Customers acting as controllers can enter our Data Processing Agreement, which sets out processing instructions, sub-processors, security measures, and deletion obligations. It is available on request at info@revealyst.com.

9. Anonymized benchmarks (opt-in)

You may optionally consent to contribute anonymized, aggregated metrics to future published benchmarks. This is off by default, recorded as an explicit opt-in, and can be withdrawn at any time. We do not use your data for benchmarks unless you opt in.

10. Your rights

Depending on your location you have rights to access, correct, delete, or restrict processing of your personal data, and to object or lodge a complaint with a supervisory authority. For workplace data, direct requests to the customer (controller); we assist them as processor. Contact: info@revealyst.com.

11. Changes

We may update this Policy; material changes will be notified. Continued use after changes take effect constitutes acknowledgement.