Skip to main content
Pharos
PHAROSlive stablecoin signals

Privacy Policy

Last updated: March 2026

Policy Summary

Pharos does not ask for accounts or wallet connections. Portfolio data is stored locally by default, share links encode holdings in the URL, analytics are anonymized when enabled, and support requests route through the feedback/contact channels listed below.

What We Collect

When a Google Analytics 4 (GA4) measurement ID is configured for the current deployment, Pharos collects anonymized usage analytics such as page views, session duration, approximate geographic region, device or browser type, and a small set of product-interaction events. If you choose to share a Telegram or X handle in the feedback form, that handle is included in the GitHub issue created for the submission. Telegram alert subscriptions store chat ID, optional username, followed coins, alert settings, quiet hours, snooze state, and short-lived pending-command or pending-alert metadata.

No Accounts or Wallet Connections

Pharos does not require user accounts, logins, or wallet connections. There is no sign-up process, no email collection, and no authentication of any kind. Optional feedback contact details are self-declared and are not used as site accounts or persistent user identities.

Cookies

When analytics is enabled, the only cookies set by Pharos are those required by Google Analytics 4 (e.g., _ga, _ga_*) for distinguishing unique visitors. No advertising or tracking cookies are used.

Data Retention

When GA4 is enabled, analytics data is retained for 14 months per Google's default settings. We do not maintain user-account databases. Feedback submissions are sent to GitHub Issues for product support and issue tracking; optional follow-up contact details are included there when you provide them. The worker stores rate-limit metadata for feedback abuse prevention. A legacy `feedback_submissions` table exists in the D1 schema, but the current submission path does not write to it.

Third-Party Services

Pharos is hosted on Cloudflare Pages with API endpoints served by Cloudflare Workers. Analytics data is processed by Google (GA4) only when analytics is enabled for the current deployment. Feedback submissions are also forwarded to GitHub Issues for product triage; optional Telegram/X handles are echoed publicly in those GitHub issues.

Contact

Questions about this policy? Reach out on @PharosWatch or via the About page.