Extension privacy policy

What the extension reads on your device

The extension uses the current tab’s address locally to recognize a supported firm and page type. On supported pages it inspects the coupon input, associated controls and checkout messages to find and verify a coupon. It may compare the displayed cart context during an attempt so a changed selection is not mistaken for a successful application.

Coupon application starts from your action and is limited to supported, qualified flows. Copying a code writes that code to your clipboard. The extension does not submit payment or complete an order. Page addresses, page text and form contents are not included in diagnostic reports.

Optional accounts

Coupons and manual reports can be used as a guest. If you sign in, your email and password are sent securely to Supabase Auth to authenticate your existing PropFirmTrader account. The extension stores session access and refresh tokens and the returned account data locally to keep you signed in; it does not save your password.

Favourite firm choices and giveaway entries are linked to your account in our Supabase database. We use them to sync your favourites and process the giveaway you choose to enter. Your extension session is separate from website sign-in. Signing out removes the extension’s local session; it does not delete your account, saved favourites, giveaway records or reports already submitted.

Guest diagnostics

To identify broken coupon flows, the extension sends an operational record for coupon attempts and limited observations of missing controls on recognized checkout pages. These are sent as guest requests even when you are signed in. Availability observations are counted separately from attempts.

Records contain a random event ID, firm identifier, extension/adapter/catalogue versions, page category, result, stage, elapsed time, flags indicating whether the coupon field and Apply control were found, and an optional catalogue coupon identifier. Client and server timestamps are recorded. These observations help investigate failures; they are not proof of a sale.

Diagnostic payloads do not include your account ID, session tokens, email, raw URL, query string, fragment, HTML, screenshots, cookies, form values or a persistent device tracking identifier. The service receives normal network metadata, including the source IP. A server-held secret and daily context turn the proxy-provided IP into a short-lived abuse-limit hash, which is kept separately from diagnostic records.

Reports you choose to send

A manual report includes a random report ID, the chosen firm, page category and reason, an optional linked attempt ID, and your optional note of up to 500 characters. Common email, link, token, long-identifier and number patterns are redacted in the preview and again on the server.

Redaction cannot recognize every piece of personal information. Do not include passwords, account or order identifiers, payment information or other sensitive details. Authorized staff can read submitted notes to investigate the problem you report. Sending a report does not sign you up for marketing.

Local storage and retention

The extension locally caches offers, firm information and controls, stores preferences and session data, and maintains a bounded delivery queue. A queued report has not yet been confirmed by the server. Retries reuse the same ID so an acknowledged record is not counted twice.

Pending work expires after seven days, or can fail earlier after repeated delivery failures or a permanent rejection. Failed records can remain for a further seven days. Delivered payloads, including notes, are removed locally; delivery receipts last up to seven days. Queue capacity can shorten receipt or failed-record retention.

The server runs an hourly deletion job for diagnostic and manual-report records older than 30 days. This schedule applies to those application records. Account, favourite and giveaway information is separate and is not erased by that job. Contact us about access, correction or deletion of your account information; provide a report ID if your request concerns a guest report.

Infrastructure access/security logs and provider backups are separate from these records. They may contain IP addresses and request metadata and follow the provider plan and service settings; the 30-day report schedule is not a promise that every infrastructure log or backup is deleted at the same time.

Providers, affiliate visits and limited use

Supabase provides authentication, database storage and the extension’s API functions. Vercel hosts the website, including the private extension support console. These services receive the information needed to deliver and protect those functions. For context, Supabase’s privacy policy, Supabase’s log documentation and Vercel’s privacy policy describe their services.

Some offer buttons open affiliate links, and PropFirmTrader may earn a commission on a qualifying purchase. The destination firm or affiliate provider receives that visit and may use its own cookies. Its privacy policy applies there. We do not send your diagnostic note or account session to those destinations.

We use extension data to provide the features described here, investigate user-reported problems and prevent abuse. We do not sell extension user data, use it for personalized advertising, or provide it to advertising data brokers. Human access to private reports is restricted to authorized support and operational purposes.

Our use of data accessed through the extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Your choices and contact

You can remain a guest, sign out of the extension, omit a report note, or disable or remove the extension to stop its future activity. Removing it does not automatically delete information already received by our service or close your website account.

For questions or requests to access, correct or delete information, email contact@propfirmtrader.com. Please include the report ID for a guest report rather than sending account or payment secrets. We will update this page when the extension’s data practices change.