Kebijakan Privasi

1. Who We Are

mt5depot.com ("the Service") is operated by Attempia Limited ("we", "us", "our"), the data controller for the personal data described here. See our Terms of Service for the operator's registration details. For privacy enquiries, contact us via the contact form.

2. Data We Collect

We collect the following categories of data:

• Account data: If you create an account, we collect the email address and password you provide, your country of residence, an optional display name, and your marketing-email preference. Passwords are transmitted over HTTPS and stored only by our authentication service (see Section 8); we do not retain them in plain text.
• Consent records: When you register, we record the fact and version of the Terms of Service and Privacy Policy you accepted, and your acknowledgement of the reverse-solicitation notice, together with the date. When you buy a Builder licence, we additionally record that you requested immediate access and acknowledged losing the right of withdrawal, with the time of that acknowledgement. We keep these records to evidence consent and to defend against payment disputes.
• Purchase and licence data: If you buy a Builder licence, we store the transaction identifier returned by PayPal, the state of your licence (type, whether it is perpetual, status), the purchase date, and the billing history shown in your account. We never receive or store your card, bank, or PayPal login details — those are handled entirely by PayPal.
• IB programme data: If you submit a broker introducing-broker (IB) link request, we collect the broker name, the broker account reference you provide, and the status of the request.
• Contact form submissions: Name and email address when you submit a contact request.
• Analytics data: Anonymised page-view data via Cloudflare Analytics (no cookies, no cross-site tracking). This may include approximate country-level location derived from IP address.
• Product usage events: Anonymous, first-party feature-usage counters for the EA Builder (for example: a template was loaded, a compile succeeded or failed, a file was downloaded). These events contain no account identifiers, no IP address, and no cookies — only the event name and a coarse label such as a template id.
• Log data: Standard server access logs, including those generated by account registration and sign-in requests — IP address, browser type (user-agent), referring URL, and pages visited — used for security and abuse prevention.
• Cookies and local storage: See Section 10 for the full list. We minimise cookie use and set no advertising cookies. When you are signed in we store a session token in your browser's local storage; we also store your cookie-banner choice and your light/dark theme preference there. PayPal's checkout script may set its own cookies on the pricing page when you are signed in — Section 10 states the exact conditions.

3. How We Use Your Data

• Creating and managing your account, authenticating sign-in, and verifying your email address.
• Processing and verifying broker IB link requests you submit.
• Taking payment for a Builder licence, activating the paid features on your account, and issuing receipts.
• Handling refund requests under our Refund Policy, and responding to chargebacks or payment disputes — which includes providing the payment provider with the record of the purchase, the licence activation time, and your checkout consent.
• Sending marketing emails only where you have opted in (you can withdraw consent at any time).
• Recording your acceptance of our Terms and Privacy Policy, the reverse-solicitation notice, and your consent to immediate access at checkout.
• Responding to contact form enquiries.
• Analysing aggregate site usage to improve the Service.
• Maintaining security and preventing abuse.
• Complying with legal obligations.

We do not sell, rent, or share your personal data with third parties for marketing purposes.

4. Legal Basis for Processing (GDPR)

Where GDPR applies, our legal basis for processing is:

• Contract performance / pre-contractual steps (Art. 6(1)(b)) for creating and operating your account, IB link requests, contact form responses, and supplying and maintaining a Builder licence you have purchased.
• Legitimate interests (Art. 6(1)(f)) for analytics, security logging, abuse prevention, and establishing or defending legal claims — including evidencing your checkout consent when a payment dispute is raised.
• Legal obligation (Art. 6(1)(c)) for retaining consent and regulatory-acknowledgement records, and keeping transaction records for accounting and tax purposes.
• Consent (Art. 6(1)(a)) where we request it explicitly (e.g. optional marketing emails).

5. California Residents (CCPA)

If you are a California resident, please note: mt5depot is not directed at California residents as part of its passive-solicitation regulatory model. We do not sell personal information. You may request deletion of any personal data we hold about you by contacting us via the contact form.

6. Data Retention

Account data and consent records are retained for as long as your account is active and for a reasonable period afterwards to meet legal and regulatory obligations. IB link request data is retained for the duration of the relationship and any applicable record-keeping period. Contact form data is retained for up to 12 months. Access logs are retained for up to 30 days. Analytics data is aggregated and anonymised with no individual retention period.

Purchase records and the related consent record are kept longer than other data. Because a Builder licence does not expire, we keep the record of your purchase and licence state for as long as the licence exists, and we retain transaction records for the period required by applicable accounting and tax rules — typically several years after the transaction. This applies even if you close your account, since we would otherwise be unable to honour the licence or to answer a payment dispute or tax enquiry about it.

You may request deletion of your account and associated data at any time (see Section 7). Where we must keep a purchase or consent record for one of the reasons above, we will delete or anonymise everything else and tell you what was retained and why.

7. Your Rights

Subject to applicable law, you may have the right to:

• Access personal data we hold about you.
• Request correction or deletion.
• Object to or restrict certain processing.
• Data portability (where applicable).

To exercise these rights, contact us via the contact form.

8. Third-Party Services

We use the following third-party services that may process data:

• Our authentication service (api.mt5depot.com): Account, consent, purchase, and IB link data are processed and stored by our own authentication API, which we operate on a dedicated server. This data is not shared with other third parties except as described here.
• PayPal: Our payment processor for Builder licences. When you buy a licence you transact with PayPal directly; PayPal collects and processes your payment details and provides us with a transaction record so we can activate your licence and issue a receipt. PayPal acts as its own controller for that data and is subject to PayPal's privacy policy. If you raise a chargeback or dispute, we will supply PayPal with the purchase record, licence activation time, and your checkout consent in order to respond to it.
• Cloudflare: Hosting and delivery of the site, DDoS protection, and privacy-first analytics. Subject to Cloudflare's privacy policy.
• GitHub: Hosting of the site's source code and the build pipeline that publishes it.

Broker links on this site lead to third-party websites. We are not responsible for their privacy practices.

9. International Transfers

We are incorporated in Seychelles, so personal data may be transferred there. Data processed by Cloudflare and by PayPal may be handled in various jurisdictions, including the United States and the European Union. We rely on standard contractual clauses or equivalent safeguards where applicable.

10. Cookies and Local Storage

mt5depot.com is a static site served via Cloudflare, and we minimise cookie use. We do not use advertising cookies, behavioural tracking cookies, or third-party analytics cookies that track you across sites.

Cookies we use

We set no first-party cookies of our own beyond the Cloudflare security cookies above. These are essential for the secure operation of the site and cannot be disabled without breaking site functionality. One third-party script — PayPal's checkout SDK — can set its own cookies, but only in the situation described under Payments below.

Local storage

In addition to the cookies above, we use your browser's local storage (not cookies) for three first-party, functional purposes only:

These entries stay on your device and are not used for advertising or cross-site tracking. You can remove them at any time by clearing your browser's site data, or by logging out (which removes the session token).

The consent banner

On your first visit we show a consent banner. Because the only cookies we set are Cloudflare's strictly necessary security cookies — which are exempt from prior consent under the ePrivacy framework and are required for the site to function — choosing Decline does not remove them, and does not change what data we store. The banner's purpose is to disclose our cookie use and record that you have seen this notice; your choice is saved in local storage (see above). We set no optional, advertising, or tracking cookies that a decline would need to switch off.

Analytics

We use Cloudflare Web Analytics, which is cookieless and does not track users across sites. No cookies are set for analytics purposes, and no personal data is sent to third-party analytics providers. The EA Builder additionally records anonymous first-party usage counters (for example, "a compile succeeded"). These are sent to our own infrastructure only, set no cookies, and contain no user identifiers.

Payments

Builder licences are paid through PayPal. So that the payment buttons can render, we load PayPal's checkout script from www.paypal.com on the pricing page. PayPal may then set its own cookies and browser storage under its own policy — typically for fraud prevention and to carry your PayPal session through checkout. Two limits are worth stating precisely:

• The script is loaded only on the pricing page, and only if you are signed in. Signed-out visitors never trigger it, and it does not run on any other page of the site.
• We do not receive, read, or control PayPal's cookies. They are governed by PayPal's own cookie and privacy policies, not by this one.

If you never open the pricing page while signed in, no PayPal script runs and no PayPal cookies are set by this site. Section 8 above covers what PayPal shares with us after a purchase.

Third-party links and managing cookies

Links to broker websites and other third-party sites may result in those sites setting their own cookies, subject to their own policies; we are not responsible for those. You can control cookies through your browser settings — viewing what is stored, deleting individual or all cookies, and blocking cookies from specific or all sites. Disabling the essential Cloudflare cookies may prevent some security features from working correctly. For general guidance, see allaboutcookies.org.

11. Changes to This Policy

We may update this Policy at any time, including if we add features that require new cookies. An updated effective date will be displayed above. Continued use of the Service constitutes acceptance of the updated Policy.

12. Contact

Privacy questions or rights requests: use the contact form. We aim to respond within 30 days.