Skip to content
Widgram

Personal data policy

This page describes what data Widgram processes, why, where it is stored and how to delete it.

1. Who processes the data

Data is processed by the provider named in the terms of use; its details are at the end of the terms. Payment data is processed by Telegram (payments in Stars) and YooKassa (payments in roubles), each on its own and under its own rules.

The data of people who receive widgets and leave leads in them is processed on behalf of the widget's author: the author decides why it is needed and what to do with it.

2. What data and why

  • Widget authors. Telegram identifier, name and username, interface language — so that you can sign in and the bot can message you.
  • Widget recipients. Telegram identifier and what the person did in the widget: a vote, a giveaway entry, an issued promo code, a rating — so that the widget works fairly: one vote per person, one promo code each.
  • Leads. The Telegram name and username of a person who tapped the lead button; the widget's author sees them. Leads are stored encrypted.
  • Connected bots and keys. The tokens of your bots are stored encrypted; API keys are stored as an irreversible hash.
  • Payment records. Payment identifier, amount, plan, the payer's Telegram identifier; an email address if a fiscal receipt is required. The card number is not passed to the service and is not stored by it.
  • IP address and request time — in service logs, to protect against brute force and abuse.
  • Widget reports — the reporter's identifier, so that one report is not counted twice.
  • Link clicks. If the widget's author turned on click counting, a link in the widget goes through the go.<service domain> address: the service counts the click and sends you straight to the author's address. Who clicked is not recorded.

The service does not receive phone numbers. The bot sees only what is sent to the bot itself. The legal basis is the performance of the agreement with you, legal requirements and a legitimate interest in protecting the service from abuse. Data is not sold and is not used for automated decisions with legal effect.

3. Who the data is shared with

  • Telegram — widgets and messages are sent through its bot interfaces; the service cannot work without it.
  • YooKassa — for payments in roubles, to the extent needed for the payment and the receipt.
  • The hosting provider whose hardware runs the service (Germany).
  • Your own server — if you set up outgoing webhooks or a proxy for your bot: events of your widgets go to the address you gave.
  • The AI model provider — only if you use widget generation from a description: it receives the text of your request and the widget code, without recipients' data.

Cross-border transfer. The service's hardware is in Germany, so data is processed outside Russia. By using the service you agree to this transfer.

4. How long data is kept

  • The account, widgets, leads and widget state — while the account exists or until you delete them.
  • Statistics events — for the period your plan gives (7 to 365 days); daily totals are kept longer.
  • Service records of incoming Telegram updates — 7 days.
  • Payment records — for as long as tax law requires.

5. Your rights and data deletion

You may ask what data about you is processed, have it corrected, blocked or deleted, and withdraw your consent. An author can delete the account: data is deleted within 30 days of the request, and the deletion can be cancelled during that time. A widget recipient can ask for their data to be deleted by writing to the address below and stating their Telegram identifier; the request is fulfilled within 30 days.

Withdrawing consent ends the service for you: sign-in and widgets are impossible without a Telegram identifier.

6. Cookies

The dashboard keeps a session cookie to remember that you are signed in. On the site such a cookie appears only on pages with a live widget preview: it separates your test taps from those of other visitors. There are no advertising or analytics cookies.

7. Protection

The connection is protected by TLS. Bot tokens, leads and event bodies are stored encrypted. Staff access is limited to what is needed to run the service and answer requests, and is recorded in a log.

8. Contact

Questions about data processing: the contact address will be published here before payments are accepted . You will get an answer within 30 days.

Edition of 18.11.2026.