Privacy, in plain language.

Messaging and your account

Core Telegram messaging uses Telegram's infrastructure. Rovegram's advertising service does not receive your messages, contacts, phone number, Telegram account ID, or search query. Account matching and ad frequency limits used by the client stay on the device.

For Telegram's own services, read Telegram’s privacy policy and terms of service.

Translation and local files

Official translation uses Telegram's translation service. Local translation uses on-device ML Kit language models; downloading models connects to Google's infrastructure. Your chosen mode and fallback setting determine which service is used. See ML Kit translation.

Downloads, saved media, local task state, and language models use device storage and Android permissions. They are not uploaded to the Rovegram advertising server.

Advertising requests and events

An ad request includes the placement, app build/channel, interface language, and contextual mode. The server can infer an approximate exit country from trusted network infrastructure. Network addresses are processed to deliver requests and limit abuse. Ad render, qualified-view, click and report events use opaque delivery identifiers; they are not Telegram user identifiers.

Our current service is hosted in New York, United States, behind Cloudflare. Both hosting and edge delivery involve network processing. We do not use chat text or contact lists to target Rovegram ads.

Retention and backups

Processed raw advertising records are normally removed after 14 days; unresolved work is retained until it can be handled safely. Aggregated statistics are retained for 12 months. The server keeps seven daily encrypted backups, so raw records in a backup can be about 21 days old; restoring requires cleanup before service resumes.

Financial ledger and administrator audit records are separate from raw impression events. A production advertiser-account retention schedule must be published before public advertiser onboarding. Continuous independent backups and operational recovery checks remain release work.

This website

We add no analytics, ad pixels, signup forms, or browser storage to this website. Its origin access log is configured to record time, hostname, request method, status, response size and duration, without visitor IP addresses, URLs or query strings.

Cloudflare and the hosting provider still process network information to deliver and protect the site. Cloudflare may use security cookies. Following a Telegram or other external link takes you to that provider's service.

Questions and requests

Contact @roveadminbot for privacy questions, corrections, or requests about Rovegram's own service. Requests about Telegram's account data should also follow Telegram's own process. Do not send credentials or verification codes to the bot.