Privacy policy

This deployment does not offer sign-up or sign-in. There is no user account, no password, no email capture, no profile and no marketing list. You are not identified, and nothing you do here is associated with you as a person.

The demonstration wallet, your simulated balance, positions and transaction history, is stored entirely in your own browser using localStorage. It is never transmitted to Predicta, is not visible to us, and is deleted when you clear your browser storage or press "Reset demo" in the product.

Four preference cookies may be set: your colour mode, your accent colour, your language, and your region. Each stores a single short value, none identifies you, and they are listed individually in the cookie policy.

Ordinary web-server request data, the URL requested, timestamp, HTTP status, and the IP address and user agent your browser sends, is processed to serve the page and may appear in application and platform logs. Predicta does not use this to build a profile, does not join it to any other data, and does not sell or share it for advertising.

Requests you make to the market API (browsing the catalogue, requesting a quote) reach our servers as requests. Simulated orders update your browser wallet only.

Market data is fetched by our servers from public provider APIs. Your browser does not contact those providers directly for market data.

Market artwork is loaded by your browser from the image hosts that publish it, including provider CDNs and Wikimedia Commons. Loading an image discloses your IP address to that host, as it does on any site that displays a remote image.

Application hosting and the database are operated on infrastructure providers under contract. There is no analytics package, no advertising network, no session recorder and no third-party tracking script on this site.

Because no account exists, there is no user record to export or erase. Browser-stored data is under your control directly. Server logs are retained by the hosting platform under its own default retention.

A production deployment handling identified end users requires a named data controller, a lawful basis, a retention schedule and a route for data-subject requests. Those follow from decisions that have not been made; this page does not assert them.

This is a pre-launch draft. It accurately describes how the system currently behaves and it has not been reviewed by a lawyer.

A production deployment requires a named contracting entity, a governing law and jurisdiction, and jurisdiction-specific regulatory analysis for every market in which event contracts would be offered. Those are commercial and legal decisions that have not been made, and this document does not pretend otherwise.

If you are evaluating Predicta commercially, ask for the current draft of the agreement rather than relying on this page.