Skip to content

Legal

Privacy policy

This page describes how the hosted service at app.silencewatch.com handles your personal data, in line with the General Data Protection Regulation (GDPR) and the French data-protection law. It does not apply to an instance you host yourself: in that case the publisher has access to nothing.

The controller is the publisher of the service, whose details are in the legal notice. For any question or request: contact@silencewatch.com.

Data Why How long it is kept
Account: email address, and what your way of signing in needs: the public key of each passkey (never the private one), a password hash (scrypt, never the password itself), or the identifier your Google or Microsoft account has with us, with recovery codes as hashes. No profile picture and no token of those providers is kept To create and run your account As long as the account exists
Sessions: a session token, and the IP address and browser of the sign-in To keep you signed in and to detect a stolen session 30 days from the last time it was used, and until you sign out
Security log: sensitive actions (sign-in, password change, API keys, deletions…), with the email, IP address and browser Security of the service and investigation after an incident 1 year. It keeps the email of whoever acted even after the account is deleted
Sign-up: the network the request came from, truncated (IPv4 /24, IPv6 /48) To slow automated sign-ups 7 days
Your configuration: projects, checks (names, schedules, environments, tags), alert channels (email addresses, webhook addresses, Slack, Teams, Discord), API keys (as a hash) To provide the service As long as you keep them
Heartbeat history: time, result, duration, the caller’s IP address and browser, and any text attached (10,000 bytes at most) To detect that a job has stopped and to show the history 90 days by default, adjustable per project
Subscription (paid plans): plan, subscription state, period dates, and the customer and subscription identifiers at Stripe. The service neither receives nor keeps a card number Run your subscription and its limits As long as the account exists; Stripe keeps invoices as long as accounting law requires (10 years)
Alerts sent: recipient, time, outcome To tell you, and to know whether the alert went out 30 days
Visits to the application: a keyed hash of the connection’s address, the browser and the day, never the address or the browser themselves. No cookie is set, and nothing links one day’s visit to the next. Not recorded when your browser sends Do Not Track or Global Privacy Control To count the application’s unique visitors per day, a figure only the publisher sees 30 days

Do not send third parties’ personal data in the text attached to a heartbeat: it is stored as it is with the history.

The service uses no third-party audience-measurement tool, no advertising and no tracker, and neither sells nor rents any data. Its only measurement is the count of unique visitors described above, made on its own servers.

  • Performance of the contract (GDPR article 6.1.b) for everything that makes the account and the service work.
  • Legitimate interest (article 6.1.f) for security: rate limiting, the security log, and fighting automated sign-ups; and for the count of unique visitors, which identifies no one.
  • A legal obligation (article 6.1.c) where the law requires information to be kept or disclosed.

Data is shared only with the providers the service needs, as processors:

  • OVH SAS (France): hosting of the servers and the database.
  • Google and Microsoft, only if you choose to sign in with them: they tell us your email address and an identifier, and they learn that you sign in to SilenceWatch. We receive no profile picture and keep none of their tokens.
  • Stripe (Stripe Payments Europe, Ireland), only if you subscribe to a paid plan: it receives your email address and your payment data, and issues the invoices. It acts on its own account for its fraud-prevention and compliance duties, and may process data outside the European Union with the safeguards the GDPR provides.
  • Mailjet: sending the alert emails you have asked for. The service sends no other email: nothing is sent to confirm an address or to reset a password.

OVH and Mailjet are established in the European Union. Every provider receives only what its task requires. The alerts you configure towards Slack, Microsoft Teams, Discord or a webhook of your choosing are sent to the service you designated yourself, under your responsibility.

You may ask for access to your data, its rectification, its erasure, the restriction of its processing, its portability, and you may object to processing based on legitimate interest. Write to contact@silencewatch.com giving your account’s address; you will get an answer within one month.

You can delete your account yourself, in Settings → Account → Delete account: deletion is immediate and permanent, and takes your projects, checks, their history, API keys and alert channels with it. Only the entries in the security log are kept, for the period given above.

If you think your rights are not respected, you may complain to the CNIL, the French data-protection authority, or to the authority of your own country.

The application sets one cookie that lasts, sw.session_token: the one that keeps you signed in. It is HttpOnly, SameSite=Lax, Secure, and essential to the service. While you sign in it also sets a few cookies that live for minutes (the passkey challenge, the handshake with Google or Microsoft). As such none of them needs your consent.

It also stores your display preferences (language, light or dark mode) and the selected project in your browser’s local storage. These values stay on your device and are never sent to the server.

The silencewatch.com site sets no cookie; its display theme is also kept locally.

Passwords, where they are used, are stored as scrypt hashes, and recovery codes and API keys as hashes too. Passkeys are public keys, from which no one can sign in. The session cookie is signed with a secret the database does not hold, and traffic is encrypted (HTTPS). The measures are detailed on the Security page. A vulnerability is reported through the procedure in SECURITY.md.

This policy may change; the date of the last update is at the foot of the page, and a significant change is brought to the attention of account holders.

Last updated: 9 November 2026.