autopostSocial media autoposting

autopost Service Terms

Version 1.2 of 9 November 2026

1. What this document is and who provides the Service

These Service Terms are an Annex to the Riadov Systems Terms of Service (the “main Terms”): riadov.systems/terms/. They specify the main Terms with respect to autopost — the website and panel at autopost.riadov.app, the Telegram Mini App and the Service’s Telegram bot (the “Service”). The terms “Subscription” and “Annex” have the meaning given in the main Terms, as specified in this Annex.

Order of precedence. The Service is governed by the main Terms and this Annex. If they conflict, this Annex prevails for the Service (main Terms, section 4); neither of them limits the rights that the law grants to a consumer. Matters this Annex does not govern — in particular prices, invoices, the right of withdrawal, complaints, liability and disputes — are governed by the main Terms. Payment for the Service is accepted by Riadov Systems directly, through the Stripe payment service: taking out and changing a plan, payment, the Subscription and invoices are governed by this Annex itself (sections 4 and 6) — they are in the Service’s panel and on the Stripe page that opens from the panel. The Service’s Refund and Cancellation Policy forms part of these Terms.

The services are provided by the following business:
Riadov Systems Vladyslav Riadov
NIP: 6972395549 · REGON: 526790012
Address: ul. Jana Ostroroga 1a/28, 64-100 Leszno, Polska
Phone and WhatsApp: +48 888 577 884
E-mail: [email protected] · Telegram: @Riadov_Systems

The Service is intended for persons aged 18 and over.

2. Type and scope of services

The Service helps you prepare and publish posts on social networks:

  • Account, projects and team. The Service’s data belong to the projects of your account — for example, a separate project for each business or client. An account has one owner — the person who created it, who is also the owner of the Subscription. The owner and administrators invite members to the account’s team: they choose a role (administrator, editor, viewer) and access — to all projects of the account or only to selected ones, and only within what they have access to themselves; the role determines what a member can do. An invitation is a one-time link that the person inviting passes on themselves. Projects are created by the owner and administrators within the plan limit, while only the owner changes and deletes a project; an account or project cannot be transferred to another owner. One person can be a member of the teams of several accounts.
  • Topics and sources. In a project you create topics — the subjects you write about, with a description, style and text rules — and add material for posts to them: GitHub repositories through the GitHub App (only the repositories you have chosen, read-only), website pages and RSS at the addresses you have specified, your own texts, files and photos. The Service stores immutable snapshots of sources. From GitHub, the files of the chosen repositories — documentation and code — go into a snapshot within the limits of the plan, together with the path tree and commit messages (without their authors); paths you have marked “Do not read”, files with keys and settings (such as .env) and binary files are not read. A file in which something resembling an access key or password is found is not taken until you yourself allow it to be read.
  • Draft generation. On your command, the Service sends the topic’s material to an artificial intelligence model from OpenAI or Anthropic (Claude), depending on the Service’s settings — including up to 4 photos from the material, so that the model sees their content (for example, a menu, a price list or a sign) — and receives draft posts for the selected platforms. Drafts are suggestions: they must be checked and corrected where necessary.
  • Analysis of GitHub repositories. After a repository is connected, the Service sends its files and commit messages to the same artificial intelligence model in order to compile the project card — a short description of what the product does, for whom, which of its features are useful to people and what has changed. Afterwards the card is updated on your action — with a button on the source page or before a generation, if the repository has new changes. The card is the basis for topics and draft posts. The first analysis after connection does not use artificial intelligence generations from the plan’s limit; each card update uses 2 generations.
  • Approval and calendar. No post is published without approval by a person. You schedule an approved post for a date and time in the calendar; you can also approve with buttons in the bot.
  • Publication. The Service publishes approved posts to the accounts and channels you have connected: Telegram channels and groups (through the Service’s bot), LinkedIn, Facebook Pages, Instagram, Threads, YouTube, TikTok and X. The availability of each platform and of formats depends on its rules and on whether it has approved the Service (app review, audit); until approval is granted, some functions are limited — this is shown in the application. Publishing to X costs the Service money, so a post with a link, which costs more, is published only with your separate confirmation.
  • Notifications in Telegram. The bot sends approval cards and publication statuses to your private chat with the bot. In groups and channels the bot does not respond to commands — it only publishes the posts you have scheduled there.

The Service is an independent product: it is not associated with or endorsed by OpenAI, Anthropic, GitHub, Telegram, LinkedIn, Meta (Facebook, Instagram, Threads), Google (YouTube), TikTok or X (main Terms, section 13).

3. Technical requirements

You need a device with internet access and a modern browser with JavaScript and cookies enabled for the Service’s website. To sign in — a Telegram or GitHub account (section 4); for the Mini App and the bot — an up-to-date Telegram app and a Telegram account. To connect sources and platforms — your accounts with them. Payment — in the browser on the Stripe page, which opens from the Service’s panel (section 6); a Telegram account is not needed to pay.

Using services over the internet involves typical threats, such as malware or attempts to trick you into revealing data (phishing). We never ask for passwords to your social network, GitHub or Telegram accounts: you grant access to them only on the platform’s own page.

4. Conclusion of the contract and the account

Account. The account is created on your first sign-in to the Service — through Telegram (on the website with the help of the Service’s bot, or in the Mini App), and also through GitHub if the sign-in page offers that method. The contract for using the Service is concluded when the account is created and remains in force indefinitely — until the account is deleted.

Subscription. A paid plan for the account is taken out and paid for by its owner in the Service’s panel (the “Billing and limits” section); the contract for a paid service is concluded at the moment of successful payment on the Stripe page (section 6).

Deleting the account in the bot. You may terminate the contract at any time by deleting your account with the /delete_account command in your private chat with the bot. Before deletion, the bot warns you what will be deleted and asks for one confirmation. Together with the account, all projects of your account are deleted with all their data; the members of your team lose access to them. Deletion is carried out 24 hours after the confirmation; until then it can be cancelled with the button under the bot’s reply or in the Service’s panel (the “Data and privacy” or “My account” section), and the account, projects and Subscription then remain. When deletion is carried out, the account’s active Subscription is cancelled without an automatic refund (section 6). You merely leave the teams of other accounts in which you are a member: those accounts and their projects do not change. The request is queued: if, after the 24 hours, deletion does not succeed at once, the Service retries by itself and notifies you in the bot when it has finished.

Deleting on the website. In the Service’s panel (the “Data and privacy” or “My account” section) you can delete your account. Together with it, all projects of your account, including switched-off ones, are deleted with all their data, and the account’s active Subscription is cancelled when deletion is carried out, without an automatic refund (section 6). Deletion is carried out 24 hours after the request; until then it can be cancelled, and the account, projects and Subscription then remain. You merely leave the teams of other accounts in which you are a member: those accounts and their projects do not change. The owner deletes an individual project on the “Projects” page — also after 24 hours, with the option to cancel — or switches it off instead of deleting it (section 6). Cancelling the Subscription does not delete data, and deleting a project does not cancel the Subscription.

Automatic deletion. If you do not use the Service for a year — do not sign in on the website or in the Mini App and do not start the bot with the /start command — the account is deleted automatically with the same consequences as with the /delete_account command, but without the 24-hour cancellation window. 30 and 7 days before that, the bot sends you a warning if Telegram is linked to the account. A member of the team of an account with an active Subscription is not considered inactive.

Breaches. If you breach the rules in section 5, we may suspend access to the Service or terminate the contract in accordance with section 12 of the main Terms.

5. Rules of use

  • You are responsible for the material you add to the Service and for the posts you approve and publish: they must not violate the law, the rights of third parties (in particular copyright and the right to one’s image) or the rules of the platforms you publish to.
  • If you have allowed a file in which the Service found something resembling an access key or password to be read, that file is stored in the snapshot and sent to the artificial intelligence model like the other files. You are responsible for ensuring that the connected repositories do not contain real access keys, passwords or personal data of other people that you are not entitled to pass on to the Service.
  • Connect only those sources, accounts and channels that you are entitled to manage, and invite to the team only those who may see the data of the projects you give them access to.
  • It is prohibited to circumvent plan limits, disrupt the operation of the Service or of platforms, attempt to gain unauthorised access, or use the Service for spam. Other prohibitions — section 12 of the main Terms.

6. Plans, payment and Subscription

The seller of the Service is Riadov Systems Vladyslav Riadov: it accepts payment for the Service directly, and payments are processed by the Stripe payment service. The plans, their limits (number of projects, team members, posts per month, artificial intelligence generations and X units per month, GitHub repositories, their connections per billing period and repository size) and prices in euro are shown on the pricing page of the Service’s website and in the Service’s panel before payment. The limits apply to all projects of the account combined, except the GitHub limits — they apply to each project separately; without a paid Subscription the Free plan applies. On a paid plan you can buy additional projects (“+1 project”). Every connection of a GitHub repository, including a repeated one, counts towards the connection limit; you can disconnect a repository at any time, but a used connection is not returned, and reconnecting the same repository within 24 hours of disconnecting it does not count. A repository larger than the size limit is read partially rather than rejected. Publishing to X is counted in X units: a tweet is 1, a post with a link is 10, in a thread every tweet counts; the plan’s monthly X units are used first, then purchased ones. On a paid plan you can buy a pack of X units as a one-off purchase: purchased units do not expire at the end of the month and apply while the account has a paid plan (the Free plan does not include publishing to X); if a publication to X does not happen, the units are returned, and unused units are lost when the account is deleted. You pay exactly the amount shown in the Service’s panel and on the payment page.

Payment. Only the account owner takes out, changes and cancels a plan — in the Service’s panel (the “Billing and limits” section); from the Telegram Mini App this section opens in a regular browser. Payment is made through the Stripe payment service (Stripe, Inc. / Stripe Payments Europe, Ltd.) on a secure Stripe page; we do not store full bank card details and have no access to them. Before each payment you tick a checkbox on the Stripe page: you accept the main Terms and these Terms and request that the service start immediately after payment; Stripe stores this tick together with the payment, and we add to the payment the version number of these Terms and the version of the checkbox text. A paid plan takes effect when Stripe confirms the payment.

Subscription and plan changes. The Subscription renews automatically for the next billing period until you cancel it. An upgrade and adding “+1 project” take effect immediately after payment: you pay only the difference for the remainder of the paid period. A downgrade and reducing the number of “+1 project” take effect from the end of the paid period, and until then the current plan applies; a scheduled change can be cancelled until the end of the period. Before you confirm a change, the Service’s panel shows what will change and from when, and how much will be charged now and afterwards. The payment method is changed in the Service’s panel on the Stripe page.

Switched-on and switched-off projects. The project limit counts only switched-on projects. The owner may switch a project off at any time instead of deleting it: a switched-off project keeps its settings, data and connections, but does not publish, does not generate drafts and does not count toward the limit — it can be viewed, exported and deleted, and its scheduled publications wait until the project is switched on again. A project can be switched on if there is free room in the limit. When scheduling a downgrade or fewer “+1 project”, the owner can choose which projects stay switched on from the new period. If there is no choice, and also when the Subscription ends, the earliest-created projects within the new limit stay switched on. The remaining projects are switched off but not deleted; after that the owner chooses which projects stay switched on.

Cancelling the Subscription. The owner cancels the Subscription in the Service’s panel (the “Billing and limits” section): it remains in force until the end of the paid period and is not renewed after that, and until then the cancellation can be withdrawn. When the Subscription ends, the account moves to the Free plan: the data remain, the limits of that plan apply, and projects above its limit are switched off (paragraph above). Deleting the account cancels the Subscription when the deletion is carried out (24 hours after the request; until then it can be cancelled), without an automatic refund (section 4).

If payment is not received. If a renewal could not be paid, Stripe retries. If payment is not received within 7 days of the first failed attempt, the account’s projects become read-only until payment is received: scheduled publications wait for payment and are not cancelled, and viewing, export and deletion of data remain available.

Refunds and invoices. The Service does not make automatic refunds. If you are a consumer, you have the right to withdraw from the contract within 14 days without giving any reason. Requesting that the service start immediately after payment does not deprive you of this right: if you withdraw within this period, you pay only for what was provided up to the withdrawal, and we refund the rest. The procedure, refund deadlines and model form are in section 10 of the main Terms: riadov.systems/terms/#withdrawal. Other refund requests are considered individually — write to support; refunds are made manually through Stripe. The account owner can see Stripe invoices for the Subscription and one-off purchases in the Service’s panel (the “Billing and limits” section). We issue an invoice on request through support (main Terms, section 9). Details — in the Refund and Cancellation Policy.

7. Non-conformity of the service and complaints

If the Service does not conform to the contract — to the description in these Terms, on the pricing page and in the Service’s panel before payment — you have the rights described in section 11 of the main Terms: riadov.systems/terms/#complaints. You can submit a complaint with the /support command in the bot, in Telegram to @Riadov_Systems or to [email protected]: describe the problem, state the project and, where relevant, the post or payment, and what you are requesting.

8. Liability

Drafts are created by an artificial intelligence model: they may contain errors, inaccuracies or similarities to other people’s texts. That is why every post is approved by a person before publication, and you make the decision to publish. Platforms may reject, restrict or remove a post under their rules, or change their interfaces or terms; technical interruptions and restrictions on their side may delay or prevent publication — in that case the Service shows the publication status and the reason reported by the platform.

Our liability and its limits are determined by sections 13 and 14 of the main Terms. Nothing in these Terms excludes or limits consumer rights arising from mandatory provisions of law.

9. Personal data

How the Service processes personal data is described in the Service Privacy Policy (also shown by the /privacy command in the bot), together with the Riadov Systems Privacy Policy: riadov.systems/privacy/. Cookies and analytics on the Service’s website are described in the Riadov Systems Cookie Policy. Accepting these Terms is not consent to data processing.

10. Changes to the Terms

We may change these Terms only for the reasons and in the manner set out in section 15 of the main Terms; this Annex does not narrow them or establish any other procedure for changes. Each new version has a new number and date and its own permanent address, and is available on the Service’s website — autopost.riadov.app/terms — and with the /terms command in the bot.

The bot notifies you of a new version with one message if Telegram is linked to the account: the number and date of the version, a link to its full text and the date from which it applies. For your active Subscription, the new version applies from the first billing period that starts on or after that date. If you do not agree, before then cancel the Subscription in the Service’s panel or delete your account with the /delete_account command at no cost (the /my_data command gives you a copy of your data beforehand). You do not need to accept or confirm the new version, and your use of the Service is not restricted because of it. The right to terminate the contract in the event of a material negative change to the Service’s functions — section 15 of the main Terms.

11. Language, governing law and contacts

This document has Ukrainian, English, Polish and Russian versions with the same content. The Service’s interface is currently available in Ukrainian.

These Terms are governed by Polish law. If you are a consumer, this choice of law does not deprive you of the protection afforded by the mandatory provisions of the country of your habitual residence. Dispute resolution — section 16 of the main Terms.

Contacts: the /support command in the bot, Telegram @Riadov_Systems, e-mail [email protected].