Updated June 11, 2026
Cookie policy
This policy explains how Keyndo uses cookies, local storage, and similar browser-side technologies for sessions, security, cart state, preferences, and ordinary storefront operation.
1. What cookies and storage are
Cookies are small records stored by the browser and often sent back to the server with requests. Local storage is browser-side storage that usually remains on the device until cleared. Similar storage can be used to keep sessions, preferences, cart state, checkout continuity, security tokens, and interface state working across pages.
2. Essential session storage
Essential cookies may keep the buyer signed in, separate the Keyndo session from other site surfaces, protect authenticated actions, and let the server recognize the account during wallet, checkout, support, order, and reveal flows. Without essential session storage, account features may not work.
3. Security and CSRF storage
Keyndo may use CSRF-related tokens, same-origin checks, session identifiers, rate-limit signals, and request metadata to reduce forged forms, automated abuse, repeated failed actions, suspicious traffic, and unauthorized state-changing requests. These controls are part of the store security model.
4. Cart and checkout storage
Cart contents, selected quantities, product slugs, promo entry state, checkout continuity, and recently selected preferences may be stored locally so that the buyer can move between pages without losing the current selection. Server-side order records are created only when checkout is accepted.
5. Locale and currency preferences
The browser may store the chosen language and display currency. Display currency is a presentation preference and does not by itself change the internal settlement logic of the wallet or order records unless the checkout system expressly records a different settlement value.
6. Support and legal page behavior
Storage may help support forms, navigation, legal pages, and interface controls behave consistently. Keyndo does not need browser storage for third-party account passwords, third-party account cookies, 2FA codes, recovery codes, payment card secrets, or private platform credentials.
7. Optional analytics and diagnostics
The store may use technical logs or privacy-conscious diagnostics to understand errors, performance, suspicious traffic, and page behavior. This policy does not claim the use of a specific analytics vendor. If analytics or diagnostics are added, they should remain tied to storefront operation, security, or product improvement rather than sale of private account access.
8. Clearing or blocking storage
A buyer can clear or block cookies and local storage through browser settings. Doing so may sign the buyer out, empty the local cart, reset language or currency, interrupt checkout, hide a pending top-up intent from the local interface, or require a fresh session. Completed orders and server-side audit records may remain.
9. Shared devices
On a shared or public device, the buyer should sign out and clear storage if needed. Anyone with access to the browser session may see account pages, order history, wallet state, or masked order information. Keyndo cannot protect a buyer from all risks created by an unlocked shared device or compromised browser profile.
10. Storage changes
Keyndo may change cookie names, storage keys, lifetime, format, or purpose as the store evolves, provided the storage remains connected to sessions, security, preferences, cart behavior, checkout, order display, support, diagnostics, abuse prevention, or required records.
11. Order and reveal safety storage
Browser storage can help keep the correct order and reveal context attached to the current session. This reduces accidental repeated actions and helps the interface recover after refresh. Sensitive code values should still be controlled by server-side delivery logic rather than trusted only to browser storage.
12. Fraud and rate-limit identifiers
Keyndo may use cookies or similar identifiers to slow repeated failed actions, prevent brute-force attempts, reduce promo abuse, and keep checkout available for ordinary buyers. These identifiers may remain for a period after logout because abuse prevention cannot depend only on a visible signed-in session.
13. Operational diagnostics
The store may record limited diagnostics about broken pages, failed checkout steps, delivery errors, slow routes, and device categories. These diagnostics are used to keep the service reliable and are not meant to turn essential store activity into unrelated advertising profiles.
14. Third-party component storage
If a payment, support, security, media, or embedded component appears in a specific flow, that component may use its own cookies or storage under its own policy. Keyndo cannot control cookies set by the third-party sites where you later redeem a purchased digital item.
15. Retention after logout
Logging out ends the active account session, but it may not remove every preference, rate-limit marker, security value, or local cart entry from the browser. Server-side order, balance, reveal, and support records also remain because they are part of the store ledger and dispute history.
16. Cookie questions
For cookie or privacy questions, contact support from the relevant account where possible. Include the browser, device, and account context needed to understand the problem, but do not send passwords, two-factor codes, recovery phrases, payment card numbers, or unrelated private documents.