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/politique-de-confidentialite. It applies to the revoria.cloud website, the app.revoria.cloud web application and the Revoria mobile apps.
This policy explains which personal data is processed when you use the revoria.cloud website, the app.revoria.cloud web application and the Revoria mobile apps, why, on which legal basis, with whom, for how long, and how to exercise your rights (Regulation (EU) 2016/679, “GDPR”, and the French Data Protection Act of 6 January 1978).
1. Data controller
- Application concerned: Revoria — revoria.cloud website, app.revoria.cloud web application and Revoria mobile apps.
- Operator and data controller: BTF COMPANY (trade name BTF COMPANY, sole proprietor), publisher of the Revoria service.
- SIREN: 909687691.
- Address: 4 Place du Poirier Baron.
- Contact: Christian — contact@revoria.cloud (contact form, category “Personal data”).
- No data protection officer has been appointed: Christian handles your requests directly. Personal data contact: contact@revoria.pro.
2. In short
- Your data is only used to run Revoria for you. It is never sold, rented or used for targeted advertising.
- Social networks are connected through their official procedure (OAuth): Revoria never collects your social network passwords.
- Payments are processed by Stripe: Revoria never sees your card number.
- Your connection tokens (Google, Facebook, Meta, Apple and other networks) are never sent to artificial intelligence providers (section 9).
- Hosting in the European Union, except calls to artificial intelligence providers when you use those features (section 9).
- General rule: your data is kept during the relationship, then for 1 year, then deleted; some of it much sooner (section 14).
3. Data we process
3.1 Revoria account data
First name, last name, e-mail address, password (stored only as a hash by the application engine, never in plain text), company or workspace name, language, time zone, role in the workspace (owner, administrator, member), notification preferences and profile picture if you add one. The phone number and date of birth requested at sign-up are used to secure the account and can be changed in your profile. If you sign in with Google, Facebook, Apple or TikTok, we receive an account identifier, your name, your e-mail address (for TikTok, the address you type and confirm; for Apple, possibly a private relay address) and, where applicable, your picture: details are in sections 5 (Google) and 6 (Facebook and Apple).
3.2 Payment and invoicing (Stripe)
Plan, billing period, subscription status, payment history, invoices, billing address and VAT number if you provide them. Card details are entered on Stripe’s secure page: Revoria never sees or stores your card number; we only receive a Stripe customer identifier, the card type and last 4 digits, and payment statuses.
3.3 Technical data and logs
IP address, date and time of sign-ins, failed sign-in attempts, browser, sensitive actions (connecting a network, creating an ad, deletions…) in the workspace activity log, technical error logs. Logs contain neither passwords nor access tokens.
3.4 Content and media you upload
Texts, images, videos and sounds of your posts, media library, brand profiles (description, tone, colours, logo, gallery), scheduled posts and drafts, blog articles, requests sent to Samira and documents you attach, files created in the Studio (edited images, voice-overs, music, clips).
3.5 Data obtained via OAuth (social networks and websites)
When you connect a social network or a website, the platform sends us, with your consent, the information needed for the features you use: account identifier and public name, profile picture, list of pages or boards you manage, access tokens and, depending on the network, comments, private messages or statistics. Section 7 gives the details per platform. For websites (WordPress, Shopify, Webflow, Wix, Ghost, Joomla, Drupal, webhook), the credentials or tokens you provide are encrypted by Revoria (AES-256-GCM) before being stored.
3.6 Website, contact form and deletion requests
Messages sent through the contact form (name, e-mail, category, subject, message): they reach us by e-mail and an acknowledgement is sent to you; the website keeps no copy (except, for 10 minutes at most, the fields to correct after an input error). The IP address is used as a hash, for 10 minutes, to limit abuse. Deletion requests sent from the Data deletion page are recorded by the application (encrypted e-mail, scope, tracking number, dates). Website preferences: see the cookie policy.
3.7 Team, devices and account life
- Team chat: messages exchanged between the members of a workspace (text, any attachments, mentions), author, date and read status. They are only visible to the workspace members allowed by their role, are kept for at most 1 year (messages and photos older than that are erased automatically every day), can be deleted earlier by their author or an administrator, and are erased with the workspace.
- Presence: “online” status and last activity date (“last seen”), visible to the members of your workspace; updated while you use Revoria and deleted with your account.
- Roles and permissions: each member’s role (owner, administrator, editor, member or custom role) and granted rights, to limit what each person can see and do.
- Samira auto-replies: only if you turn on automatic mode or keyword rules for a connected account. The comment or message received, with your brand context, is then sent to the AI provider (section 9) to draft the reply, which is published in your name according to your rules; the history of replies sent (date, network, reply text) remains available in Revoria. You can turn this mode off at any time.
- Articles imported from your websites: when you connect a website (WordPress, Shopify, Wix…), Revoria can import your existing articles (title, excerpt, link, date, cover image, categories) to show them in the articles calendar and help Samira match your style. They are deleted when the website is disconnected or with the workspace.
- Devices and sessions: list of your open sessions (device type, browser, operating system, approximate country or city derived from the IP address, sign-in and last activity dates), so that you can see them and close them remotely. Kept during the session, then for 90 days at most with the security logs.
- Cancellation and deletion surveys: optional answers (reasons ticked, free comment) when you cancel your subscription or delete your account. They are only used to improve the service, with no automated decision; they are kept for 1 year at most and dissociated from your identity once the account is deleted.
- Delayed account deletion: a deletion requested from the application is scheduled 30 days later. During that period the account is deactivated and you can recover it by resetting your password (“Forgot password”); after that, deletion is permanent.
3.8 Revoria community forum
- Data: forum display name and profile picture, topics and replies you post (text, any images), dates, reactions and topic subscriptions.
- Visibility: your display name and picture are visible to other users; what you post in the forum is public to all Revoria users (not to the rest of the Internet). Do not post personal or confidential data there.
- E-mails: notification of replies to topics you follow, with an unsubscribe link in every e-mail and a setting in My space › Preferences.
- Deletion: you can delete your posts; when the account is deleted, your forum profile is erased and your published posts are anonymised (“Deleted member”).
3.9 Approximate sign-in location (administration console)
- Data: approximate city or country of the sign-in, derived from headers set by the proxy in front of Revoria or from a local geolocation database, without calling any external service; masked IP address (never the full address), coordinates rounded to city level, device and date.
- Purpose: service security and publisher statistics (detecting unusual sign-ins, user distribution), visible only in Revoria’s administration console. Legal basis: legitimate interest.
- Retention: sign-in locations 12 months, last position 90 days, sign-up location as long as the account exists; everything is erased with the account.
4. Details per data category
For each category, this section lists the exact data processed by the Revoria application, its purpose, legal basis, retention period, recipients, deletion conditions and how to exercise your rights. It describes how the application actually works on the update date shown at the top of the page.
4.1 Revoria account data
- Exact data: e-mail address; name (and first/last name entered when accepting an invitation); password, stored only as a hash (bcrypt); workspace and company name; role in the workspace; language and time zone; notification preferences; profile picture if you add one; phone number and date of birth, optional; onboarding status; sign-up and last sign-in dates.
- Purpose: create and manage your account and workspace, authenticate you, send service e-mails (address confirmation, security, failed post, billing), provide support.
- Legal basis: performance of the contract (GDPR article 6.1.b); optional fields (phone, date of birth, picture): your consent, which you can withdraw at any time by clearing the field (article 6.1.a).
- Retention period: as long as the account exists. An account with no sign-in for 1 year is deleted automatically, after a warning e-mail sent 30 days before (signing in cancels the deletion).
- Recipients and processors: the publisher; the application host (Hostinger International Ltd.); the self-hosted publishing engine, which manages the identifier and hashed password; the e-mail server (SMTP) for service e-mails.
- Deletion: Settings › Data and privacy › “Delete my account” (confirmed with your password, or an e-mail code for an account created with Google, Facebook, Apple or TikTok): deletion scheduled 30 days later, which you can cancel during that period by resetting your password, then permanent. Through the public form: after e-mail confirmation, account deletion is likewise scheduled 30 days later and can be recovered the same way.
- Your rights: Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
4.2 Google OAuth authentication data (“Sign in with Google”)
- Exact data: openid, email and profile scopes (userinfo.email, userinfo.profile); authorization code returned by Google; Google access token, used once on the server to read your profile; signed state parameter and PKCE verifier, kept for 10 minutes at most; technical cookie
rv_oauthlinking the request to your browser during sign-in. - Purpose: sign you in to Revoria with your Google account, without an extra password, and protect that sign-in against forgery.
- Legal basis: performance of the contract, at your request (article 6.1.b).
- Retention period: no Google token is kept: the access token is discarded as soon as the profile has been read; no refresh token is requested for sign-in; state and PKCE: 10 minutes, single use.
- Recipients and processors: Google LLC (identity provider); the application host.
- Deletion: automatic (see above). You can also remove Revoria’s access at any time at myaccount.google.com/connections.
- Your rights: Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
4.3 Google identifier, e-mail address, name and profile picture
- Exact data: Google account identifier (sub); e-mail address, only if Google marks it as verified; full, first and last name; profile picture (avatar), shown in your Revoria profile. This sign-in gives no access to YouTube.
- Purpose: find your Revoria account on later sign-ins; create the account if it does not exist yet; show your name in the application.
- Legal basis: performance of the contract (article 6.1.b).
- Retention period: as long as the link with Google exists: deleted when you unlink it or when the account is deleted (including after 1 year of inactivity).
- Recipients and processors: the publisher; the application host; the self-hosted publishing engine for the account e-mail and name. Never sold or shared for advertising.
- Deletion: Settings › Profile › “Sign-in methods” › “Unlink”; or account deletion (section 4.1).
- Your rights: Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
4.4 Connected social media accounts
- Exact data: for each account you connect: account identifier and public name (page, channel, profile, business profile, board), profile picture, OAuth access and refresh tokens, expiry date, list of pages or profiles you manage when the platform provides it. Details per platform are in sections 5 (Google), 7 (other networks) and 8 (Meta Business).
- Purpose: publish and schedule the content you choose on these accounts, show their statistics, reply to comments and messages where the platform allows it.
- Legal basis: performance of the contract, at your request (article 6.1.b).
- Retention period: while the account is connected; tokens erased immediately when the account is disconnected, with “Delete tokens” or when the workspace or account is deleted.
- Recipients and processors: the publisher; the host; the self-hosted publishing engine, which keeps the publishing tokens; the relevant platform, which receives your posts.
- Deletion: Connected accounts › account menu › “Disconnect”; Settings › Data and privacy › “Delete tokens”; or removing access in the platform’s settings.
- Your rights: Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
4.5 Posts, media, comments, statistics and schedules
- Exact data: texts, images, videos and sounds of your posts and media library; scheduling dates and accounts; drafts and team approvals; identifier and link of published posts; brand profiles; blog articles; requests to Samira and attached documents. Comments: read from the platform to be displayed, kept only in temporary memory, not stored. Private messages (Messenger and Instagram): encrypted. Statistics: read on demand from the platform; the publishing engine caches them for 1 hour at most; no lasting copy. Post history: when you connect an account, Revoria imports from that account only the posts already online (last 10 days, then the periods you browse in the calendar): date, network, public link, caption excerpt limited to 280 characters, media type, counters (likes, comments, shares, views) and a small preview image (JPEG of 40 KB at most, made from the photo or cover image; no video file is downloaded). No comment or comment author name is kept.
- Purpose: prepare, schedule and publish your content; show your results, including for posts made outside Revoria; compute your best posting times; help you reply; when you ask for it, have Samira generate or analyse content.
- Legal basis: performance of the contract (article 6.1.b).
- Retention period: as long as you keep them, then 1 year after the relationship ends; private messages: 90 days at most; documents attached to Samira: 30 days; Studio audio files: 30 days; Studio working files: 24 h; statistics: 1-hour cache at most; imported history: 1 year, and deleted immediately when the account is disconnected or the workspace or account is deleted.
- Recipients and processors: the publisher; the host; the self-hosted publishing engine; the platforms you publish to; AI providers (section 9) only for the requests you make to Samira or the Studio, with only the data needed for that request (for example statistics figures when you ask for an analysis).
- Deletion: deleting an item in the application (post, media, brand, conversation); deleting the workspace or account (Settings › Data and privacy). Posts already published on a network remain there: delete them on the platform if you wish.
- Your rights: Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
4.6 Payment and invoicing
- Exact data: plan, billing period, subscription status, Stripe customer identifier, card type and last 4 digits, payment history, invoices, billing address and VAT number if you provide them, VAT number verification status. Revoria never sees or stores your card number: it is entered on Stripe’s secure page.
- Purpose: collect the subscription, issue invoices, handle plan changes and cancellation, prevent fraud.
- Legal basis: performance of the contract (article 6.1.b); legal accounting and tax obligations (article 6.1.c).
- Retention period: invoices and accounting records: 10 years (article L123-22 of the French Commercial Code); other subscription data: duration of the relationship then 1 year.
- Recipients and processors: Stripe (Stripe Payments Europe Ltd., Ireland); the publisher; tax authorities upon legal request.
- Deletion: when the workspace or account is deleted, the subscription is cancelled and subscription data is erased; invoices are kept for the legal period.
- Your rights: Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
4.7 Technical logs, security and IP address
- Exact data: IP address, date and time of sign-ins, country derived from the IP address, failed sign-in attempts, browser, workspace activity log (sensitive actions: connecting a network, creating an ad, deletions), technical error logs. These logs contain neither passwords nor tokens.
- Purpose: secure accounts (temporary lock after repeated failures, alert on sign-in from a new country), prevent abuse, diagnose errors.
- Legal basis: legitimate interest in securing the service (article 6.1.f).
- Retention period: 90 days, then automatic purge.
- Recipients and processors: the publisher; the host.
- Deletion: automatic after 90 days; activity log anonymised when the account is deleted.
- Your rights: You may object to this processing on grounds relating to your situation (GDPR article 21), subject to security needs. Access, rectification, erasure, objection, restriction, portability: from Revoria (Settings › Profile to correct; Settings › Data and privacy to export or delete), through the form on the Data deletion page, or by e-mail to contact@revoria.cloud (see section 15).
5. Data obtained via Google
The Revoria application uses Google APIs in five cases, always at your initiative and after you agree on Google’s official consent screen. The scopes below are those actually requested by the application’s code; Revoria requests no others.
| Feature | Google scopes requested | Google APIs called |
|---|---|---|
| Sign in with Google | openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile (requested as “openid email profile”) | OpenID Connect (userinfo endpoint) |
| Connect a YouTube channel | https://www.googleapis.com/auth/userinfo.profile, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/youtube.readonly, https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/yt-analytics.readonly | Google OAuth2 userinfo; YouTube Data API v3 (channels.list, playlistItems.list, videos.list, resumable videos.insert, thumbnails.set); YouTube Analytics API (reports.query) |
| Connect a Google Business Profile | https://www.googleapis.com/auth/userinfo.profile, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/business.manage | Google OAuth2 userinfo; My Business Account Management API (account list); My Business Business Information API (locations and their photos); Google My Business API v4 (localPosts: creating posts); Business Profile Performance API (daily metrics) |
| Connect a Blogger blog (separate Google client) | https://www.googleapis.com/auth/blogger | Blogger API v3 (blog list, posts: creation, scheduled publishing, editing, deletion to the trash, reading; page views) |
| Connect Google Search Console (optional, separate Google client) | https://www.googleapis.com/auth/webmasters.readonly | Search Console API (property list, Search Analytics: queries, clicks, impressions, positions) — read only |
5.1 Sign in with Google
- Scopes requested:
openid,https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/userinfo.profile(“openid email profile”). No other scope. - Data accessed: Google identifier (sub), name (first and last name), verified e-mail address (an address Google does not mark as verified is not used) and profile picture (avatar).
- Purpose: create or find your Revoria account, then sign you in securely (signed state parameter, PKCE, cryptographic verification of the Google ID token). No other use.
- Never an automatic YouTube connection: signing in with Google gives Revoria no access to your YouTube channel. Connecting a channel is a separate step (section 5.2) that you start yourself from Connected accounts, with its own Google consent screen.
- Existing accounts: an existing Revoria account is never linked to Google on the basis of the e-mail address alone; linking is done from your profile, once signed in.
- Storage: the identifier, e-mail address, name and avatar URL are stored to link your Google account to your Revoria account, as long as that link exists (section 4.3). The Google access token is used once and discarded; no refresh token is requested.
5.2 YouTube
Connecting a YouTube channel requests exactly the following scopes, and no others: https://www.googleapis.com/auth/userinfo.profile, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/youtube.readonly, https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/yt-analytics.readonly.
| Permission | Data accessed | Action allowed | Visible purpose in Revoria | Why a narrower permission is not enough |
|---|---|---|---|---|
https://www.googleapis.com/auth/userinfo.profile | name and picture of the Google account that owns the channel. | read-only access to the basic profile. | identify the chosen channel and its owner in Connected accounts. | it is already the narrowest profile permission: name and picture, without any access to the channel. |
https://www.googleapis.com/auth/userinfo.email | e-mail address of the Google account that owns the channel. | read-only access to the e-mail address. | tell Google accounts apart when you connect several channels, and warn you when the connection must be renewed. | it is the only permission that provides the e-mail address; it gives access to no other content. |
https://www.googleapis.com/auth/youtube.readonly | channel identity (identifier, name, image); list of uploaded videos (“uploads” playlist) with date, title, link, official thumbnail and public counters (views, likes, comments). | read only: no change or deletion possible. | show the connected channel, its videos and their metadata, the publishing history in the calendar and your best posting times. | it is the read-only YouTube permission; no narrower permission allows reading the channel and its list of videos. |
https://www.googleapis.com/auth/youtube.upload | no reading: file upload only. | upload a video and, if you chose one, its thumbnail. | schedule and upload, on the date you choose, the video you asked to publish, with the chosen title, description, tags and visibility (public, unlisted, private). | it is the narrowest permission that allows uploading a video: it allows neither reading, editing nor deleting existing videos. |
https://www.googleapis.com/auth/yt-analytics.readonly | YouTube Analytics reports of the channel and its videos: views, watch time, subscribers gained or lost, likes, shares. | read-only access to statistics. | show the channel’s statistics in Revoria: views, watch time and engagement. | watch time and subscriber changes are only available in YouTube Analytics, read only; revenue data (a separate permission) is not requested. |
- What Revoria does not do on YouTube: deleting or editing your existing YouTube videos, and managing their comments, is done in YouTube Studio: these actions are not offered for YouTube in Revoria. Revoria publishes nothing without your action or approval.
- Data accessed: name, e-mail address and picture of the Google account; YouTube channel identifier, name and image; list of the channel’s videos (“uploads” playlist) with date, title, link, official thumbnail and counters, for the post history; for videos published from Revoria, their statistics (views, likes, comments); channel statistics provided by YouTube Analytics (views, watch time, subscribers gained or lost, etc.).
- Use: show the connected channel in Revoria; upload to your channel, on the date you choose, the video you prepared, with the title, description, thumbnail, tags and visibility you chose; show the statistics of your videos and channel; show already published videos in your calendar and compute your best posting times. Revoria only reads the existing videos of your channel for these features.
- Storage: OAuth tokens (access and refresh), channel identifier, name and image, in the database of the self-hosted publishing engine, while the channel is connected (erased immediately when the channel is disconnected or with “Delete tokens”); identifier and link of videos published from Revoria, with your posts. Post history: for each video, date, link, title excerpt (280 characters at most), counters and a thumbnail of 40 KB at most, kept for 1 year and deleted as soon as the channel is disconnected; no video file is downloaded. Channel statistics are not stored durably: they are cached for 1 hour at most.
- YouTube services: by connecting a channel you also use YouTube’s services and agree to the YouTube Terms of Service; the Google Privacy Policy apply to data processed by Google. Revoria’s use of the data complies with the Google API Services User Data Policy.
- Revoking access: at any time on the Third-party apps and services page of your Google Account (myaccount.google.com/connections), or in Revoria (section 5.8).
5.3 Google Business Profile
- Data accessed: name and e-mail address of the Google account; list of accounts and business locations you manage (identifier, name, public business address, location metadata, location photo); daily location metrics (website clicks, calls, direction requests, Google Maps impressions on desktop and mobile).
- Use: let you choose the location to connect; publish on that location, on the chosen date, the updates, offers or events you prepared; show the location’s statistics. Revoria does not change business information (name, address, opening hours), reviews or existing photos.
- Storage: OAuth tokens, location identifier, name and photo, in the database of the self-hosted publishing engine, while the location is connected (same erasure rules as YouTube); identifier and link of posts published from Revoria. Statistics: 1-hour cache at most, no lasting copy.
5.4 Sharing of Google data
- Google data is only shared with the processors needed to run the service: the application host (Hostinger International Ltd.) and the self-hosted publishing engine, run by the publisher on its own servers.
- If you ask Samira to analyse your YouTube or Google Business Profile results, the figures needed for that analysis are sent to the AI provider used for your request (section 9), only to produce the answer shown to you. Google OAuth tokens are never sent to an AI provider, and Google data is never used to develop, improve or train artificial intelligence models.
- They may be disclosed to authorities where required by law, or in a merger or transfer of the business, with prior notice to users.
5.5 Limited Use commitments
- Google data is only used to provide or improve the user-facing features described above, which you use in Revoria’s interface.
- It is neither sold nor rented.
- It is not used for advertising: no targeted, retargeted or interest-based advertising.
- It is not used to determine creditworthiness or for lending purposes, and is not used for surveillance.
- It is not used to train artificial intelligence or machine learning models, either by Revoria or by its providers.
- No human reads it, except in the permitted cases: with your explicit consent for specific data (for example for a support request), where necessary for security (investigating abuse), to comply with the law, or when aggregated and anonymised for internal operations.
- It is only shared with the providers strictly necessary for the service (section 5.4).
- Google OAuth tokens stay on the server: they are never sent to the browser or the mobile apps, and never written to logs.
- You can revoke access at any time from Revoria or from your Google account (section 5.8). Disconnecting a channel or a profile in Revoria immediately erases its token; caches and post history follow the periods in section 14.
- Revoria’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Limited Use disclosure: “Revoria’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.”
5.6 Blogger
- Scope requested:
https://www.googleapis.com/auth/blogger, and no other (no Gmail, Drive or YouTube). It is requested by a Google client separate from Sign in with Google and from YouTube, only when you connect a blog in Website › Connected sites. - Data accessed: list of your blogs (identifier, name, address); posts (title, content, labels, status, publication and update dates, link); blog page views over 7 days, 30 days and all time.
- Actions performed, only at your request: publish, schedule, edit and delete (to the Blogger trash, restorable in Blogger) a post; import your existing posts so that Samira learns your brand’s style; show page views.
- Retention: the refresh token is stored encrypted (AES-256-GCM) on the server; access tokens stay in memory for the duration of the operation. When you disconnect the blog, the token is revoked at Google and erased; imported posts follow the periods in section 14.
- Why a narrower permission is not enough: Blogger offers no limited write scope; the only other scope,
blogger.readonly, does not allow publishing, scheduling, editing or deleting a post. - The sharing rules (section 5.4) and Limited Use commitments (section 5.5) apply to this data.
5.7 Google Search Console (optional)
- Scope requested:
https://www.googleapis.com/auth/webmasters.readonlyonly (read only), through a separate Google client, and only if you choose to connect Search Console in Website › SEO. - Data accessed: for the sites you own in Search Console, search queries, clicks, impressions and average positions.
- Purpose: show your sites’ real search performance in Revoria and give you recommendations (Samira). No writing: Revoria changes nothing in your Search Console.
- Retention: token stored encrypted on the server, revoked at Google and erased when you disconnect Search Console; your workspace’s SEO snapshots follow the periods in section 14. Sections 5.4 and 5.5 apply.
5.8 Removing access and deleting Google data
- In Revoria: Connected accounts › channel or location menu › Disconnect; Blogger blog: Website › Connected sites › Disconnect; Search Console: Website › SEO › Disconnect; for Sign in with Google: My space › Profile › Sign-in methods › Unlink.
- Settings › Data and privacy › Delete tokens immediately erases all OAuth tokens of the workspace; Delete my account erases the account and all its Google data.
- At Google: myaccount.google.com/connections › Revoria › “Remove access”.
- Without access to the application: form on the Data deletion page or e-mail to contact@revoria.cloud.
6. Sign in with Facebook or Apple
6.1 Sign in with Facebook
- Permissions requested:
public_profileandemail, nothing else. - Data accessed: Facebook identifier specific to the Revoria app (app-scoped ID), name, profile picture (avatar) and e-mail address when Facebook provides it (it may be missing).
- Purpose: create or find your Revoria account, then sign you in. No other use.
- E-mail address not considered verified: the address sent by Facebook is not treated as verified and no account is merged automatically based on the e-mail. If a Revoria account already uses that address, sign in to that account first, then link Facebook from Settings › Profile › Sign-in methods.
- Never a Meta Business connection: signing in with Facebook connects neither your Pages, nor your Instagram accounts, nor your ad accounts. The Meta Business connection (section 8) is a separate step that you start yourself, with its own Meta screen.
- Storage: identifier, name, e-mail address and avatar URL, as long as the link exists; the Facebook access token is used once to read the profile and then discarded.
- Removal: Settings › Profile › Sign-in methods › Unlink; or, on Facebook, Settings & privacy › Settings › Apps and websites › Revoria › Remove. Meta then notifies us automatically (section 8 and Data deletion page).
6.2 Sign in with Apple
- Data accessed: Apple identifier specific to Revoria (sub), e-mail address — possibly a private Apple relay address if you choose “Hide My Email” — and name, sent by Apple only at first consent.
- Purpose: create or find your Revoria account, then sign you in. E-mails sent to a relay address are forwarded by Apple.
- Existing accounts: no automatic merge based on the e-mail address; linking is done from your profile, once signed in.
- Revocation on account deletion: when your account is deleted, Revoria also revokes its “Sign in with Apple” authorization with Apple.
- Removal: on iPhone, Settings › [your name] (Apple ID) › Sign in with Apple › Revoria › Stop using; or in Revoria, Settings › Profile › Sign-in methods.
7. Data from social networks
Principles common to all platforms: only you decide to connect an account; Revoria only accesses the data needed for the visible features you use (publishing, scheduling, showing your statistics, replying to your comments or messages); nothing is published without your action or approval (Samira suggests, you approve, unless you turn on automatic publishing yourself); data is never sold, used for targeted advertising or profiling, or shared with third parties beyond the processors needed to run the service (section 11) and legal obligations. Publishing goes through Revoria’s publishing engine, self-hosted open-source software, installed and administered by the publisher on its servers in the European Union: it is not a third-party service and your data is not sent to the software’s publisher.
Google & YouTube
- Data accessed: Sign in with Google (optional): Google identifier, name, verified e-mail address and avatar (openid, email, profile scopes). YouTube channel: channel identifier, name and image, name and e-mail address of the Google account, list of your uploaded videos and their statistics (views, likes, comments, YouTube Analytics data), for the youtube.readonly, youtube.upload and yt-analytics.readonly scopes, with userinfo.profile and userinfo.email to identify the channel owner (details in section 5.2).
- Why: to sign you in to Revoria without an extra password; to publish on your channel the videos and Shorts you prepare; to show their statistics in Revoria.
- Actions performed: uploading a video and its thumbnail with the title, description and visibility (public, unlisted, private) you choose, at the date you choose; reading the video list and statistics. Deleting or editing a YouTube video is done in YouTube Studio.
- Authorization: Google’s official consent screen (OAuth 2.0; for signing in to Revoria: signed state parameter and PKCE).
- Passwords: Revoria never sees, asks for or stores your Google & YouTube password.
- Where tokens are stored: Sign in with Google: no token kept (only the identifier, name and e-mail are linked to your Revoria account). YouTube: the access token (and refresh token, when Google issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your Google settings (links on the Data deletion page). Google page: myaccount.google.com/connections.
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on Google: delete them there if you wish.
- Statistics: read from YouTube on demand to be displayed; Revoria does not keep a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
Commitments specific to Google data: data received from Google APIs is only used to provide and improve the visible features you request in Revoria; it is not sold; it is not used for advertising, targeted or otherwise; it is not transferred to third parties, except to the processors needed to run the service, to comply with the law, or with your explicit consent; no human reads it, except with your consent for support, for security reasons or to comply with the law. It is not used to train artificial intelligence models.
Revoria’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google Business Profile
- Data accessed: name and e-mail address of the Google account, list of the business profiles you manage (name, public address of the business, identifier), published updates (business.manage, userinfo.profile, userinfo.email scopes).
- Why: to publish on the profile you choose the updates, offers or events you prepare in Revoria.
- Actions performed: creating a post (text, image, call-to-action button) on the chosen profile, at the chosen date; reading profile statistics when Google provides them. Revoria does not change business information (opening hours, address) or reviews.
- Authorization: you connect the account yourself through Google Business Profile’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Google Business Profile password.
- Where tokens are stored: the access token (and refresh token, when Google issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your Google settings (links on the Data deletion page). myaccount.google.com/connections.
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on Google: delete them there if you wish.
- Statistics: read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
- Data accessed: Sign in with Facebook (optional, section 6.1): identifier, name, e-mail and picture. Publishing: list of the Pages you manage (identifier, name, picture), Page posts and insights (pages_show_list, pages_manage_posts, pages_read_engagement, pages_manage_engagement, read_insights, business_management). Meta Business connection (Facebook Login for Business, if you turn it on, section 8): chosen Pages and ad accounts, comments received and their authors’ public names, Messenger messages (text, attachments, sender name), ad campaigns and their statistics (pages_messaging, pages_manage_metadata, ads_read, ads_management…).
- Why: to publish and schedule on your Pages; to show you, and let you handle, your comments and messages; to show your statistics; to create and monitor the ads you launch.
- Actions performed: publishing texts, photos, videos and links; replying to and hiding comments and replying to messages within Meta’s 24-hour window, only at your request; creating campaigns paused, launched only after your explicit confirmation, within a budget cap.
- Authorization: you connect the account yourself through Facebook’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Facebook password.
- Where tokens are stored: publishing: the access token (and refresh token, when Facebook issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared. Meta connection (comments, messages, ads): tokens encrypted by Revoria (AES-256-GCM) in the application database; private messages are encrypted too.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your Facebook settings (links on the Data deletion page). For the Meta connection: Messages or Comments › Meta connection › Disconnect. On Facebook: Settings › Security and login › Business integrations, or Apps and websites (www.facebook.com/settings?tab=business_tools).
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on Facebook: delete them there if you wish. Meta disconnection: tokens deleted immediately, Pages unsubscribed from notifications (webhooks), stored private messages erased.
- Statistics: Page and ad statistics read on demand, without a lasting copy; the workspace activity log keeps a record of ads created or launched (90 days).
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
- Private messages (Messenger and Instagram Direct): stored encrypted, 100 messages at most per conversation and 90 days at most, then erased automatically. Meta deauthorization and deletion: when you remove Revoria from Facebook, Meta notifies us (
https://app.revoria.cloud/api/revoria/privacy/meta/deauthorize) and access is revoked; a deletion request sent by Meta (https://app.revoria.cloud/api/revoria/privacy/meta/data-deletion) is carried out immediately, and its status can be checked on the Data deletion page with the code provided by Meta.
- Data accessed: Instagram professional or creator accounts (identifier, username, picture, follower count), posts and their insights, comments (instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights, or their “instagram_business_*” equivalents for direct Instagram login); Instagram Direct messages if you turn on the Meta connection (instagram_manage_messages).
- Why: to publish and schedule your photos, carousels, Reels and stories; to show your statistics; to reply to your comments and messages from Revoria.
- Actions performed: publishing the content you choose, replying to comments and messages at your request.
- Authorization: you connect the account yourself through Instagram’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Instagram password.
- Where tokens are stored: the access token (and refresh token, when Instagram issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared. Direct messages and Meta connection tokens: encrypted by Revoria (AES-256-GCM).
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your Instagram settings (links on the Data deletion page). On Instagram: Settings › Security › Apps and websites.
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on Instagram: delete them there if you wish. Stored Direct messages are erased on Meta disconnection.
- Statistics: read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
Threads
- Data accessed: connected Threads profile, posts, insights, mentions, public replies and public conversations, OAuth tokens, for the 8 permissions threads_basic, threads_content_publish, threads_manage_insights, threads_read_replies, threads_manage_replies, threads_manage_mentions, threads_delete and threads_profile_discovery (details and a plain explanation of each in section 8a).
- Why: to publish and schedule your Threads posts, show their insights, read mentions and public replies, reply to them and moderate them from Revoria.
- Actions performed: publishing the posts (text, images, videos) and replies you write; hiding, unhiding, approving or ignoring a reply; deleting one of your posts after confirmation. No private messages.
- Authorization: you connect the account yourself through Threads’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Threads password.
- Where tokens are stored: the access token (and refresh token, when Threads issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your Threads settings (links on the Data deletion page). On Threads: Settings › Account › Websites and apps.
- What is deleted on disconnection: the token is removed from the active integration immediately; Revoria’s Threads cache is deleted immediately, at the latest within 30 days; encrypted backups expire within 90 days at most. Posts already published stay on Threads.
- Statistics: read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
- Data accessed: Pinterest profile (identifier, username, account type, picture), boards (list, names, identifiers), Pins created from Revoria and their statistics, and OAuth tokens (user_accounts:read, boards:read, boards:write, pins:read, pins:write scopes).
- Why: only to connect your account and publish or schedule the Pins you chose, on the board you chose.
- Actions performed: creating Pins (image or video, title, description, link) at the chosen date; reading your boards to offer you a destination. Revoria does not modify or delete your existing boards or Pins and does not follow any account.
- Authorization: you connect the account yourself through Pinterest’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Pinterest password.
- Where tokens are stored: the access token (and refresh token, when Pinterest issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your Pinterest settings (links on the Data deletion page). On Pinterest: Settings › Security and logins › Connected apps (www.pinterest.com/settings/security).
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on Pinterest: delete them there if you wish.
- Statistics: Pin statistics read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
- Pinterest contact: service e-mails are sent from notifications@revoria.cloud; for any question or deletion request about your Pinterest data, write to contact@revoria.cloud. Actual retention: token and identifiers while the account is connected; token erased immediately on disconnection (see “What is deleted” above); Pin content kept in your Revoria media library until you delete it.
TikTok
- Data accessed: Sign in with TikTok (optional): identifier, display name and picture; the e-mail address is the one you type and confirm through a link. Publishing: account identifier, username, display name and picture, account statistics (followers, following, total likes, video count) and list of your videos (user.info.basic, user.info.profile, user.info.stats, video.list, video.upload, video.publish).
- Why: to publish your videos with the privacy settings you choose and show your account figures.
- Actions performed: direct publishing or sending as a draft to the TikTok app, as you choose. Revoria does not read or reply to TikTok comments and has no access to private messages: TikTok does not allow this for apps like Revoria.
- Authorization: you connect the account yourself through TikTok’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your TikTok password.
- Where tokens are stored: Sign in with TikTok: no token kept. Publishing: the access token (and refresh token, when TikTok issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your TikTok settings (links on the Data deletion page). On TikTok: Settings and privacy › Security › Apps and services permissions.
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on TikTok: delete them there if you wish.
- Statistics: instant account figures read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
X (Twitter)
- Data accessed: X account identifier, name, username and picture; posts sent from Revoria.
- Why: to publish and schedule your posts.
- Actions performed: publishing posts (text, images, videos), with the choice of who can reply.
- Authorization: X’s official authorization procedure (OAuth); you can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your X (Twitter) password.
- Where tokens are stored: the access token (and refresh token, when X issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your X settings (links on the Data deletion page). On X: Settings › Security and account access › Apps and sessions (x.com/settings/connected_apps).
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on X: delete them there if you wish.
- Statistics: read on demand when X provides them, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
- Data accessed: profile identifier, name and picture; company pages you administer; posts and their statistics (openid, profile, r_basicprofile, w_member_social, rw_organization_admin, w_organization_social, r_organization_social).
- Why: to publish on your profile or on the chosen company page, and show post statistics.
- Actions performed: publishing the texts, images, videos and documents you prepare.
- Authorization: you connect the account yourself through LinkedIn’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your LinkedIn password.
- Where tokens are stored: the access token (and refresh token, when LinkedIn issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your LinkedIn settings (links on the Data deletion page). On LinkedIn: Settings › Data privacy › Other applications (www.linkedin.com/psettings/permitted-services).
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on LinkedIn: delete them there if you wish.
- Statistics: read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
Reddit and other enabled connectors
- Data accessed: Reddit: username, available communities and flairs, posts sent (identity, read, submit, flair, media). Bluesky, Mastodon, Telegram, Discord, Slack, Twitch, Kick, VK, Farcaster, Nostr, Lemmy, Medium, Dev.to, Hashnode, WordPress, Dribbble, Skool, Whop, Listmonk, Moltbook: identifier and public name of the chosen account, channel or community, and posts sent.
- Why: to publish and schedule the content you prepare.
- Actions performed: publishing only, at the chosen dates.
- Authorization: OAuth when the platform offers it; otherwise a dedicated token, key or app password you create yourself on the platform (for example a Bluesky “app password” or a Telegram bot) — never your account’s main password.
- Passwords: Revoria never sees, asks for or stores your Reddit and other enabled connectors password.
- Where tokens are stored: the access token (and refresh token, when the platform issues one) is stored in the database of the publishing engine — self-hosted open-source software run by Revoria on its own servers in the European Union. Access to this database is restricted to the server; tokens are not shown in the interface and are never shared.
- How to disconnect: in Revoria, open Connected accounts, open the account menu and choose Disconnect; you can also revoke Revoria’s access directly in your the platform settings (links on the Data deletion page). Reddit: www.reddit.com/prefs/apps.
- What is deleted on disconnection: the account is removed from Revoria, its scheduled posts are cancelled and its access (and refresh) token is immediately erased from the publishing engine’s database. The same applies with Delete tokens in Settings › Data and privacy and when you delete the workspace or account. Posts already published stay on the platform: delete them there if you wish.
- Statistics: read on demand when the platform provides them, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
Vimeo
- Data accessed: Vimeo account identifier, name and picture; videos published from Revoria (title, description, visibility, link); comments on your latest videos (author, text, date). OAuth scopes:
public,private,upload,edit,delete,interact. - Why: to publish the videos you prepare, on the chosen date, and let you read comments and reply to them.
- Actions performed: uploading a video with its title, description and visibility; editing or deleting a video published from Revoria, at your request; reading comments and posting your replies.
- Authorization: you connect the account yourself through Vimeo’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Vimeo password.
- Where tokens are stored: OAuth tokens encrypted (AES-256-GCM) in Revoria’s database, on the server only; never sent to the browser or written to logs.
- How to disconnect: in Revoria, Networks › Connected accounts › account menu › Disconnect.
- What is deleted on disconnection: the account is removed from Revoria, access is revoked on the platform, the token is erased and scheduled uploads are cancelled.
- Statistics: read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
Dailymotion
- Data accessed: Dailymotion account identifier, name and picture; videos published from Revoria (title, description, visibility, link). Scopes:
manage_videos,userinfo. - Why: to publish the videos you prepare, on the chosen date.
- Actions performed: uploading a video with its title, description and visibility; deleting a video published from Revoria, at your request.
- Authorization: you connect the account yourself through Dailymotion’s official consent screen (OAuth). You choose which accounts to share and can refuse at any time.
- Passwords: Revoria never sees, asks for or stores your Dailymotion password.
- Where tokens are stored: OAuth tokens encrypted (AES-256-GCM) in Revoria’s database, on the server only; never sent to the browser or written to logs.
- How to disconnect: in Revoria, Networks › Connected accounts › account menu › Disconnect.
- What is deleted on disconnection: the account is removed from Revoria, access is revoked on the platform, the token is erased and scheduled uploads are cancelled.
- Statistics: read on demand, without a lasting copy.
- Requesting erasure: use the form on the Data deletion page (choose “Connected social account”) or write to contact@revoria.cloud. We reply within 30 days at most.
8. Meta Business: Pages, Instagram professional accounts, ads, catalogs and pixels
- Separate from “Sign in with Facebook”: the Meta Business connection is used to manage your business assets; it goes through a dedicated Meta configuration, with its own consent screen, and is never turned on by simply signing in to Revoria with Facebook (section 6.1).
- Assets concerned: Facebook Pages, Instagram professional accounts, ad accounts, catalogs, pixels and the Conversions API. You explicitly select each shared asset in Meta’s window; nothing is selected for you.
- Comments, mentions and statistics: reading the comments and mentions of your Pages and Instagram professional accounts to display them and reply at your request (or according to the auto-replies you turned on); reading Page, post and ad statistics. Comments are not stored durably; statistics are read on demand.
- Connection: “Connect Meta Business” uses Facebook Login for Business (a Meta configuration, never your password). You freely choose the shared assets (Pages, Instagram professional accounts, ad accounts, catalogs, pixels); none is selected for you. The token is encrypted (AES-256-GCM) and isolated per workspace; the permissions actually granted are checked and unauthorised features stay disabled.
- Ads and catalogs: reading campaigns, statistics and spend, and your catalogs’ products and feeds; creations and changes only at your request, paused by default, with explicit confirmation before any spend. Meta notifications (webhooks) are signature-checked and kept for 30 days at most.
- Pixels and Conversions API: only if you explicitly enable it. The events you send require the consent of the person concerned; customer data (e-mail, phone, name, city…) is normalised then hashed (SHA-256) before being sent to Meta, and an event identifier prevents duplicates. For this data about your own customers you are the controller and the publisher acts as processor. No automatic collection takes place.
- Revocation and deletion: disconnect in Connected accounts › Meta Business (tokens deleted, webhook subscriptions removed), or remove the app in Facebook settings (Settings & privacy › Settings › Business integrations or Apps and websites); Meta then notifies us: deauthorisation and data deletion requests are handled automatically, for the Meta Business connection as for “Sign in with Facebook” (see the Data deletion page).
8a. Threads: data, purposes, retention and deletion
This section describes the data processed when you connect a Threads account to Revoria, why, for how long, with whom, and how to delete it.
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 (section 9), 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: section 11.
Legal bases
Performance of the contract, at your request (GDPR, art. 6.1.b), for the connection, publishing, insights, mentions, replies and moderation; legitimate interest (art. 6.1.f) for the activity log and the security of the service.
9. Artificial intelligence (Samira and Studio)
Samira and the Studio tools rely on external artificial intelligence providers, called by the Revoria server only when you use these features. Only the providers configured by the publisher (or by you, with your own key) are used:
| Use | Supported providers |
|---|---|
| Text and conversation (Samira, writing, analyses, replies) | OpenAI (ChatGPT), Anthropic (Claude), Google (Gemini), Mistral AI, DeepSeek, xAI (Grok), MiniMax, OpenRouter, or an OpenAI-compatible provider configured by the publisher |
| Images (creation, editing) and background removal | OpenAI, Google (Gemini), fal, Replicate, remove.bg |
| Voice-overs, music and sounds | ElevenLabs, OpenAI |
| Videos | Runway, Luma AI, Kling, MiniMax, fal, Replicate |
- What is sent: only the content needed for the request (your instructions, an excerpt of your brand profile, the files you attach and, for an analysis you ask for, the relevant figures).
- Never your tokens: OAuth tokens from Google, Facebook, Meta, Apple and the other networks are never sent to AI providers, and neither are your passwords.
- Content from your networks: any use in an AI feature of content from your connected accounts (posts, comments, messages, statistics) results from an explicit action on your part (a request to Samira, clicking “Reply with Samira”, turning on auto-replies), is limited to what is strictly necessary for the visible feature concerned and complies with the platforms’ and providers’ terms. Google data is additionally subject to the Limited Use commitments (section 5.5).
- Threads: Samira drafts a reply only on your explicit click (“Reply with Samira”); auto-replies do not apply to Threads and nothing is sent there automatically. Threads data is never used to train an AI model (section 8a).
- No training: Revoria trains no AI model with your data. Revoria uses the providers’ API offerings; under their terms on the update date, data sent through the API is not used by default to train their models. For OpenRouter or a compatible provider, the end provider’s terms apply.
- Your own API keys (Settings › AI): if you save your OpenAI, Anthropic, Gemini, Mistral, DeepSeek, Grok, MiniMax or OpenRouter key, it is encrypted (AES-256-GCM), never shown again (only the last 4 characters are) and only used for your own requests, without consuming Revoria credits. These calls are also governed by your contract with that provider. You can delete the key at any time.
- Transfers: some providers are based outside the European Union (section 12). Avoid including sensitive data in your requests, and always review what the AI suggests before publishing.
Samira on Telegram
- Linking: optional, at your initiative, through a personal link valid for 10 minutes and usable once. Only private conversations with the Revoria bot are taken into account; groups and unknown people are ignored.
- Chat identifier: stored as a hash (HMAC) to recognise you and as an encrypted copy to reply to you.
- Messages: sent to Samira (and to the AI provider used, as in the app) to produce the reply; they appear in your “Telegram” conversation on the Samira page and are never written to logs. Photos you send are saved to your media library; voice messages are transcribed to text.
- Security: from Telegram, Samira publishes, deletes and puts nothing online; you approve in Revoria. Messages pass through Telegram’s servers, under Telegram’s privacy policy.
- Erasure: the chat identifier and the link are erased when you unlink Telegram (Samira page › Unlink Telegram) or delete your account.
10. Purposes and legal bases
| Purpose | Legal basis (GDPR, art. 6) |
|---|---|
| Creating and managing your account and workspace, providing the service: publishing, scheduling, showing your statistics, comments and messages, Samira, Studio, websites | Performance of the contract (6.1.b) |
| Sign-in with Google, Facebook, Apple or TikTok; connecting your networks and websites | Performance of the contract, at your request |
| Team chat, presence, roles; Samira auto-replies you turn on; articles imported from your websites | Performance of the contract |
| Devices and sessions list, 30-day delayed deletion | Legitimate interest in securing accounts and preventing accidental deletions (6.1.f) |
| Optional cancellation and deletion surveys | Consent, by answering (6.1.a) |
| Collecting payments, invoicing, bookkeeping | Performance of the contract; legal obligation (6.1.c) |
| Securing accounts and the service (logs, IP addresses, attempt limits, abuse detection) | Legitimate interest (6.1.f) |
| Answering your messages and support requests; handling your rights requests | Legitimate interest; legal obligation for GDPR rights |
| Service e-mails (address confirmation, security, invoices, trial end) | Performance of the contract |
| Reminders and usage tips (can be turned off in Settings › Notifications) | Legitimate interest; you can object at any time |
| Website audience measurement, if ever enabled | Consent (6.1.a) |
11. Recipients and processors
Your data is only accessible to the publisher and, within the limits of their task, to the following processors, bound by confidentiality and security commitments:
| Recipient | Role | Location and safeguards |
|---|---|---|
| Hosting of the website and the application (servers, backups) | European Union |
| Publishing engine (self-hosted open-source software) | Open-source software used technically as the publishing engine: connected accounts, tokens, scheduled posts, media. Run by the publisher on its own servers. | Publisher’s servers (EU); nothing sent to the software’s publisher |
| Stripe (Stripe Payments Europe Ltd.) | Payments, subscriptions, invoices, fraud prevention | Ireland; possible transfers to Stripe, Inc. (USA) covered by the EU–US Data Privacy Framework and standard contractual clauses |
| AI providers, only when you use those features | Text: OpenAI, Anthropic, Google (Gemini), Mistral AI, DeepSeek, xAI (Grok), MiniMax, OpenRouter or a compatible provider configured by the publisher. Images, voices, videos, background removal: depending on configuration, OpenAI, fal, Replicate, ElevenLabs, Runway, Luma AI, Kling, MiniMax, remove.bg. | See sections 9 (AI) and 12 (transfers) |
| E-mail sending server (SMTP) | Service e-mails sent from notifications@revoria.cloud; receiving messages at contact@revoria.cloud | E-mail provider configured by the publisher |
| Identity providers (Google, Meta, Apple, TikTok) | Only if you use “Sign in with…”: verifying your identity (sections 5 and 6) | Depending on the provider; transfers covered by the Data Privacy Framework or standard contractual clauses |
| Cloudflare Turnstile | Anti-bot check on sign-up and sign-in forms, only if enabled in the application console | Cloudflare, Inc.; Data Privacy Framework and standard contractual clauses |
| Social networks and websites you connect | Receive the content you publish and the replies you send; they process them under their own policies | Depends on the platform |
| Meta Platforms | Provider of the Threads API, only if you connect a Threads account: receives the posts, replies and moderation actions you carry out (section 8a) | Per Meta; Meta processes this data under its own privacy policy |
| unavatar.io | Website home page demo: optional server-side lookup of a public profile picture from the name typed (can be disabled) | No cookie, no account data |
Data may also be disclosed to authorities where the law requires it. No other transfer takes place.
12. Hosting and international transfers
The website and the application, including the publishing engine and databases, are hosted in the European Union. Three cases may involve a transfer outside the Union:
- Calls to artificial intelligence APIs: when you use Samira or image, voice or video generation, the necessary request (instructions, brand profile excerpt, any attached image or document) is sent to the chosen provider. US-based providers are covered by the Data Privacy Framework or European Commission standard contractual clauses. Some optional providers are based in countries without an adequacy decision (for example China for DeepSeek, MiniMax or Kling): they are only used if enabled and chosen for the request. Avoid including sensitive personal data in your requests.
- Stripe: possible transfers to Stripe, Inc. (USA), covered by the Data Privacy Framework and standard contractual clauses.
- Social networks: the content you publish is sent to the platforms you choose, often based outside the Union, at your request and to perform the service.
13. Security
Encrypted connections (HTTPS only); hashed passwords (bcrypt); Meta tokens, private messages, website credentials, MCP connections and console API keys encrypted with AES-256-GCM; signed state parameter and PKCE for Google sign-in; httpOnly session cookies and CSRF protection; sign-in attempt limits and alerts; role-based permissions in each workspace; logs without tokens or passwords; backups. Details are on the Security and integrations page.
14. Retention periods
General rule: data is kept throughout the relationship, then for 1 year after it ends (account deletion, end of trial or subscription without reactivation), then deleted. Before an inactive account is deleted, a warning e-mail is sent 30 days in advance; simply signing in again cancels it. The shorter periods below are applied automatically by the application.
| Data | Period |
|---|---|
| Account, workspace, brand profiles, content, media, posts | Relationship + 1 year, then deletion; immediately if you delete the item; for a deleted account, from the application or through the public form, 30 days after the confirmed request (recoverable during that period by resetting the password) |
| Team chat messages | At most 1 year (automatic daily erasure); can be deleted earlier by their author or an administrator; erased with the workspace |
| Presence (online, last activity) | Value replaced at each activity; deleted with the account |
| Devices and sessions | Duration of the session, then 90 days at most |
| Articles imported from your websites | While the website is connected; deleted on disconnection |
| Answers to cancellation or deletion surveys | 1 year at most, dissociated from your identity when the account is deleted |
| Network and website connection tokens | While the account is connected; Meta tokens, publishing engine tokens (YouTube, Google Business Profile, Pinterest, TikTok, LinkedIn…) and website credentials erased on disconnection |
| Threads: token, Threads cache (permissions, mentions and replies, 24 hours at most), backups | Token removed immediately on disconnection or request; cache deleted immediately, at the latest within 30 days; encrypted backups expired within 90 days at most (section 8a) |
| Messenger and Instagram Direct private messages | 90 days at most (100 messages per conversation), erased on Meta disconnection |
| IP addresses, sign-in attempts, workspace activity log | IP addresses and sign-in attempts: for as long as the account exists, for security purposes (adjustable duration), erased with the account; activity log: 90 days (automatic purge) |
| Documents attached to Samira | 30 days |
| Studio audio files (voice-overs, music, effects) | 30 days |
| Studio working files (clip previews, edits in progress) | 24 h |
| Confirmation link of a deletion request | 7 days |
| Deletion request (encrypted and hashed e-mail, scope, status, dates) | Account: deletion scheduled 30 days after confirmation (recoverable by resetting the password); network, tokens or workspace: carried out 48 h after confirmation; record reduced to number, scope, status and dates after 1 year |
| Messages received through the contact form | 1 year after the last exchange |
| Invoices and accounting records | 10 years (article L123-22 of the French Commercial Code) |
| Approximate sign-in locations (administration console) | Sign-in locations 12 months; last position 90 days; sign-up location as long as the account exists |
| Telegram link (chat identifier) | Until unlinking or account deletion |
| Forum profile and posts | As long as the account exists; on deletion, profile erased and posts anonymised |
| Blogger, Google Search Console, Vimeo and Dailymotion tokens | As long as the connection exists; revoked and erased on disconnection |
| Cookies and browser storage | See the cookie policy |
15. Your rights
- Access: obtain a copy of your data.
- Rectification: correct inaccurate data (most can be edited in your profile).
- Erasure: have your data deleted (see the Data deletion page).
- Objection: object to processing based on legitimate interest, including reminders.
- Restriction: ask for a processing operation to be temporarily frozen.
- Portability: receive the data you provided in a structured, machine-readable format (JSON export in Settings › Data and privacy).
- Withdrawal of consent at any time, and instructions on what happens to your data after your death.
How to exercise them: from Settings › Data and privacy in the application; through the contact form (category “Personal data”); or by e-mail to contact@revoria.cloud, preferably from your account address. We may ask you to confirm your identity. We reply within one month, which may be extended by two months for a complex request (you will be informed).
Complaint: if you believe your rights are not respected, you can lodge a complaint with the French data protection authority (CNIL), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France — www.cnil.fr/en/.
16. Deletion, portability and revoking integrations
- Portability: Settings › Data and privacy › export my data downloads a readable JSON file (account, workspace, preferences, activity log about you, deletion requests), without any token or password.
- Revoking an integration: Connected accounts › account menu › Disconnect. The account is removed, its scheduled posts are cancelled and its OAuth token is erased immediately. You can also remove access on the platform (Google, Meta, Threads, Pinterest, TikTok…): links on the Data deletion page.
- Delete tokens (Settings › Data and privacy): erases at once all the workspace’s OAuth tokens and website credentials.
- Deleting the account: from Settings, or without access to the application with the form on the Data deletion page (tracking number, timelines and retained items are detailed there).
17. Contact and complaints
For any question about your personal data: contact@revoria.pro (contact form, category “Personal data”). Data controller: BTF COMPANY. You can also lodge a complaint with the CNIL: www.cnil.fr/en/.
18. Cookies
The website and the application only use essential cookies and local storage (session, security, language, display). No advertising cookie, no social network tracker. Full list and settings: cookie policy.
19. Changes and history
This policy evolves with the service. The last update date is shown at the top of the page; for significant changes, you are informed in the application or by e-mail before they take effect.
| Date | Change |
|---|---|
| November 10, 2026 (v2.6.0) | Section 5: Blogger (5.6, blogger scope, separate Google client) and optional Google Search Console (5.7, webmasters.readonly scope, read only); access removal renumbered 5.8. Section 7: Vimeo and Dailymotion. Section 9: Samira on Telegram. Sections 3.8 (community forum) and 3.9 (approximate sign-in location, administration console); periods added to section 14. Publishing engine described without naming the software. |
| November 8, 2026 (v2.4.0) | Policy hosted on revoria.cloud (official address shown at the top); Google section at the stable anchor #donnees-google, with one row per YouTube permission (data, action, purpose, why a narrower permission is not enough) and expanded commitments; OAuth tokens erased immediately when an account is disconnected, for every network; new sections 16 (deletion, portability, revocation) and 17 (contact and complaints). |
| November 8, 2026 (v2.3.1) | New section 8a “Threads”: the 8 permissions explained, data and purposes (profile, posts, insights, mentions, public replies and conversations, tokens), no sale, no behavioural advertising, no AI training, Samira only on click, retention (token removed immediately, cache within 30 days, backups within 90 days), revocation, Threads data-deletion callback, Meta Platforms as API provider. |
| November 7, 2026 (v2.3.1) | Separate sections for Sign in with Google, Facebook and Apple; exact YouTube scopes (youtube.readonly, youtube.upload, yt-analytics.readonly) with the data and operations of each; Meta Business section separate from Facebook sign-in; new artificial intelligence section (supported providers, OAuth tokens never sent, personal keys); team chat, presence, Samira auto-replies, imported articles, devices and sessions, surveys and 30-day delayed deletion. |
| November 7, 2026 (v2.3) | Added imported post history (no video downloaded, 40 KB previews, 1 year), the use of YouTube video lists for that history, and the Meta Business section (ads, catalogs, pixels, Conversions API with SHA-256 hashing and consent). |
| November 7, 2026 (addendum) | Added per-category details (exact data, purpose, legal basis, retention, recipients, deletion, rights) and the “Data obtained via Google” section listing the scopes actually requested (Google sign-in, YouTube, Google Business Profile); automatic deletion of accounts inactive for 1 year now applied by default; application fonts served from our own servers (no more Google Fonts calls). |
| November 7, 2026 | Overhaul: one section per social network (Google, YouTube, Google Business Profile, Facebook, Instagram, Threads, Pinterest, TikTok, X, LinkedIn, Reddit…), Google Limited Use commitments, mention of the self-hosted publishing engine, retention periods checked against the code, deletion form with tracking number. |
| November 6, 2026 | Previous version: Meta and TikTok data, private messages, retention periods. |