ARYAMERX / PRIVACY & CHOICES

Privacy policy

TJA – Trading Journal Aryamerx

A clear view of what your extension handles, where it stays, and what you control.

Effective & updated Policy version 1.0

The full policy below includes this product’s data practices and the common privacy terms. No account is needed to read it.

01 / At a glance

At a glance

Products covered
Extension / covered versionData handledStorage & syncExternal connectionsYour controls
TJA – Trading Journal Aryamerxv2.0.0Local profile, trades, notes, AI conversations and API keychrome.storage.local; no Chrome SyncOptional Perplexity coachingTrade editing, CSV/JSON/PDF; partial clear

About this policy

AryamerX is the publisher of the browser extensions identified on this page. This policy explains the data handled by the listed versions and their user controls. Check your installed version in Chrome’s extension details. Earlier releases can have different storage and permissions; in particular, Financial Clock’s local-only writing behavior described here applies to version 3.0.0.

This is the browser extensions policy. The website and platform privacy policy covers the separate website, app and platform services, including MentalCoach. Opening a link to those services does not automatically transfer your extension journal or settings to them. This document’s extension-specific explanations govern the extension behavior described here.

Local storage, Chrome Sync and external services

Local storage means data is saved in the extension’s browser profile using chrome.storage.local or localStorage. Saving, reading and calculating with it is still data processing. AryamerX does not operate an extension-data backend for these versions and does not automatically receive a copy of their local records.

Chrome Sync is different: when enabled in Chrome, synchronized extension preferences may be transferred through Google and appear on other signed-in browsers. You control Sync in Chrome and your Google account. Local deletion and uninstalling should not be relied on to erase every synchronized or backed-up copy; use Chrome’s Sync controls too.

An external API request transfers the specified request data to its provider, even when it goes directly from your browser without an AryamerX server. The provider also receives normal connection information such as IP address, request time and HTTP/client metadata. Provider retention, security, account controls and any processing by its service providers follow its own applicable terms and privacy policy. We cannot delete a provider’s records by clearing extension storage. Review the provider links below before using connected features.

Covered extension version 2.0.0

TJA – Trading Journal Aryamerx

Chrome Web Store item: eeahnbjhbngiidoghdfdfhfochodmill

Local profile and journal data

Local registration stores a username, email, local password, creation time and profile preferences in chrome.storage.local, together with the current signed-in profile. This sign-in organizes records within this browser; it is not registration with an AryamerX server or the separate MentalCoach website.

The journal saves trade symbols, entry/exit times and prices, position size, direction, strategy, notes, tags and record timestamps, grouped by local user. It calculates statistics from those records. Language, display preferences, optional Perplexity API key and coaching conversation history are also saved locally. Required storage and unlimitedStorage permissions support the journal and its growing local records; they do not grant access to unrelated website content. No Chrome Sync, browsing-history collection or journal upload to AryamerX is implemented in this version.

Optional AI coaching and its recipient

You can use journaling, statistics and focus tools without an API key or AI coaching. If you save your own Perplexity key and send a coach message or choose a quick prompt, the extension sends a direct HTTPS request to api.perplexity.ai/chat/completions. Perplexity receives the key in the authorization header, the coaching system instructions and recent conversation content: up to six recent alternating user/assistant messages, with a leading assistant message removed, including the current message. It does not automatically attach the whole trade database or local account credentials. Anything you include in the conversation is sent as message content.

The response is displayed and saved in local coaching history. Perplexity receives normal connection metadata and processes API content under its applicable API terms, data processing terms and account configuration; its consumer privacy notice does not govern API content processed on behalf of API customers. Its API privacy documentation is linked below. Do not assume zero retention at the provider. Clearing local conversation history does not withdraw requests already sent or erase provider records. Remove the saved key to stop using it and revoke it at Perplexity when necessary. The key is stored locally without dedicated extension encryption; do not treat local sign-in as encrypted key storage.

Exports, retention and deletion limits

Records persist until edited, deleted or removed from browser storage. Delete individual trades in the journal. Settings → Clear All Data removes the current local user’s trades and coaching sessions; it does not remove the local user registry, current profile, saved API key or all preferences. Signing out removes the current sign-in state, not the saved user registry. For complete local removal, remove the extension through Chrome or clear all of its extension storage. Do not rely on the partial clear button as an account/key deletion tool.

CSV exports contain trade data. JSON exports include the current user’s username, email, creation date and settings, trades and coaching sessions, but not the local password or saved API key. The PDF action produces a printable trade report in a new window. These are user-directed local exports; files, printouts and any copies you share need separate deletion. Links to MentalCoach are separate website visits, not automatic journal synchronization.

Purpose and limited use of extension data

AryamerX uses extension data to provide the functions described for each product: time planning, journaling and optional coaching, calculations, or market tracking and requested analysis. These versions do not collect browsing history, cookies or the contents of unrelated websites, and do not include advertising or analytics SDKs that upload your extension records.

AryamerX does not sell extension user data, transfer it to data brokers, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility. Transfers are limited to the disclosed services necessary for the selected feature, user-directed exports and links, or where necessary to meet legal obligations or protect against security threats and abuse. A transfer in a business acquisition would require explicit prior user consent.

AryamerX personnel do not have automatic access to your local extension records. Human access to data you share with us is limited to your explicit permission for a specific support purpose, security needs or legal obligations. These restrictions apply to raw and derived data. Chrome Sync is a browser service; these extensions do not request Google account OAuth access or receive Gmail, Drive or other Google account content through Google APIs.

Security, retention and your choices

Browser-profile storage is not a private encrypted vault. These versions do not add dedicated encryption to saved extension data or API keys; a local sign-in screen is not the security boundary of a remote account. Protect your device and browser profile, use a unique local password, avoid entering broker credentials or other secrets in notes or AI messages, and revoke a service API key at its provider if needed. External APIs described here use HTTPS, but no storage or transmission method guarantees complete security.

Saved records generally remain until you edit or delete them, reset the relevant storage or remove the extension. Product-specific limits and incomplete reset controls are explained in the product sections. Transient in-memory data lasts for the current extension session unless cached or saved as described. These local records have no automatic expiry, and we cannot recover records that were never sent to us.

You can decline optional AI features, change stored entries, use the available exports, turn off reminders and revoke permissions in Chrome, or uninstall. Delete exported files, backups and pasted text separately in their destinations. Calendar imports and operating-system notification history are separate copies; notifications may be visible to others looking at your screen. Clipboard/export processing occurs only for products and actions that offer it.

Continuing to use an extension is not a substitute for any explicit consent needed for optional transfers. Review the disclosed destination before enabling a connected feature. You can ask us about access, correction, deletion or other applicable privacy rights through the contact below; we can act on records we actually hold, and explain when a local or third-party control is required.

This website and voluntary support messages

Reading this policy does not give the website access to your extension storage. These static policy pages add no analytics SDK, advertising tag or nonessential cookie, and do not require sign-in or a consent banner to read the text. They load their styling, fonts and logo from AryamerX. The web server and Cloudflare delivery/security layer process ordinary request information, such as IP address, URL, time and browser metadata; security services may set operational cookies. This website traffic is separate from the extension’s local records and follows the website policy and Cloudflare policy.

If you email us or use the contact form, you voluntarily provide your contact details, message and any attachments or diagnostic information you choose to include. Form delivery uses AgentMail and our email provider. We use that information to answer your request, resolve support issues and meet necessary security or legal obligations, retaining it as needed for those purposes. Do not send passwords or API keys. Local deletion in an extension does not delete a support conversation; contact us separately about support records.

Changes and privacy contact

We publish changes at these stable policy URLs with an updated date and policy version. If a future release changes data handling, the policy, Chrome Web Store disclosures and relevant in-product explanations must reflect that change. Material new optional processing should be explained before it starts, with consent where required.

Publisher: AryamerX. For privacy questions or requests, email [email protected] or use aryamerx.com/contact. Include the extension name and version, and describe your request without disclosing credentials. This contact does not require a paid account.

Provider privacy policies