Privacy Policy
Version 2026-07-27.1 · Effective 2026-07-27
About this Policy
This Privacy Policy explains what information Foreseez processes when you use the Service. It reflects the current Public V1 architecture (version 2026-07-27.1). It is not a compliance certification and does not promise automated deletion workflows, fixed retention schedules, or rights portals that are not yet built.
Account and profile information
When you create an account, authentication providers store credentials and account identifiers needed to sign you in. Your Foreseez profile may include a username, display name, optional avatar URL, optional bio, and account-type metadata. Profile fields intended for public display can be visible to other users and visitors according to product rules. Authentication email addresses are handled by the identity provider and are not exposed as a public profile field.
Authentication
Foreseez uses Supabase Auth for sign-in sessions. Available sign-in methods may include email/password and Google Sign-In. The login and signup interface shows which methods are currently enabled for the deployment you are using. When you use Google Sign-In, Google account identifiers and authentication information are processed through Google and Supabase. Session state is maintained with essential cookies required to keep you signed in and to protect authenticated routes.
Calls, Cred activity, and Receipts
When you make a Call, the Service stores the Prediction, chosen Outcome, Cred commitment, optional Confidence, and related Receipt data needed to operate settlement and your Record. Public Receipt and Record surfaces may show Cred amounts, Confidence, Outcomes, and results that the product intentionally makes world-readable. Internal settlement quantities that the product treats as non-public are not exposed on public Receipt views.
Social graph and community features
If you use social features, the Service may process follows, comments, reactions, blocks, and reports. Follow relationships are used to personalize discovery and to show follow counts where the product exposes them. Comments and reactions you create can be visible to others on the relevant Prediction or Receipt surfaces. Blocks are used to limit interactions and are not presented as a public social list. Reports are intake records for operator review and are not published as a public feed.
Operational logs, cookies, and analytics
The Service and its hosting providers process operational logs needed to run, secure, and debug the application (for example request and error telemetry available to operators through the hosting platform). Essential cookies support authentication and basic application function. The production web app may also load Vercel Analytics, which can collect aggregated usage metrics for the hosted site. Foreseez does not add separate advertising trackers in this Public V1 surface.
Infrastructure processors
Foreseez is hosted on Vercel and uses Supabase for authentication and application data. Those providers process data as needed to deliver the Service under their own terms and infrastructure controls. We do not sell personal data. We do not operate a separate advertising data marketplace.
Retention, correction, and deletion
Data needed for account operation, Receipts, settlement integrity, and auditability may be retained while the Service operates and as needed to preserve ledger and Record integrity. This Policy does not claim a specific automated retention countdown, self-serve deletion portal, or guaranteed deletion SLA. If you need a correction or deletion request evaluated, contact us through the Contact page. We will handle requests manually where feasible and where doing so does not break append-only financial or audit records the product must preserve.
Privacy contact
For privacy questions, use the channels listed on /contact. If a public support email is configured for your deployment, it will appear there. No separate privacy officer mailbox is published in this version.
Changes to this Policy
We may update this Policy by publishing a new version at /privacy with an updated version identifier. Material product changes that affect data practices should be reflected in a later version of this Policy.