Updated June 11, 2026
Delivery policy
This policy explains how Keyndo delivers digital goods, how masked key reveal works, and what buyers should do before relying on or redeeming a code.
1. Digital-only delivery
Keyndo sells intangible digital goods. Unless a product page clearly states otherwise, delivery does not involve physical shipping, postal tracking, courier service, customs processing, or physical transfer. The main delivery location is the buyer order page inside the Keyndo storefront.
2. Order page as delivery record
The order page, order ID, delivery email, product line, key status, reveal status, wallet ledger, and timestamps are the main delivery record. Buyers should keep the order ID and access to the Keyndo account used for checkout. Support may rely on these records when reviewing whether delivery happened.
3. Masked key state
A delivered key may appear masked until the buyer clicks reveal. Masking helps reduce accidental exposure and gives the buyer a chance to re-check product region and account compatibility. Once revealed, the buyer should treat the code as sensitive and should not post it publicly or send it to people who are not trusted.
4. Before reveal checklist
Before revealing a key, the buyer should check product name, platform, region, edition, account country, device support, activation page, account age or status requirements, and any publisher restrictions. If the buyer sees a mismatch, the safer step is to contact support before revealing the code.
5. Normal timing and exceptions
Many orders can be delivered quickly after checkout, but timing is not guaranteed for every product or every account state. Delivery can be slowed by managed-stock checks, fraud controls, suspicious activity, payment or balance review, technical incidents, catalog corrections, support review, or outside provider limitations. Most orders are delivered on the order page right after payment; orders flagged for manual review are normally completed within 24 hours — if that is not possible, you can request a store-balance refund or a replacement.
6. Managed stock
Some products may depend on imported managed key stock. If managed stock is unavailable or inconsistent, checkout may fail, delivery may be delayed, a product may show low-stock or preorder state, or support may need to review the order. Keyndo should not intentionally oversell managed-stock items where the system can prevent it.
7. No credential delivery
Delivery of a digital code does not require Keyndo to log into the buyer third-party account. Keyndo should not need passwords, account cookies, recovery codes, 2FA codes, remote desktop access, or account takeover steps. Buyers should redeem codes only through official redemption pages or apps for the relevant platform.
8. Email and account access
The buyer is responsible for using a correct email and keeping access to the Keyndo account. If the buyer loses mailbox access, device access, or browser session access, support may need reasonable verification before discussing order details. Support may refuse to disclose sensitive order information to someone who cannot show a connection to the order.
9. Third-party redemption
After a key is delivered, redemption is handled by the relevant third-party platform, publisher, app store, card issuer, or software vendor. Their rules, outages, anti-fraud checks, regional restrictions, account bans, age limits, sanctions restrictions, or technical errors can affect redemption even if Keyndo delivery records show that a code was supplied.
10. Delivery evidence and disputes
If delivery is disputed, Keyndo may review order records, key status, reveal logs, wallet ledger, timestamps, request metadata, support history, and buyer evidence. The buyer should avoid revealing or sharing the code further while support review is ongoing, because additional exposure can make the dispute harder to verify.
11. Replacement or refund path
Where delivery fails or the delivered code is proven invalid before use, support may choose a replacement, a store-balance refund, or another reasonable correction. The exact remedy depends on stock, reveal status, redemption evidence, product type, abuse signals, and what the system can safely verify.
12. Reveal as a delivery event
For masked digital goods, the reveal action is a key delivery event. Once the buyer chooses to reveal the value, Keyndo may treat the item as exposed for refund and support review even if the browser is later closed, local storage is cleared, the device is changed, or an email notice was not received.
13. Allocation and stock failures
A checkout can depend on stock allocation. If a stock record becomes unavailable, fails validation, is withdrawn, or cannot be safely delivered, Keyndo may pause the order and choose replacement, cancellation, or balance credit. A product visible in the catalog is not an unlimited promise of future supply.
14. Browser and session interruptions
Blocked cookies, disabled JavaScript, privacy extensions, unstable network state, VPN changes, wrong device time, or expired sessions can interrupt checkout and reveal screens. If the order exists but the page looks wrong, use order history and support instead of repeating the purchase or trying to inspect hidden application state.
15. Manual delivery checks
Some orders may require manual checks before the sensitive value is shown. Triggers can include high-risk payment state, unusual account behavior, stock quality review, promo abuse signals, or inconsistent technical events. Manual review protects the buyer and the store, and does not require the buyer to share third-party passwords.
16. Keep revealed codes private
After reveal, protect the code like a password for that product. Do not publish it, forward it to unknown people, include it in public screenshots, or store it in shared documents. If the code leaves your control, Keyndo may be unable to prove whether later use came from a store issue or outside disclosure.
17. Delivery is not redemption control
Keyndo delivers the digital value described by the order. Redemption is performed by the destination platform, publisher, wallet, console, launcher, or subscription service under its own rules. Delivery evidence can show that Keyndo provided the item, but it cannot force a third-party service to accept an account that fails its own checks.
18. Delivery support evidence
For delivery issues, provide the order identifier, product name, screenshot of the order state, screenshot of the redemption message if any, and the time the issue occurred. Support can compare these details with order status, allocation records, reveal logs, and ledger entries.