Privacy Policy

Privacy Policy

This policy explains how SignalReview handles account, seven-day pilot, retained research, product telemetry, and payment-related information. Effective August 6, 2026.

1. Information We Process

Depending on the feature used, SignalReview may process account identifiers such as an email address and authentication user ID; pilot entitlement, expiry, and usage allowance; selected fixture identifiers; War Room run identifiers; retained Saved Reviews; bounded launch-intent choices; technical request and reliability metadata; and support messages you deliberately submit.

During the seven-day pilot, SignalReview does not ask for card details and does not create a payment order.

2. Pilot Product Telemetry

SignalReview records a small bounded set of authenticated pilot events needed to evaluate product activation and retention: pilot account viewed, fresh fixture selected, Saved Review reopened, and price-intent prompt presented.

Event records use a server-derived HMAC pseudonymous subject rather than the user's email address. Pseudonymous data can still be personal data, so SignalReview treats these records as protected user data.

Event payloads do not contain email addresses, free-text feedback, card data, prompts, authentication tokens, raw provider payloads, or model secrets.

3. Saved Reviews

When an authenticated pilot retains a completed War Room review, SignalReview stores the associated fixture, prediction, Quant Passport context, agent messages, and bounded verdict so the same pre-match state can be restored later.

Saved Reviews are associated with the authenticated account and are not public by default. Controlled demo routes do not write Saved Reviews or Watchlist data, and persistence failures remain visible.

4. Payment Information

Payment collection is disabled during SR-BETA-FAST. No checkout order or hosted payment form should be created while the paid-launch flag remains off.

After a separately approved paid launch, payment information may be processed by a third-party payment provider under its own privacy terms. SignalReview does not intend to store full card numbers on its servers, but may retain billing status, provider identifiers, renewal timestamps, and transaction references required to manage paid access.

5. How We Use Information

We use information to authenticate users, enforce account ownership and bounded access, provide fresh-fixture selection and War Room analysis, retain Saved Reviews, measure activation and cross-day retention, record non-binding launch intent, maintain security, investigate failures, respond to support requests, and comply with applicable law.

6. Legal Bases

Depending on location and processing activity, the legal basis may include performance of a requested service, legitimate interests in operating and improving a secure product, consent where required, and compliance with legal obligations. Rights and objections remain subject to applicable law.

7. Third-Party Services

SignalReview may use hosting, database, authentication, model, sports-data, observability, email, and later payment service providers. They process information for the relevant service purpose under their applicable terms and safeguards.

Provider, model, database, payment, and internal credentials remain server-side and are not intentionally exposed to the browser.

8. Cookies and Local Storage

We may use cookies, local storage, and similar technologies for authentication, session management, preference storage, security, and product functionality. Pilot telemetry is retained server-side after authenticated bounded events.

9. Data Retention

Information is retained only as long as reasonably required to provide the service, complete the pilot experiment, maintain security and audit evidence, resolve disputes, meet legal obligations, and evaluate aggregated product outcomes.

Pilot events are deterministically deduplicated to avoid unnecessary repeated records.

10. Security

SignalReview uses server-side session verification, ownership checks, environment isolation, restricted secrets, bounded event schemas, pseudonymous telemetry subjects, and operational logging designed to exclude tokens, email addresses, and raw provider payloads. No system can guarantee absolute security.

11. Your Choices

Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent. You may also stop participating in the pilot and request removal from the pilot allowlist, subject to legal and security retention requirements.

12. Contact

Privacy questions and requests can be sent to support@signalreview.co.