Last updated: 21 August 2026
What we process, in what capacity, for how long, and what you can require of us. This page separates two very different roles we hold depending on the data.
For account, billing and site usage data, Alexandre Ribes is the controller within the meaning of article 4.7 GDPR. Those processing operations are described below.
For the monitoring data your application sends us, Alexandre Ribes is a processor within the meaning of article 4.8. You, the client, remain the controller: you decide what your application sends, which retention period applies through your plan, and whether encryption is on. We process that data only on your instructions.
Those instructions and our commitments are set out in our article 28.3 data processing agreement, available at https://quietguard.dev/en/data-processing. If your application processes data on behalf of your own clients, we act as a sub-processor and it is for you to have obtained the authorisation required by article 28.2.
The card number is entered directly with our payment provider and never passes through our servers. We know only the type and the last four digits.
The client package sends exceptions, application logs, the dependency inventory and scheduled task signals. Those payloads may contain personal data of your own users.
We keep them for the retention period of your plan: seven days on the free plan, thirty days on Indie, ninety days on Studio. Deletion at the end of that period is automatic.
The client package masks before anything is sent, on your own server, so the values concerned never reach ours. It does so in two ways.
By field name: values whose key matches a configurable list (password, token, secret, cookie, authorization header, API key). By the shape of the value: email addresses, IBANs, card numbers, French social security numbers and French phone numbers, recognised wherever they sit, including in the free text of an error message or in a URL segment. The shapes that carry a check digit are verified rather than merely matched, so a sixteen digit order reference is not taken for a card number.
That is still not anonymisation. These patterns recognise known shapes; they do not recognise a name, a postal address, or an identifier particular to your business. As the controller, it is for you to configure both lists, to add your own patterns, to limit what your application logs and, if your payloads may carry personal data, to turn encryption on.
On paid plans you can encrypt the captured content. It is off by default and is turned on by the team owner. A key pair is generated; the private key is kept by us, encrypted under a key derived from your passphrase, which is never sent to us. If you lose it, nobody can restore the data, us included.
Encryption covers the exception message, its stack trace and its context, and the message and context of your logs. The metadata needed for grouping and search stays readable by us: exception class, file path, line, environment, release, channel, level and timestamps.
One limit we would rather state: if you use the server-side unlock instead of the browser unlock, your private key is rebuilt on our servers and stays there for the duration of your session. The browser unlock is the stronger guarantee, the key then never leaves your tab.
We do not sell, rent or trade your data. It is disclosed only to the providers needed to run the service, named below.
Where we act as your processor, we will tell you of any addition or replacement of a sub-processor at least thirty days before it takes effect, at your team owner's address. You have thirty days to object on data protection grounds under article 28.2. If your objection stands, you may terminate at no cost.
The application, the database and the backups are hosted in France. Your monitoring data, meaning the exceptions, logs and backups your application sends us, does not leave the European Union.
The emails we send you, alerts, invitations, reports and invoices, are delivered by a provider established in Switzerland. They carry a name, an email address and incident metadata. Switzerland is the subject of an adequacy decision by the European Commission, so this transfer rests on that rather than on standard contractual clauses.
One transfer exists, for payment. Our provider contracts with us from Ireland, but some processing is carried out by its United States parent. That transfer is covered by the standard contractual clauses adopted by the European Commission on 4 June 2021, together where applicable with the provider's certification under the EU, United States data protection framework. You may obtain a copy of those safeguards by writing to legal@quietsystems.dev.
When you pay, you are redirected to a page hosted by that provider. What you enter there is collected directly by them.
You have the rights of access, rectification, erasure, restriction, objection and portability. Write to legal@quietsystems.dev. We answer within one month of receipt, extendable by two months where the request is complex, under article 12.3 GDPR.
None of our processing rests on your consent, so there is no consent to withdraw. Providing account data is necessary to perform the contract: without it the service cannot be supplied.
If you are an end user of an application monitored by one of our clients, address your request to that client: they are the controller. We assist them in answering it.
If you disagree with how we handle this, you may lodge a complaint with the CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, or at cnil.fr.
Given the nature and scale of our processing, appointing an officer is not mandatory under article 37 GDPR and we have not appointed one. Your requests are handled at legal@quietsystems.dev.
We take no decision based solely on automated processing producing legal effects concerning you within the meaning of article 22. The service's automatic mechanisms, quota enforcement, alert rate limiting and deletion at the end of the retention period, are ways of performing the contract and involve no evaluation of you as a person.
Encryption in transit, API keys stored hashed, per-team data isolation, configurable client-side masking, optional end to end encryption of content and backups.
In the event of a breach affecting your monitoring data, we will inform you without undue delay so that you can meet your own obligations under articles 33 and 34 as the controller.
Any substantial change is announced to team owners before it takes effect. The date at the top of this page governs.