1. Data controller
The controller is Jean-Gabriel Mérin, acting in his own name.
Rights contact: contact@cryptolookout.app, with “Personal data” in the subject line.
2. Data, purposes and legal bases
| Data | Purposes | Intended basis |
|---|---|---|
| Email, hashed password, account and login dates. | Create, secure and manage the account. | Performance of the requested service. |
| Session identifier, login state and available user-agent data. | Maintain the session, attach pre-registration alerts and prevent unauthorised access. | Service performance and legitimate security interests. |
| Pairs, thresholds, indicators, exchanges, preferences and alert status. | Run the requested monitoring and display the account history. | Performance of the requested service. |
| Telegram chat identifier, username when supplied, and link status. | Connect the bot and deliver selected notifications. | Performance at your request. |
| Plan, subscription state and Stripe technical identifiers. CryptoLookout does not receive the full card number. | Process purchases, manage subscriptions, prevent fraud and keep required records. | Contract and applicable accounting/tax duties. |
| Support email/message, IP, user agent, page and referrer. | Answer, limit abuse and diagnose reported context. | Pre-contractual steps, contract or legitimate interest. |
| Reset-token hash and creation, expiry and use dates. | Secure password reset. The raw token is not stored. | Service performance and security. |
| Technical logs that may include IP, date, requested URL and errors. | Security, availability, incident detection and diagnosis. | Legitimate security interest. |
3. Recipients and providers
Depending on the features used, authorised CryptoLookout operators and necessary providers may access data: Stripe for billing; Telegram for linked notifications; the SMTP provider (selection and contracting in progress); OVH SAS, 2 rue Kellermann, 59100 Roubaix, France, for hosting and infrastructure; and the analytics service loaded from analytics.cryptolookout.app. Market-data providers receive symbol and market requests, not account identity in the current code.
Some providers may process data outside the EEA. Documentation of the applicable transfer safeguards and contractual terms is being regularised; this policy will be updated with the relevant references.
4. Retention
- Reset links expire after 30 minutes; the technical record is deleted after 7 days by default.
- Account and alert data: while the service is used, then deletion or anonymisation no more than one year after account closure. A valid deletion request may result in earlier deletion.
- Support messages: six months after the support request is closed.
- Caddy and backend technical logs: a rolling six-month period. Only records required for an incident, dispute or legal duty may be isolated and kept longer for the strictly necessary period.
- Billing data: for the contract, followed by restricted retention of required information for applicable statutory periods, including ten years for invoices and accounting records. Other contractual evidence is kept for its applicable period.
These periods are the target policy. Log rotation, automated deletion and restricted intermediate archives are being deployed and audited. In the meantime, rights requests are handled manually through the contact address.
5. Your rights
Depending on the processing and applicable law, you may request access, rectification, deletion, restriction or portability, object to certain legitimate-interest processing, and withdraw consent when consent is the basis.
Email contact@cryptolookout.app. Identity evidence may be requested only where there is reasonable doubt. You may also complain to the CNIL.
Alert triggering follows your configured condition and is not an automated decision producing legal or similarly significant effects.
6. Browser storage and analytics
The interface uses browser local storage for language, theme, session ID, login state and some alert preferences. Clearing it may sign you out or reset the interface.
The consent interface lets you allow or decline optional audience measurement. The “Audience measurement preferences” button at the bottom of the page reopens this interface so you can change your choice. The analytics script is served by this site and is loaded only after permission.
7. Security and updates
Passwords are hashed. Reset links use random, single-use tokens, only the hash is stored, and active sessions are revoked after a password change. This policy will be updated when processing, providers or obligations change.
Identity and contact details updated on October 20, 2026.

