At a glance
| Extension / covered version | Data handled | Storage & sync | External connections | Your controls |
|---|---|---|---|---|
| AryamerX Financial Clock — Session Plannerv3.0.0 | Settings, schedules, checklists and notes | Local; one-time legacy Sync read | No automatic external requests | Edit, erase local data, calendar and clipboard |
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.
AryamerX Financial Clock — Session Planner
Chrome Web Store item: kfckocecbefclalkmjdkkpaoehicbede
Information and purpose
The clock calculates reference market sessions and time-zone conversions inside your browser. It detects the browser time zone and uses the device clock. It saves language, theme, time format, time zone, selected sessions and currency pairs, personal availability and plans, checklists and preparation notes, custom clocks, broker/session schedules, quiet hours and reminder rules in chrome.storage.local. Operational records include migration status, reset generation and handled reminders to avoid duplicate notifications.
No account, name, email, payment details, broker login or live trading connection is required. Version 3.0.0 does not read browsing history, cookies or website content, execute trades, request market feeds or send your settings and notes to AryamerX, analytics, advertising or AI services. Runtime code, reference sessions and interface assets are bundled with the extension.
Permissions and migration
Required storage saves the above records; alarms schedules local reminders and toolbar updates; sidePanel displays the clock beside a website without reading that site. The notifications permission is optional and requested when you enable desktop reminders. Disable reminders or revoke that permission in Chrome at any time. Browser closure, device sleep and operating-system settings can delay delivery.
Version 3.0.0 can read supported older preferences from chrome.storage.sync once during migration, then writes new settings and content only to local storage. It does not write new version 3 data to Sync. An older synchronized copy can remain in Chrome/Google storage. Manage that copy separately through Chrome Sync settings.
Retention, deletion and exports
Edit or remove plans, notes, schedules and reminders in the interface. Settings → Erase local data resets personal planning data, preferences and reminder state. Minimal migration-complete and reset-generation markers remain to stop old Sync preferences or pending reminder work from restoring erased data. Local records otherwise remain until changed, reset or removed with the extension.
Calendar files and copied time summaries are generated locally only when requested. Delete exported files, calendar imports, copied text, operating-system notification history and legacy Sync copies separately. Opening reference or AryamerX links is user-initiated and does not attach your saved notes or preferences. The destination website receives an ordinary visit under its own policy.
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.