Updated June 11, 2026
Acceptable use policy
This policy describes conduct that is not allowed on Keyndo and the actions the store may take to protect buyers, inventory, support, security, and third-party rights.
1. Lawful storefront use
Keyndo may be used only for lawful browsing, account management, internal balance use, checkout, support, and redemption of legitimately obtained digital goods. Users must not use the store to harm other buyers, support staff, third-party platforms, publishers, payment systems, infrastructure providers, or the storefront itself.
2. No stolen payments or account abuse
Users must not use stolen payment methods, unauthorized accounts, fake identities, account takeovers, compromised mailboxes, stolen cards, unauthorized crypto wallets, or any other method intended to create a payment or balance record without lawful authority from the owner.
3. No credential goods
Users must not buy, sell, request, upload, exchange, or support the exchange of third-party account passwords, account cookies, session tokens, 2FA codes, recovery codes, stolen accounts, compromised accounts, private keys, seed phrases, or access to accounts that do not belong to them. Keyndo is for digital goods, not account theft or account access brokerage.
4. No technical abuse
Users must not scrape, overload, scan, reverse engineer, bypass rate limits, tamper with requests, exploit bugs, probe private endpoints, bypass CSRF or session controls, automate checkout, interfere with inventory, enumerate keys, decrypt keys, reveal keys not linked to their own order, or attack the site or its providers.
5. No support manipulation
Users must not threaten, harass, impersonate, spam, or mislead support; submit false screenshots; hide material facts; claim a code is invalid after sharing it; pressure support through chargeback threats; or create multiple accounts to repeat the same dispute. Support exists to resolve real order issues, not to generate free goods.
6. No promo and referral abuse
Promo codes, discounts, referral links, bonuses, and store credits may be limited by account, order, device, region, time, inventory, or support decision. Users must not create duplicate accounts, manipulate identifiers, automate redemptions, resell promo benefits, or exploit technical mistakes to multiply discounts or credits.
7. Respect third-party rules
Users must follow the rules of the platform, publisher, game, app store, software vendor, card issuer, or service where a code is redeemed. Keyndo may limit activity connected to regional bypassing, sanctions evasion, prohibited resale, account bans, botting, cheating, unauthorized automation, or attempts to avoid third-party restrictions.
8. Content and communication rules
Messages, names, ticket text, screenshots, or other content submitted to Keyndo must not contain unlawful material, threats, malware, credential dumps, private data of other people, hate content, spam, misleading claims, infringement, or instructions for abuse. Keyndo may remove or ignore content that creates risk or prevents support from safely handling the case.
9. Enforcement actions
If Keyndo detects or reasonably suspects misuse, the store may reject checkout, delay delivery, require reasonable verification, remove promo benefits, refuse refunds, revoke or disable keys where possible, restrict wallet actions, limit support, suspend accounts, preserve logs, block traffic, or take other proportionate action needed to protect the storefront and users.
10. Reporting abuse
A user who discovers suspected fraud, credential theft, leaked keys, impersonation, platform abuse, or a security weakness should contact support with a clear description. Reports should not include unnecessary secrets, exploit steps beyond what is needed to understand the issue, or private data of unrelated people.
11. No balance exploits
Do not exploit rounding, duplicate requests, race conditions, refund loops, promo stacking mistakes, delayed top-up status, or any ledger bug to create or spend value that was not legitimately yours. If you discover a balance error, report it instead of testing how far it can be pushed.
12. No key extraction
Do not try to decode, derive, scrape, guess, enumerate, inspect, or bypass masked key values, reveal endpoints, stock records, or another user's order data. A masked value is protected delivery data, not a puzzle or public inventory source.
13. No automation or scraping
Automated catalog scraping, scripted checkout, order enumeration, bot-driven promotion farming, brute-force redemption attempts, and traffic patterns that degrade service are prohibited. Keyndo may block automation even when it uses ordinary public routes because scale and intent can create risk.
14. No region evasion
Do not use false addresses, misleading account data, VPN rotation, proxy chains, borrowed accounts, or payment mismatches to bypass product region restrictions, sanctions, platform country rules, currency limits, or publisher eligibility checks. Region mistakes caused by evasion are not a support priority.
15. No false evidence
Do not submit edited screenshots, fabricated error messages, incomplete timelines, false account-region claims, fake chargeback stories, or statements that hide successful redemption, resale, transfer, or public disclosure of the code. False evidence can lead to refund denial and account restrictions.
16. Resale-pipeline limits
Unless Keyndo separately approves it in writing, do not use the store as a bulk resale source, automated stock feed, arbitrage pipeline, or marketplace backfill. High-volume purchasing, scripted behavior, frequent disputes, or stock-sweeping patterns may be limited to protect ordinary buyers.
17. Responsible disclosure
If you find a vulnerability, report it privately and stop before accessing other users' data, revealing keys, changing balances, modifying orders, or keeping unauthorized access. A good-faith report is welcome; exploitation, publication of working abuse steps, or retention of obtained data is not.
18. No impersonation
Do not impersonate Keyndo, support staff, publishers, payment providers, suppliers, creators, or other buyers. Do not create screenshots, listings, messages, domains, or social posts that falsely imply official affiliation, guaranteed redemption support, or authority to resolve third-party account issues.
19. Enforcement evidence
Enforcement can rely on order history, support records, ledger entries, reveal logs, payment state, technical signals, and promotion use. Keyndo may explain the general reason for an action without revealing detection rules, supplier details, risk thresholds, or private information about other users.
20. Appeals and conduct during review
If you think a restriction is wrong, contact support with clear evidence from the affected account. Creating new accounts, hiding the connection, threatening staff, filing false disputes, or continuing the same behavior while asking for review can make reinstatement less likely.