Skip to content
Quiet Social

Documents

Data processing agreement

This agreement governs the processing of personal data we carry out on your behalf. It is annexed to the terms and conditions and forms part of them.

Last updated: 20 November 2026

This is a translation provided for convenience. Only the French version is legally binding.

1. Purpose and relation to the terms and conditions

This agreement frames the processing of personal data the Publisher carries out on the Client's behalf within the Quiet Social service, within the meaning of article 28 of Regulation (EU) 2016/679 ("GDPR").

It supplements the Terms and the Terms of sale, and prevails over them on any question relating to that processing.

2. Capacity of the parties

The Client is the controller for the data it entrusts to the service: the content it writes, the accounts it connects, the members it invites and the people it sends an approval request to. This agreement applies where the Client processes that data for professional purposes; an individual who uses the service for purely personal needs is not a controller within the meaning of article 2, paragraph 2, c), GDPR.

The Publisher is the processor for that processing.

The Publisher is, by contrast, the controller and not the processor for its own customer records — account holder identity, account sign-in and security data, billing, support correspondence —, and for the use it makes, solely for security, support and evidence purposes, of the IP addresses and user agents recorded in the activity log and of approval decisions. That processing falls under the Privacy policy.

3. Subject matter, duration, nature and purpose of the processing

Purpose: to let the Client write, schedule, have approved and publish content to the social network accounts it administers, then consult the history and the status of each delivery and the statistics of the delivered posts, on the Networks whose reading is open.

Nature of the operations: collection — including the reading of the statistics of the delivered posts: without a token, of their public counters, for Mastodon and Bluesky; with the connection's token, through calls that only read, for Facebook, Instagram, Threads, LinkedIn and Pinterest —, recording, organisation, structuring, storage, consultation, transmission to the recipients the Client designates, communication to the Client and its members, and erasure.

Duration: the term of the contract, then the erasure periods of article 11 — 30 days for a closure from the interface, 60 at most for a written request —, except error reports kept by Quiet Guard (annex 20).

Categories of data subjects: the members of the Client's workspace, the people the Client sends an approval link to, the holders of the connected social network accounts, and the people the published content mentions or shows.

4. Processing on documented instructions

The Publisher processes the data only on the Client's documented instructions, including with regard to transfers to a third country or an international organisation, unless required to do so by Union or Member State law to which it is subject; it then informs the Client of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. The following are documented instructions: this agreement, the terms and conditions, and the actions the Client takes in the service — connecting an account, attaching a destination, scheduling a publication, inviting a member, requesting an approval.

Sending content to a Destination is an instruction from the Client. The Publisher chooses neither the content, nor the recipient, nor the time.

If the Publisher considers that an instruction infringes the GDPR or another data protection provision, it informs the Client without delay.

5. Confidentiality

The Publisher ensures that the persons authorised to process the data have undertaken to respect its confidentiality, or are under an appropriate statutory obligation of confidentiality.

Access to a workspace's data is reserved to the people the Client has invited into it and to the Publisher's named operator accounts, strictly as far as operation and support require. The sub-processors in annex 20 that host or administer the server have technical access to it, governed by their data processing agreement.

6. Security

The Publisher implements the appropriate technical and organisational measures described in annex 18, taking account of the state of the art, the costs, the nature of the processing and the risks to the data subjects.

Annex 19 sets out what those measures do not cover. It is published so that the Client takes it into account in its own risk assessment, rather than discovering it after an incident.

7. Sub-processors

The Client gives the Publisher general authorisation to use sub-processors. Those involved as at today are named in annex 20.

The Publisher informs the Client of any addition or replacement at least thirty days before it takes effect, at the workspace owner's email address. The Client has thirty days to object in writing, on reasonable data protection grounds. If the objection is maintained, the Client may terminate free of charge and without penalty.

The Publisher imposes on each sub-processor, by contract, the same obligations as those in this agreement, and remains fully liable to the Client for the performance of their obligations.

The receiving Networks are not sub-processors. Article 10 explains why.

8. Assistance with data subject rights

The service gives the Client the means to consult and delete the data it entrusts, and, on plans that include the API, to read its posts, media and destinations through it, which lets it answer most rights requests itself.

Where those means are not enough, the Publisher assists the Client by appropriate technical and organisational measures, as far as possible and taking account of the nature of the processing.

If a data subject contacts the Publisher directly, the Publisher does not answer in the Client's place: it directs the person to the Client and informs the Client without delay.

One limit must be stated: the Publisher can neither change nor delete content already published on a Network. That is done at the Network, by the Client. The service can delete its own copy and its history, not the post that now lives at the recipient.

9. Data breaches and assistance

The Publisher notifies the Client of any personal data breach affecting the data processed on its behalf, without undue delay and, as far as possible, within forty-eight hours of becoming aware of it. That deadline is designed to leave the Client time to meet its own, which is seventy-two hours.

The notification describes the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences and the measures taken or proposed. Where those details cannot be provided all at once, they are provided in stages, without further undue delay.

The Publisher assists the Client in meeting its obligations under articles 32 to 36 of the GDPR, including for an impact assessment and for prior consultation of the supervisory authority.

10. Location, recipients and transfers

The application, the database and the uploaded media are hosted in France, by OVH SAS; error reports are entrusted to Quiet Guard, hosted in France by OVH SAS, and the backups, encrypted before they are sent, are kept in France by Scaleway SAS. A single sub-processor is established outside the European Union: Laravel Holdings Inc. (Laravel Forge), in the United States, which administers the server and has technical access to it, without hosting any data there; that access is a transfer, governed as the last paragraph sets out. For data the Publisher is itself responsible for, other transfers exist: Cloudflare's anti-bot check, on the contact form and account creation, the team's mailbox, hosted in Switzerland by Proton AG, and, once paid plans open, the payment of subscriptions through Stripe.

One thing that sets this service apart must be stated plainly: publishing means transmitting content to a Network the Client has chosen. That transmission is the very purpose of the contract, and it leaves the Publisher's systems.

The Networks are not the Publisher's processors: they act not on its instructions but on the Client's, and they themselves determine the purposes and the means of what they do with the content received. They are separate recipients, with whom the Client has its own contractual relationship by accepting their terms.

The entities the service addresses are established in the Union: Meta Platforms Ireland for Facebook, Instagram and Threads, LinkedIn Ireland for LinkedIn, Pinterest Europe for Pinterest — with two exceptions. The Mastodon server, which the Customer chooses itself, may be established outside the Union. Bluesky Social, PBC, which hosts the Bluesky accounts opened with it and is their authorisation server, is established in the United States, and is not on the list of participants in the EU–US Data Privacy Framework (consulted on 2026-11-14); a Bluesky account hosted elsewhere sits on a server its holder chose, inside the Union or not. Sending to Bluesky takes place only from its opening in the service, announced to account holders. Once statistics reading for Bluesky is open, the public address of the delivered Bluesky posts is also sent, without a token, to Bluesky Social, PBC, wherever the account is hosted, to read their public counters. Sending to these recipients is carried out on the Customer's documented instructions (article 28, paragraph 3, a, GDPR). No adequacy decision or appropriate safeguard binds the Publisher to Bluesky Social, PBC, nor to the server established outside the Union that an account holder chose: it is for the Customer, as controller, to ensure that the transfer it orders rests on a derogation under article 49 GDPR applicable to the persons the content concerns. Those recipients then carry out, on their own account, transfers outside the Union governed by their own terms and their own safeguards. The Publisher has no control over those transfers and cannot answer for them.

By choosing a Destination, the Client accepts that consequence and remains responsible for the lawfulness of the transmission it orders, in particular for informing the people the content concerns.

The transfers to Laravel Holdings Inc., Cloudflare, Inc. and Stripe rest 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. The one to Proton AG rests on the adequacy decision Switzerland benefits from. Any other transfer would be framed the same way, together with a transfer impact assessment. The Client may obtain a copy of these safeguards on request to bonjour@quietsocial.dev.

11. What happens to data at the end of the contract

Throughout the term of the contract, the Client may consult and delete its data at any time and, on plans that include the API, read its posts, media and destinations through it.

At the end of the contract, at the Client's choice, the data processed on its behalf is returned to it and then deleted, or deleted without being returned. To have it returned, the Client reads its posts, media and destinations through the API itself, on the plans that include it, or asks before closure, by email to the Publisher's contact address, for a copy of its data in a structured, commonly used and machine-readable format, which the Publisher provides within thirty days. The data is then deleted, backups included, within 30 days when closure is requested from the interface, and no later than 60 days after a written request. Only the error reports kept by Quiet Guard follow their own period, shown in annex 20.

Closure is requested by the Client from its workspace settings and carries an effective date. The detailed steps are on the Data deletion page.

Deletion covers the content, the uploaded media, the delivery history, the statistics read, the activity log and the connection tokens. It does not cover the posts already distributed on a Network, which are beyond the service: the Client deletes those at the Network.

Beyond that, the Publisher keeps only what a legal obligation requires it to keep, and only for the duration of that obligation.

12. Documentation and audit

The Publisher makes available to the Client the information needed to demonstrate compliance with the obligations of article 28 of the GDPR.

The Client may have one audit carried out per year, on thirty days' written notice, during working hours, at its own cost, by itself or by an independent auditor who is not a competitor of the Publisher and who is bound by confidentiality. The audit must not disrupt the service or give access to another client's data.

A further audit may be requested following an established data breach affecting the Client.

13. Client obligations

The Client, as controller, warrants that it has a legal basis for the processing it entrusts to the Publisher.

  • Connect only social network accounts it is entitled to administer.
  • Inform the people its content mentions or shows, and hold the necessary authorisations, in particular image rights.
  • Include in content, in a brand name or in a file name no data falling under article 9 of the GDPR, and no bank details.
  • Send an approval request only to an address it legitimately knows, and pass on to the person concerned the information owed to them.
  • Open workspace access only to authorised people, and withdraw it without delay when that authorisation ends.

The service transmits content as the Client writes it. It performs no review, no detection and no automatic redaction: what the Client writes goes out as written.

14. Liability

Each party bears the consequences of its own breaches of this agreement.

The limitation of liability stated in the terms and conditions applies to this agreement. It does not stand in the way of article 82 of the GDPR in relations with data subjects and with the supervisory authority.

The Client indemnifies the Publisher, under the conditions of the indemnity stipulated in the terms and conditions, against any claim, action or penalty resulting from an unlawful instruction from the Client or from a breach by the Client of the obligations of article 13.

15. Term, amendment and governing law

This agreement takes effect when the account is created and remains in force for as long as the Publisher processes data on the Client's behalf.

Any substantial change is notified to the Client at least thirty days before it takes effect. Continuing to use the service after that date constitutes acceptance. A change made necessary by a development in the applicable law takes effect on the date that development comes into force.

This agreement is governed by French law.

16. Annex: description of the processing

Categories of data processed on the Client's behalf:

Category Detail Origin Retention
Workspace members Name, email address, role Entered and invited by the Client Term of the contract
Connections Account identifier and name at the Network, access and refresh tokens, permissions granted; for Bluesky, the connection's own private key, the server hosting the account and the authorisation server The Network's authorisation flow Tokens and key: until revoked; the row remains, without a token, until the account is deleted
Destinations Identifier, name, username and avatar of the Page, account or board The Network's API Once detached, the row remains, without a token, until the account is deleted
Content Text, link, scheduled date Written by the Client Term of the contract
Media Images and videos uploaded by the Client, metadata removed; only the version produced on upload is stored Uploaded by the Client Images: term of the contract. Videos: file erased 30 days after the last publication
Brand logos Image file, metadata removed Uploaded by the Client Until replaced, until the brand is permanently deleted or the account erased
Deliveries Target destination, status, timestamp, error message from the Network The Network's response Term of the contract
Metrics Aggregate counters of the delivered posts — depending on the Network, impressions, reach, likes, comments, shares, quotes, saves, clicks, video views — and the part of the Network's response that carries them, read around day 1, day 7 and day 30 (three days later at most); nothing about the accounts that saw the post or reacted to it Anonymous read, without a token, of the public counters for Mastodon and Bluesky; the Network's API, with the connection's token, for Facebook, Instagram, Threads, LinkedIn and Pinterest That of the publication
Webhooks Event sent to the address the Client declared, status and response received Configured by the Client 30 days
Client approval Recipient email address, decision, reason for refusal Entered by the Client, answered by the recipient Term of the contract
Activity log Author, action, timestamp, IP address and user agent of the request, email addresses named (invited member, approval recipient); serves as proof of actions and approval decisions Actions in the service 12 months
Invitations Email address of the invited person, proposed role, link token Entered by the Client Term of the contract
API and webhooks Name and secret hash of the API keys; address and secret of the webhooks; idempotency keys and the related response Configured by the Client Keys and webhooks: until deleted; idempotency: 24 hours
Own applications Identifier and encrypted secret of the application the Client obtained from a Network Entered by the Client Until deleted
Templates and notifications Texts of publication templates; in-app notifications (approval decision, delivery failure, connection to restore) Entered by the Client; service Term of the contract

17. Annex: what is not asked for

The service does not ask for, require or expect any data falling under article 9 of the GDPR, any data relating to criminal convictions, or any bank details; a subscription is paid on a Stripe page, without the Publisher receiving the card number.

Such data can only reach the service through what the Client enters or uploads. It is for the Client to avoid it, and article 13 says so expressly.

18. Annex: technical and organisational measures

These are the measures actually in place on the date shown at the top of this page.

  • Encryption of traffic in transit on every entry point.
  • Encryption at rest of the access and refresh tokens of social connections, and of the private key specific to each Bluesky connection, excluded from every log and every API response.
  • Separation of data by workspace, enforced at the data access layer and checked by automated tests that fail if one workspace reaches another's data.
  • API authentication by a secret specific to each client, stored hashed, shown once at creation and revocable at any time.
  • Rate limiting on public routes: API, contact form, approval and invitation links.
  • Pages reached through a tokenised link — client approval, team invitation — are served as "noindex" and without a referrer header, so that the address carrying the secret leaks neither to a search engine nor to a third-party site.
  • The public site loads no third-party resource — no remote font, no analytics script, no social network button — with two named exceptions: the contact form and account creation load Cloudflare's anti-bot check, described in annex 20 and on the page devoted to cookies. The payment confirmation page (3-D Secure), behind sign-in, also loads js.stripe.com, only when the bank requires it.
  • The public contact form is protected by that anti-bot check and by rate limiting per address; the messages received are not stored in a database, they go, encrypted in the sending queue, to a mailbox.
  • Emails carrying a tokenised link — invitation, client approval — wait to be sent encrypted in the queue.
  • Conversion of every image on upload and removal of its metadata — position, camera, capture time — before it enters the library; the original is erased from temporary storage within 48 hours.
  • Automatic deletion of expired data, run daily.
  • Administration reserved to named operator accounts, designated by the deployment configuration and not by a role that can be changed from an interface.

19. Annex: what these measures do not cover

The Publisher holds, as at today, no ISO 27001 certification, no SOC 2 report, and no twenty-four-hour security on-call. These points are stated here rather than passed over in silence, so that the Client takes them into account in its own risk assessment.

The token of a client approval link is kept as it is, and not hashed: the link has to be rebuildable in order to be sent again. That is a deliberate choice, offset by the link's limited lifetime, its revocability, and the non-indexing measures described in annex 18.

Once content has been transmitted to a Network, the Publisher has no further means of acting on it. No security measure of the Publisher extends beyond that boundary.

20. Annex: sub-processors and recipients

Authorised sub-processors. Any change is notified under the conditions of article 7.

Sub-processor Address Role Country Transfers
OVH SAS 2 rue Kellermann, 59100 Roubaix Hosting of the application, the database and the media, on a virtual private server France —
Scaleway SAS 8 rue de la Ville l'Évêque, 75008 Paris Storage, for Quiet Guard, of the database and file backups, encrypted on the Publisher's server before they are sent; does not hold the decryption key France —
Spirion SAS (service-smtp.fr) 149 avenue du Maine, 75014 Paris Delivery of the service's emails, including invitations and approval requests sent to the people the Client designates France —
Laravel Holdings Inc. (Laravel Forge) 60 Broad Street, 24th Floor, #1559, New York, NY 10004 Server administration (deployment, configuration); technical access to the server, without hosting any data United States Adequacy decision of 10 July 2023 (EU–US framework), to which Laravel Holdings Inc. adheres

Quiet Guard, published by the Publisher itself, is hosted by OVH SAS and keeps the backups at Scaleway SAS: that is why both providers appear in the table above.

Services published and operated by the Publisher itself. They are not third parties: they are listed here because data leaves the application to be processed there. Changes to them are notified like those of a sub-processor.

Service Role Hosting Retention
Quiet Guard (quietguard.dev) Receiving the application's error reports, to diagnose failures, and keeping its backups (database and files, media included), encrypted on the Publisher's server before they are sent France: reports at OVH SAS, backups at Scaleway SAS Reports: depending on the plan, 90 days at most. Backups: the last 14 of the database, the last 7 of the files
Quiet Metrics (quietmetrics.dev) Audience measurement of the site's public pages. Receives no data processed on the Client's behalf. France, by OVH SAS (backups at Scaleway SAS) 25 months at most

Recipients on the Publisher's own account, for data it is itself responsible for and not a processor of: they receive no data processed on the Client's behalf, other than what the Client itself chooses to send to support.

Recipient Address Role Country Transfers
Cloudflare, Inc. 101 Townsend St., San Francisco, California 94107 Anti-bot check on the contact form and on account creation. Receives the visitor's IP address, the fingerprint of the encrypted connection and the user agent, on those two pages only. Acts as a processor for the check, and as a separate controller for improving its bot detection. United States Adequacy decision of 10 July 2023 (EU–US framework), to which Cloudflare adheres; failing that, standard contractual clauses of 4 June 2021 in its data processing agreement
Stripe Payments Europe, Ltd. / Stripe, LLC 1 Grand Canal Street Lower, Grand Canal Dock, Dublin D02 H210, Ireland Payment and invoicing of subscriptions, once paid plans open. Will receive the account holder's name, email and billing addresses, VAT number and payment method; no data published by the Client. Ireland, and United States (Stripe, LLC) Adequacy decision of 10 July 2023 (EU–US framework), to which Stripe's US entity adheres; standard contractual clauses in Stripe's data processing agreement
Proton AG Route de la Galaise 32, 1228 Plan-les-Ouates, Geneva, Switzerland Hosting of the team's mailbox: contact and support messages, beta access requests. Switzerland European Commission adequacy decision for Switzerland

Recipients designated by the Client. These are not sub-processors: they act on their own account, under the conditions of article 10.

Recipient Receives Country of establishment
Meta Platforms Ireland Limited The posts sent 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 Unlimited Company The posts sent to LinkedIn; also queried, with the connection's token, for the statistics of these posts, once their reading is open Ireland
Pinterest Europe Ltd The pins sent to Pinterest boards; also queried, with the connection's token, for the statistics of these pins, once their reading is open Ireland
The Mastodon server chosen by the Customer The posts sent to Mastodon accounts; also queried, without a token, for the public counters of these posts That of the server
Bluesky Social, PBC The posts sent to the Bluesky accounts it hosts; authorisation server for those accounts; also queried, without a token, once their reading is open, for the public counters of Bluesky posts, wherever the account is hosted, and, for the accounts it hosts, for the existence of a post those counters no longer show United States
The server hosting a Bluesky account, if it is not Bluesky Social's The posts sent to that account; its authorisation server; 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) The public identifier (DID) of the connected Bluesky accounts, without a token, to find the server hosting them 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

No content is transmitted to a Network to which the Client has attached no Destination.