PRIVACY / AUG 24, 2026

A choice should not become a dossier.

ViewsMeet works without an account. Public cohort contribution is optional, aliases are lightweight, and private challenge controls stay with unguessable local tokens.

Daily play data.

A submission contains the pack ID, version, digest, five self choices, five panel predictions, and whether public contribution was selected. A server may return an opaque session ID and privacy-safe result metadata.

ViewsMeet does not request a legal name, email address, contacts list, social graph, photo, or private account to play.

Full-profile rounds stay private.

The browser submits 21 listed choices to calculate a seven-axis result, then keeps the local answer vector needed to create an optional friend challenge. The score response contains only aggregate profile output. Full-profile choices are not accepted by the public cohort route, and friend comparison responses do not return either participant’s answer sheet.

Public contribution is off unless you choose it.

The “include my picks” control adds the five self choices to an aggregate cohort. A challenge alias is not attached to that public contribution. Results remain unpublished below configured privacy/sample thresholds.

For the public world view, ViewsMeet retains only the two-letter country code supplied by Cloudflare at the edge. It does not retain the raw address for the world view, request precise location, or publish country cells smaller than three responses.

When public opt-in is available, selecting it lazily loads a managed Cloudflare Turnstile widget and produces a one-use admission token. The widget is not loaded for private-only play. If an edition does not supply a Turnstile site key, the production interface disables public opt-in instead of claiming inclusion.

Public cohorts are not described as verified or representative populations. Do not submit sensitive information; questions are curated specifically to avoid soliciting it.

Anyone with a friend URL can use it.

A challenge stores the creator’s picks, optional alias, immutable pack reference, responses, safe reactions, and expiry. After someone completes the challenge, their per-question Knowledge and Match result can reveal the creator’s issued choices to them. No participant receives another respondent’s answer sheet.

Exact privacy-safe group tallies appear only after the link has five total people, including its creator. Challenge URLs are private-by-sharing, not encrypted messages. Do not post a link publicly if you want it to remain within a small group.

Control tokens stay in this browser.

The browser stores opaque challenge-management and response-deletion tokens in local storage. They let the holder inspect privacy-safe management summaries or delete the associated challenge/response. A random browser key and per-challenge participant key help the service limit duplicate aggregate or friend submissions without creating an account. These values are not synchronized between devices by ViewsMeet.

Clearing browser storage removes your local control token.

The underlying challenge can still expire normally, but this browser may no longer be able to delete it early.

Operational data.

The Cloudflare edge can process IP address, user agent, route, response status, approximate region, timing, rate-limit, abuse, and security signals needed to deliver and protect the service. Private-only play loads no third-party advertising trackers, analytics scripts, fonts, or images. If public opt-in is selected, the interface loads Cloudflare’s Turnstile script and verification frame for that admission check; no other third-party script is introduced.

Software-agent ballots carry configuration and provenance metadata supplied or derived through the machine interface. Payment data is not part of the launch gameplay described by this notice.

Your controls.

  • Play without opting into the public cohort.
  • Leave aliases blank.
  • Keep challenge links within the intended group.
  • Use the local response control to delete your challenge response.
  • Use the creator control to delete a challenge.
  • Clear local storage to remove tokens from the current device, understanding that this also removes local deletion access.

Expired, deleted, and low-sample states are explicit. This notice will receive a new effective date if data practices materially change.