Privacy Policy

Who is responsible

TradeMate is a product brand operated by a business registered in Lebanon.

Information and purposes

• Account access: email, account identifier, verification and session records, to verify access and protect accounts.
• Licensing: hashed package code and reference, ownership, activation and expiry dates, device name and device-binding identifier, to redeem a code and manage the two-computer entitlement.
• Security: IP-related rate-limit information and account/device event records, to prevent abuse and investigate faults. Hosting providers may also process request metadata.
• Purchases, when checkout launches: contact and delivery details, order information, payment status and shipment details. Payment and courier providers remain to be selected.
• Support: fault descriptions, screenshots and diagnostic information you send. Remove broker passwords, full payment details and unrelated personal information.

Email verification is necessary for account access; a package code is needed to claim a licence; pairing details are needed to connect a computer. Without them, those services cannot be provided. Marketing permission should be optional and separate.

Reasons for processing

Proposed purposes are providing requested accounts, licences and orders; meeting applicable record-keeping duties; securing the service; and answering support requests. Marketing needs a separately established lawful basis and opt-out. Reading this notice is not blanket consent.

Providers and international transfers

The prepared architecture uses Cloudflare infrastructure and a Resend email integration. Production accounts and real email are not connected in the inspected local implementation. Payment, courier and support providers remain to be selected. Necessary information may be shared with providers for their roles, or disclosed where law requires.

Cookies

The prepared account service uses an operational sign-in cookie with a seven-day session lifetime in its current configuration. Sign-out revokes the session. Blocking the cookie prevents persistent sign-in. The marketing preview has no live account service.

Retention and security

Keep information only for documented service, security and legal needs. The prepared implementation hashes package codes and session secrets, limits sign-in attempts and schedules cleanup of short-lived records. No service can guarantee absolute security.

Your requests and changes

Depending on applicable law, you may request access, correction, deletion, restriction or portability, object to certain uses, withdraw consent, and complain to the competent authority. Some records may need to remain for lawful purposes. Proportionate identity verification may be needed. The final notice must show its effective date and explain material changes.