Account name, username, email, hashed password, session/device information, planning preferences, and the research or financial records you choose to save are stored for your account. Private records can include bets, cash and bonus ledger entries, fees, cashouts, offers, imported provider ticket details, model definitions, historical datasets, backtests, alerts, and saved evidence. Import originals, editable reviews, and approved financial records are stored separately.
Do not upload documents you are not entitled to process. Avoid unnecessary personal information, account credentials, payment-card data, and third-party confidential material. Downloaded backups and archives may contain sensitive financial information; protect them as private files.
Your imports, financial records, account email, and private research are not a public feed. Profile visibility, settled-record sharing, community publication, and model discovery require explicit opt-in. Review what becomes visible before enabling them. Settled-record sharing exposes recent closed financial rows with event, selection, odds, stake, payout, fees, currency, timing, and source provenance, alongside per-currency summaries. Open bets and exposure stay private. Published profile details, picks, model definitions, selected model summary metrics, and comments can also be visible to others; copied models and external copies cannot be recalled by changing your visibility.
Sharing is not proof of a real wager or independently verified performance. Sandbox provider records and synthetic datasets are examples, not live results; sandbox records are excluded from shared performance totals. Public wallet watching reads public Polymarket positions using the address you supply; it does not verify wallet ownership or authorize private account access.
Cloudflare provides Worker hosting, D1 records, private R2 files, and disposable KV caching. Public market/order-book/wallet research contacts supported Polymarket and Kalshi APIs; configured licensed odds reads may contact The Odds API or OpticOdds. Those sources do not authorize private account access. Optional SharpSports linking opens the vendor’s hosted consent/login interface, not a Stakesift sportsbook form and not OAuth. Sportsbook passwords and authentication challenges are entered only with the vendor; Stakesift does not collect them. With explicit consent, Stakesift stores a private owner binding and limited account/ticket data. Sandbox data is synthetic; live access requires separate keys, rights, and supported book coverage.
Disconnecting stops local access and requests vendor revocation. Partial/failed revoke remains visible for retry; records already imported into Stakesift are not deleted by disconnecting. Revocation does not erase the sportsbook or vendor’s independent records. Never submit sportsbook passwords, private keys, or API secrets in an import.
Web screenshot OCR runs in your browser using Tesseract.js; engine and English language assets may download from their asset hosts. The screenshot is not sent to a public image model by OCR. Server CSV extraction reads your private original into editable drafts. Optional explanations require configured availability and consent for the selected evidence on each request; deterministic calculations and factor backtests do not require that transmission.
Web sessions use cookies; native uses Better Auth’s Expo transport and protected device storage. Providers may receive normal network information needed to serve requests. Request budgets may retain short-lived hashed identifiers to limit abuse. Alerts/source checks run on request, not an advertised background push service. Local drafts, downloads, and copies remain under your device’s control.
Saved records and originals remain until you remove them or delete the account; no automatic retention deadline is promised. Version 3 private JSON includes supported financial/research records, full backtest datasets/results, alerts/history, and profile/model-share snapshots. It excludes passwords, sessions, sportsbook bindings, provider snapshots, original bytes/extracted text, and public picks/comments/follows. A separate original-file archive may contain private source files. Restore does not renew consent, republish profiles/models, reconnect accounts, or make historical observations fresh.
Removing an import deletes its original/review, not approved bets or offers. Minimal source/row identities prevent duplicate financial records after re-import. Current-password-confirmed whole-account deletion removes owned records/contributions and requires linked-provider revoke and private-file cleanup. Pending/failed erasure blocks private writes and is incomplete while required cleanup remains unresolved; interrupted provider/file operations may require maintenance and retry.
We cannot delete downloaded copies, recall material shared elsewhere, or promise deletion from vendors’ independent systems. Logs, caches, and provider recovery copies may have separate retention; immediate removal from every such system is not promised.
Use the account export and deletion controls for supported self-service requests. If you have an existing private communication channel with the service operator, use it for questions or stuck erasure requests without sending your password. No unverified contact address or staffed support response time is promised here.