autopostSocial media autoposting

autopost Service Privacy Policy

Version 1.3 of 10 November 2026

1. Controller and what this document is

This Policy is an Annex to the Riadov Systems Privacy Policy (the “main Policy”): riadov.systems/privacy/. It describes what personal data autopost processes — the website and panel at autopost.riadov.app, the Telegram Mini App and the Service’s Telegram bot (the “Service”) — why, who receives it, how long it is kept and how you exercise your rights. General rules — in particular on support and backups — are in the main Policy; the names and lifetimes of cookies are in the Riadov Systems Cookie Policy. The terms “Subscription”, “account”, “project” and “topic” have the meaning given in the Service Terms.

The controller of personal data is:
Riadov Systems Vladyslav Riadov
NIP: 6972395549 · REGON: 526790012
Address: ul. Jana Ostroroga 1a/28, 64-100 Leszno, Polska
E-mail: [email protected] · Telegram: @Riadov_Systems

We process data in accordance with Regulation (EU) 2016/679 (GDPR) and Polish law. This Policy is information we are obliged to provide to you (Art. 13 GDPR), not consent to data processing.

2. What data we process

  • Account: your name in the Service, e-mail (if GitHub passed it on when you signed in), language (chosen in the panel or passed by Telegram when you sign in), the dates of creation and modification; sign-in methods — Telegram or GitHub, with the identifier in that system (for GitHub, also the login) and the time of last use; sessions — the date of start, of last activity and of expiry (the session key itself is stored only as a fingerprint).
  • Telegram: Telegram ID, the identifier of the private chat with the bot and a flag if you have blocked the bot. When you sign in through the Mini App, the Service verifies the Telegram launch data and keeps only their fingerprint for the time needed to protect against replay.
  • Projects and team: the owner of the account; the name, time zone and profile of a project and whether it is switched on; members of the account’s team — role and access to all or to selected projects; invitations — role, access, who invited, validity period, who accepted the invitation and when. An invitation is a link, so the Service does not collect the invitee’s e-mail.
  • Project content: topics — description, brand profile, style and text rules; campaigns; sources — snapshots of files from the chosen GitHub repositories (documentation, code, the path tree and commit messages — without their authors), website pages and RSS, your texts, files and photos; the project card — a description of a connected repository compiled by artificial intelligence: what the product does, for whom, which of its features are useful to people and what has changed; media files you upload, information about them (type, size, width and height, duration) and their derivatives — previews, copies without the file's metadata and copies prepared to a platform's requirements (for example, re-encoded video); drafts, platform variants, revisions and approvals — who approved and when.
  • Connections: for each platform — the identifier and name of the account, page or channel, the permissions granted, the connection status; access keys to platforms are stored only in encrypted form. Except for TikTok, the Service also stores a small copy of the profile picture of the account, page or channel (avatar), so that you can recognise the connected account. For Telegram channels and groups — the identifier, type and name of the chat, its public username (@username) and a small copy of the chat photo, if any (so that you can recognise the chat in the list), the bot’s status in it and its rights, and the link between the chat and those users of the Service who are its administrators: only an administrator of a chat can connect it. The link is set up when you pick the chat in the bot (the Service checks through Telegram that very chat — whether you are its administrator and whether the bot is there with the right to post), or when the bot is added to the chat: then the Service receives from Telegram the chat’s list of administrators — only their Telegram IDs — and matches it against the Telegram IDs of the Service’s users; the list itself is not stored, and the Service does not store data of administrators who are not its users. If another person adds the bot for you using your one-time link, the Service keeps that person’s Telegram ID only together with the link — until it is used or expires (7 days) — to know for whom the bot was added; otherwise the Service does not record who added the bot. To connect a channel or group to a project, the Service checks through Telegram whether you are currently the owner or an administrator of that chat — only when syncing and saving; the result of the check is not stored, and if you are no longer an administrator, the link is removed. For GitHub — the GitHub App installation and the chosen repositories.
  • Publications: the schedule, status and results of publications, the link to the published post, the failure reason reported by the platform; your confirmation where the platform requires it (for example, TikTok declarations or a more expensive post on X) — who confirmed what and when.
  • Subscription and usage records: the account’s payment status passed on by Stripe — plan, status and period of the Subscription, the number of additional projects (“+1 project”), a cancellation or a scheduled downgrade; purchased packs of X units (number of units, payment number and time) and their use; the account’s limits and usage (projects, members, posts, generations, X units, platform API costs), records of artificial intelligence costs without personal data. The Service does not store payment card data.
  • Payments (Stripe): in the Service — your account’s Stripe customer identifier and the identifiers of the Subscription and of a scheduled plan change in Stripe; in Stripe — the contact details you enter on the payment page (e-mail, name, an address where needed), the payment method (only Stripe sees the card details), the Subscription, invoices and payments (type, amount, currency, status); to the payment session, the Subscription and the payment we add the Service account identifier, the version number of the Service Terms and the version of the checkbox text, and the tick of the checkbox before payment is stored by Stripe. We do not collect invoice data (company name, tax number, company address) during payment. The Service shows invoices to the account owner by fetching them from Stripe each time and does not keep a copy of them.
  • Project activity log: who (member identifier) did what in the project and when — without secrets or source content.
  • Privacy: an account deletion request until it is carried out; inactivity warnings and notices of new document versions — what was sent and when, without the text; a log of data requests without personal data; a log of completed deletions — only a fingerprint of the identifier computed with a secret key, the date and the scope.
  • Temporary data: one-time sign-in and invitation links and tokens, bot button tokens, bot request deduplication.
  • Technical logs: the time and type of events, internal identifiers and error codes — without access keys, source content or post texts.

Browser. The panel and the Mini App set the necessary sign-in cookies and store in the browser’s storage (localStorage) the chosen theme, the language and your choice on the cookie banner; the website pages store there the chosen theme and your choice on the cookie banner. The choice on the banner is shared by the website and the panel. On the website pages, in the panel and in the Mini App we may collect and analyse your actions — sign-ins, time spent, navigation and clicks — and use remarketing, that is, showing ads to people who have already visited the website, the panel or the Mini App, for analysing behaviour, improving the Service and advertising. For this we may use analytics and advertising cookies — Google Analytics 4 and Meta Pixel. On the cookie banner you can choose “Accept” or “Necessary only”, and change your choice with the “Cookie settings” button at the bottom of the website, panel and Mini App pages. The types of events, the names of the records and their lifetimes are in the Riadov Systems Cookie Policy.

3. Purposes and legal bases of processing

  • Account, sign-in, projects and team, sources, draft generation, analysis of GitHub repositories, approval, publication, notifications in the bot, Subscription, payments through Stripe, invoices in the panel and limits — performance of a contract (Art. 6(1)(b) GDPR).
  • Payment records, invoices and records for accounting and tax purposes, handling your data request — a legal obligation (Art. 6(1)(c) GDPR). We issue an invoice at your request through support: the data you send for it are used only for the invoice and for accounting.
  • The project activity log, evidence of the accepted Terms and of the request to start the service immediately after payment, evidence of notices of new versions, the log of completed deletions (to repeat deletions after a restore from a backup), automatic deletion of inactive accounts, security and stable operation of the Service, investigating failures using technical logs — the legitimate interest of the controller (Art. 6(1)(f) GDPR). The checkbox before payment is part of the contract, not consent to data processing.
  • Analysing behaviour on the website pages, in the panel and in the Mini App and improving the Service (Google Analytics 4), measurement of advertising and remarketing — showing ads to people who have already visited the website, the panel or the Mini App (Meta Pixel) — your consent (Art. 6(1)(a) GDPR); you can withdraw it at any time with the “Cookie settings” button at the bottom of the website, panel and Mini App pages, and this does not affect the lawfulness of processing before withdrawal.

Providing data is voluntary, but the Service cannot be used without a sign-in method. We do not take decisions about you based solely on automated processing that have legal effects or similarly significantly affect you (Art. 22 GDPR): artificial intelligence drafts are only suggestions, and every publication is approved by a person. We do not sell personal data.

4. Recipients of data

  • Contabo GmbH — hosting of the server on which the Service, the bot, the database and the files run.
  • Cloudflare (Cloudflare, Inc.) — a delivery and protection network: all requests to autopost.riadov.app (website, panel, Mini App, webhooks) pass through it, and it processes the IP address and technical request data: cloudflare.com/privacypolicy.
  • OpenAI or Anthropic — draft generation and analysis of GitHub repositories. The artificial intelligence model is provided by one of these providers — which one is determined by the Service’s settings, and at any given time only one of them receives the data. On your command the Service sends it the topic’s material (brand profile, style and rules, campaign, source snapshots, your texts, and also up to 4 photos from the material — copies without the file’s metadata, such as the place where it was taken); instead of your names or e-mail, the provider receives only a fingerprint of the project identifier. In addition, after a GitHub repository is connected, and afterwards on your action (with a button or before a generation, if the repository has new changes), the Service sends the provider the repository’s files (documentation and code) and commit messages in order to compile and update the project card. OpenAI receives the material with storage of the response on its side switched off and processes it under its API terms: openai.com/policies/privacy-policy. Anthropic (the Claude model) processes it under its commercial terms: it does not train models on this data and deletes API inputs and outputs on its side within 30 days, unless longer retention is required by law or to enforce its usage policy: anthropic.com/legal/commercial-terms, anthropic.com/legal/privacy.
  • Stripe (Stripe, Inc. / Stripe Payments Europe, Ltd.) — payment processing: the payment page, the Subscription, the account’s invoices and payments. The Service passes Stripe the Service account identifier, the payment page language, the chosen plan and the number of “+1 project” or of packs of X units, the version number of the Service Terms and the version of the checkbox text; from you on the Stripe page Stripe receives the card details, e-mail and whatever Stripe asks for to make the payment. From Stripe the Service receives the payment status (plan, status, period, scheduled changes), invoices to show to the account owner and, for the copy of your data (section 7), the customer, Subscription and invoice data of your account: stripe.com/privacy.
  • Telegram (Telegram Messenger Inc., Telegram FZ-LLC) — the platform through which the bot and the Mini App work; Telegram processes data as a separate controller under its own policy: telegram.org/privacy.
  • Google (Google Ireland Limited) — Google Analytics 4, if we use it on the website pages, in the panel or in the Mini App (section 2).
  • Meta (Meta Platforms Ireland Limited) — Meta Pixel, if we use it on the website pages, in the panel or in the Mini App (section 2). If you are logged in to Facebook or Instagram in that browser, Meta may link this data to your Meta account.
  • Platforms you connect — GitHub, LinkedIn, Meta (Facebook, Instagram, Threads), Google (YouTube), TikTok, X and Telegram channels and groups. On your instructions the Service reads account and source data from them and passes them the posts and media you have approved. For some platforms a media file is passed via a temporary signed link that is valid for a limited time. Each platform processes data as a separate controller under its own policy.
  • Riadov Systems’ internal Telegram chat — notifications about technical failures (for example, if account deletion has not succeeded for more than a day) without personal data: only the queue number, the time and the error code.

Members of the account’s team see the content of the projects they have access to and, depending on their role, the names of members and the project activity log; the account owner sees all of its projects.

5. Transfers of data outside the EEA

We keep the database, files and logs on a server in the European Union (Germany). OpenAI, Anthropic, Stripe, Telegram, Google, Meta and the platforms you connect may process data outside the European Economic Area. Telegram and the platforms do so as separate controllers under their own policies. In other cases the transfer takes place on the grounds provided for in the GDPR — in particular on the basis of a European Commission adequacy decision (Art. 45 GDPR) or standard contractual clauses (Art. 46(2)(c) GDPR).

6. Retention periods

  • Account and projects with their content (including switched-off projects) — until you delete the account or a project (Service Terms, section 4) or until a year passes without your activity — signing in on the website or in the Mini App or starting the bot: the account is then deleted automatically together with all projects of your account. 30 and 7 days before that, the bot warns you if Telegram is linked. A member of the team of an account with an active Subscription is not considered inactive. There is currently no separate period for automatic deletion of source content or a project after the Subscription ends; if one is set, we will add it to this Policy in a new version. Media files have their own periods (next item).
  • Media files — the original file and its copy without metadata are kept until all publications of the posts that use the file are finished (the post is published, the publication is cancelled or has finally failed), and for 7 more days after the last of them; while the post is not scheduled, the file is not deleted. Copies prepared to a platform's requirements (re-encoded video, video with a cover for TikTok) are deleted right after those publications. A file that is not used in any post, cover or source (including after the post is deleted) is deleted once 24 hours have passed since it was uploaded; an unfinished upload is also deleted after 24 hours. The preview and information about the file, post texts and links to published posts are kept as long as the project exists — until the project or your account is deleted (previous item). After the file is deleted, the Service keeps its preview and a “file deleted” mark; to publish the post again, upload the same file once more.
  • After the account is deleted, the account identifier remains without the e-mail and name — it is referenced by immutable revisions, approvals and the activity log of the projects of which you were a member. The activity log is kept without your personal data; its retention period is [activity log retention period — to be set by the controller].
  • Deletion of an account or a project on the website is carried out 24 hours after the request (until then it can be cancelled); the project export archive is kept for 72 hours, and the link to it is valid for 15 minutes.
  • Sessions last up to 14 days; the session record without the key — until the account is deleted.
  • Temporary data — 30 days from creation; completed tasks and delivered notifications — 30 days from completion.
  • A deletion request — until the deletion is carried out; the Telegram ID in it is erased as soon as the bot notifies you of the result. Completed queue rows — 30 days.
  • The log of data requests, the log of completed deletions and the evidence of notices of new versions — 730 days from the record; inactivity warnings — 365 days from sending.
  • Technical logs — 30 days, files are limited to three of 5 MB each; container logs are overwritten when they reach the size limit (three files of 5 MB each). The bot’s internal delivery log — identifiers without text, up to 7 days.
  • Browser records — the cookie banner choice, the theme and the language are kept in your browser until you clear the website data; Google Analytics cookies — up to 2 years, Meta cookies — up to 90 days (Riadov Systems Cookie Policy, section 2).
  • Backups of the database — the period in section 8 of the main Policy: deleted data disappears from a backup when its retention period expires. If the database has to be restored from a backup, we repeat the deletions using the log of completed deletions before reopening the Service.
  • Payments — the Stripe customer and Subscription identifiers in the Service are kept until your account is deleted; at that point we delete the customer in Stripe, and the active Subscription is cancelled. Invoices, payment records and the ticks of the checkbox before payment remain in Stripe after the account is deleted: for accounting and tax purposes we keep them for 5 years from the end of the year in which the tax payment deadline expired. Stripe also keeps payments under its own policy; platforms keep published posts until you delete them.

7. Your rights

You have the right to:

  • access to your data (Art. 15 GDPR) and data portability (Art. 20 GDPR) — the /my_data command in your private chat with the bot immediately sends a ZIP file with your data: account, sign-in methods, Telegram, sessions, team memberships, your actions, your account’s payment status, your account’s payment data from Stripe — the customer, Subscriptions and invoices, without card details (section 2, “Payments (Stripe)”), as well as the data of the projects of your account; if the file exceeds 20 MB, a full copy of a project is provided by the project export in the application (owner), which also includes the payment data from Stripe. If Stripe is temporarily unavailable, the file says so, and we then provide a copy of the payment data on request through support;
  • rectification of data (Art. 16 GDPR) — you change project content in the application; other data, including the name or e-mail of the account, we will correct at your request through support;
  • erasure of data (Art. 17 GDPR) — the /delete_account command in the bot or deleting the account on the website (together with all projects of your account; deletion is carried out 24 hours after the request, and until then it can be cancelled in the Service’s panel, and a request in the bot also with the cancel button under the bot’s reply; on deletion, the account’s active Subscription is cancelled without an automatic refund, and we delete the customer in Stripe — invoices, payment records and the ticks of the checkbox remain in Stripe for the period in section 6) or deleting an individual project on the website (Service Terms, section 4). Your membership in the teams of other accounts is deleted, while those accounts and their projects do not change. A request in the bot is queued: if, after the 24 hours, deletion does not succeed at once, the Service retries by itself and notifies you of the result. Deletion does not erase posts already published on platforms or messages in Telegram — you delete them on the platform; you remove the GitHub App on GitHub, and the bot from channels and groups in Telegram;
  • restriction of processing (Art. 18 GDPR) and objection to processing based on legitimate interest (Art. 21 GDPR) — through support: the /support command, Telegram @Riadov_Systems or [email protected];
  • withdrawal of consent to analytics and advertising (Art. 7(3) GDPR) — with the “Cookie settings” button at the bottom of the website, panel and Mini App pages.

If you cannot use the bot or the website, send your request to support: we send the reply only to a channel linked to the account (its e-mail or Telegram). We reply to requests through support without undue delay, and in any event within one month (Art. 12(3) GDPR); in complex cases this period may be extended, and we will inform you of this within that month.

You also have the right to lodge a complaint with the President of the Personal Data Protection Office of Poland (Prezes Urzędu Ochrony Danych Osobowych, uodo.gov.pl) — Art. 77 GDPR — or with the supervisory authority of the country where you live or work.

8. Security and age

We apply appropriate technical and organisational measures that protect data against unauthorised access, loss and destruction: the website works only over HTTPS, access keys to platforms are stored encrypted, and the encryption key is kept separately from the database; access keys, session cookies and source content are not written to logs; a project’s data are seen only by the account owner and team members with access to that project. The bot has no access to the database and contacts the Service only with a secret service key. The Service is intended for persons aged 18 and over.

9. Changes to the Policy and language

Each new version of the Policy has a new number and date and its own permanent address, and is available on the Service’s website — autopost.riadov.app/privacy — and with the /privacy command in the bot. The bot will notify you of a new version with one message if Telegram is linked to the account — with the number and date of the version, a link to the full text and the date from which it applies; you do not need to confirm anything.

This document has Ukrainian, English, Polish and Russian versions with the same content.