Skip to content
Quiet Social

Documents

Access revocation

Withdrawing Quiet Social's permission to publish, from our interface or directly from Meta, LinkedIn, Threads, Pinterest, Mastodon and Bluesky.

Last updated: 20 November 2026

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

From Quiet Social

In your workspace, open social connections and revoke the one you want. For a Meta connection, except in the case described in the next paragraph, we first ask Meta to withdraw the authorisation, then destroy the token on our side: when Meta confirms, both sides are in the same state. If Meta rejects the connection's token — expired, invalidated, or with changed permissions — we ask for the withdrawal again with our own application credentials, which Meta also accepts for this request. If Meta answers that you had already removed Quiet Social from your account, there is nothing left to withdraw there and we destroy our copy. Other than in that case, for as long as Meta does not confirm the withdrawal, nothing is changed here and the screen reports that the revocation did not go through: it needs to be run again, after reconnecting the account if necessary. If we no longer hold a token for that connection, there is nothing to ask Meta for: we mark it revoked, and that is all that is left for us to do.

With Meta, one authorisation covers an entire Facebook account: withdrawing it withdraws it everywhere. So when that same Facebook account still publishes from another workspace, we ask Meta for nothing: the connection is revoked in your workspace only, the other workspace keeps publishing, and the screen tells you so.

LinkedIn, Threads and Pinterest give an application like ours no way to withdraw, by itself, the authorisation you granted it. For these three networks, we destroy our copy of the token, but the authorisation stays listed with the provider until you remove it from your account settings, or until it expires.

For a Mastodon connection, we ask its server to revoke the token, then destroy it on our side; until the server confirms, nothing changes here. As with Meta, the same Mastodon account connected from several workspaces holds a single authorisation there: while it still publishes from another workspace, we ask the server for nothing. A server we no longer call, or that has not answered for thirty days, cannot receive that request: we then destroy our copy of the token only.

For a Bluesky connection, we ask the account's authorisation server to revoke the session opened for that connection, then destroy its tokens and its key on our side; if the server is temporarily unreachable, nothing changes here and the revocation has to be run again. Unlike Meta and Mastodon, each connection has its own authorisation there: revoking it in your workspace does not touch the one another workspace opened with the same account. A server that has not answered for thirty days, that refuses the request or that offers no way to revoke cannot receive it, nor can a session opened with a Quiet Social key withdrawn since: we then destroy our copy only, and the session stays listed in your Bluesky account, from which you can remove it. On an account hosted by Bluesky, access tokens already issued remain valid for up to fifteen minutes after revocation; ours is destroyed at once.

From Meta

You can also withdraw access without going through us, from your Facebook account settings, under the apps and websites connected to your account. Remove Quiet Social there.

That route is immediate and does not depend on us. It applies to the whole Facebook account: it also cuts that account's connections in other workspaces. It leaves on our side the connection — or the connections, if that account is linked to several workspaces — that the next check flags as needing a reconnection, and that you can restore by running the authorisation flow again.

From LinkedIn

From your LinkedIn account settings, under authorised applications, remove the access granted to Quiet Social.

As with Meta, the effect at the provider is immediate.

From Threads

From your Threads account settings, open "Account", then "Website permissions": under "Active", remove Quiet Social.

That route does not depend on us. It leaves a connection on our side that can no longer publish, and that you can restore by running the authorisation flow again.

From Pinterest

From your Pinterest account settings, in the "Security" section, which lists the apps connected to your account, remove the access granted to Quiet Social.

That route does not depend on us. It leaves a connection on our side that can no longer publish, and that you can restore by running the authorisation flow again.

From Mastodon

On your Mastodon server, open "Preferences", then "Account" and "Authorized apps": click "Revoke" under Quiet Social.

That route does not depend on us and applies to the whole account: it also cuts that account's connections in other workspaces. It leaves on our side a connection that can no longer publish, which you can restore by running the authorisation flow again.

From Bluesky

If your account is hosted by Bluesky, open bsky.social/account and sign in, then the "Apps" section: choose Quiet Social and click "Revoke access". Quiet Social may appear there several times, once per workspace that connected this account. If your account is hosted by another server, use that server's account management.

That route does not depend on us. It withdraws only the authorisation you chose, and leaves on our side a connection that can no longer publish, which you can restore by running the authorisation flow again. On an account hosted by Bluesky, it may take up to fifteen minutes to take effect: a post scheduled in that interval may still go out.

What revocation does

A connection revoked from Quiet Social immediately stops being able to publish. Scheduled posts that depend on it are not delivered: they are flagged as needing a reconnection, rather than retried until they run out of attempts. The same applies when you withdraw access from the network itself, except that we only learn of it from the network's first refusal: at the daily check of connections, or at the next post, which is then flagged in the same way. For an account hosted by Bluesky, that refusal may only come fifteen minutes after the withdrawal.

Posts already delivered stay online on the networks concerned: revocation withdraws access, it does not erase the past. Statistics reading also stops for the posts of a connection that is no longer active with us — revoked, expired or awaiting reconnection —; statistics already read remain, until the post is deleted in Quiet Social. A withdrawal made from the network makes the reads made with your token fail as soon as the network rejects it, and nothing is then read; for Mastodon and Bluesky, read without a token, reading stops only when the connection stops being active with us.

Revoking does not erase your data here. For that, see the Data deletion page.