SharpSignal Privacy Notice (AI + Automation)

Last updated: October 15, 2026

Optional website analytics

With your permission, we use Google Analytics and our own event storage to understand visits, referral sources, article reading, clicks, scroll depth, signup steps and checkout interest. Random browser and session identifiers connect these steps. They do not tell us who an anonymous reader is. With analytics allowed, we also associate acquisition campaign labels and released-record viewing events with your account to measure activation and return visits. Account creation and email confirmation are checked against our authentication provider. We do not use fingerprinting.

Heatmaps combine coarse click positions and scroll milestones. We do not record screens, keystrokes, form values, passwords, authentication links or private dashboard content. For consented record-view measurement, we store a non-readable record fingerprint, account identifier and viewing time; not the selection or research content. URLs are stripped of query strings and fragments before analytics collection. Campaign labels are retained separately. Auth and administrator pages are excluded from optional page tracking.

Choose “No thanks” to decline optional analytics, or reopen “Analytics choices” in the footer to change your choice. We also honor Global Privacy Control and Do Not Track. Account, payment and security records needed to provide the service remain separate. Stripe records may include an anonymous visitor ID and campaign labels when analytics is allowed, so we can measure paid conversion.

Optional event data is stored with our hosting/database providers; Google receives the consented Google Analytics events. The private reporting page shows up to 90 days. That reporting window is not an automatic deletion guarantee. Contact us to request deletion; clearing browser storage alone does not remove past server records.

What we collect

• Account information (email, authentication identifiers)
• Subscription/payment metadata (via Stripe; we do not store full card details)
• Usage/event metadata (page views, basic product analytics if enabled)
• Operational logs required to run the service (timestamps, status, error codes)

What we do NOT collect (by default)

• We do not intentionally collect sensitive personal data (e.g., SSNs, health data).
• We do not request device-level permissions beyond what the web app requires.

AI / model inputs

If SharpSignal includes AI-powered features (e.g., chat, summaries, assistants):

• We minimize the data included in model requests.
• We avoid sending personally identifying information (PII) unless required for the feature.
• We do not use user-provided AI inputs to train models unless explicitly disclosed and opt-in.

Data sharing & third-party processors

SharpSignal uses third-party services strictly to operate the product. Examples may include:

• Stripe (payments/subscriptions)
• Telegram (notifications/alerts, if user opts in)
• The Odds API / data providers (sports data feeds)
• Google APIs (Sheets access for internal logging, if enabled)
• Cloud infrastructure providers (hosting, storage, logging)

We only share the minimum necessary data to provide the service.

Data security

• Least-privilege access for tokens/credentials
• Secrets stored in environment variables / managed secrets (not in source code)
• TLS/HTTPS for data in transit where applicable

User choices & deletion requests

You may request deletion of your account data by contacting support. We will delete or anonymize data where feasible, subject to legal/operational requirements.

Contact

Support / privacy requests: SharpsSignal@gmail.com