Your data. Clear boundaries.

This policy describes the Tradexers website and its supported app features, built by Piratechs. It covers information handled through this application; independent websites, Google accounts, payment services and brokerage accounts also have their own privacy notices.

Public research pages and market browsing are available without signing in. Optional account, connection and billing actions send additional information to the services needed for those actions. Privacy questions and requests can be sent to info@piratechs.com.

Firebase Authentication handles Google sign-in on web and email/password sign-in, verification and password reset. The authentication service processes the credentials you enter. Tradexers uses the resulting account identifier and available name, email and profile image to provide the signed-in experience; passwords are not stored in public Firestore profile documents.

Cloud Firestore stores account identity mappings, display name and bio, active status and role, private workspace preferences, Watchlist, Starred, symbol research lists and manual position records. Signed-in notification read receipts are private to the account. Administrative access is checked separately from ordinary account access and paid subscription state.

Guest workspace records are not automatically uploaded when you sign in. An explicit Profile import can move supported device preferences, lists and manual records into an untouched cloud workspace; brokerage credentials and temporary provider sessions use separate storage.

Guest lists, saved symbols, manual entries, appearance preferences and notification read history can be stored on this browser or device. Local connection credentials, when you choose to save them, use a separate device scope. They are not public content and do not create a cloud account.

The web app also uses account-scoped session storage for temporary bridge sessions and unresolved order-recovery records. These records help look up the same client order identifier after an uncertain response; they do not automatically submit another order.

Clearing storage or changing browser/device can remove local records and recovery information. Signing out or clearing local storage does not erase cloud records, close a brokerage account or cancel an external subscription.

With a configured full private market bridge, an authorized connection lets the bridge use your selected provider credentials to obtain permitted account information, holdings or market data. Active bridge sessions keep their working data separately from ordinary workspace preferences.

Where the signed-in connection vault is configured, saved credentials are encrypted on the server and stored in private account-scoped records. Saved credentials are not returned to the app. Provider tokens and keys are separate from public account documents, public notifications and the internal market-data API. Device-local credentials are not covered by that server-encryption claim.

On supported hosted web configurations, the signed-in app can request read-only snapshots using your saved connection reference. The application server checks your current account and connection ownership before using credentials from the encrypted vault with the brokerage. It returns permitted holdings, available balances and fetch times without returning stored credentials or creating trading or streaming sessions. Imported snapshots are temporary workspace data, distinct from manual positions and preferences saved in Firestore. After a failed refresh, the last confirmed snapshot can remain visible with its original fetch time and a failure message.

If you use supported Alpaca order submission or paper bots, the service processes the account binding, strategy settings, order instructions and provider responses needed to perform and reconcile the action. Private bot records can include order history, bot-owned quantities and account/value snapshots.

Removing a saved connection removes the app's saved credentials for that connection; revoking a key at the provider is a separate action. Do not submit provider passwords, keys or access tokens through Contact.

When available, the Contact form saves your name, email address, optional phone number, subject and message in private Cloud Firestore records for project-owner review. Submission references and technical retry/rate-limit records support duplicate prevention and abuse controls.

A saved form message is not an email delivery confirmation. Email info@piratechs.com with a reference to ask about access, correction or removal of a submission. Include only the information needed to explain your request.

When web billing and an offer are configured, payment details are entered on Stripe-hosted Checkout or billing-management pages. Tradexers stores private account-linked customer, subscription and session references, reviewed offers, purchase attempts, event receipts and limited billing status used to reconcile access. The application does not provide a card-entry form or store full card numbers and security codes in these records.

Billing requests send the current Firebase identity token to the configured billing endpoint. A trusted server verifies provider/account bindings and payment state before publishing limited subscription access to your private account. A return URL, saved draft or edited public price does not establish payment.

Native app purchases and billing changes are not enabled. Clearing account display fields or device records does not cancel a Stripe subscription; use the supported billing controls in Profile when available. Stripe processes its own payment information under its privacy notice and service terms.

Production web pages include Vercel Web Analytics to measure site visits. The app removes URL query strings and fragments from events before sending them; the page path remains part of measurement. This is separate from advertising and from any private traffic-report dashboard.

Hosting and service infrastructure process network requests and technical connection information needed to deliver pages, authenticate requests and operate the service. This page does not claim that all requests are anonymous, that all infrastructure logs are disabled or that no browser storage is used.

Available market and news services obtain public quotes, chart history and source material from providers such as Yahoo Finance, publisher feeds and supported YouTube or Reddit integrations. Feed availability and freshness vary. These sources do not receive your private workspace merely because you browse a public reading list.

Loading an externally hosted asset or following an external article, video or discussion can disclose ordinary connection information to that provider. External websites apply their own privacy and cookie practices. Read their notices before signing in, providing information or enabling their optional features.

Tradexers does not currently serve advertisements. Google ad requests, personalized advertising, Auto ads and native advertising SDKs are not enabled.

If Google advertising is introduced, Google and other disclosed advertising vendors may use cookies, web beacons, IP addresses or other identifiers, including information about visits to this and other sites, for ad delivery, measurement and personalization where permitted. Before introducing advertising, we will update this policy to identify the actual vendors, explain the available choices and obtain any required consent.

Google explains how it uses information from partner sites at https://policies.google.com/technologies/partner-sites. Its advertising-personalization controls are available at https://adssettings.google.com/. Using those external controls does not activate advertising on Tradexers.

If advertising is introduced, the site will explain its actual advertising technologies and provide applicable consent and withdrawal choices. Google's Ads Settings can also be used to control ad personalization in Google's services and participating partner sites.

Changing a Google advertising setting does not change your Tradexers sign-in, erase your private workspace or cancel a subscription. These optional external controls are provided for information while advertisements remain disabled here.

Use supported Profile, list, connection and read-history controls to manage the records those controls describe. They do not perform a full cloud-account deletion. Cloud account, contact, billing and operational records can remain after signing out or clearing device storage; this page does not promise a fixed automatic deletion schedule.

To ask about your information, request a correction or discuss deletion, email info@piratechs.com. We may need to confirm the relevant account or submission before acting. Provider-held data and any records needed for billing, security or applicable recordkeeping may require separate handling; a privacy request is not a brokerage order or a subscription-cancellation instruction.

We will update this policy when the application's information handling changes. The date above identifies this version. Introducing ads or another data use requires corresponding disclosure and any applicable choices; it is not authorized merely by this policy's description of a possible future feature.