Adsly
Sign inGet started

Privacy

Last updated 14 October 2026

Information under Articles 13 and 14 GDPR. This describes what this platform actually does with data, not what a template assumes it might.

Controller

Name and address of the operator — the same as in the imprint

Data protection officer: required only above the thresholds in § 38 BDSG

When you visit without an account

Our server records the request: the page, the time, the browser’s user agent and the address the request came from. This is how a web server works and we cannot serve a page without it. Legal basis: Article 6 (1) (f) — operating and securing the service.

A session cookie is set only once you sign in. A campaign you assemble before signing in is kept in your own browser’s local storage and never sent to us until you choose to continue with it.

When you click an advert

Adverts posted through this marketplace use a tracked link. When it is opened we record the time, the campaign and channel it belongs to, the referring page, a coarse device class, and the country as reported by Cloudflare — XX for unknown and T1 for Tor are stored as no country rather than as a place.

Your IP address is not stored. It is combined with a server-side secret and hashed, and only the hash is kept. The hash exists so the same visitor is not billed to an advertiser twice; it cannot be turned back into an address, and we do not use it to recognise you anywhere else.

Legal basis: Article 6 (1) (f) — billing advertisers for real delivery rather than for bots.

When you hold an account

We store your name, email address, a hash of your password (never the password), your organisation and role, your sessions, and the records your use of the marketplace creates: campaigns, channels, bookings, messages, wallet entries and payouts. Legal basis: Article 6 (1) (b) — performing the contract.

Financial records are kept for as long as commercial and tax law require, which is longer than an account lives. Everything else is deleted with the account.

Channel data

For a Telegram channel we read what its public page publishes — name, description, picture, subscriber count and recent view counts — and, where its owner has added our bot as an administrator, what the Bot API reports about posts we placed. We do not read your private messages and we have no access to your subscribers.

Telegram does not publish audience country or interests, and this product refuses to guess them. Where you see those fields empty, that is why.

Who else sees it

Cloudflare sits in front of this site and sees every request, including your IP address, as a processor.

Heleket handles payments. What you enter on their pages is theirs; we receive only the outcome and the amount.

Telegram receives the adverts we post and the requests we make about public channels.

Outbound email is currently switched off on this deployment: no message is sent to the address on your account, and none is queued for later.

Hosting provider: name and country of the server

Your rights

You may ask what we hold about you, have it corrected or deleted, have its processing restricted, receive it in a portable form, and object to processing we base on a legitimate interest. Write to the address above. You may also complain to a supervisory authority.