Privacy Policy

Last updated: 2026-09-03.

1. Operator

This service is operated by Odyssea Research LLC, dba Predict Here, registered at 1309 Coffeen Ave, Ste 1200, Sheridan, WY, 82801, with primary jurisdiction in the United States of America.

2. What we collect

What we collect depends on how you use the site. This section is organized by product: Predict Here Institutional / Monitor (our current product, across its Explore, Institutional Evaluation, and Institutional tiers), legacy wallet services, and the Partner Sandbox.

How to read this policy. Each part below is labeled with the scope it covers, matching the scopes used in our Terms of Service. Current Institutional covers the public website and Predict Here Institutional / Monitor — organizations, member accounts, watchlists, alerts, and the institutional API — across all three access tiers (Explore, Institutional Evaluation, and Institutional). Legacy / Partner Addendum covers the legacy wallet service and the Partner Sandbox, including its previous order routing and historical integrations. Sections 3 through 8 apply to both scopes, and say which product each clause is about where they differ.

Site visitor (no account, not signed in). Across every part of the site, we collect very little:

• Standard request data every web server sees — IP address, user-agent, and country code (from our hosting provider's edge headers).
• Aggregate page views on approved public route names and fixed interaction categories via cookieless Vercel Analytics. The analytics filter removes query and fragment values, replaces dynamic public path values with generic route names, and drops private or unrecognized routes. Interaction events use an allowlisted vocabulary and do not include form content, email addresses, organization names, or free-text answers.
• If a page errors, an error report may be sent to our error-monitoring tool (Sentry). It never carries cookies, auth headers, wallet addresses, or amounts — those fields are stripped before the report leaves our server.

Predict Here Institutional / Predict Here Monitor (current product)

Scope: Current Institutional. Everything under this heading is about the institutional product — the access request, organizations, member accounts, watchlists, alerts, and the institutional API.

Institutional access request. If you submit the Request Institutional Access form, we store what you enter — first and last name, email address, organization, role, country, your primary workflow and any detail you add, delivery preference, a description of your current usage, and (optionally) your organization's size band — together with a hashed (not raw) version of your IP address, your browser's user-agent string, and your selected language. We use this to evaluate and follow up on your request, including the decision whether to admit your organization.

Institutional Evaluation request. If you instead choose "Request an Institutional Evaluation" within that same form, we additionally store your job title, your organization type, a description of the event universe you want covered, which source-data licenses you already hold, and any notes you add.

Partner inquiry. The Contact page's links open your own email client to send a message to partner@predicthere.com or support@predicthere.com. We receive whatever you choose to write in that email. The Request Institutional Access form above is a separate, server-side form that does store its submissions in our database, independent of any email.

Institutional org member (Monitor user). Once your organization is admitted (Institutional Evaluation or Institutional) or automatically provisioned (Explore) and you are authorized as a member, we collect:

• Your account and session identity — a verified email address and an email one-time-code sign-in, with an optional authenticator-app (TOTP) step for institutional accounts — together with your organization membership record and role. No wallet signature is used to sign in to Predict Here Institutional / Monitor.
• Your organization's profile (display name, legal name, jurisdiction) and the membership records (role) of the people your organization authorizes.
• Venue account references you or your organization connect — a public venue proxy-wallet address, or a label you assign to an uploaded-file source. We never ask for, and never store, a private key, seed phrase, password, or API credential for any connected account.
• Position and collateral data — either fetched from a connected venue's public read-only data endpoints, or from position files you upload directly (CSV/JSON: venue, market reference, outcome, quantity, cost basis, and collateral balance).
• The canonical events, watchlists, and alert rules you create or save, and the alerts that fire from them.
• Usage analytics — which parts of Monitor you use (events viewed, features used, and, if your organization has API access, API calls made) — used for product analytics, support, and to inform entitlement decisions.
• Entitlement records — which data sources and delivery modes (Workstation, API, historical export) your organization is authorized for, and an audit log of account connections, imports, reviews, and exports performed within your organization.
• If you create a Developer Sandbox or production API key, its metadata — a key prefix identifying it as sandbox or production, scopes, and creation/revocation/last-used timestamps. We never store the key itself; only a one-way hash of it, used solely to verify a presented key at request time.
• The risk analyses, liquidity/price-at-size figures, and any exported report Monitor computes from the data above.

This data is used only to operate Predict Here Institutional / Monitor for your organization, and is visible only to your organization's authorized members and to us. Request access, correction, or deletion of this data at support@predicthere.com — see also Section 7.

Legacy wallet services (existing users only)

Scope: Legacy / Partner Addendum. This applies only if you were a user of the closed legacy wallet product. It does not describe anything we collect from an institutional Monitor or API user.

Legacy wallet user. Predict Here previously operated a real-money wallet product on the Polygon network. It is closed to new users and no longer accepts new deposits. If you were an existing user of that product, we retain your wallet address and your order/transaction history so you can view your balance and withdraw any remaining funds at /legacy/connect and /legacy/wallet.

Historical & partner services — Partner Sandbox

Scope: Legacy / Partner Addendum. This applies only if you use the Partner Sandbox — Practice markets or a partner's embedded experience — or previously used the retired Sourced (Solana) lane. It does not describe anything we collect from an institutional Monitor or API user.

Practice user. Entering Practice markets in the Partner Sandbox creates an anonymous profile:

• A randomly generated account id and a synthetic placeholder address for that id — never a real email or a real wallet.
• Your practice-credit balance and trading activity inside Practice markets.
• If you arrived via a partner's branded preview link, we record which partner link you came through (used once, for partner-attribution counting, then discarded — see Cookies below).

Wallet user — Sourced markets (Solana), Partner Sandbox. Sourced markets, inside Practice, offered Solana-settled markets that tracked prices from a third-party venue (Polymarket; the Kalshi adapter was built, not enabled, with no live calls). That lane has been retired and is no longer available. Where it was used we collected, and still hold:

• Your public wallet address, linked to your profile when you sign a Sign-In-With-Solana message.
• Order records — market, side, amounts, transaction signatures, and order status.
• USDC balance reads at your address.
• The country code derived from our host's edge headers, used for eligibility.

Unlike the play-credit Practice markets described above, orders in that lane were real, non-custodial on-chain transactions — you signed and submitted them yourself; Predict Here never held your funds. The Solana blockchain is public — transactions signed from your wallet remain visible to anyone, independent of Predict Here.

Partner-integration end user. If you use a prediction-market experience embedded by one of our business partners, that partner creates an account for you in our system using an identifier and display name they provide — we do not collect your name, email, or other identity information directly, and your partner is your point of contact for that data. We process your credit balance, orders, and transaction ledger on your partner's behalf to operate that experience.

We do not collect: government ID, selfie, social-security number, password, or any identity document, for any of the above. We do not perform identity verification.

3. How we use it

Scope: both. Each purpose below names the product it belongs to where they differ.

To operate the site and its products; to evaluate and admit institutional organizations, authorize their members, and enforce their entitlements; to compute and display Monitor's analytics for your organization; to have relayed Partner Sandbox orders to our order-routing provider and the source venues, before that lane was permanently retired; to display your positions; to enforce geographic eligibility; to count how many sign-ups a given partner link drove; to detect and fix errors; and to send opt-in result notifications if you asked for them.

4. Sharing

We use six subprocessors. They are not all involved in every product, so they are listed in two groups below, each labeled with the product it serves. None of the six is removed or added by this grouping.

Subprocessors — institutional platform

Scope: Current Institutional. These four serve the public website and Predict Here Institutional / Monitor, and apply to you whichever part of the site you use.

With our infrastructure providers: Vercel (hosting, edge network, and Vercel Analytics), Sentry (error monitoring — scrubbed of cookies, auth headers, and wallet/amount fields before ingest), Supabase (database), and Resend (delivering account email — the sign-in verification code every time you authenticate, and, separately, opt-in product notifications if you provided an address for them).

Subprocessors — legacy wallet & Partner Sandbox products

Scope: Legacy / Partner Addendum. The two providers below are involved only where you used the legacy wallet product or the Partner Sandbox — not in Predict Here Institutional / Monitor.

Order details from the Partner Sandbox went to our order-routing provider and, through it, the source venue, as needed to execute the trades you signed, before that lane was permanently retired. Our RPC providers see the wallet addresses we query on your behalf for the legacy wallet product, and saw the addresses queried for the Partner Sandbox's Sourced markets before that lane was permanently retired.

Other sharing

Institutional org data (watchlists, alerts, venue connections, analyses) is visible only to your organization's authorized members and to us — never to another organization. With law enforcement under valid request. We do not sell your data, and we run no advertising trackers.

5. Cookies

Scope: both. The first three cookies apply site-wide. The rest belong to Predict Here Monitor, the Partner Sandbox, the legacy wallet product, or the retired creator/streamer product, and each entry says which.

Every cookie below is functional — none are advertising or tracking-network cookies.

• ph_session — your signed-in session (httpOnly, 7 days).
• ph-locale — your chosen language (EN/ES), 1 year.
• ph-theme — your chosen light/dark theme, 1 year.
• ph_demo_theme — your light/dark theme choice, site-wide (path=/), 1 year.
• ph_demo_brand — the cosmetic "preview your brand" skin (display name / accent color / credits label) for a branded partner preview, scoped to /demo, 30 days. Carries no auth weight.
• ph_demo_attribution_signed — set for one visit when you arrive via a partner's branded link; records which link, is read exactly once when your profile is created, then cleared. Site-wide, httpOnly, expires after 7 days if unused.
• ph_campaign_signed — set only if you arrive via a specific marketing link; records which link drove your visit for our own counting, read once at sign-up, then no longer used. httpOnly, expires after 30 days if unused. Its practical use today is limited: it counts new-account sign-ups for the legacy wallet product, which is closed to new users (Section 2).
• ph_creator_ref_signed — a retired referral-attribution cookie from the creator/streamer product, which has been removed from the site. It is historical: nothing on the site issues one and nothing reads one. Every way to newly obtain it was already gone (the marketing-site link that set it and the API route that minted it are both retired), and the sign-in path that used to read it no longer does. A copy set before that retirement, if still present in an existing user's browser, is ignored, expires within 30 days of when it was set, and is not renewed. httpOnly.
• ph_embed_ancestors — set only when a partner embed handshake runs, scoped to /demo, httpOnly. Holds the signed list of partner origins allowed to frame an embedded market.
• ph-intel-selected-org — remembers which organization you last selected in Predict Here Monitor, so it can offer the same one on your next visit. httpOnly, 30 days. It is a display preference, not an authorization: which organizations you can select from is still checked on every request.
• ph_last_wallet — a sign-in convenience for the legacy wallet product: pre-fills your most recently used wallet address so you do not have to reconnect it manually. Not httpOnly (readable from client JS by design), 1 year. It carries no session data and confers no authorization — wallet addresses are already public on-chain.

6. Retention

Scope: both. Each sentence names the record type and the product it belongs to.

Order and transaction records are retained for operational, audit, and legal purposes. Practice profiles and activity are retained for product analytics and may be pruned or reset without notice (Terms §4). Notification email is retained until you ask us to delete it — request deletion at support@predicthere.com. On-chain data is permanent by nature and cannot be deleted by us.

Institutional data. Two categories are purged automatically on a daily job: raw quote ticks after 90 days, and order-book snapshots after 30 days. Both are market data, not customer data.

Your organization’s own records — the org and its membership, watchlists, alert rules, API keys, uploaded positions and collateral, risk runs, evaluation records and access requests — have no automatic expiry today. We keep them for as long as the organization exists, and we delete them on request: write to support@predicthere.com and we will remove the organization’s records within 30 days, other than anything we are required to keep for legal or accounting reasons and the append-only security log described on our Trust page, which cannot be edited or deleted by design.

Deleted records can persist in encrypted database backups for up to approximately eight days, after which the backup containing them is rotated out. We do not selectively edit backups.

We do not yet offer a contractual retention schedule or a self-serve deletion control; both are tracked as open work on our Trust page rather than described here as if they existed.

Partner-integration end-user data follows the retained partner product’s own terms and is deleted on the partner’s instruction.

7. Your rights

Scope: both. These rights cover the data we hold under either scope; the same contact address serves both.

Access, correction, or deletion of the data we hold (notification email, practice profile, wallet-linked records, institutional org data) — contact support@predicthere.com. We can delete the data we hold, but we cannot alter or erase records on a public blockchain.

8. Contact

Scope: both. One address for every product.

Privacy questions: support@predicthere.com.