Last updated: November 22, 2026.
Revoria is a digital service published under the trade name BTF COMPANY, operated by a sole proprietor. Contact: Christian. SIREN: 909687691.
Official address of this document: https://revoria.cloud/securite-et-integrations. It applies to the revoria.cloud website, the app.revoria.cloud web application and the Revoria mobile apps.
You trust us with access to your social networks, your websites and your brand content. Here is what Revoria actually does to protect them.
1. OAuth 2.0 connections, without passwords
Networks are connected through each platform’s official authorization procedure (OAuth 2.0, or OAuth 1.0a for X): you sign in on the platform, which issues Revoria a token limited to the permissions you accept. Revoria never collects your social network passwords. The return from the authorization window is protected by a signed, single-use state parameter valid for 10 minutes and, for Google sign-in, by PKCE (S256). Redirect URLs are fixed and HTTPS-only.
2. Encryption and protection of secrets
- HTTPS only between your browser or the mobile apps and Revoria.
- AES-256-GCM (key derived from a server secret) for: Meta connection tokens (comments, messages, ads), private message text and sender names, connected website credentials (WordPress, Shopify, Webflow, Wix…), MCP connection tokens (Claude, ChatGPT) and API keys stored in the admin console.
- Publishing tokens: kept in the database of the self-hosted publishing engine, on our servers in the European Union, accessible only to the server.
- Passwords of Revoria accounts hashed with bcrypt by the application engine, never stored in plain text.
- Session: httpOnly, secure cookie, double-token CSRF protection, permissions checked on every request according to role (owner, administrator, member).
- Sign-in: a sum to solve, e-mail alert after 3 failures, 15-minute lock after 8 failures, per-IP limit; Cloudflare Turnstile anti-bot check if enabled.
- Meta notifications: each incoming call is verified by its
X-Hub-Signature-256signature.
3. Logs without secrets
Technical logs and the activity log contain neither passwords nor access tokens; where needed, tokens are shown masked (last characters only). IP addresses and sign-in traces are kept for as long as the account exists, for security purposes, and erased with the account.
4. Revoking a connection
In Revoria: Connected accounts › Disconnect for a network, Messages › Meta connection › Disconnect for the Meta connection, Sites for a website, Settings › MCP connections for Claude or ChatGPT, and Settings › Data and privacy to delete tokens. On the platform: direct links on the Data deletion page.
4a. Threads: security, data and revocation
This section describes how Threads data and tokens are protected, and how to revoke Revoria’s access.
Operator: BTF COMPANY / BTF COMPANY, sole proprietor. Contact: contact@revoria.cloud.
The 8 Threads permissions requested
| Permission | What it allows, in plain words |
|---|---|
threads_basic | Read your connected Threads profile (identifier, username, name, picture, biography) and the list of your own posts. |
threads_content_publish | Publish or schedule the posts you prepare in Revoria, and the replies you write. |
threads_manage_insights | Show, read-only, the insights of your account and posts (views, likes, replies, reposts, followers). |
threads_read_replies | Read the public replies to your posts and the public conversations that follow, to show them in Revoria. |
threads_manage_replies | Reply from Revoria, hide or unhide a reply, approve or ignore a pending reply, when Threads allows it. |
threads_manage_mentions | Show the public posts that mention your account, so that you can read them and reply. |
threads_delete | Delete one of your own posts, only after your explicit confirmation. |
threads_profile_discovery | View the public profile and public posts of an account whose exact username you type; manual lookup, nothing is stored. |
You grant these permissions yourself in Threads’ official window (OAuth); Revoria never sees your password. A feature whose permission was not granted stays disabled.
Data processed and purposes
- Connected profile: Threads identifier, username, name, picture and biography. Purpose: show the connected account, link it to your workspace and check the permissions granted.
- Posts: texts, images and videos you prepare, and the list of your posts (text, link, date, media type, number of replies). Purpose: publish, schedule and show your posts, and delete one of them after your confirmation.
- Insights: metrics of your account and posts, read-only. Purpose: show you how they perform. Read on demand, without a lasting copy.
- Mentions: public posts from other accounts that mention yours (text, author’s username, date, link). Purpose: read them and reply from Revoria.
- Comments and replies: public replies to your posts and public conversations (text, author, date, link, hidden or pending status). Purpose: read them, reply from Revoria and moderate them (hide, unhide, approve, ignore).
- Public profile lookup: the exact username you type, then the public profile and public posts returned by Threads. Purpose: show them to you once; nothing is stored.
- OAuth tokens: access token issued by Threads and its expiry date. Purpose: call the Threads API on your behalf. Stored on the server, in the database of Revoria’s self-hosted publishing engine (European Union), read at each call; never displayed, never written to logs, never sent to AI providers.
- Activity log: for each reply, moderation or deletion, who, when, which account, which action and the object identifier, without message text or token. Purpose: security and traceability in your workspace.
Our commitments
- No sale: Threads data is never sold, rented or transferred.
- No behavioural advertising: it is never used for advertising, targeted or behavioural, or for profiling.
- No AI training: Revoria never uses Threads data to train an artificial intelligence model.
- Samira only on your click: Samira drafts a reply only when you click “Reply with Samira”; the reply concerned and your brand context are then sent to the AI provider (privacy policy), and you review the draft before sending it. No automatic reply is ever sent on Threads.
- Nothing without your action: no post, reply, moderation or deletion happens without your action; deleting a post requires explicit confirmation.
- No private messages: Revoria does not read or send any Threads private messages; only public conversations are involved.
Retention periods
- Access token: removed from the active integration immediately on disconnection or deletion request; it is never used again.
- Revoria’s Threads cache (check of the permissions granted, short-lived cache of mentions and replies, 24 hours at most): deleted immediately, at the latest within 30 days.
- Connected profile: kept while the account is connected to your workspace; after a deletion request, erased with the Threads cache, at the latest within 30 days.
- Encrypted backups: they expire after 90 days at most; deleted data disappears from them by then.
- Activity log (replies, moderation, deletions): 90 days, automatic purge.
- Contractual and accounting data (Revoria account, subscription, invoices): kept according to their legal basis (invoices: 10 years).
- Posts already published: they stay on Threads; delete them from Revoria (after confirmation) or in Threads.
Disconnecting Threads and revoking access
- In Revoria: Connected accounts › Threads account menu › Disconnect. The token is removed immediately and a confirmation is shown.
- In Threads: Settings › Account › Websites and apps, then remove Revoria.
- Threads offers no public token-revocation endpoint: to withdraw the authorization at Meta, use this Threads setting; disconnecting in Revoria erases the token on our side.
- Reconnecting the same account replaces the token in the same integration: your scheduled posts are kept.
Deleting your Threads data
- Request: the form on the Data deletion page (choose “Connected social account”), Settings › Data and privacy › Delete tokens, or an e-mail to contact@revoria.cloud. We reply within 30 days at most.
- Removal in Threads: if you remove Revoria from your Threads websites and apps, Meta notifies Revoria at the uninstall address
https://app.revoria.cloud/api/revoria/threads/uninstall; the token is removed from the active integration at once. - Threads data-deletion callback: if you also ask for your data to be deleted, Meta sends the signed request to
https://app.revoria.cloud/api/revoria/threads/data-deletion. Revoria verifies the signature, deletes the Threads data as described above and returns a confirmation code with a tracking link.
Technical providers
- Meta Platforms: provider of the Threads API; receives the posts, replies and moderation actions you carry out and processes your Threads data under its own privacy policy.
- Hosting: Hostinger International Ltd., server of the application and of the self-hosted publishing engine, in the European Union.
- AI provider chosen for Samira: only when you click “Reply with Samira”.
- Full list of recipients and processors: privacy policy.
Security measures
- The Threads token stays on the server: it is never sent to the browser or the mobile apps.
- Uninstall and deletion requests sent by Meta are accepted only if their signature (signed_request) is valid.
- Each call is limited to the Threads account of your workspace and checked on the server according to your role (read, reply, publish); public profile lookup is strictly rate-limited.
5. You stay in control
- Samira suggests, you approve: “I review” mode is on by default.
- Meta ads are created paused and only launched after explicit confirmation, within a budget cap, by an owner or administrator.
- Every sensitive action is recorded in the workspace activity log.
6. Reporting an incident or a vulnerability
Write to contact@revoria.pro or use the contact form (“Security” category), describing the problem, the URL concerned and the steps to reproduce it. Never send a password, API key or token. We acknowledge receipt within 72 business hours, keep you informed of the fix and ask you not to disclose the issue before it is fixed. Do not test on other users’ accounts and do not run load tests. In the event of a personal data breach, we notify the CNIL within 72 hours and the people concerned where the law requires.
7. Supported platforms
- FacebookPages: posts, stories, photos, videos, and links.
- InstagramBusiness or creator accounts: posts, carousels, Reels, and stories.
- TikTokShort videos, with your privacy settings.
- YouTubeVideos and Shorts: title, description, visibility.
- LinkedInPersonal profile and company page.
- XShort messages, with a choice of who can reply.
- ThreadsConversations that continue from Instagram.
- PinterestPins saved to the board of your choice.
- Google Business ProfileUpdates for your business profile.
- BlueskyPosts on the decentralized network.
- MastodonPosts on your instance.
- RedditPosts in your communities.
- TelegramMessages in your channels.
- DiscordAnnouncements in your servers.
- SlackMessages in your team channels.
- TwitchAnnouncements for your channel.
- KickAnnouncements for your channel.
- VKPosts on your page.
- FarcasterPosts on Farcaster (Warpcast).
- NostrNotes on the Nostr protocol.
- LemmyPosts in your communities.
- MediumBlog posts.
- Dev.toArticles for developers.
- HashnodeTechnical blog posts.
- WordPressArticles on your blog.
- DribbbleYour visual creations.
- SkoolPosts in your community.
- WhopAnnouncements for your community.
- ListmonkNewsletter campaigns.
- MoltbookPosts on Moltbook.
- TumblrPosts on your Tumblr blog.
- MeWePosts on your profile or groups.
Websites: WordPress / WooCommerce, Shopify, Wix, Webflow, Ghost, Joomla, Drupal and any site reachable by webhook. External AI assistants: Claude and ChatGPT via MCP, with per-connection permissions checked on every call. Detailed data per platform: privacy policy.