Privacy statement

Kalibr is a public research alpha and playable measurement prototype. Playing produces detailed information about your actions and results. This statement explains that information, gameplay recordings, providers and your choices. The Terms & Conditions describe the service agreement.

This statement, the Terms & Conditions and the data-deletion request link are in Fathom Settings. For account or server-side deletion, contact the Kalibr administrator at admin@usekalibr.com. The device data controls below act on this browser only.

1 · Responsibility and scope

Kalibr is operated by Kalibr Labs Limited, company number 17296211. Kalibr Labs Limited is the controller responsible for the personal data described in this statement. References to Kalibr, we, us or our mean that company.

Registered office: 3rd Floor, 1 Ashley Road, Altrincham, Cheshire, United Kingdom, WA14 2DT. For privacy questions and deletion requests, email admin@usekalibr.com.

This statement covers Kalibr websites and game services, including Fathom and Untangle where available. External websites have their own privacy practices when you follow a source link or leave Kalibr.

Automatic collection is not recorded as your consent or acceptance of the Terms. Contact the administrator using the email above for privacy questions or requests.

2 · Information you provide

Accounts and contact. Registration and sign-in can supply your account ID, email, handle or display name, creation time and authentication/session information. An external sign-in provider may supply a name and email. If you contact us, we receive your message, contact details and any attachments you choose to send.

Optional context. The optional demographic intake can include year of birth, country or city, education, field, employment and gender. You can skip it. Its answers stay in browser storage and are not submitted with gameplay sessions. Separately saved profile information and personalisation choices, where available, have their own controls and permissions and are private by default. Kalibr does not claim an established comparison pool or validated norms.

If you choose the location lookup in that intake and permit browser geolocation, the browser supplies coordinates for a local nearest-city lookup. The saved answer is the city/location you select; that lookup does not submit precise coordinates with a gameplay session.

Game content. We process questions, clues, choices, orders and other inputs needed for the mode you use. Published questions and news can be visible to others in the round. Administrator question research can send submitted text to the AI provider in section 8. Avoid putting personal or confidential information in game content that will be published or researched.

If you use Friends, Kalibr stores the player name and avatar you choose, your friend requests, accepted friendships and blocks. Sharing your player link lets other signed-in players see that chosen name and avatar. It does not share your email, private statistics or session history.

Reflections, feedback and game suggestions are optional. Only pressing Save or Send submits your text and any voice recording to Kalibr. Your submissions are available to you and authorized Kalibr staff, not other players. They help you keep a strategy history and help Kalibr understand gameplay, difficulty and requested features. Original voice recordings are stored for later transcription. They do not change ratings or measurements.

Please keep sensitive information out of optional free-text and voice submissions.

3 · Information produced by play and use

Operational gameplay. Depending on the game and mode, records can include actions, per-trial responses and timing, game states, orders and fills, scores and results, game versions and seeds, session/round IDs, timestamps, room membership, connection state and evidence supporting saved history. Some information stays in browser storage; supported online modes also send information to Kalibr servers. Live rounds can depend on temporary server memory and may be lost on a restart before their results are saved.

Measurement and competitive evidence. Where a mode has an active measurement path, records can include measurement estimates and uncertainty, integrity flags, provenance, and the collection policy version, mode and first-use time. Canonical ratings require signed, server-verified competitive evidence. Solo play and bots do not write competitive ratings. Not every game or mode has an active measurement path. Gameplay recording does not determine official ratings or establish a cognitive score.

Technical data. Requests to Kalibr and its providers expose information such as IP address, browser/device information, requested resource and connection time. Game records may include viewport, input type and focus or visibility changes. Hosting, authentication and security providers may process request, error and access logs to deliver and protect the service.

Guest identity. Guest play uses persistent random identifiers and, for supported history, separate browser ownership credentials. Earlier guest rounds join an account only after explicit confirmation. Usage analytics can also link guest activity to a signed-in account. These records are pseudonymous personal data; the absence of your name does not make them anonymous.

4 · Granular gameplay recordings

Kalibr automatically collects gameplay actions, results and supported detailed replay data when you play. Fathom research records include optional submitted estimates and 90% ranges, published contract descriptions, information-presentation timing and separately recorded host market events. Draft forecasts and unrelated typing are not collected. This build has no pre-play agreement prompt and no in-app switch to disable collection. A collection-policy record describes automatic processing; it does not record that you accepted Terms or gave consent.

Research uses a code instead of your name. Kalibr can link coded records back to your account, so this is pseudonymous personal data, not anonymous data. Your private history remains linked to you. Automatic collection does not give permission to display your name in research views.

Supported private recordings of Untangle and Fathom Open Question, Cards & Dice and Map are stored in Kalibr's PostgreSQL database on Railway. A replay reconstructs browser observations. Late joins, reloads and interruptions can produce partial coverage. Playback depends on the game and recording format. Replays do not change ratings or measurements.

Verified multiplayer. Verified Untangle duels and Fathom Arena fields keep account-to-seat bindings and the commands used to run the match. Kalibr uses these server records to resume a match, verify its outcome, and apply eligible competitive results.

Current gameplay recordings go to Kalibr’s first-party capture service and PostgreSQL on Railway. They do not depend on PostHog or an analytics SDK. Detailed recording covers supported modes; it is not evidence that every game, tutorial or study has a collector or active measurement path.

Untangle. Supported full, daily and participating Contract 1v1/BR runs can record pointer/drag movement, clicks, grabs/releases, game keyboard actions, puzzle transitions, board geometry, moves, crossings, timing, focus/visibility, viewport and game/build versions. Moving-pointer sampling can reach 14 observations per second; relevant actions are recorded individually. Tutorials and replay viewing are excluded.

Fathom Open Question. Recordings include the products observed in your round, your trading selections and commands, their responses, your holdings, orders and fills, published questions/clues, public market updates and settlement. They can include pointer movement, scrolling, focus/visibility, viewport, animation-frame intervals and server ping probes, replies and timeouts. These observations do not prove that a clue was read or measure underlying packet loss. Administrator observations are labelled separately from player performance.

Cards & Dice. Supported actual solo and seated multiplayer rounds record timed market states across recorded products, revealed draws, your holdings, orders, trades, command timing and final results. Tutorial and guided practice are excluded.

Map / Meadow. Supported solo, private and public player rooms record observed objects, explored cells, surveys, released clues, public positions and market information, your orders/fills and settlement. Ordinary frames are sampled every half second; commands and relevant phase changes are recorded separately. Coverage remains partial. Observer-only visits, lobbies, tutorials and cinema studies are excluded from this player recorder.

Native gameplay packets exclude direct account name/email fields, authentication and guest ownership credentials, invitation links/codes, arbitrary typed text, unpublished question/news drafts and other players’ private orders. Published questions and clues can be recorded as written, including personal information someone places in that content. Native page/DOM or screen-video recording is disabled. These event-based reconstructions can nevertheless describe play in considerable detail.

A replay reconstructs the observations received, not a perfect video of the game. Late starts, reloads, interrupted connections and capture limits can produce partial coverage. Playback availability depends on game, mode and recording format. Recording a game does not establish measurement or competitive rating authority.

5 · Purposes and lawful bases

Service delivery. Account information, live game actions and saved results support the functions you use. Information required to run an online mode cannot simply be omitted while still delivering that mode. Where contract is the applicable legal basis, it covers processing objectively necessary for the agreed service; research or detailed recording does not become legally necessary merely by being mentioned in the Terms.

Automatic collection. The current build records supported gameplay and configured usage analytics automatically. Its technical policy record is not an opt-in, a research consent or a Terms-acceptance receipt. Research uses coded identities; automatic collection does not give permission to display your name. Separate permissions still apply to explicitly supplied optional profile facts. Describing a purpose in this statement does not itself make that purpose legally necessary or create a lawful basis for it.

Integrity and support. Necessary, proportionate handling of security events, abuse, technical faults and support serves the legitimate interests of protecting players and the service and resolving problems. Legal obligations can also require particular records or disclosures, including handling data-rights requests. Where legitimate interests apply, you may object and ask about the interests and balancing assessment.

Research and aggregate insights. Gameplay collected under the current policy may support instrument research and aggregate benchmark distributions or norms, including commercial aggregate insights. Pseudonymised records remain personal data. An output must be genuinely anonymous, with no reasonable means of identifying a player, before it is treated as outside data-protection law. Removing a name is insufficient. Kalibr does not sell identifiable player data or use it for advertising or profiling outside Kalibr.

6 · Usage analytics, browser storage and controls

General usage analytics uses PostHog in the EU for pages opened, selected button actions and session completion or abandonment, linked to a guest or account identifier. With the analytics service configured, collection starts automatically. The SDK uses persistent browser storage. SDK/project settings can also supply technical properties, approximate location derived from IP information and performance events. Native DOM/video recording and automatic capture of every page interaction are disabled.

General usage analytics is collected automatically through the configured analytics service. There is no in-app collection switch. Deletion requests go to admin@usekalibr.com. Deleting stored information is separate from future collection if you keep using Kalibr.

The configured client respects Do Not Track and may be affected by browser privacy restrictions. That is not a promise that every browser signal controls every service, or that blocking analytics stops the separate gameplay capture service.

Kalibr also uses browser storage and authentication/session technologies for sign-in, guest continuity, supported local history, preferences and technical policy records. Clearing or blocking storage can sign you out or reset device information. Local deletion does not turn off automatic collection on later use, delete server records, or retrospectively invalidate processing that was lawful when carried out. Use the administrator contact for server-side erasure requests.

In Friends, you can edit your chosen name and avatar, decline or cancel requests, remove friends and block or unblock players. Blocking removes the social connection and prevents further friend requests; it does not revoke game invitation links. Device-data downloads and deletion do not include or erase these server-side social records.

7 · Visibility to players and administrators

Multiplayer modes disclose information needed to play together. Depending on the mode, this includes display names, presence, public market information, rankings, profit/loss, final positions and results. Room organisers and participants can access a saved room leaderboard. Your recording does not expose other players’ private commands. Other participants can independently copy information visible to them.

Signed-in players can open supported saved replays from their private history. Guests can see the result of the round they just played; saved history requires sign-in. Earlier guest rounds join an account only after explicit confirmation. Authorised Kalibr administrators can access stored replays to operate and support the service. Replays are not public. Private profile information is not automatically a public player profile.

8 · Service providers and other recipients

Kalibr uses Vercel for frontend hosting; Railway for backend, live game services and application PostgreSQL storage; and Supabase for authentication. PostHog in the EU receives automatic usage analytics when configured. Current v6 native gameplay archives use Railway, not PostHog. Historical analytics-based recordings may still exist under earlier policies. Each provider processes information needed for its role; not every provider receives every category.

Configured Sentry error reporting helps diagnose failures. Depending on the service, reports include exception types, code locations, release/runtime information and limited request or navigation details. The current configuration excludes session replay, performance tracing, request bodies, headers and cookies, and applies filtering to error text and URLs. Error diagnostics are separate from gameplay recordings and usage analytics.

Configured administrator question research uses OpenAI and its hosted web search. Submitted question text, instructions and related context can be sent to prepare a question and source report. Kalibr requests that responses are not stored through the provider’s response-storage feature; that does not promise the provider keeps no security or other service records. Kalibr can retain research, sources and response/usage metadata. Automatic public question generation does not send a player’s question through that research function. AI research is separate from general usage analytics.

Necessary information may also be disclosed to advisers or competent authorities for legal obligations, valid legal requests or the protection of legal rights. Hosting, authentication, requested multiplayer visibility and legally required disclosures do not all depend on a separate consent to sharing.

9 · Locations and international transfers

An EU analytics project does not mean all Kalibr services, backups or support operations are in the EU. Hosting, authentication, AI and subprocessors may involve other countries. Ask the administrator for the locations and safeguards applicable to your information. Restricted international transfers require an appropriate arrangement under applicable law, such as adequacy or approved contractual safeguards. Automatic collection does not substitute for those safeguards.

10 · Retention

Browser-held game data and preferences generally remain until you clear them, the browser removes them or a store replaces older entries. Authentication credentials and other accounts’ data are outside the device-erasure control’s scope. Clearing the browser does not erase copies held elsewhere.

Server retention depends on the purpose: maintaining an account and supported history, completing games, reproducing research covered by the applicable policy, investigating security issues, resolving disputes or meeting legal obligations. Request correspondence may be retained as evidence of the request and response. Identifiable information must not be kept merely because storage is available.

Stored private replays have no automatic expiry. To request account or server-side data deletion, email admin@usekalibr.com; Kalibr's administrator handles requests personally. There is no self-service server deletion. Clearing device data does not delete server records or disable collection when you play again. Applicable erasure rights and retention exceptions are described in the Privacy statement.

Reflections and feedback, including voice recordings, are stored in Kalibr's PostgreSQL database on Railway, with your account or possession-bound guest identity and submission time. They have no automatic expiry. Request access or deletion at admin@usekalibr.com. Device-data export and deletion do not include or erase these server-side submissions. Signing in does not automatically claim guest submissions; adding them to your account requires separate confirmation on the feedback page.

Player cards, requests, friendships and blocks are stored in the application database on Railway to support Friends and its social controls.

Usage analytics and historical provider-based recordings depend on the deployed PostHog project policy. History-view limits are not deletion guarantees. Ask the administrator for applicable periods or to request erasure. Open-ended storage does not remove the duty to review necessity and comply with lawful erasure requests.

Erasure can require action across account, game database, analytics and backups. If particular information must remain, we explain the reason, scope and applicable period. Backup copies may remain until their normal replacement cycle; immediate removal from every backup is not promised. Genuinely anonymous aggregate findings that can no longer be linked to you may remain after personal data is deleted.

11 · Your rights and administrator deletion requests

Depending on applicable law and circumstances, you can request access, correction, erasure, restriction, portability and objection to particular processing, and withdraw consent where it is the basis. Rights have conditions and exceptions; deletion is not a guarantee that every record can be removed immediately.

Account and server-side deletion requests are handled by the Kalibr administrator. Email admin@usekalibr.com and say whether you want account closure, deletion, access or another action. There is no complete self-service account/server erasure control in this build. We also recognise valid requests through other available contact channels; a special form or legal wording is not required.

Provide the account email, if any, and non-secret information that helps locate the play, such as game, approximate dates and available session IDs. For guests, contact us before clearing the originating browser if possible: losing its ownership credential can make identification harder. We may need proportionate identity checks to avoid disclosing or deleting someone else’s information. Do not email passwords, sign-in tokens, guest ownership credentials or a full browser-storage dump; we can explain a suitable verification route.

Under UK/EU rules we normally respond without undue delay and within one month. If a permitted extension is needed, we notify you within the first month with the reason. We explain any different deadline required by applicable law. Requests are normally free. If we refuse part or all of a request, we explain the grounds and complaint route, subject to lawful limits.

The device export covers supported stores for the current browser profile and excludes authentication and guest bearer credentials. It is not an export of all account, server or PostHog data. Saved gameplay recordings, voice recordings, reflections and feedback require a separate request to the administrator. Device erasure removes supported current-profile stores and technical device records; it does not close the account, sign you out, erase another account’s stores or delete server copies. Account closure and server-side erasure use the administrator request described above. Future use can produce new records after deletion; local erasure is not an ongoing collection opt-out.

12 · Automated results and sensitive information

Game rules automatically compute outcomes and, where supported, provisional measurement or competitive rating estimates with uncertainty. Inputs include actions, timing and verified outcomes under the mode’s rules. Results describe recorded play within Kalibr. They are not a diagnosis or Certified Measure and should not be treated as a validated assessment for employment, education, credit, insurance or healthcare. Replay analysis is not official rating or measurement evidence. Contact the administrator to query a result or an error.

The optional intake does not intentionally request race, ethnicity or health information, or diagnose conditions. This does not make detailed behavioural information non-personal or inherently non-sensitive.

13 · Age and security

Age eligibility is set out in the Terms & Conditions. The service is not intended for children below the eligible age. Contact the administrator if you believe an under-age child has supplied personal data so the information and appropriate action can be reviewed.

Kalibr uses authentication, ownership checks and access restrictions for supported private records. No online service guarantees absolute security. Keep account and guest credentials private and sign out on shared devices. A guest ownership credential grants access even though it is not a password.

14 · Complaints and changes

Raise privacy concerns with the administrator. You can also complain to the UK Information Commissioner’s Office or the competent data-protection authority where you live or work. Contacting Kalibr first is not a condition of that right.

This statement changes when actual practices change. A technical policy record is not permission for a new purpose. Processing that legally requires consent must not begin until valid consent has been obtained. Privacy questions and requests: admin@usekalibr.com.