How the store is built

What protects your purchase, from payment through to the files on your machine

A purchase isn't kept safe by one big claim. It's kept safe by several small mechanisms that don't depend on one another, and by an honest account of where our part ends and someone else's starts.

Described as they are — no certificates on the wall, nothing dressed up

The moving parts

What actually guards an order

Each one closes a different way an order could go wrong, and none of them leans on the others. "Your purchase is protected" would cover all six and tell you nothing about any of them.

The money never passes through us

You pay on Heleket's own page, never on ours. What the gateway gets is an amount and an order number. Not a card number, not a wallet key, not even your email.

A payment that looks wrong stops

A transfer that lands short of the invoice, or arrives after the payment window has closed, stops the order there and leaves it for a person. No rule settles that quietly in the background.

Nothing exists to be stolen while you pay

There's nothing to take during the payment window, because the archive doesn't exist yet. Your accounts are held aside and left alone; the packing only starts once the payment confirms. Until then the order you bought has no finished form for anyone to get at.

The archives aren't somewhere you can browse to

Guessing at addresses gets you nowhere, because there are no addresses to guess. The files answer to nothing on the open web, and every download is served by the store itself, through the link that belongs to that one order. There's no back way to a file — only the front one.

There's no account of yours to break into

Ordering takes an email and nothing else: no username, no password, nothing to sign into. Leaked credentials and reused passwords are a whole class of trouble that needs you to have an account first, and here you never make one.

Analytics doesn't reach your order page

Checkout, your order page and the download itself carry no third-party analytics. Those are the pages that have your order link on screen, and they're kept clear of anything measuring from outside. What is measured, and where, is the privacy policy's to set out.

Before an item goes on sale

The check a batch goes through before it's listed

It's a short, practical check, and it happens once — before the batch is listed. A check is all it is: it can tell you what's in the folders today, not how an account will fare later on.

Both formats are actually in the folder
A listing names TDATA and SESSION + JSON, and both are in each account's folder before the page goes up.
2FA.txt where there's 2FA to record
Where two-factor authentication is switched on for an account, its password sits in that account's folder as 2FA.txt. Where it isn't, there's nothing to put there.
The age is the age on the page
Each product page carries the account age set for that batch, and the batch is checked against it before anything is listed.
The folders open clean
You open a folder and the account files are right there, with nothing wrapped around them. No installers, no executables, nothing of that kind anywhere in the batch.
Where the line runs

What we answer for, and what we don't

Our side of it is the part we build and can be held to. If an order is packed wrong, released early, stored carelessly or waved through on a payment that never confirmed, that's ours to answer for, and there's no one else to point at.

The payment itself isn't ours. It happens on Heleket's page, under Heleket's terms, and what reaches us is the confirmed result rather than the mechanics of how you sent it.

Past that, there's a part nobody here owns. Telegram runs its own platform on its own rules, and it can restrict an account that breaks them; that call isn't ours to make and isn't ours to undo. The same goes for the far end of the process: once the archive is on your machine, the files and the link are with you, and whoever holds them holds the accounts.

One thing this page leaves alone is the order link itself — how access to a single order works, why it's bounded, what to do if it goes astray. Order protection covers that ground.

What this page doesn't claim

There are limits to all of this, and they're worth stating outright rather than leaving to be discovered.

  • Security, on this page, is the list of mechanisms above and nothing beyond it. A mechanism can keep an order from going wrong; it cannot tell you what follows once one has. That question belongs to the refund policy.
  • We don't publish how any of this works underneath. That's deliberate, not an oversight: a detailed map of a protection mechanism is worth far more to someone attacking it than it is to you.
  • There's no certification behind this, no audit report, no monitoring desk. There's the list above, and it's meant to be read rather than trusted on sight.

Where the rest is set out

That's the store-wide view. The parts it only gestures at each have a page of their own, and the catalog is there if you'd rather go and see what's available by country.