Privacy Policy

The short version

There is no account form. We never ask for your name, your email or a password, so there is nothing of that kind to store, leak or be asked to hand over.

What we hold

• Your Telegram user ID, received when you press Start in the sign-in bot. This is the only identifier we have for you. We do not store your username — it can change, and nothing here depends on it.
• Your licence — its key, term and the machine fingerprint it is activated on. This is held by Keygen, our licensing provider.
• Your payments — amount, date, and the invoice reference. Held by NOWPayments, who process the transaction. We keep the reference so the panel can show your history.
• A session cookie while you are signed in.

What we do not hold

We never see the Telegram accounts you run through the application, the channel you target, your proxies, your API keys or anything the application does on your machine. None of it is sent to us. The application talks to Telegram directly from your computer.

We do not hold payment details. You pay through NOWPayments and your wallet never touches our servers.

Who else is involved

• Telegram — identity and messages from the bot.
• Keygen — licence issuing and verification.
• NOWPayments — payment processing.
• Cloudflare — content delivery and the storage the installer is served from.

Each of these has its own policy covering what it does with the data it receives. Link them here once the accounts are set up.

How long we keep it

State the retention period for each item above. Payment records usually have to be kept for a fixed number of years for tax purposes; session and login records do not and should be short.

Your rights

Describe how someone asks for a copy of their data or asks for it to be deleted, and how quickly you answer. If you sell to customers in the EU or the UK, this section is not optional and the wording matters.

Cookies

One cookie. It is called bsid, it holds nothing but a random session identifier, and it exists so the panel knows you are the person who signed in. It is deleted when you sign out and it expires when you close the browser.

It is marked HttpOnly so no script on the page can read it, Secure so it is only ever sent over an encrypted connection, and SameSite=Lax so another site cannot cause your browser to send it.

There is nothing else. No analytics, no advertising, no tracking pixels, no third-party scripts and no fonts loaded from anyone else's server — everything the panel needs is served from this domain.

This is why you are not being asked to accept cookies. Consent is required for cookies that track you or that serve someone other than you; a cookie whose only job is to keep you signed in is exempt, and asking about it would be theatre. If that ever changes — if we add analytics, for example — you will be asked before it is set, and this section will say so.

Contact

Day-to-day questions reach us on Telegram at @PRIMECOVE.

Formal requests under this policy — a copy of your data, or its deletion — go to primecove@proton.me. That address is also how you confirm you are talking to us: a Telegram username can change hands, an address cannot be taken from us the same way.