VIBE SHIFT

Clear, local-first privacy

Privacy Policy

VIBE SHIFT is designed to work without accounts, advertising, analytics or tracking. This policy explains exactly what stays on your device and how purchases and support are handled.

Updated 6 September 2026VIBE SHIFT 1.2.0–1.3.0English

1. Who this policy covers

This Privacy Policy applies to the VIBE SHIFT app for iPhone and iPad and to this support website. VIBE SHIFT is developed and published by Lars Ask.

This update covers versions 1.2.0 and 1.3.0. Participant roles, challenge variations, recent-challenge history, host controls and the practice duel described below are features of version 1.3.0; they apply when that version is installed.

For questions about this policy, use the contact details on the Support page.

2. Data collection

The developer does not collect data from the VIBE SHIFT app. Player and game information is processed locally on your device and is not sent to the developer.

The app has:

  • no user accounts or sign-in;
  • no advertising;
  • no third-party analytics SDKs;
  • no cross-app or cross-website tracking; and
  • no developer-operated server.

3. Data stored locally on your device

VIBE SHIFT stores the information needed to run the game, remember your choices, continue an unfinished game and reduce repeated challenges.

Participants and preferences

  • participant names, locally generated identifiers, default-name markers and roles: player, jury member or spectator;
  • selected card packs and round count;
  • language, haptic feedback and onboarding preferences; and
  • a local completed-game count used to decide when the app may ask for an App Store review.

Unfinished games and host controls

An unfinished-game snapshot contains participants and roles, player scores, a session identifier and creation time, selected packs, language, card content and order, challenge variations, assigned participants, progress and a random seed. It also remembers host settings such as pause, score visibility, the intensity limit, the selected next player and a counter of host adjustments. This lets you continue the same game later on the same device.

Only players receive challenges and points. Jury members can decide shared votes and duels, but the app does not save individual ballots or spoken answers. The shared decision can change players’ accumulated scores; there is no separate log of individual votes.

Recent-challenge history

A separate local history remembers up to 180 recent card and variation code pairs, in order of use, to reduce repetition. A challenge is added when it is displayed, including when you pass it, not just because it was planned for a future round. The oldest entries are replaced as the limit is reached.

This history contains no participant identifiers, names, answers, votes, scores or timestamps. It is not a record of who performed a challenge. The creation time in an unfinished-game snapshot is separate from this history.

Practice duel

The free practice duel uses two temporary, generic players. Its participants and result exist only in memory while that trial is open. It does not save a game, scores or challenge history, and does not change an existing saved game.

Local storage and backups

Participant, unfinished-game and recent-history files are stored in the app’s local container using iOS file protection and are marked as excluded from device backups. Ordinary preferences are stored separately and may be handled by Apple’s normal device-backup settings. The app does not provide its own cloud sync. None of these gameplay records is sent to the developer.

4. In-app purchases

Optional one-time purchases are processed by Apple through StoreKit. The app obtains product, transaction and entitlement information to display prices, confirm access, restore purchases and respond to purchase changes. It can check products and entitlements when opened, not only when you make a purchase.

The developer does not receive your payment card number, billing address or other payment credentials. Apple’s handling of App Store and payment information is governed by Apple’s Privacy Policy.

5. Retention and deletion

  • Participant names and roles in the participant list remain until you edit or remove them, choose Reset participants in Settings, or delete the app. An existing saved game contains a separate copy: editing the participant list does not erase names or roles in that snapshot. They remain there until the saved game is removed as described below.
  • An unfinished game remains when you close the app. Its saved snapshot is removed when you finish it, discard it from the game or Home, reset participants, or delete the app.
  • Recent-challenge history is independent of the saved game. Finishing a game or resetting participants does not clear it. In Settings, choose Clear challenge history and confirm. Only the recent card and variation codes are removed; participants, scores, purchases and saved games stay unchanged. Challenges displayed afterwards are remembered again. Old entries also disappear as the 180-entry limit is reached.
  • Preferences remain until you change them, reset them where available, or delete the app.

Reset participants restores three default players and removes the unfinished game; it does not reset every preference or challenge history. Version 1.2.0 uses the earlier Reset players control and has no separate challenge-history feature. Deleting the app removes its local data; offloading the app is not the same as deleting its data. Apple-managed backups and purchase records are controlled separately by Apple.

The developer has no server copy of your gameplay records to access or delete. Use the app’s controls to manage data on your device, and the contact details below for support correspondence.

If a local deletion cannot be completed, the app displays an error so you can try again.

6. Support messages

If you contact support, the developer receives the information you choose to include, such as your email address, device details and message. It is used only to respond, investigate the issue and maintain necessary correspondence.

Support correspondence is kept only for as long as reasonably necessary to resolve the request and meet applicable legal obligations. You may ask for a support message to be deleted by replying to the same conversation. Do not include player names or other sensitive personal information unless it is genuinely needed.

GitHub Issues are public. If you choose that channel, do not post personal, confidential or payment information. GitHub processes information under its own privacy terms.

7. This website

This website uses no cookies, analytics, advertising, tracking pixels, external fonts or contact forms. It is hosted by GitHub Pages. When you visit, GitHub may process technical request information, such as your IP address and browser details, under the GitHub General Privacy Statement.

8. Changes and contact

This policy may be updated if VIBE SHIFT’s features or data practices change. The effective date at the top of this page will be updated when material changes are published.

Questions, privacy requests and support enquiries can be sent through the contact methods on the Support page.