Required Safety Terms

Transaction Safety, Verification, Delivery and Sale Scope Terms

Before proceeding with any payment, escrow approval, delivery request, delivery acceptance, release approval, or acquisition completion, the buyer is required to read these terms.

These terms are provided for the protection of both the buyer and the seller. By continuing with the transaction, the buyer acknowledges that they had the opportunity to read the Safety Terms and agrees to be bound by them.

Buyer Protection, Verification, Transaction Security, Delivery, and Sale Scope Terms

This section has been prepared to ensure that the sale process related to the WordES mobile game asset is handled in a secure, verifiable, recorded, and platform-controlled manner. The purpose of the WordES sale process is not only to sell the asset, but also to create a clear structure that protects the buyer’s funds, identity, contact information, payment process, acquisition decision, and transaction security.

WordES is presented as a pre-revenue mobile game asset / source-code project. This website is an informational sales / landing page prepared to help buyers review the WordES project, sale scope, delivery boundaries, technical status, risk notes, verification rules, and transaction-security approach more clearly.

Official Website and Domain Notice

The only official sales and information website used for the WordES mobile game asset is:

wordesgamesale.com

Any other domain name, extension, copied website, mirror website, similar-looking website, or variation, including but not limited to .net, .org, .tr, .com.tr, or other regional/domain extensions, is not official, approved, or authorized unless expressly confirmed in writing by the WordES Creator/Seller.

Buyers should not make payments, share personal information, request source-code delivery, or rely on transaction instructions through similar-looking websites, different domains, copied pages, fake accounts, third-party redirects, or unofficial links.

The wordesgamesale.com domain is used as a temporary official sales / landing page domain. This domain is not included in the WordES asset sale unless separately agreed in writing.

Buyer-First Transaction Principle

The priority in the WordES sale process is not to pressure the buyer into making a fast decision or to move the buyer outside the platform. The priority is to allow the buyer to make a decision within a secure, verifiable, recorded, written, and platform-controlled process.

For this reason, pressuring the buyer, moving the buyer off-platform, directing the buyer to make private payments, asking the buyer to pay different accounts, requesting direct file/source-code transfer, or making delivery outside the official transaction dashboard is not consistent with the WordES transaction-security approach.

General Fraud, Impersonation, and Account-Takeover Risks

In high-value digital asset transactions, malicious actors may attempt to mislead buyers through fake websites, similar-looking domains, compromised email accounts, compromised sales-platform accounts, cloned or spoofed phone numbers, compromised WhatsApp accounts, fake social media profiles, deepfake video calls, cloned images, fake representatives, or convincing private messages.

For this reason, no single communication channel is considered sufficient verification in the WordES sale process. A website, email, phone call, WhatsApp message, video call, social media account, private message, or sales-platform message alone is not sufficient for payment, delivery, source-code sharing, or sale approval.

The secure transaction approach is based on the combined use of a verified sales/escrow platform, the platform’s official transaction dashboard, platform messaging, the final written agreement, the buyer’s own independent verification, and transaction-specific additional verification steps where necessary.

Communication Channels and Phone / WhatsApp Boundary

Official communication channels related to WordES may include the information stated on this website, the official messaging system of the verified sales/escrow platform, and communication channels expressly stated in writing by the WordES Creator/Seller.

However, email accounts can be compromised, phone numbers can be misused through caller-ID spoofing / SIM swap / number porting / cloning methods, and WhatsApp accounts can be compromised or impersonated. Therefore, no payment instruction, bank account, crypto wallet, private payment link, file delivery request, source-code sharing request, or off-platform transaction instruction received through email, phone, WhatsApp, video call, or social media is valid on its own.

The WordES Creator/Seller does not initiate transaction communication through phone or WhatsApp unless necessary. Phone or WhatsApp, if used, may only serve as an additional communication or verification channel; it is not a channel for payment, escrow, source-code delivery, sale approval, refund, account change, or off-platform transaction instructions.

Unscheduled calls, messages from different numbers, different WhatsApp accounts, “new phone number,” “new email,” “new payment method,” “let’s move off-platform,” “make urgent payment,” or “receive the files here” requests are not considered part of the secure transaction process.

No Off-Platform Transaction Policy

The WordES Creator/Seller does not complete private, direct, off-platform, unrecorded, or informal sales.

The sale, payment, escrow process, source-code delivery, and final transfer must be handled only through the verified sales/escrow platform, the platform’s official transaction dashboard, platform messaging, the final written agreement, and the platform’s own payment/delivery rules.

No payment should be made to any bank account, IBAN, crypto wallet, PayPal/Wise-like account, private payment link, private invoice, or off-platform payment instruction privately provided by the seller.

Payment or delivery instructions received through phone, WhatsApp, email, social media, private message, or platform message should be considered invalid unless they fully match the verified transaction/escrow dashboard and the final written agreement.

Private and Transaction-Specific Verification Approach

For security reasons, not all verification procedures are publicly listed. Serious buyers may be required to complete additional verification steps that are transaction-specific and variable.

The purpose of this approach is to avoid giving malicious actors an operational roadmap and to protect the buyer within a safer transaction structure.

Before making any payment, escrow approval, source-code delivery approval, file-access approval, project-transfer approval, or acquisition confirmation, the buyer should also use their own independent verification methods. These may include platform-message checks, escrow-dashboard checks, domain checks, official transaction-panel review, written-agreement review, payment-instruction verification, technical/source-code/project asset review, identity verification, and professional legal/technical advisory steps where considered necessary.

The buyer should not make payment, accept delivery, approve source-code delivery, or start the payment-release process in any situation that cannot be verified or that conflicts with transaction security.

Transaction Pause Principle in Case of Contradiction

If there is any different domain, different email address, different phone number, different WhatsApp account, different payment method, different delivery method, urgency pressure, request to move off-platform, direct payment request, crypto wallet, bank transfer instruction, private payment link, social media message, private message, direct source-code request, or file delivery request outside the official transaction dashboard, the process should be paused.

In such situations, the buyer should not make payment, request file delivery, give approval, or proceed unless the transaction is reviewed again only through the official dashboard of the verified sales/escrow platform and the final written agreement.

Buyer’s Review and Acceptance Responsibility

During the inspection period on the verified sales/escrow platform, the buyer is responsible for independently reviewing the delivered files related to the WordES asset, the project scope, technical structure, handover materials, data room documents, final written delivery list, and written agreement terms.

The delivery content that governs the sale is not general promotional language, marketing text, potential scenarios, or the buyer’s later expectations. The governing delivery content is only the final written agreement and the written delivery list accepted by the parties.

If the buyer raises any non-conformity claim regarding the delivered asset, such claim should be considered only if an item expressly listed in the final written delivery list was not delivered or if there is a direct conflict with an explicit term in the written agreement.

Expectations outside the sale scope, later-requested additional work, support requests, store publishing, live iOS testing, live AdMob setup, account transfer, domain transfer, trademark clearance, revenue expectations, download expectations, technical development requests, or issues arising from the buyer’s own publishing/setup process are not considered incomplete delivery.

If the buyer believes that an item expressly listed in the final written delivery list was not delivered, or that there is a situation directly conflicting with the written agreement, the buyer should report this clearly and specifically within the inspection period only through the official dashboard of the verified sales/escrow platform.

If the buyer considers the verification and review process sufficient and gives acceptance, marks delivery as received, approves release, releases payment, or provides similar confirmation through the platform/escrow dashboard, such confirmation is considered the buyer’s acceptance based on their own review, verification, and acquisition decision.

To the maximum extent permitted by applicable law, the WordES Creator/Seller shall not be held responsible for payment, data, identity, access, file, delivery, or transaction losses arising from the buyer’s own acceptance/approval decision, expectations outside the sale scope, reliance on off-platform instructions, use of unauthorized channels, reliance on fake representatives, third-party fraud attempts, or the buyer’s own failure to complete adequate verification.

Sale Scope

The WordES sale is a transfer of the WordES mobile game source-code / project-file / game-content asset package.

The main asset included in the sale consists of seller-prepared source-code / project files, game content files, icon/audio assets, technical notes, handover documents, and any additional files expressly listed in the final written delivery list.

Data room materials are provided for buyer review and transaction documentation. They are included in the delivered sale package only if expressly listed in the final written delivery list.

This sale does not include ongoing technical support, development services, publishing services, store management, advertising-account management, maintenance services, revenue sharing, operational partnership, or active post-sale work.

Items Not Included in the Sale

Unless separately agreed in writing, the following are not included in the sale:

The wordesgamesale.com domain, the seller’s personal email accounts, Google Play account, AdMob account, Cloudflare account, domain registrar account, payment accounts, personal devices, private accesses, personal identities, private passwords, third-party accounts, social media accounts, personal infrastructure, or private systems belonging to the seller.

After the sale, the buyer is responsible for setting up, managing, and verifying their own store accounts, advertising accounts, payment infrastructure, domain/hosting structure, live ad IDs, store settings, production release processes, and required third-party accounts.

The seller does not provide the buyer with access to the seller’s personal accounts, devices, email accounts, Google Play / AdMob / Cloudflare / domain registrar / payment accounts, or private systems.

Trademark / Brand Boundary

The WordES name, logo usage, brand elements, and project identity are presented as assets used by the seller within the project scope.

The WordES Creator/Seller does not guarantee registered trademark rights, trademark clearance, global-use suitability, App Store / Google Play brand approval, or absence of third-party trademark disputes for the WordES name or related brand elements.

The buyer is responsible for conducting their own brand, name, domain, store listing, trademark, regional suitability, and third-party rights checks before purchase and before publication.

Unless separately agreed in writing, the sale is not a transfer of a registered trademark; it is a transfer of a source-code / project files / game-content asset package.

Matters Not Guaranteed

WordES is presented as a pre-revenue mobile game asset. The WordES Creator/Seller does not guarantee revenue, profit, downloads, user numbers, active users, App Store approval, Google Play approval, live AdMob revenue, live advertising performance, live iOS device testing, TestFlight approval, production purchase/restore testing, trademark clearance, valuation, exit outcome, return on investment, growth result, acquisition result, or any specific commercial success.

All strategic assessments, potential scenarios, market references, growth possibilities, revenue-potential discussions, or buyer-side opportunity comments are informational and illustrative only. They should not be interpreted as guarantees of revenue, profit, growth, downloads, valuation, exit, or commercial success.

The buyer should complete their own independent technical, legal, commercial, store-readiness, platform, advertising, purchase, device, publishing, trademark, monetization, and production-readiness checks before purchase.

Delivery Integrity and Incomplete Delivery Boundary

Delivery is made only within the written sale scope and the verified sales/escrow platform process.

An incomplete-delivery claim may be considered only if an item expressly listed in the final written delivery list was not delivered.

Expectations outside the sale scope, later-requested additional developments, personal-account accesses, store publishing, live advertising setup, live iOS testing, trademark registration, domain transfer, revenue result, download result, or post-sale support requests are not considered incomplete delivery.

For the delivered ZIP/project package, the file name, delivery date, SHA-256 hash where possible, folder/file list, and platform delivery message may be recorded. These records may be used to show delivery integrity and sale scope.

The buyer should review the delivered asset within the inspection period and make their evaluation regarding scope, files, technical structure, limitations, and the written delivery list during that period.

After the source-code / project files are delivered and the buyer accepts through the platform/escrow system, off-platform refunds, off-platform repayment requests, private payment reversals, bank/crypto/PayPal/Wise instructions, or off-platform dispute processes are not accepted. Any issue must be handled only under the rules of the selected verified sales/escrow platform and the final written agreement.

No Post-Sale Support

The WordES sale is not a sale of support services. This sale is a transfer of a documented source-code / project asset.

Ongoing post-sale support, technical assistance, live setup, bug fixing, store-release preparation, advertising-account setup, iOS/Android publishing, remote connection, AnyDesk/TeamViewer session, computer access, personal-account login, operational assistance, or active project management is not included.

The WordES Creator/Seller has no post-sale technical support or operational support obligation. Any post-sale support is valid only if it is expressly, separately, and clearly agreed in writing with a defined scope and duration. If there is no such separate written agreement, the buyer is responsible for handling all post-sale setup, publishing, testing, advertising, store, payment, domain, hosting, platform, and maintenance processes.

Buyer-Side Misuse and Misleading Claims

After receiving the delivered source-code / project files, the buyer may not claim rights outside the sale scope.

The buyer may not claim that the domain was included, live iOS testing was guaranteed, App Store/Google Play approval was guaranteed, revenue or download guarantees existed, live AdMob revenue was ready, trademark clearance was guaranteed, the seller would provide post-sale support, or the seller would provide access to personal accounts, unless such matters are expressly added to the written sale scope.

The buyer may not request remote connection, computer access, personal-account login, Google Play account, AdMob account, Cloudflare account, domain registrar account, email account, payment account, personal-device access, or private-system access from the seller.

The buyer should not attempt to alter the transaction process through off-platform refunds, off-platform repayment requests, private payment reversals, chargeback directions, bank/crypto/PayPal/Wise methods, or any other off-platform payment or refund route.

Any payment, delivery, dispute, refund, acceptance, review, or transaction outcome must be handled only under the rules of the selected verified sales/escrow platform and the final written agreement between the parties.

WordES Creator/Seller Limitation of Responsibility

The WordES Creator/Seller is responsible only for the obligations expressly accepted through the verified sales/escrow platform, the platform’s official transaction dashboard, and the final written agreement between the parties.

To the maximum extent permitted by applicable law, the WordES Creator/Seller shall not be held responsible for losses or damages arising from unauthorized communication channels, fake domains, copied websites, compromised email accounts, compromised sales-platform accounts, cloned phone numbers, fake WhatsApp accounts, caller-ID spoofing, deepfake video calls, fake representatives, social media impersonation, off-platform payment instructions, private payment links, third-party fraud attempts, or the buyer’s own failure to complete adequate verification.

Binding Transaction Terms, Buyer Acknowledgment, and Acceptance

These Buyer Protection, Verification, Transaction Security, Delivery, No Post-Sale Support, and Sale Scope Terms form part of the binding transaction-safety, delivery-boundary, no-support, and sale-scope terms for the WordES asset sale when referenced on this website, in the listing, data room, transaction communication, escrow process, delivery notes, or final written agreement.

By proceeding with the purchase, entering escrow, submitting payment, accepting delivery, approving release, marking the asset as received, or otherwise completing the acquisition of the WordES asset through a verified sales/escrow platform, the buyer acknowledges, agrees, represents, warrants, and undertakes that they had the opportunity to review these terms, that they understand these terms, and that the transaction is subject to these terms, together with the final written agreement and the rules of the selected verified sales/escrow platform.

The buyer should not proceed with payment, escrow approval, delivery acceptance, release approval, or acquisition completion unless the buyer fully accepts, agrees to, and undertakes to be bound by these transaction safety, verification, delivery, no-support, and sale-scope terms.

If there is any conflict between these terms, the selected platform rules, and the final written agreement, the final written agreement and the selected verified sales/escrow platform rules will control to the extent of the conflict.

Nothing in these terms creates a revenue guarantee, valuation guarantee, store-approval guarantee, launch-success guarantee, investment advice, trademark guarantee, post-sale support obligation, personal-account access obligation, or any obligation outside the final written delivery list.

To the maximum extent permitted by applicable law, the WordES Creator/Seller shall not be held responsible for losses, disputes, or claims arising from the buyer’s failure to review these terms, failure to complete adequate verification, reliance on unauthorized channels, reliance on off-platform instructions, expectations outside the final written delivery list, acceptance of the transaction despite unresolved verification concerns, or any claim outside the written sale scope.