Privacy Policy

Effective date: November 3, 2026

Who is responsible for your data

This policy explains how we handle personal data when you use the website opentg.ai, the OpenTG API at api.opentg.ai, our Telegram bot and our console.

The controller is Yuriy Landovskyy, a sole proprietor (фізична особа-підприємець) registered in Ukraine and trading as OpenTG ("we", "us"). Address: Lehotskoho street 74/11, Uzhhorod, Ukraine. Email: support@opentg.ai.

1. Visiting the website

When you visit opentg.ai we process:

Connection data: your IP address, browser user-agent and the page requested. Our host, Cloudflare, uses them to deliver the page and to block attacks and abusive traffic. We do not keep your IP address in our own database.
Usage statistics: pages visited, referring site, country, and outbound clicks. Cloudflare Web Analytics measures these without cookies. Google Analytics also runs, in Consent Mode: until you accept our cookie banner it sets no cookies and sends only cookieless signals with your IP address anonymised.
Site search: what you type into search, with your country, to understand what people look for. It is not linked to your IP address or to an identifier.

We also store your language and your cookie choice in your browser. These are strictly necessary and need no consent.

Legal basis: our legitimate interest in running, securing and improving the site (GDPR Art. 6(1)(f)).

2. Cookies you can accept

If you accept our cookie banner, Google Analytics sets cookies with a random identifier so it can count unique visitors and sessions. Legal basis: your consent (Art. 6(1)(a)).

If you decline, no analytics cookies are set. To withdraw your consent, clear the cookies and site data for opentg.ai; the banner will appear again on your next visit.

3. People who appear in posts

OpenTG shows posts from public Telegram channels. Posts can mention or show people: public figures, and sometimes private individuals.

We process this content to make publicly available posts readable, searchable and linkable on the open web. Legal basis: our legitimate interest, and the public's interest in access to information (Art. 6(1)(f)).
We show posts as they were published and do not build profiles of the people in them.
If a post on OpenTG is about you, you can object or ask us to remove it (Art. 17 and 21). Email support@opentg.ai with the link. We remove it unless there is an overriding reason to keep it, such as clear public interest in reporting about a public figure. Our Content Policy describes the removal process.
API customers receive the same public posts and are responsible for how they use any personal data in them.

4. Channel administrators and our bot

If you use our Telegram bot or add it to a channel, we receive your Telegram user ID, display name and username from Telegram. We also read the channel's list of administrators. We use this to confirm who administers the channel and to answer your commands. Legal basis: performance of our service to you (Art. 6(1)(b)). We keep it while the channel is on OpenTG.

5. Console accounts and API keys

If you create an account at opentg.ai/account, you sign in with Google or with a one-time code sent to your email address. There is no password.

What we collect

Your email address, and your name if you sign in with Google, to identify your account (performance of a contract, Art. 6(1)(b)).
If you sign in by email: a one-time code, stored only as a hash, valid for 10 minutes, deleted once used and purged within a day if it is not. It is sent through Cloudflare's email service and never used for marketing.
A session record (identifier, expiry, IP address and browser user-agent), to keep you signed in and detect abuse (legitimate interest, Art. 6(1)(f)).
API key details: a hash of the key, its short display prefix, an optional name and timestamps. We never store the full key.
Usage metrics: for each API request and each search you run on the website while signed in, your account ID, the endpoint, the response status, whether it was cached, and your country (no IP address). We use them to count your quota and to run the Service.
A one-way hash of each search text you were charged for today, so repeating that search is free for the rest of the day. We keep the hash, not the text, and it is deleted shortly after the UTC day ends, or when you delete your account.
Support requests you send from the console: the reason you pick, your message and your account email.
A short security log of account actions: your account ID, the action, a key prefix and the time.

What we do not collect

Your Google profile photo, contacts or any Google data beyond email and name (we request only openid email profile), Google access or refresh tokens (discarded immediately after sign-in), or any password.

How long we keep it

Profile, API key details and support requests: until you delete your account (keys also until you rotate or revoke them).
Email sign-in codes: 10 minutes; unused codes are purged daily. To stop abuse, how many codes an address requests is counted under a one-way hash of that address for up to 2 days.
Sessions: 7 days, or until you log out.
Usage metrics: about 90 days.
Search-text hashes: until shortly after the end of the UTC day they were made.
Security log: about 90 days. After account deletion it keeps only an account ID that no longer identifies you (Art. 17(3)).

Your controls, in the console

Export my data downloads everything we hold about your account as JSON (Art. 15 and 20).
Delete my account permanently erases your profile, sessions, sign-in methods, API keys, request log and support requests, and cancels any paid plan (Art. 17).
To correct your name or email, change it at Google and sign in again, or contact us (Art. 16).

Both controls are on the console's Settings page. The session cookie is strictly necessary, HttpOnly and SameSite-restricted. While you are signed in, a second strictly necessary cookie, holding only the value 1 and no identifier, lets the public pages show a Console link instead of Login. The console sets no analytics or advertising cookies.

6. Search and API request logs

On the Starter, Pro and Enterprise plans, we keep a log of the searches you run on opentg.ai while signed in and of the API requests made with your key, so you can review and export them from the console.

Each entry holds the time, a request ID, part of your key's ID (or “site” for a search on opentg.ai), the method, the endpoint, the full path and query (for example your search terms), the response status and any error code, the units charged, whether it was cached, the response time and your country.
It does not hold your IP address, your API key or your user-agent.
Kept for 24 hours on Starter and 30 days on Pro and Enterprise. There is no log on the Free plan.
Deleted when you move to the Free plan and when you delete your account.

Legal basis: performance of a contract, since the log is a feature of your plan (Art. 6(1)(b)). It is stored with Cloudflare.

7. Payments

Paid plans are sold by Creem (Armitage Labs OÜ, Estonia), our Merchant of Record. Creem collects your payment details, billing address and tax information, and is responsible for them under its own privacy notice. We never see or store your card details.

From Creem we receive and keep: your Creem customer ID, the email address you gave Creem, your plan and billing period, the subscription status, renewal and cancellation dates, and a record of each billing event Creem sends us. We use this to give you the plan you paid for and to show your billing status (performance of a contract, Art. 6(1)(b)).

We keep it while you have an account. When you delete your account, we cancel any live subscription with Creem and delete these records. Creem keeps its own transaction records for as long as tax and accounting law require.

8. Contact form

If you write to us through the contact form, we collect your email address, your name if you give it, your message and the language of the page. We use them only to answer you (legitimate interest, Art. 6(1)(f)), never for marketing.

Your message is stored in our database and forwarded to our support inbox by email, both through Cloudflare.
Stored messages are deleted after 180 days.
To limit abuse, we count messages per IP address under a salted one-way hash kept for up to 2 days. We do not store your IP address with your message.

To have a message deleted sooner, email us.

9. Paid-plan waitlist

While a paid plan is not yet on sale, you can join its waitlist. We store only your email address and the plan you picked, and use them only to tell you when you can buy it (your consent, Art. 6(1)(a)).

The entry is stored with Cloudflare and deleted once we have told you the plan is available.
To limit abuse, we count sign-ups per IP address under a salted one-way hash kept for up to 2 days.

To leave the waitlist, email us.

We do not sell your personal data or share it for advertising. We use these providers:

Cloudflare: hosting, database, file storage, security, web analytics and email delivery. All traffic passes through Cloudflare.
Google: Google sign-in (if you choose it), Google Analytics in Consent Mode with advertising features off, and Google Fonts, which your browser loads from Google's servers.
Creem (Armitage Labs OÜ, Estonia): payments, invoicing and tax, as Merchant of Record.
Telegram: the source of the channel posts we show, and the platform our bot runs on.

Some of these providers process data outside Ukraine and the European Economic Area. Where they do, transfers are covered by the European Commission's Standard Contractual Clauses or an equivalent safeguard.

We may also disclose data where the law requires it.

11. How long we keep data

Each section above says how long we keep that data. Posts from public channels stay on OpenTG while the channel is listed, unless they are removed under our Content Policy or at the request of someone they concern. If a post is deleted on Telegram, it is not removed from OpenTG automatically; ask us and we will remove it.

12. Security

We protect data with encrypted connections (HTTPS), security headers, access controls and encryption at rest in Cloudflare's infrastructure. API keys and sign-in codes are stored only as hashes.

13. Your rights

Depending on where you live, you can ask us to give you a copy of your data, correct it, delete it, restrict or object to its use, or send it to you in a portable format, and you can withdraw consent at any time. Account holders can export and delete their data themselves in the console.

Email support@opentg.ai to use any of these rights. We answer within one month.

You can also complain to a data protection authority: in Ukraine, the Ukrainian Parliament Commissioner for Human Rights; in the EU or UK, the authority where you live or work.

14. Children

The website is not directed at children under 16, and you must be 18 or older to create an account. We do not knowingly collect personal data from children. If you think a child has given us personal data, email us and we will delete it.

15. Changes to this policy

We may update this policy. We will post the new version here with a new effective date, and email account holders about material changes before they take effect.

16. Contact us

Yuriy Landovskyy, sole proprietor, trading as OpenTG, Lehotskoho street 74/11, Uzhhorod, Ukraine

Email: support@opentg.ai
Contact form: opentg.ai/contact