Cookie Policy
The cookies and similar technologies used by paysell.me and the merchant cabinet, all of which are strictly necessary today.
- Updated
- 2026 ж. 06 қыр.
On this page
Version 1.0 · Effective [[Effective date]] · Last updated [[Effective date]]
In short: Paysell sets only three cookies, and all of them are strictly necessary to sign you in and remember your language. We do not use advertising, profiling or analytics cookies today, and no third party sets cookies through our site. If that ever changes, we will ask for your consent first.
1. What this policy covers#
This Cookie Policy explains the cookies and similar local storage used by [[Company legal name]] ("Paysell") on the website https://paysell.me and in the merchant cabinet. It should be read together with our Privacy Policy, which explains how we handle personal data more generally.
A cookie is a small text file that a website stores in your browser and that the browser sends back on later requests. Similar technologies — such as localStorage and sessionStorage — store data in the browser without sending it automatically with each request. We describe both below.
2. Cookies we set#
| Name | Type | Purpose | Lifetime | HttpOnly |
|---|---|---|---|---|
access_token | Strictly necessary | Authenticates each request you make in the merchant cabinet and to the cabinet API after you sign in. Short-lived by design so that a stolen token quickly becomes useless. | Approximately 15 minutes | Yes |
refresh_token | Strictly necessary | Lets the cabinet obtain a new access_token without asking you to sign in again, and identifies your session so that it can be listed and revoked from the security page. | Up to 180 days, or until you sign out or revoke the session | Yes |
NEXT_LOCALE | Strictly necessary (preference) | Remembers the interface language you selected so that pages render in the same language on your next visit. | 1 year | No |
All cookies are set on the paysell.me domain, are transmitted only over HTTPS (Secure), and use a SameSite policy that prevents them from being sent with cross-site requests. The two authentication cookies are HttpOnly, meaning that scripts running in the page cannot read them.
We set no cookies at all on the public website before you sign in, apart from NEXT_LOCALE if you change the language.
3. Local storage in the cabinet#
In addition to cookies, the merchant cabinet may keep a small amount of non-essential interface state in your browser's local storage — for example a collapsed sidebar, a chosen table view, a dismissed notice, or an unsent draft in a form. This data stays in your browser, is not sent to our servers with each request, and contains no authentication credentials. Clearing your browser's site data removes it.
4. Why we do not ask for consent#
Under the law of [[Jurisdiction]], consent is not required for cookies that are strictly necessary to provide a service the user has expressly requested. Signing in to the merchant cabinet is such a service: without access_token and refresh_token we cannot keep you authenticated, and without NEXT_LOCALE we cannot honor your language choice. For this reason we do not display a cookie banner.
5. Third-party and advertising cookies#
We do not use advertising networks, social media pixels, retargeting tags, session-replay tools or third-party analytics on https://paysell.me, and no third party sets cookies through our pages. We do not sell or share data collected through cookies.
Pages of merchants who use Paysell are outside our control. If you follow a link to a merchant's website, that site's own cookie practices apply.
6. Analytics and future cookies#
We may in the future introduce privacy-respecting analytics to understand how the cabinet is used and to detect errors. If and when we do:
- this policy will be updated with the name, provider, purpose and lifetime of each new cookie;
- non-essential cookies will be set only after you give consent through a cookie banner or a setting in the cabinet;
- you will be able to withdraw consent at any time, and refusing will not limit your access to the Service.
Placeholder for future entries: [[Analytics provider, cookie names, purpose, lifetime]].
7. How to control cookies#
You can control cookies in several ways:
- Sign out. Signing out of the cabinet invalidates and clears your authentication cookies.
- Revoke sessions. The security page of the cabinet lists your active sessions with their IP address, user agent and last activity, and lets you revoke any of them, which invalidates the corresponding
refresh_token. - Browser settings. Every major browser lets you view, delete and block cookies for a specific site.
- Clear site data. Clearing data for
paysell.meremoves all cookies and local storage described here.
Blocking or deleting access_token and refresh_token will sign you out and prevent you from using the merchant cabinet. Blocking NEXT_LOCALE only means the interface reverts to its default language.
8. Changes to this policy#
We may update this Cookie Policy when we change the cookies we use or when the law changes. The version number and effective date at the top of the page identify the current text. Material changes — in particular the introduction of any non-essential cookie — will be announced in the cabinet before they take effect.
Contact#
Questions about this policy can be sent to [[DPO email]] or [[Legal email]], or raised through a support ticket in the merchant cabinet. Postal address: [[Company legal name]], [[Registered address]].