Privacy policy
This page lists the information TopUpKit actually keeps, taken from the app itself: what you enter, what a supplier returns, and what a sign-in records.
What we collect
Account: your name, your email address, a hashed password, and your language. A password is hashed with scrypt and is never stored as you typed it.
Supplier accounts: for each account you add, its supplier, region, identifier and username, the credential you supply, encrypted at rest; a saved password only if you ask us to save one; and the authenticator setup key needed to pay for a Garena order.
Orders and redeems: the player identifier, the player's nickname when the supplier returns one, the item, the quantity, the status, the supplier's reference, and any idempotency key you send.
Deposits: the amount, the method, the transaction identifier and the answer the payment provider returns.
API keys: a label, the key's hash, its IP allowlist and its callback URL. The key itself is shown once and is not stored.
Sessions: a session identifier in a cookie, the IP address and browser string of the sign-in, and when it expires.
Telegram, if you link it: the chat identifier, so the bot can send you the same news as the notification bell.
Two-step verification, if you turn it on: the authenticator setup key and hashed recovery codes.
Activity log and notifications: who changed what and when, and the messages the app sent you.
What we do not collect
We do not hold your supplier credit: Shell, Smile Coin and UniPin Credits stay on your own account at the supplier.
The app runs no third-party analytics, advertising or tracking script, and sets no advertising cookie.
Cookies
One cookie keeps you signed in. It holds a session identifier, is HttpOnly, and is cleared when you sign out, when your user is deactivated, or when 30 idle minutes pass.
No cookie is used to follow you to another website.
Why we use it
To sign you in and keep you signed in; to place the orders and redeems you ask for; to charge the service fee and keep the balance right; to show you what happened to each order and card; to answer your support questions; and to keep the records accounting and disputes require.
Who it is shared with
Supplier websites receive the order or the cards you ask us to send, with the player details that order needs.
Payment providers receive what a deposit needs to be confirmed: the amount, the reference and the transaction identifier.
Telegram receives a message if you linked a chat.
We do not sell your information, and we do not share it for advertising.
How long we keep it
Orders, redeems, deposits and the activity log are kept as the record of money that moved. A removed supplier account is kept, marked as removed, so that past orders still name it.
A session ends on sign-out, on deactivation, or after 30 idle minutes. Notification messages and the Telegram copy of them are not the record, and may be dropped.
How it is protected
Passwords are hashed with scrypt. Supplier credentials are encrypted before they are stored. Sign-in, registration, password changes and two-step codes are rate-limited, and the app is served over HTTPS.
Your choices
You can change your password and turn two-step verification on or off in settings, unlink Telegram, and remove a supplier account.
To ask for a copy of your information, to correct it, or to ask us to delete what we are not required to keep, contact us. Some records, such as a settled order or a credited deposit, must be kept for accounting, and we will say so if that applies.
Changes
This policy changes when what the app stores changes. A material change is announced in the news channel.