- Legal documents
- Privacy
Documents
Privacy policy
Quiet Social posts to your social networks on your behalf. This document sets out what data that requires, how long it stays, and what we do not do with it.
Contents
Data controller
The data controller is Alexandre Ribes, a sole trader operating under the trade name La Boîte à Code, SIRET 840 048 680 00069, registered at Bureau 326, 59 rue de Ponthieu, 75008 Paris, France.
No data protection officer has been appointed: the business meets none of the criteria that would require one. Requests are handled at bonjour@quietsocial.dev.
Account data
Requesting access requires a name, an email address, a password and, if you wish, a sentence on what you want to try. We also record your language, your time zone, the date your address was verified, the date you accepted the terms, then the date and author of the opening of your access. Your password is never stored in the clear: only its hash is kept, and it cannot be reversed. If you turn on two-factor authentication, its secret and recovery codes are kept encrypted; an account deletion request is recorded with its date and, where relevant, the operator who filed it at your request. The sign-up page is protected by Cloudflare's anti-bot check, described in the contact form section.
Added to that is what you enter while using the service: your workspace name, your brand names, and the members you invite.
The legal basis is performance of our contract.
During the beta, every access request is reviewed by hand. It gives rise to a notice emailed to the team — name, email address and message of the request —, kept in its mailbox for three years at most, to follow up requests and prevent abusive sign-ups; legal basis: our legitimate interest. A refused request is erased from the service, together with the account it created; it may remain up to 14 days in the database backups. A pending request is kept until we decide, or until you ask us to erase it.
Every visit to the site or the application opens a server-side session, which records your IP address and your user agent. It expires after 120 minutes of inactivity; its record is then erased by a clean-up the server triggers at random among requests, with no guaranteed delay. Your IP address is also used, hashed, as a key by the rate limiters, which keep it in cache for their window, one hour at most. Legal basis: our legitimate interest in securing access.
As long as payment is not open, no paid plan is offered and nothing is sent to Stripe. Once payment opens, subscribing to a paid plan will happen on a Stripe page, which will collect your name, billing address, VAT number and card; the card will not pass through our servers. We will keep only your Stripe customer identifier, the card type and its last four digits, whether you are an individual or a business, and the date on which you asked for immediate performance of the service. Legal basis: performance of the contract. Invoices will be issued by Stripe, which keeps them for ten years under the accounting obligation.
We send emails for the needs of the service, in particular: address verification, sign-in codes, access granted or refused, invitation, approval request, publication failure, reconnection alert, suspension or scheduled deletion of a workspace, notice of the end of the beta or of a change to the terms and, once paid plans open, reminder before a yearly subscription renews. Stripe will then send receipts and payment reminders itself. These messages are never used for marketing. Legal basis: performance of the contract and, for the renewal reminder, a legal obligation.
Connected social accounts
Connecting a Meta, LinkedIn, Threads, Pinterest, Mastodon or Bluesky account is the whole point of the service. Authorisation goes through the provider's official flow: we never see your password, and you can withdraw it at any time.
What the authorisation hands us, and what we keep:
- your identifier and name at the provider, so we know who a connection belongs to;
- access and refresh tokens, encrypted at rest, excluded from every log and every API response;
- for Bluesky, the private key specific to each connection, which binds its tokens to Quiet Social, encrypted and hidden in the same way, along with the account's permanent identifier (DID), the address of the server hosting it and that of its authorisation server: we find them from your handle, by querying that handle's domain name and the network's public directory of identifiers or, for a did:web identifier, the domain it designates, then check them at every verification of the connection;
- the list of permissions granted, so we can tell you what is missing when a post fails or a statistic cannot be read;
- for each Page or account you attach to a brand: its identifier, name, username and avatar.
We request, per network: for Meta, pages_show_list, pages_read_engagement, pages_manage_posts, instagram_basic and instagram_content_publish; for LinkedIn, r_organization_social, w_organization_social and rw_organization_admin; for Threads, threads_basic and threads_content_publish; for Pinterest, boards:read, pins:read and pins:write; for Mastodon, write:statuses, write:media and profile (read:accounts on a server older than version 4.3); for Bluesky, atproto, include:app.bsky.authCreatePosts and blob:image/*, which allow creating posts and attaching an image to them, not editing or deleting them. They are used to find the Pages, accounts and boards you administer, to publish to them and, for Facebook, Instagram, LinkedIn and Pinterest, to read the statistics of those posts. When statistics reading is open for Meta or for Threads, we also request optional permissions: read_insights and instagram_manage_insights for Meta, threads_manage_insights for Threads. You may decline them where the provider's authorisation screen allows it; withdrawing them afterwards goes through revoking the connection. Neither the connection nor publishing depends on them: without them, we read neither views, nor reach, nor clicks at Meta, nor any counter at Threads. They are not requested when a workspace connects with its own application. We read neither your private messages nor your comments: of comments and replies, we read only the number. Statistics are read for each post Quiet Social delivered, about one, seven and thirty days after it was published, with at most three days of catch-up: for Mastodon and Bluesky, through an anonymous read, without your token, of the public counters the network shows any visitor; for Facebook, Instagram, Threads, LinkedIn and Pinterest, with the connection's token, through calls that only read. This reading stores the token nowhere and does not log it. Only aggregate counters of the post are kept — depending on the network, impressions or views, reach, likes or reactions, comments or replies, shares, quotes, saves, clicks, video views — together with the part of the network's response that carries them, kept for verification: nothing that identifies the people who saw the post or reacted to it. On Mastodon, a private or direct-message post is not read. Statistics reading is opened for a network only when that network allows it, with no guaranteed date, and a network may not provide some counters. Beyond these counters, we neither keep nor use your followers or your accounts' statistics, even when a network's response contains them.
A revoked token is erased; the connection remains, without a token, until the account is deleted. An expired token can no longer act, but stays encrypted in our database until the connection is revoked or the account deleted. How to withdraw access is set out on the Access revocation page.
Publications and media
The posts you write, their images, and their scheduled time are kept so they can be delivered, and afterwards so you have their history. On upload, a library image is converted to a JPEG at most 1,440 pixels wide, except a JPEG that is already compliant and light, left as is; in every case its metadata is removed, and that version is the one we keep. A brand logo is not converted, but its metadata is removed in the same way. The original only passes through: an abandoned upload or one left in temporary storage is erased within 48 hours. Meanwhile it may appear in the file backups, until they rotate. A video is repackaged or re-encoded as MP4 on upload, its metadata removed, and the original is not kept; its file is erased 30 days after its last publication, or 30 days after its upload if it was never published and no pending publication holds it. Its record and cover image stay in the library.
Each delivery produces a record: the target network, the timestamp, the provider's post identifier, and on failure the code and message returned. Without that history, a partially failed publication would be invisible.
An activity log keeps the actions taken in a workspace — connecting and revoking an account, attaching a destination, creating, publishing and approving a post, inviting a member, a member joining or leaving — with their author, their date, and the IP address and user agent of the request. It names the email address of an invited member and that of the recipient of an approval request. When a client approves or rejects a post from their link, without an account, the decision is recorded with their email address, IP address and user agent, as proof of the decision. These IP addresses and user agents are not shown to members: they serve support and security. Legal basis: our legitimate interest in securing the service and proving decisions.
Messages sent through the contact form
The contact form sends us your name, your email address, the subject you chose and your message. The message is not stored in our database: it waits, encrypted, in the sending queue, then is carried by Spirion SAS to the team's mailbox, hosted by Proton AG in Switzerland, where it is kept. If sending fails, an encrypted copy stays 7 days in the failed jobs list, so it can be retried.
The legal basis is our legitimate interest in answering the questions put to us or, depending on the request, taking steps prior to a contract or performing it. These exchanges are kept in the team's mailbox for three years after the last contact, then deleted.
We never use an address received through this form to send you marketing, and we add it to no mailing list.
The page is protected by Cloudflare's anti-bot check, which then receives your IP address, the fingerprint of your encrypted connection and your user agent. Account creation is protected the same way. Legal basis: our legitimate interest in protecting this form and account creation against automated submissions. The Cookies page sets out how that works.
Audience measurement on the public site
We measure traffic to the public pages of the site with Quiet Metrics, an audience measurement service we also publish, hosted in France by OVH, its encrypted backups being kept in France by Scaleway SAS. Measurement starts from our server: no script is loaded in your browser. The application and the pages opened through an invitation or approval link are not measured.
For each page view, our server sends Quiet Metrics the address of the page, the address of the page you came from, your IP address, your user agent and your browser language. Your IP address and user agent are not written to the measurement tables: they pass, encrypted, through Quiet Metrics' processing queue, then are used, for the time of collection, to infer your country, your region, your browser and your device type, and to compute a pseudonymous fingerprint whose salt changes every day and is destroyed at most thirty hours later.
Purpose: knowing the site's traffic, as aggregate statistics. Legal basis: our legitimate interest. Retention: twenty-five months at most.
To object, use the link provided for that purpose on the Cookies page, or add ?qm_ignore=1 to the address of a public page of the site; ?qm_ignore=0 turns measurement back on. The cookies involved are described on the same page.
Hosting and recipients
The service's data is hosted in France. Messages sent to the team — contact form, support, beta access requests notified to it — are kept in its mailbox, hosted in Switzerland by Proton AG. The recipients are as follows:
| Recipient | Role | Location |
|---|---|---|
| OVH SAS | Hosting of the application, the database and the media, on a virtual private server | France |
| Scaleway SAS | Storage of the encrypted backups of Quiet Social (through Quiet Guard) and of Quiet Metrics; does not hold the decryption key | France |
| Laravel Holdings Inc. (Laravel Forge) | Server administration tool: deployment and configuration. It has technical access to the server, and therefore to the data on it, but hosts none of it | United States |
| Spirion SAS (service-smtp.fr) | Delivery of the service's emails (address verification, sign-in codes, invitations, approval requests, alerts, reminders) and of contact form messages to the team's mailbox | France |
| Proton AG | Hosting of the team's mailbox: contact and support messages, beta access requests | Switzerland, a country recognised as adequate by the European Commission |
| Quiet Guard (same publisher) | Receiving the application's error reports and keeping its backups (database and files, media included), encrypted on our server before they are sent | France (OVH for the reports, Scaleway SAS for the backups) |
| Quiet Metrics (same publisher) | Audience measurement of the site's public pages | France (OVH; encrypted backups at Scaleway SAS) |
| Cloudflare, Inc. | Anti-bot check on the contact form and on account creation, on those two pages only. Cloudflare acts as a processor for the check, and as a separate controller for improving its bot detection | United States |
| Stripe Payments Europe, Ltd. / Stripe, LLC | Payment and invoicing of subscriptions, once paid plans open: name, email and billing addresses, VAT number, payment method | Ireland; United States for Stripe, LLC |
| Meta Platforms Ireland | Recipient of the posts you send to Facebook, Instagram and Threads; also queried, with the connection's token, for the statistics of these posts, once their reading is open | Ireland |
| LinkedIn Ireland | Recipient of the posts you send to LinkedIn; also queried, with the connection's token, for the statistics of these posts, once their reading is open | Ireland |
| Pinterest Europe Ltd | Recipient of the pins you send to your Pinterest boards; also queried, with the connection's token, for the statistics of these pins, once their reading is open | Ireland |
| The Mastodon server you choose | Recipient of the posts you send to your Mastodon account; its operator is that of the server where you opened that account; also queried, without a token, for the public counters of these posts | That of the server |
| Bluesky Social, PBC | Recipient of the posts you send to a Bluesky account it hosts, and authorisation server for that account; once delivered, these posts are public and copied by the services that make up the network; also queried, without a token, to resolve your handle, at connection and at every check, and, once their reading is open, for the public counters of your Bluesky posts, wherever your account is hosted, and, for an account it hosts, for the existence of a post those counters no longer show | United States |
| The server hosting your Bluesky account, if it is not Bluesky Social's | Recipient of the posts you send to that account, and its authorisation server; its operator is the one you chose when opening the account; also queried, without a token, once statistics reading is open, for the existence of a post the public counters no longer show | That of the server |
| The public directory of Bluesky identifiers (plc.directory) | Queried without a token with the public identifier (DID) of your Bluesky account, to find the server hosting it | That of its operator: Bluesky Social, PBC (United States), whose takeover by a Swiss association, announced in September 2025, could not be verified as of 2026-11-14 |
Meta, LinkedIn, Pinterest, Bluesky Social, Mastodon servers and the servers hosting Bluesky accounts are not processors: they are recipients you designate. What you send them is then governed by their own terms, over which we have no control. Four other recipients are established outside the European Union, each with its safeguard: Laravel Holdings Inc., Cloudflare, Inc. and, once paid plans open, Stripe, in the United States, on the European Commission's adequacy decision of 10 July 2023 on the EU–US Data Privacy Framework, to which these companies adhere, and failing that on the standard contractual clauses adopted by the Commission on 4 June 2021; Proton AG, in Switzerland, on the adequacy decision that country benefits from. If the Mastodon server you choose, or the one hosting your Bluesky account, is established outside the Union, sending to it is done at your request, because it is necessary for the performance of the contract (article 49, paragraph 1, b, GDPR). This is the case for Bluesky Social, PBC, established in the United States, which hosts the accounts opened with it and is their authorisation server: it is not on the list of participants in the EU–US Data Privacy Framework (consulted on 2026-11-14), and we rely on no safeguard that would bind us to it. Sent to it on that basis alone, and only since Bluesky opened in the service, as announced to account holders: your Bluesky posts, and the handle and identifier (DID) used to find and authorise your account, and, once the reading of their statistics is open, the public address of those posts, wherever your account is hosted, to read their public counters. To exercise your rights with it, its representative in the Union is Ametros Ltd, in Cork (Ireland), gdpr@ametrosgroup.com. You may obtain a copy of these safeguards at the address given in the “Your rights” section.
Quiet Guard and Quiet Metrics are services we publish and operate ourselves: they are not third parties. They are named here because data leaves the application to be processed there. Quiet Guard receives error reports, to diagnose failures, and backups, to restore the service; legal basis: our legitimate interest in the security and continuity of the service. An error report may contain the page address, the request headers including your user agent, the data of the form being submitted and your account identifier; passwords and tokens are removed, and email addresses masked, before it is sent.
Retention periods
| Data | Period |
|---|---|
| Account and workspace | As long as the account exists |
| Pending access request | Until we decide or you ask for it to be erased |
| Refused access request | Erased on refusal; up to 14 days in the database backups |
| Session (IP address, user agent) | 120 minutes of inactivity, then erased at the next clean-up, with no guaranteed delay |
| Social access tokens | Until the connection is revoked or the account deleted, even once expired |
| Revoked connections and removed destinations | The row remains, without a token, until the account is deleted |
| Publications, delivery history and brands | As long as the account exists; in the bin, until permanently deleted |
| Post statistics (counters read and the part of the network's response that carries them) | Those of the publication: erased with it |
| Brand logos | Until replaced, until the brand is permanently deleted or the account erased |
| Media | Images: as long as the account exists. Videos: file erased 30 days after their last publication, or after their upload if they were never published. Refused media: 7 days. In the bin: 30 days (31 at most). Then up to 7 days in the file backups |
| In-app notifications | As long as the account exists |
| API idempotency keys (including the response returned) | 24 hours |
| Webhook log | 30 days |
| Activity log (including IP address and user agent) | 12 months |
| Queued jobs (emails, publications) | 1 hour after running; 7 days if they fail |
| Billing data (Stripe customer identifier, card type and last four digits, customer type, date of the request for immediate performance) | As long as the account exists |
| Invoices | Ten years, at Stripe, under the accounting obligation, once paid plans open |
| Server technical logs | 14 days |
| Error reports (Quiet Guard) | Depending on the plan, 90 days at most |
| Encrypted backups (Quiet Guard) | The last 14 daily backups of the database, the last 7 of the files |
| Audience measurement (Quiet Metrics) | 25 months at most |
| Support exchanges and contact messages | 3 years after the last contact, in the team's mailbox |
| Access request notice sent to the team | 3 years at most, in the team's mailbox |
When you delete your account from the interface, everything is erased within 30 days, backups included: a 7-day delay, then 14 days of backup rotation. Three exceptions: error reports follow their own period, support exchanges and the notice of an access request are kept 3 years in the team's mailbox, and actions you took in another holder's workspace stay in its activity log until they expire. The procedure is described on the Data deletion page.
What we never do
These commitments describe how the product is built, not only what it intends:
- we do not sell any data, to anyone, in any form;
- we do not use your posts or your media to train a model;
- we never publish without an action of yours — a post written, scheduled, or triggered by your application;
- we set no advertising cookie and track no one from one site to another;
- we request only the permissions used to find your Pages, accounts and boards, to publish to them and to read the statistics of those posts, the statistics permissions requested at Meta and Threads being optional; the broadest, rw_organization_admin at LinkedIn, also allows managing the page, which we do not use, just as we do not use, within Bluesky's include:app.bsky.authCreatePosts set, the setting of who may reply to or quote a post, nor the sending of videos;
- we strip from every image and every video the metadata that makes it traceable — GPS position, camera, capture time — before adding it to your library and publishing it.
Your rights
You have the right of access, rectification, erasure, restriction, portability and objection. Exercise them at bonjour@quietsocial.dev. We answer within one month; that period may be extended by two months, given the complexity or number of requests, in which case you are told so within the first month. Portability is exercised by email, or through the API for your posts, media and destinations.
You may also set instructions on what happens to your data after your death. The data requested at sign-up is necessary to open the account: without it, the account cannot be created. No decision producing legal effects concerning you is taken solely on the basis of automated processing. You may at any time lodge a complaint with the French data protection authority, CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07.
Changes
This document may change, in particular as new networks are supported. Any substantial change is announced to account holders before it takes effect, and the date at the top of this page is updated.