Your games are personal data, not raw material by default.

01

Product data the private alpha may process

When product accounts open, Boardvision is expected to process the minimum information needed to authenticate you, analyze games, run training sessions, preserve learning state, and keep the service secure.

• Account data: your Sign in with Apple subject identifier and any name or relay email Apple provides during first authorization.
• Chess data: imported PGNs, normalized games, positions, engine analysis, clocks when present, and source metadata.
• Learning data: review predictions, candidate moves, explanations, confidence, due reviews, skill observations, style observations, and assessment responses.
• Service data: device installation records, push tokens, App Attest records, request and job identifiers, app version, reliability diagnostics, and security events.
• Purchase data: signed App Store transaction records and entitlement state if subscriptions are introduced.

Boardvision does not need your Apple password, private keys, or raw Keychain contents and should never ask you to send them.

02

How product data is intended to be used

• Import, normalize, analyze, and display your games.
• Estimate skills, style, and uncertainty as separate signals.
• Deliver adaptive games, structured review, spaced practice, and neutral assessment as those phases become available.
• Authenticate requests, prevent abuse, investigate failures, and keep state consistent across devices and reconnects.
• Provide support, data export, account deletion, and entitlement reconciliation.

Boardvision is not designed to sell private game histories or use identity-level labels such as “bad at tactics.” Feedback is meant to reference observable decisions and remediable process.

03

Population-model training requires a separate choice

A Boardvision account may use private imported games without allowing those games to train a population model. Product use and population-training consent are separate.

Withdrawal removes private data from future training manifests. Boardvision will not promise retroactive model unlearning until that workflow is implemented and tested. Player embeddings are treated as personal data and are not exposed to other users.

04

Storage, security, and service providers

The planned architecture keeps authoritative account and learning state in PostgreSQL, large encrypted artifacts such as PGNs in private object storage, and recoverable jobs in a durable queue. The iOS app uses local storage as a cache and offline queue—not as the account source of truth.

Expected service categories include Apple for identity, push, and purchases; Render for application infrastructure; an S3-compatible object-storage provider; and tightly scoped reliability or error-monitoring services. A finalized provider list and contractual details will be published before broad availability.

Planned protections include encryption in transit, private service networking, account-scoped authorization, short-lived signed upload links, rate limits, artifact checksums, and audited access to sensitive content.

05

Your controls

The product requirements include the ability to:

• Request an export of your account data.
• Delete your account, imported PGNs, reports, player embeddings, device records, and queued work.
• Opt out of future population-model training without losing ordinary product access.
• Change notification preferences and remove push tokens.
• Sign out one device or revoke all active sessions.

Some billing or security audit records may need to remain where legally required; they should be minimized and kept separate from deleted chess content.

06

Retention is not yet a blank check

Exact retention periods will be finalized before private-alpha accounts open. They will distinguish active account data, recoverable backups, short-lived logs, billing records, and deletion evidence. Until those periods and operational deletion tests are complete, this page should be read as a prelaunch design commitment rather than a final legal notice.

07

Questions or data requests

Use the email link below for privacy questions, alpha data requests, or corrections to this notice. Do not include Apple identity tokens, App Store transaction payloads, passwords, or private keys.