Pupdoku Privacy Policy

01Information saved on your device

Pupdoku stores puzzle boards, placements, pencil notes, undo history, timers, hint counts, results, completion dates, streaks and app preferences so you can continue playing. It also keeps limited detailed attempt history and local copies of online sessions. Hint-treat balances, transaction-fulfillment identifiers and recovery records help preserve earned items and prevent duplicate credits. These purchase and balance records are not part of email cloud saves.

Email-account and online-guest credentials are stored separately in the device Keychain. Connection and loading diagnostics are kept locally and can be viewed, cleared or copied from Settings. These local logs are not automatically sent to us. If you choose to send a log, screenshot or result card, the selected information leaves the app through the service you choose. Device backups and local recovery copies are separate from Pupdoku's email cloud-save feature.

02Optional email sign-in and cloud saves

If you choose Save across devices, Supabase processes your email address, account identifier, sign-in codes and session information to authenticate you and protect your backup. Authentication and email-delivery services process the recipient address, sign-in email and delivery information needed to send the code. Your email is not displayed in public standings. We use it for account access and communications about your account or support request, not to publish a player profile.

While signed in, cloud saving transfers casual puzzle state, placements, notes, undo snapshots, timers, hint counts, attempt identifiers and timestamps, puzzle snapshots, results, completion dates and last-played puzzle identifiers. Puzzle snapshots can include their solutions. Detailed action-event lists are removed from new cloud-save payloads, but undo history is included. Completion dates can reflect online play; full online attempts and their resumable sessions are not cloud-synced.

The service holds the current cloud-save revision and one previous revision for recovery, linked to your email account. Preferences, Journey history, archived detailed attempt histories, hint wallets and purchase identities are excluded. Signing out stops account-based syncing but does not erase your server backup or downloaded local progress.

03Daily challenges and friend invitations

Online features use a separate, automatically assigned guest account and public player name. We store that identifier and name, Daily attempt dates, start times, status and eligible elapsed times. Public standings show player names, eligible times and positions, not account email addresses or raw account identifiers. Solved cells are transmitted to validate a Daily result; the result record stores timing and status rather than the submitted cell array.

Creating an invitation stores its code, sender's guest identifier, puzzle, optional target time, assistance information, hint rule and creation time. Invitations do not include personal messages. Any player with the code can open the invitation through the app's authenticated guest service; a code is not restricted to a named recipient. The invitation website and public link preview do not retrieve the puzzle solution.

The service records per-day request counts and invitation-opened, started and completed counts associated with the guest identifier. These records support abuse prevention and understanding how invitation features are used; they are not anonymous simply because a real name is absent. Invitation event counts do not include the invitation code or individual puzzle moves. Sending a result back to a friend is voluntary, not an automatic notification of your score.

04Purchases and subscription offers

Apple processes payment for Pupdoku+ subscriptions and one-time hint-treat packs. RevenueCat processes an app-specific customer identifier, purchased products, transaction identifiers and dates, subscription status, expiration and entitlement information to verify purchases, restore eligible access and prevent duplicate fulfillment. We do not receive your full payment-card details.

Superwall presents and measures Pupdoku+ offers using the corresponding purchase customer identifier, subscription status, offer source and trial-eligibility information. Its service can process offer views and interactions, app installation and usage timing, device/vendor identifiers, app and operating-system versions, device model, language, region, timezone, network information and approximate location inferred from IP address, such as city or country. This supports offer delivery, localization and analysis of the subscription experience. Pupdoku does not request GPS location access.

Purchase and paywall services can communicate when the app starts, even if you have not signed in or bought anything. The email cloud-save account is separate from the purchase identity. Journey history controls do not switch off these services, their operational records or online challenge counters.

05Optional Journey history

Journey history is off by default. If you enable it under Settings → Privacy and history → Journey history · optional, your device records active UTC calendar days and whether a guided Pupdoku or Classic demo was started, completed, skipped or closed early. Each observation includes its type, day and, where relevant, mode and a random demo identifier. It does not contain moves, solutions, email addresses, invitations, transaction identifiers or revenue. Earlier activity is not added retrospectively.

This history remains on this device: it is not uploaded or included in email cloud saves, and its cache is marked as excluded from device backups. The app keeps at most 300 observations across the last 30 UTC dates, removing older entries when history is refreshed during app use. Disabling history stops new recording and attempts to delete the existing history. If deletion fails, recording remains off and the app offers a retry.

06Advertising, website requests and support

Advertising is disabled in this release. Free and Plus players have no third-party ads or rewarded-ad offers, and the app does not request Apple's tracking permission. The purchase and paywall processing described above still applies. Any future material change to advertising or data use will be accompanied by updated notices and choices required by applicable law.

The Pupdoku website at pupdoku.app lets you play the Pupdoku and Classic puzzles directly in your browser. Game progress on the website is stored only in your browser's local storage on your own device and is not uploaded to us; clearing your browser data removes it. The site also displays invitation codes you can copy; it does not read your contacts or fetch a private invitation record. Hosting and image-delivery services, including Rork and its infrastructure providers, receive ordinary network requests, which can contain an IP address, browser or device information, requested URL (including an invitation code in that URL), timestamps and security or error information. The website does not add advertising or analytics cookies in its own application code. Infrastructure services may use technical storage or logs to deliver and protect the site.

When you contact support, we receive your email address and whatever you choose to include, such as a description of the issue, device details, screenshots, diagnostic extracts or an Apple order reference. We use this to answer you, investigate issues and handle account, purchase or privacy requests. Please send only information relevant to your request, never passwords, sign-in codes or full payment-card details.

07Why we use information and who receives it

We use information to provide requested gameplay and accounts, save and restore progress, validate challenge results, deliver invitations, fulfill purchases, display relevant subscription offers, understand feature and offer use, prevent fraud and abuse, resolve problems and meet legal obligations. Where a legal basis is required, we rely on performance of our agreement for requested services, legitimate interests in maintaining a secure and usable service and understanding its performance, compliance with legal obligations, and consent where required. You can object to processing based on legitimate interests and withdraw consent where processing relies on it, subject to applicable law.

Information is shared with providers needed for authentication, database and hosting operations, email delivery, payment processing, purchase verification, paywall presentation and support. These include Supabase, Apple, RevenueCat, Superwall and Rork. Information you choose to share is also received by the people and services you select. We may disclose information to comply with a valid legal requirement, protect people or service security, resolve a dispute, or in connection with a business reorganization or transfer, subject to applicable legal protections.

Ignitexgroup LLC is based in the United States. Providers may process or store information in the United States and other countries, where privacy laws may differ from those in your country. Applicable international-transfer requirements continue to apply. Contact us for information about the providers and safeguards relevant to your data or to exercise your rights. We use access controls, authenticated requests and device credential storage to protect information, but no system is completely secure.

08How long information is kept

Local detailed ended-attempt history is limited to the most recent 30 attempts, with up to 1,200 events per attempt. Connection and loading diagnostics retain the latest 150 entries. Active saves, solved results, online resumes, balances and purchase-recovery records are separate. Clearing a history list does not erase these other records, previously created recovery copies or copies on another device. The separate Journey history limits are described above.

Server accounts, challenge records, invitations and daily usage rows do not automatically expire when a puzzle or day ends. They remain associated with the relevant account unless removed through account deletion or another applicable deletion process. A cloud save contains its current and previous revision; the previous revision is replaced after the next successful save. There is no fixed inactivity-based account or invitation expiry in the current service.

Retention of provider logs, infrastructure backups, purchase records and support correspondence depends on their operational purpose, backup lifecycle, fraud prevention, accounting or legal requirements, and the need to resolve an outstanding request or dispute. Account deletion does not immediately remove all provider-held records or backup copies. We assess privacy requests in light of these requirements and explain any applicable exception; no single deletion period applies to every category.

09Your controls and privacy rights

For the email account, open Settings → Save across devices → Delete email account and cloud backup. Successful deletion removes that account and its current and previous cloud-save records from the active service. Local progress, the separate online guest profile and purchases remain. To delete the guest profile and associated server results, invitations and usage records, open Challenges → Daily challenge → Delete my online guest profile. This also clears the app's local online attempt list; cached boards, recovery files and copies already shared elsewhere are separate. Follow any retry notice if a deletion or local cleanup fails.

Settings → Privacy and history provides separate controls for ended-attempt history and optional Journey history. Account deletion is not a complete device wipe and does not cancel subscriptions, remove Apple's transaction records, automatically delete RevenueCat or Superwall customer records, or recall information shared with others. For help with information outside an in-app deletion control, contact us using the address below.

Depending on your location, you may have rights to request access, correction, deletion, a portable copy, restriction of processing, withdrawal of consent or objection to certain uses, including applicable sale, sharing or targeted-advertising opt-outs. Email support@ignitexgroup.com with the subject Privacy request and identify the relevant feature or account. We may request proportionate proof of authority to protect your information; do not send sign-in codes or payment-card details. We respond within applicable legal time limits, explain any refusal or retention exception, and provide an appeal route through the same contact where required. Exercising your rights will not result in unlawful discrimination.

You may also complain to the privacy regulator where you live, including the UK Information Commissioner's Office, the Office of the Privacy Commissioner of Canada or relevant provincial authority, the Office of the Australian Information Commissioner, or New Zealand's Office of the Privacy Commissioner, as applicable. These rights do not depend on our company being incorporated in your country.

10Young players and policy changes

Pupdoku is intended for teens aged 13 and older and adults, not children under 13. If a player is below the age at which they can agree to terms or authorize the relevant processing in their location, a parent or guardian must be involved as required by law. We do not ask for a date of birth in the current app. If you believe a child has provided personal information contrary to these requirements, contact us so we can investigate and take appropriate action, including deletion where required.

We will update this policy when our practices change and provide additional notice or seek consent where required. The last-updated date identifies this version. Questions about this policy or our handling of personal information can be sent to Ignitexgroup LLC using the contact details below.