In development
Security and privacy
Clearwing handles your customers’ data as a processor should: as little as possible, encrypted, and only on your instructions.
-
Identifiers hashed
Emails and phone numbers of visitors and customers are stored only as SHA-256 hashes, after normalization.
-
Consent enforced
Without consent, a visit stays anonymous: no lasting identifier, no attribution, nothing sent to an ad platform.
-
Encrypted
TLS in transit, encryption at rest, and ad platform tokens sealed with AES-256-GCM.
-
Customers kept apart
Every row carries its workspace. Postgres row-level security and ClickHouse row policies enforce it.
-
Least privilege
Read-only for payments. Changes at ad platforms only with ad control on; in CRMs, only Clearwing’s own fields.
-
Protected accounts
Two-factor authentication, passkeys, SAML single sign-on, roles, and an audit log of every change.
-
Hosted in the EU
The cloud runs in the European Union, at French providers. The privacy policy lists each subprocessor and its country.
-
AI without personal data
The assistant gets questions and computed figures, never raw personal data. It can be turned off per workspace.
-
Clean logs
Logs and traces are scrubbed of emails, phone numbers, IP addresses, tokens and secrets.
How long data is kept
| Data | Kept |
|---|---|
| Events from your site | 25 months |
| Raw IP addresses | 7 days |
| Visitor cookie | 13 months, never extended |
| Audit log | 12 months |
| Ad platform data | While the account is connected; erased within 10 days after it is disconnected |
| Ad platform tokens | Until you disconnect or revoke them |
The privacy policy has every detail.
Report a vulnerability
Write to ops@clearwing.app with the steps to reproduce it, and give us time to fix it before making it public. Our contact is also in security.txt.