Privacy policy

1. Who we are

Traders Proxy operates the website at tradersproxy.com, the client portal at portal.tradersproxy.com, the associated billing flows, the proxy relay service, and the MTProto relay service. References to “we”, “us”, or “our” in this policy mean Traders Proxy and any entities through which it operates.

By using the service, you acknowledge that we may process the categories of data described below for account management, security, billing, support, abuse prevention, and legal compliance.

2. Data we collect

We collect the following categories of information depending on how you use the service,

• Account data. Email address, username, hashed password, password-reset and recovery state, plan type, device limit, route preferences, and profile settings.
• Payment and billing data. Checkout is handled by Stripe, payments are processed by Stripe. We receive and store billing identifiers, order or invoice references, subscription status, purchase email, plan name, renewal state, and billing history. Raw card numbers and payment credentials are handled exclusively by the payment processors and are never stored on our servers.
• Security and login data. IP address at login, user agent string, session cookie state, CSRF token state, a browser-bound device cookie, failed login attempts, and recovery or claim token hashes.
• Connection and service data. IP addresses used during proxy sessions, connection counts, bandwidth totals, session timing, node-level latency and jitter measurements, and session lifetimes. This data is operational, used to run the service, enforce plan quotas, detect abuse, and diagnose issues.
• Operational and support data. Account-recovery events, billing-flow records, service diagnostics, and administrative notes generated in the course of running the platform.
• Technical data. Browser type and version, and request metadata necessary to operate the service securely.

2.1 YouTube account connections

If you connect a YouTube account, we request the minimum Google OAuth scopes needed for the feature you are using,

• youtube.readonly for the subscriber linking flow, so we can read the signed-in channel ID and channel title and attach that channel to your Traders Proxy account.
• youtube.readonly and youtube.channel-memberships.creator for the creator/admin flow, so we can read the creator channel details and verify active channel members against the memberships API.

We use that YouTube data only to verify membership status, assign or revoke the associated Traders Proxy entitlement, and maintain the connection record you can disconnect from the dashboard at any time. We do not use the YouTube data for advertising, resale, or unrelated profiling.

For the creator/admin workflow, we store the Google OAuth tokens server-side so the app can refresh access and run membership reconciliation. For the subscriber workflow, we only keep the link record that ties your Traders Proxy account to your YouTube channel.

Traders Proxy’s YouTube-connected features use YouTube API Services. By connecting a YouTube account you agree to be bound by the YouTube Terms of Service, and the handling of data obtained through the YouTube API is governed by the Google Privacy Policy in addition to this policy.

Data retention and deletion. We retain YouTube API data only for as long as your connection is active. The subscriber link record and any cached membership details are deleted when you disconnect YouTube from your dashboard, and server-stored creator OAuth tokens are removed when the creator connection is revoked. Cached membership records that are no longer active are pruned automatically by our reconciliation worker. You may revoke Traders Proxy’s access to your Google and YouTube data at any time through the Google security settings page, and you may request deletion of any YouTube-derived data we hold by asking support on the contact page or in your dashboard.

3. What we do not inspect

Our proxy and relay services forward network traffic at the TCP layer without inspecting packet payloads. In normal operation, we do not read, store, or log,

• the content of your trading orders or positions.
• your account balance or equity at any broker.
• your broker identity beyond the destination hostname and port used by your trading platform.
• trade details, strategy parameters, or EA configuration data.

Diagnostic exception. We may temporarily enable enhanced connection-level logging for abuse investigation, troubleshooting, or service recovery. This may capture additional metadata on a limited, time-bound basis. Payload content is never part of diagnostic logging.

4. How we use data

We use the information we collect to,

• create and manage accounts, subscriptions, and portal access.
• authenticate users and protect accounts from unauthorised access.
• provision and operate routing, proxy, and MTProto relay services.
• measure usage, enforce plan quotas, and manage billing.
• detect fraud, abuse, credential stuffing, and policy violations.
• investigate service problems and maintain platform reliability.
• improve routing quality, performance, and security.
• comply with legal, tax, audit, and enforcement obligations.

5. Cookies

The portal and site use cookies for the following purposes,

• Session cookies. Required to keep you authenticated in the portal. Expire when you close your browser or after a configured idle period.
• CSRF tokens. Required for security on form submissions and API requests. Not used for tracking.
• Browser-bound device cookie. An opaque random identifier used to bind your session to a specific browser, reducing session-hijacking risk. It is not a hardware fingerprint and is not shared across sites.
• Proxy-password cache. A short-lived, encrypted cookie set when linked-mode portal access is active. Scoped to the portal domain only.
• Chat cookie (axv). Strictly necessary for the chat with Axel. A random identifier that carries your conversation across pages, kept for 30 days. Clear chat removes it. See section 13.

We do not use advertising cookies, marketing pixels, or third-party tracking scripts on the site or portal. If we add analytics in future, we will update this section to identify the provider and the data collected. You can manage cookies through your browser settings. Disabling necessary cookies may break portal functionality.

6. Sharing and disclosures

We share information only in the following circumstances,

• Stripe (billing platform). Manages the order flow and checkout pages. Stripe receives your name and email at purchase and manages billing records on our behalf. Your payment credentials are handled directly by Stripe and are never stored on our servers. Their privacy practices are governed by the Stripe Privacy Policy.
• Cloudflare (CDN and security). Sits in front of our web infrastructure for DDoS protection and CDN delivery. Cloudflare may process request metadata including IP addresses and user agents in the course of providing these services.
• Hosting and infrastructure providers. The servers and networks running the service are hosted with third-party providers. These providers process data incidental to running the platform (such as server logs) under data processing arrangements where applicable.
• Legal and enforcement. We may disclose data when required to comply with law, respond to lawful process, protect our rights or the rights of others, investigate abuse, or respond to a verified government or regulatory request.
• Business transfer. In the event of a merger, acquisition, or asset sale, user data may transfer as part of that transaction. We will notify affected users by a notice in the dashboard or on the site if this occurs.

We do not sell personal data. We do not share personal data with advertising networks, data brokers, or marketing partners.

7. Retention

We retain data for as long as needed to operate the service, prevent abuse, resolve disputes, comply with law, and enforce our agreements. Specific periods,

• Operational and connection logs (bandwidth totals, session counts, node metrics, IP addresses during proxy sessions), 30-day rolling window. Data outside this window is deleted or aggregated by automated maintenance jobs.
• Security and login data (login events, failed attempts, session records). Retained for the life of your account, and for a reasonable period after closure to support abuse prevention and dispute resolution.
• Account data (email, plan, profile settings). Retained for the life of your account. Deleted on verified account-closure request, subject to the compliance caveat below.
• Billing and payment records. Retained for 7 years from the date of the transaction for tax, accounting, and legal compliance obligations. We may retain enough to respond to chargeback and dispute processes beyond this period where required.

Some data that must be retained for legal or compliance reasons cannot be deleted on request. We will inform you if that applies to a specific deletion request.

8. Security and breach notification

We use technical and organisational safeguards designed to protect personal data, including access controls, secret management, signed and device-bound sessions, CSRF protections, and rate limiting. No system is perfectly secure, and you use the service at your own risk.

If you believe your account has been compromised, use the portal recovery and credential-rotation flows immediately.

If we become aware of a personal data breach that is likely to result in a risk to your rights or freedoms, we aim to notify affected individuals within three days of discovering the breach, to the extent we can identify them and consistent with our legal obligations. We will also notify relevant supervisory authorities as required by law.

9. International transfers

Traders Proxy operates with infrastructure and service providers in multiple countries. Your data may be processed in a country other than your own. Those countries may have data protection laws that differ from your jurisdiction.

Axel’s messages go to an AI service provider in the United States, as section 13 explains.

Where we transfer data outside the European Economic Area or the United Kingdom, we aim to do so under appropriate safeguards, such as standard contractual clauses or equivalent mechanisms, to the extent required by applicable law.

10. Your rights

You can update certain profile details directly through the portal. Depending on where you live, you may also have additional rights under applicable law,

• Access. Request a copy of the personal data we hold about you.
• Correction. Ask us to correct inaccurate or incomplete data.
• Deletion. Request deletion of your personal data, subject to retention obligations described in Section 7.
• Restriction or objection. Request that we restrict or stop certain processing, where applicable law permits.
• Portability. Receive certain data in a portable format, where applicable.

GDPR and UK DPA rights (EEA and UK residents). If you are located in the European Economic Area or the United Kingdom, you have rights under the General Data Protection Regulation or UK GDPR respectively, including those listed above. You may also lodge a complaint with your local supervisory authority.

California residents (CCPA/CPRA). If you are a California resident, you may have rights to know what personal information we collect and how we use it, to delete personal information, to correct inaccurate information, and to opt out of the sale or sharing of personal information. We do not sell or share personal information as those terms are defined under the CCPA/CPRA. To exercise your rights, ask support on the contact page or in your dashboard.

To submit a rights request, ask support on the contact page or in your dashboard. We will respond within the timeframe required by applicable law.

11. Children

The service is not intended for persons under 18. We do not knowingly collect personal data from anyone under 18. If you believe a minor has created an account or provided us information, ask support on the contact page or in your dashboard and we will investigate and remove the data where appropriate.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the “last updated” date at the top of this page and post the updated version on the site. For material changes, we will notify users by a prominent notice in the dashboard. Continued use of the service after an update means you accept the revised policy to the extent permitted by law.

13. Chats with Axel, our AI assistant

When you write to Axel, our support assistant, we keep the conversation and a short record of what you asked about (for example the platform, plan and broker city you mentioned) so Axel can carry on as you move between pages or come back. We remove passwords, card numbers, codes and links before anything is stored, and you should never type them.

13.1 Who processes your messages

Axel’s replies are written by an AI service provider in the United States. Your messages, and the account details Axel needs to answer them, are sent to that provider to produce each reply. The provider may keep them for a limited time under its own terms, for example to check for misuse.

13.2 What we keep, and for how long

• Chats without an account. Kept on the support assistant’s server for 30 days from your last message, under a random identifier.
• Chats when you are signed in. Kept for 90 days from each message and linked to your account. Your earlier chat is linked only if you choose to bring it with you. Clear chat history in your dashboard deletes your messages and the record of what you asked about.
• Records of actions you confirm, such as a refund or a change of city, kept in an audit record with your billing and account records. Clearing your chat history does not remove it. If you close your account, your chats are deleted and the audit record is anonymised. Billing records are kept for 7 years, as in section 7.

13.3 The axv cookie

Axel sets one cookie, axv, when you send your first message. It is strictly necessary for the chat, it holds a random identifier that carries your conversation from page to page. It lasts 30 days, is sent only over a secure connection, and scripts on the page cannot read it. Clear chat in the chat window removes it. The cookie policy lists it with the others.

13.4 Automated decisions

Checks on your account are made by our rule-based software. When you ask for a refund, our systems check the request against the refund policy using your plan, your payment dates, your data use and your connection records, and issue eligible first-payment refunds through Stripe. When you ask Axel to change your city, renewal or contact details, our systems check the request against your plan before executing it.

14. Contact

For privacy-related questions, rights requests, or concerns about how we handle your data, ask support on the contact page or in your dashboard. [email protected] receives legal notices only. It doesn’t reply.

Axel handles requests in your dashboard or on the contact page, and we respond within the timeframe your jurisdiction requires.