Scope of this draft
This page describes the public Practice preview of Prediction Protector. It does not describe Kalshi’s systems, browser vendors, payment providers, or a future real-money service.
The public preview is limited to account creation and a Practice workspace. It does not accept market-account credentials, payment information, or trading instructions.
Information the preview handles
- Account details
- Name, email address, authentication information managed by the account provider, and records that a member accepted the preview documents.
- Workspace data
- Practice-mode settings and illustrative activity needed to show the user the workspace.
- Technical data
- Session identifiers and operational information needed to keep a signed-in workspace functioning.
- Not collected in this preview
- Kalshi API credentials, market-account positions, orders, payment-card information, or instructions to trade.
How the public preview handles it
Account authentication is handled by the account service. Prediction Protector does not store an ordinary readable copy of a member’s password in its application records.
The public preview does not provide a field for Kalshi API credentials and does not retain market credentials, market positions, or order data. These statements describe the current preview scope, not a guarantee against every technical or security risk.
Why the preview uses information
- To create and maintain a separate account and session for each member.
- To show the Practice workspace and the user’s account status.
- To record acceptance of the preview documents.
- To diagnose operation of the preview and protect it from misuse.
This draft does not authorize unrelated marketing, sale of personal information, payment processing, or real-money market activity. Any future practices would need to be described clearly before they are introduced.
Your choices and control
- Do not submit sensitive market credentials to this public preview; it does not require them.
- Sign out when you are finished using a shared device.
- Use a unique password and keep it private.
- Review the final privacy notice, contact method, retention details, and account-deletion process before relying on any future production service.
What must be completed before a broader release
A production privacy notice should identify the responsible operator and contact channel, explain actual storage and retention, cover hosting, analytics, and payment vendors, describe applicable user rights and complaint routes, and be reviewed for each jurisdiction where the service is offered.
Last updated: public practice-preview draft, October 2026.