Power Play AI - Privacy Policy
Effective Date: October 6, 2026 (replaces the September 21, 2026 policy)
The short version
Power Play AI has no accounts, no ads, and sells nothing about you. The prediction models run on your phone. The app does send a small amount of anonymous data to our own server so we can publish community results and fix what breaks, and if you choose to scan a paper ticket the photo is read by a third-party AI service. You can turn the usage analytics off in Settings at any time. This page lists exactly what leaves your device and why.
What the app collects, and why
- An anonymous install identifier. A one-way hash (SHA-256) of the identifier Apple assigns to this app on your device. It is not your name, email, phone number, Apple ID, advertising identifier, or anything that identifies you to us or to anyone else. We use it to count active installs and subscribers, to avoid counting the same result twice, and to cap ticket scans at 30 per device per day so nobody can run up the scanning service. Our server forgets it after 90 days without activity.
- Coarse facts about the install. App version, iOS major version, whether the app came from the App Store or TestFlight, the app language you chose, your region (US games or EuroMillions), your App Store storefront country, a coarse device generation, and your time-zone offset. We also record your notification permission setting (allowed, denied, or not yet asked), which of our home-screen widgets you have added, and whether the Apple Watch app is installed — so we can tell whether those features are worth maintaining. Never a precise location, device name, or serial number.
- Subscription state. Whether the Enhanced subscription is active, expired, in a billing grace period, or refunded — so we can see how the product performs. Never card or payment details; Apple handles all payments and we never see them.
- Anonymous usage counters. Events such as "opened the model sheet," "generated a forecast," "revealed a result," "shared a card," "turned notifications on or off," and whether a data source we depend on loaded or failed. Each event carries only short, fixed category values (for example the lottery, a jackpot size band, or the screen name). Events never contain free text, your ticket numbers, or the numbers on a scanned ticket.
- Scored forecasts (the community record). When a draw resolves, the app reports each forecast it generated together with the winning numbers and how many matched, plus one random "control" line generated alongside each forecast for comparison. These rows are anonymous and are the source of the public Community Results page. They are published only as aggregates.
- Ticket-pack summaries. For a saved ticket pack, how its lines did as a distribution (how many matched 0, 1, 2 … numbers) and the pack's size and cost — not the lines themselves.
- Scanned-ticket outcomes. If you check a scanned or typed ticket, the app reports how many numbers matched — never the numbers.
- Crash and performance signals. Counts of crashes, hangs, slow launches, and high memory use, as reported by Apple's MetricKit. No stack traces or personal data.
Subscription records from Apple
Apple sends our server signed subscription notifications, such as purchases, renewals, expirations and refunds. To avoid counting the same subscription or notification twice, we store one-way hashes of Apple's transaction and notification identifiers, together with the product, expiry date, renewal state and event date. Raw transaction identifiers and signed payloads are not retained. These records are not linked to the app's install identifier or usage history, and individual identifiers are never published. We also use Apple's daily aggregate reports to count paid subscriptions separately from devices.
Apple subscription accounting continues independently of the app's optional usage analytics. We do not send usage or consumption information to Apple in response to refund-review requests.
Ticket scanning
Reading the numbers off a paper ticket is done by a third-party AI service (OpenAI's image models). When you scan a ticket, the photo is sent through our server to that service, the numbers come back, and the photo is not stored by us. The photo is sent only when you tap Scan; nothing is read from your photo library or camera otherwise. Scans are limited per device per day to keep the service fair. You can always type a ticket in instead of scanning it.
Your controls
- Turn analytics off. Settings → Privacy & responsible play → "Share anonymous usage data." When it is off the app stops sending usage counters and stops attaching the anonymous install identifier to them. Scored forecasts still contribute to the community record, with no identifier attached. One exception, because it protects the service rather than measures you: scanning a ticket still sends the anonymous install identifier, which is how we cap scans at 30 per device per day.
- Delete. Deleting the app removes everything stored on your device. Because the data we hold is anonymous, we cannot look up or delete "your" rows on request — there is nothing that links them to you.
- Notifications and camera are each controlled by iOS permissions you can change at any time in Settings. The app does not use location at all and never asks for it.
Data we download
The app fetches public lottery draw results and jackpot amounts (from sources such as data.ny.gov and the lotteries' own sites), our own history and configuration files, and — for the Quantum model — pre-generated quantum random data. These requests carry no personal data.
Retention
Anonymous install rows expire after 90 days of inactivity. Usage counters and community results are kept as aggregates indefinitely, because they are the published track record. Apple notification records are retained for up to 365 days. A hashed subscription record is removed after its expiry, grace period and most recent notification are all more than 365 days old. Daily Apple subscription snapshots are retained for up to 365 days. Ticket photos are not retained by us. Each install row also keeps a record of the 85 most recent days on which the app was used, and a short checklist of milestones the install has reached — such as finishing onboarding, making a forecast, turning on notifications, viewing the subscription screen, or subscribing — so we can measure whether people keep using the app and where they stop. Both are only ever reported in aggregate and expire with the row.
Third parties
Our server runs on Cloudflare. Ticket scanning uses OpenAI. Payments, subscriptions, and App Store analytics are handled by Apple under Apple's privacy terms. We do not use advertising or tracking SDKs, we do not track you across other apps or websites, and we do not sell, rent, or share data with data brokers.
What we do not do
- No accounts, names, emails, or contacts.
- No advertising, no ad identifiers, no cross-app tracking.
- No location of any kind, no reading of your photo library, no reading of your clipboard.
- No storage of ticket photos or scanned numbers on our servers.
- No sale or sharing of data with third parties for their own purposes.
Children's Privacy
Power Play AI is intended for adults who can legally play the lottery where they live. We do not knowingly collect any personal information from children.
Changes to This Policy
When our practices change, we update this page and the effective date, and describe the change inside the app. The previous version of this policy stated that nothing was transmitted; that stopped being accurate when the community results feature was added, and this version corrects it. The September 21, 2026 revision adds details the app was already collecting but this page did not list: your notification permission setting, which widgets you have added, whether the Watch app is installed, and the per-install activity and milestone records described under Retention. Nothing about what the app collects changed. The October 6, 2026 revision reflects one change on our server: the per-install record of days the app was used now holds the 85 most recent such days (previously 62), so that our 12-week usage figures are worked out from complete records. What the app sends did not change.
Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us at hello@squatchcraft.com.