Cookie Policy
Permanent address of this version: https://riadov.systems/cookies/2-3/
1. What cookies and similar technologies are
Cookies are small text files that a browser stores on your device when you visit a website. In a similar way, a website can store entries in the browser’s storage (localStorage) — these are not cookies, but this Policy describes both mechanisms.
This Policy supplements the Privacy Policy. The terms “Service”, “Payment Service” and “Dashboard” have the meaning given in the Terms of Service.
2. What the website uses
Necessary — always active. The riadov.systems website sets only one cookie of its own and keeps only two entries in your browser’s storage (localStorage):
rs-lang— a cookie with the language you have chosen in the language switcher:en,uk,plorru. It appears only after you click a language in the switcher and is kept for 1 year from your last choice. The server uses it only on the home page, to open the language you have chosen; it is not passed to anyone. Your browser sends it only to this website and only over HTTPS (Secure,SameSite=Lax).rs-consent— your choice on the cookie banner:allafter “Accept” ornecessaryafter “Necessary only”. It appears only after you click one of the buttons and is kept until you clear the website data. Without it, the website would not remember your choice.rs-theme— the light or dark theme, if you have switched it with the button on the website. It is kept until you clear the website data.
The riadov.app showcase and product landing pages. The riadov.app home page and its language versions are our product showcase, and lot-check.riadov.app and smart-feed.riadov.app with their language versions are the landing pages of our products; this Policy applies to them as well. They use the same necessary entries — the rs-lang cookie and rs-consent and rs-theme in the browser’s storage — each separately for its own domain, so the choice on the banner is made on each of them separately — and, after “Accept”, load only Google Analytics, without Meta Pixel. This Policy does not cover our clients’ systems at other addresses on the riadov.app domain (Privacy Policy, section 2).
autopost — autopost.riadov.app. The website of this Service (Terms of Service, section 4) is ours, and this Policy applies to it as well: to the website pages, the Service’s panel and the Telegram Mini App. The necessary records there are:
__Host-spa_session— the cookie of your sign-in session in the Service (on the website and in the Mini App): without it the Service does not recognise you after you sign in. It is not accessible to page scripts and is sent only over HTTPS. It lasts up to 14 days or until you sign out.__Secure-spa_preauth— a temporary cookie used only while you sign in through GitHub or the Service’s bot: it links the start and the end of the sign-in in the same browser. It lasts 10 minutes.spa-themeandspa.theme(the chosen theme on the website pages and in the Service’s panel) andspa.telemetryConsent(your choice on the cookie banner) — entries in the browser’s storage (localStorage). They are kept until you clear the website data.
On the pages of the autopost website outside the Service’s panel, Google Analytics and Meta Pixel with the cookies from the table below may load if we have enabled the relevant analytics there. It is enabled only after “Accept”, and at the time this version is published it may be switched off. There is no analytics or advertising in the Service’s panel or in the Telegram Mini App.
Requests to the websites covered by this Policy pass through the Cloudflare network. If Cloudflare checks whether a request is made by a human rather than an automated program, it may set its own technical security cookie (for example, cf_clearance) — solely for that check.
Analytics and advertising — only after “Accept”. After you click “Accept”, the website connects the following services; they set their own cookies only after “Accept”:
| Service | Purpose | Lifetime |
|---|---|---|
| Google Analytics 4 | visit statistics: the service sets its own cookies by which it recognises the browser across different pages and on repeat visits; each of our websites has its own such cookies: riadov.systems, the riadov.app showcase and the product landing pages, the autopost website (if analytics is enabled there) | under the provider’s rules, up to 2 years |
| Meta Pixel | advertising effectiveness: the service sets its own cookies to measure Meta advertising, recognise arrivals from it and show ads to people who have already visited the website | under the provider’s rules, up to 90 days |
Until you click “Accept”, and also after “Necessary only”, the website does not load Google and Meta scripts, so these companies do not set cookies and receive no data from the website. The website’s fonts are loaded from our server.
3. Analytics and advertising
Google Analytics 4 counts events of visits and interactions on our websites: pages being opened, clicks on buttons and links (in particular on messengers and e-mail for contact, on bots and on videos, on signing in or signing up in autopost) and form submissions — without their content. An event contains its name and technical parameters — for example, the page address, the case or the bot, the contact method. Google receives the page address and the referring page address, data about your browser, system and screen, the browser identifier from the Google Analytics cookie and your IP address, from which it determines your approximate location. Your visits are linked to one another by the identifier. We use this data to understand how visitors use the websites and to make them more convenient.
Meta Pixel informs Meta about events of the same types on riadov.systems and, if analytics is enabled there, on the autopost website. Meta receives the page address, browser data, the browser identifier from the Meta Pixel cookie and your IP address. If you are logged in to Facebook or Instagram in that browser, Meta may link these events to your account. We use Meta Pixel to measure advertising and to show ads to people who have already visited our websites.
The set of events may change within these types and purposes; we will add a new type of data, a new purpose or a new recipient to this Policy by a new version (section 8). Google and Meta are named as data recipients in the Privacy Policy, section 7.
4. Stripe payment page
Payment takes place on a secure page of the Stripe payment service — not on our websites and not in the Dashboard. On its page, Stripe may set its own cookies for secure payment processing and fraud prevention in accordance with its privacy policy. Riadov Systems does not control Stripe cookies and has no access to their content. More information: stripe.com/privacy.
5. The pay.riadov.systems Dashboard
The Dashboard is a page of the Payment Service that the Service’s bot opens in Telegram (Telegram Mini App). The Dashboard does not set cookies, does not store sessions and does not use analytics: login is confirmed by the data that Telegram passes to the Dashboard when it is opened. Your choice of display theme is stored in Telegram’s cloud storage (Telegram CloudStorage), not in your browser. The payment page to which the Dashboard leads is a Stripe page (section 4).
6. Consent and how to change your choice
On your first visit, the website shows a cookie banner with two buttons:
- “Accept” — your consent to Google Analytics and Meta Pixel and their cookies (sections 2 and 3);
- “Necessary only” — the website works without analytics and advertising, with necessary entries only.
Consent is given only by the “Accept” button. Until you click either button, the website behaves in the same way as after “Necessary only”, and the banner is shown on every page.
In this way we comply with the Polish law “Prawo komunikacji elektronicznej” (Art. 399): information may be stored on your device or read from it only after you have been informed and have given consent, except for entries without which a service you have requested yourself cannot be provided — in our case the rs-lang cookie and the entries rs-consent and rs-theme (on riadov.systems, the riadov.app showcase and the product landing pages), and in autopost the sign-in session cookies and the entries spa-theme, spa.theme and spa.telemetryConsent (section 2). The processing of personal data collected by Google Analytics and Meta Pixel is described in the Privacy Policy; its legal basis is the same consent of yours (Art. 6(1)(a) GDPR).
You can change your choice at any time with the “Cookie settings” button at the bottom of every page: it reopens the banner. If, after “Accept”, you choose “Necessary only”, the website deletes the analytics and advertising cookies and reloads the page. The riadov.app showcase and the product landing pages likewise delete their analytics cookies. The autopost website has the same button at the bottom of its pages outside the Service’s panel and, if analytics is enabled there, likewise deletes its analytics and advertising cookies.
7. Managing cookies in your browser
You can manage cookies and website data in your browser settings:
- view and delete cookies that have been set
- clear the data of an individual website
- block new cookies from being set
Please note: blocking cookies on the Stripe payment page may make payment impossible.
8. Changes to the Policy
Riadov Systems may change this Policy, in particular when the set of cookies or services on the website changes. Each new version has a new number and date, shown below the heading of this page. The current version is always published on this page.
9. Contacts
For questions about the use of cookies, contact us:
- E-mail: support@riadov.systems
- Telegram: @Riadov_Systems