ARYAMERX / PRIVACY & CHOICES

Privacy policy

AryaMerX FX Watch

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.

Products coveredAryaMerX FX Watch v2.2.1
01 / At a glance

At a glance

Products covered
Extension / covered versionData handledStorage & syncExternal connectionsYour controls
AryaMerX FX Watchv2.2.1API keys, watchlist, notes, saved news, questions and preferenceslocalStorage and chrome.storage.localAlpha Vantage and optional PerplexityEdit saved items; Clear Data has local-storage limits

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.2.1

AryaMerX FX Watch

Chrome Web Store item: ocopaheneglknhaohfcdgkfocmpcamgj

Saved information and automatic requests

FX Watch stores API keys, theme, selected market/instruments/timeframe, news source and AI model preferences, a watchlist with notes, saved news with notes and timestamps, and recent AI questions and answers in localStorage. AI question history is limited to the latest 25 saved entries. The Alpha Vantage key is also saved in chrome.storage.local; the worker saves installation status/time, and the popup can read an existing active-market preference there. Market data and charts are also cached in memory during a session.

With configured keys, opening the popup, loading a market view, changing filters or instruments, refreshing or searching can make market/news requests automatically. These are not all restricted to pressing an AI chat Send button. The selected news source and available keys can cause fallback between providers. This version does not upload a complete local watchlist database or local notes to AryamerX; selected symbols and the context described below are sent to the connected providers.

What goes to Alpha Vantage and Perplexity

Alpha Vantage receives HTTPS requests to www.alphavantage.co/query containing your Alpha Vantage key as an API query parameter, the requested data function, currency/stock/crypto symbols, interval or time range, and news topics or search text as applicable. Saving or validating a key can also send a test request. The purpose is key validation, quotes, chart data, market snapshots and news retrieval.

If you configure Perplexity, HTTPS requests to api.perplexity.ai/chat/completions send your Perplexity key in the authorization header, the selected model and feature prompt. News requests include category, time filter or search query; market insights include an instrument and analysis instructions; AI questions include your question, selected symbol/market/timeframe and generated context from displayed market data, indicators or news as relevant. The question path sends that context and question, not the entire saved question history or all personal notes. Key/model validation can also send a short test prompt.

Both providers receive ordinary connection metadata and handle the submitted information under their own applicable policies and API terms. Perplexity features are optional, but enabled news/analysis views can generate AI requests without a new typed question. Leave the Perplexity key unset or remove it to avoid those AI calls. Opening source/news links visits their websites under their policies. Provider data is not removed by the extension’s local delete controls.

Permissions, retention and incomplete Clear Data

The manifest requires storage and unlimitedStorage for local records, alarms for scheduled reminder events, notifications for desktop notices, and host access to Alpha Vantage and Perplexity for the above requests. Notification delivery is controlled by your reminder choice, Chrome and the operating system. Turn off the notification toggle to clear the scheduled reminder; notices can be visible on screen. The worker’s hourly reminder is a generic market-update notice, not a background upload of your notes.

Edit/remove watchlist entries and notes, remove saved news, change preferences or remove the Perplexity key in the interface. Saved records otherwise remain until removed. Settings → Clear Data calls localStorage.clear and reloads, but does not clear chrome.storage.local or existing alarms. In particular, the saved Alpha Vantage key can be restored from chrome.storage.local on reopening. Turn off reminders and remove the extension or clear all its extension storage for full local removal; revoke keys at their providers if needed. No dedicated extension-level key encryption is provided.

The active version does not provide a general file-export/import feature for all records. Manually copied answers, screenshots, saved pages and content shared with another service are separate copies. Clearing the extension cannot delete them or the providers’ request records.

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