l0g Watch uses an account, a server-side session and private settings. This notice applies only to Watch. The l0g.fr editorial site has its own separate privacy notice.
Last updated: 28 July 2026
// controller and scope
An identifiable data controller.
This notice covers the authenticated service available at watch.l0g.fr, its logs and its commercial communications.
Dedicated server managed directly by the operator in Chartres, France (28000)
// processing register
Clear, limited purposes.
The stated legal bases distinguish service delivery, obligations arising from the commercial relationship and system security.
Account and authenticationContract and security
Email address, opaque identifier, role, account status, creation date, salted password hash, public keys and passkey counters. The plaintext password is not stored.
Purposes
Create and administer the account, verify access, prevent abuse and provide support.
Legal basis
Performance of the contract or steps taken before entering into it. Legitimate interests for security.
Retention
For the duration of the service relationship. Closing the account removes the account, password hash, passkeys and their counters, then revokes every session. A session expires after 12 hours and a passkey challenge after 5 minutes.
Preferences and monitoringRequested service
Topics, rules, watchlist, folders, delivery profiles, cockpit preferences, alert history and the deduplication data needed for delivery.
Purposes
Personalise monitoring, prepare alerts, prevent duplicates and present the useful history.
Legal basis
Performance of the contract.
Retention
For the duration of the service relationship. The displayed history is limited to the 100 most recent events per account. Closing the account removes the preferences, rules, lists, profiles and private histories linked to it.
Commercial access and deliveryContract and service records
Delivery address, access status, start and end dates, a hashed Stripe subscription identifier, pause or cancellation states and technical delivery records. Watch never receives a card number.
Purposes
Activate access, deliver alerts, synchronise the subscription, handle incidents and document service delivery.
Legal basis
Steps taken before entering into the contract, performance of the contract and legal obligations relating to billing.
Retention
The activation code expires after 30 days. The limited activation record is purged after 30 days. Current access status is removed when the account is closed. Only commercial and delivery records that remain necessary are kept separately, without the email address, under a pseudonymous identifier.
Logs and security auditLegitimate interests
The Apache log contains the IP address, timestamp, resource, referrer and user agent. The application audit contains events linked to an account identifier, without email, IP address, browser or user agent.
Purposes
Secure and maintain the service, diagnose errors, detect abuse and establish an incident timeline.
Legal basis
The operator’s legitimate interests in protecting and maintaining Watch.
Retention
Apache logs are retained for 14 days. The detailed application audit window is limited to 8,000 events and HMAC-chained. Its older prefix is reduced to a cumulative HMAC anchor that retains neither event details, email addresses nor IP addresses.
Support requestsResponse and follow-up
Email address, any identity information supplied, message content and technical mail-delivery data.
Purposes
Respond, resolve the incident and follow up on the request.
Legal basis
Steps taken before entering into the contract, performance of the contract or legitimate interests, depending on the purpose of the message.
Retention
For as long as needed to process and follow up on the request, followed by any applicable statutory retention period where a record must be kept.
// recipients and service providers
No advertising disclosure.
Data remains accessible to the operator and only those providers required for the subscription. Monitoring rules and watchlists are not shared with them.
Operator and local server
The operator administers the account, service, delivery and private logs. Web services, workers and mail use separate system identities.
Stripe
Stripe hosts payment and the billing portal. A signed webhook transmits the email used for payment, Stripe identifiers for the customer, session, subscription and Payment Link, the event type and date, then the subscription status. Watch validates the raw request body, stores only a hash of the subscription identifier and receives no card data. Stripe’s privacy policy describes its processing locations, recipients and safeguards for international transfers.
Watch does not automatically load any Stripe or advertising script, iframe, pixel, image, font or widget. The browser contacts an external provider only after an explicit click.
// cookie and local storage
A strictly necessary session.
Session cookie
After sign-in, Watch sets only the __Host-l0gwatch_session. It is Secure, HttpOnly, SameSite=Strict and expires after 12 hours. It is used solely for authentication and its security.
Device storage
The theme, public selection, a local copy of the watchlist, folders and comparison memory may remain in browser local storage. A visual email-test cooldown may remain in browser session storage. These items can be removed in the browser settings.
The French data-protection authority, CNIL, lists trackers required for authentication and security among those that may be exempt from consent. Watch sets no advertising or third-party analytics tracker. Read the CNIL guidance.
// access, export and erasure
You can exercise your rights directly.
The cockpit provides a direct export and controlled account closure. You can also contact the data controller.
You may request access to your data, rectification, erasure or restriction of processing. Where the right applies, you may request portability of the data you supplied and object, on grounds relating to your situation, to processing based on legitimate interests. You may also set instructions concerning your data after your death.
From My data in the cockpit, you can download a JSON export and then close your account. Closure removes access, sessions, passkeys, preferences and private monitoring data. Administrator accounts remain subject to the local security procedure. For any other request, write to olivier@l0g.fr.
Identity documentation is requested only where there is reasonable doubt. You may also lodge a complaint with the CNIL.