← Back to LottoPrism

LottoPrism / Refracted Forge LLC

LottoPrism
Privacy Policy.

What stays on your device. What connects to a service. What you control.

Effective and last updated:

The main idea: LottoPrism processes ticket images on your device and stores your ledger locally. There is no LottoPrism account or advertising. Android scanning uses Google ML Kit, which sends diagnostic and usage metrics to Google. Other connected features use Apple, Google Play, or lottery-data services, and we receive information you choose to send to support. This website is hosted by Cloudflare.

1. Who we are and what this covers

Refracted Forge LLC (“we,” “us,” or “our”) develops LottoPrism. This policy covers LottoPrism for iOS, iPadOS, and Android, visits to refractedforge.com, and support or privacy correspondence with us. We are responsible for personal information we receive and control through these activities.

LottoPrism is currently in development and coming soon. This policy describes both current development builds, including optional features where available. Shared practices apply to both platforms; differences in scanning, permissions, purchases, and backups are identified below.

2. Information processed on your device

Ticket photos and your ledger

Both versions recognize ticket text on your device and do not upload your ticket images or recognized text to us or a remote recognition service. On iOS and iPadOS, recognition uses Apple Vision; camera access requires permission, and photo import uses Apple’s system picker. On Android, recognition uses the bundled Google ML Kit text recognizer. Android’s camera app and system photo picker supply the image; LottoPrism does not request direct camera permission or full-library access. The camera app may have its own permissions. Google ML Kit’s separate metrics collection is explained in section 3.

The app stores local photo copies and the information you save: game, number combinations, drawing dates, purchase jurisdiction, ticket options and costs, favorites and their names, saved drawing results and sources, and related record identifiers and dates. The iOS build also saves the recognized ticket text locally. It uses this information to organize tickets, compare results, calculate estimated winnings and spending, and display favorites. Random number generation runs on your device. The iOS build also compares downloaded drawing history locally for optional history-based suggestions.

Location

iOS and iPadOS: if a new ticket is missing its purchase jurisdiction and you allow location access, LottoPrism requests your current location and uses Apple’s geocoding service to suggest a state or territory. Apple may process the location and network information needed to answer that request. The app saves the jurisdiction you accept or choose, not your coordinates or a location history. It does not continuously track your location. You can deny or revoke permission and enter the jurisdiction manually.

Android: the current build does not request device location permission or use a location service. The purchase jurisdiction comes from the ticket or your manual selection.

Notifications

Optional final-drawing reminders and winnings alerts are scheduled locally through your device. Notification preferences, ticket references, and records used to avoid duplicate alerts are stored locally. Notification text omits ticket numbers and prize amounts. We do not operate a remote push-notification server. If winnings alerts are enabled, iOS or Android may permit background result lookups as described below. System permissions and scheduling restrictions control delivery.

3. Features that contact other services

Drawing results and history

Result checks contact the New York State Gaming Commission’s Open NY datasets at data.ny.gov. Requests identify the game and drawing date; the iOS history features can also request a date range, selected result fields, and a limit on the number of published drawings. They do not send your purchased number combinations, ticket images, costs, saved jurisdiction, or favorites. The service and its hosting providers receive normal connection information, such as your IP address, request details, and request time. Checks can occur after saving or opening tickets, when you request results or drawing history, and during permitted background checks.

Jackpot updates

Jackpot refreshes contact the Texas Lottery’s public feed at texaslottery.com. The provider receives the feed request and normal network information, including your IP address. LottoPrism does not send it your ticket ledger. Downloaded results and jackpot information may be cached locally.

Android scanning diagnostics

Google ML Kit processes ticket images and recognized text on your Android device; it does not send those inputs or recognition results to Google. Its SDK does send diagnostic and usage metrics to Google, including device model and operating-system information, app package and version, a per-installation identifier, performance and error information, feature events, and technical input/output details such as image format, resolution, and size. Google uses these metrics to operate, debug, improve, and protect the recognition service. ML Kit can also contact Google for updates or compatibility information. These connections expose ordinary network information, including your IP address.

The current app has no separate switch for disabling ML Kit metrics. The iOS build uses Apple Vision and does not include ML Kit or an analytics SDK. Read ML Kit’s privacy information and its Android data disclosures.

Pro purchases through Apple or Google Play

Where offered, LottoPrism Pro is an optional in-app purchase handled by Apple’s App Store on iOS/iPadOS or Google Play on Android. The store processes your payment and account information. LottoPrism does not receive your payment-card details or store-account password.

On iOS, the app uses Apple StoreKit transaction and entitlement information, including product and transaction identifiers and purchase or revocation status, to unlock and restore Pro. On Android, Google Play Billing supplies purchase information, including product identifiers, purchase tokens, signed transaction records, and purchase status. The app verifies the signed purchase on your device, stores a local signed record for offline access, and contacts Google Play to check ownership and acknowledge purchases. Neither version sends purchase records to a Refracted Forge server.

Apple and Google may make sales, transaction, and diagnostic reports available to us under their developer services and your sharing settings. Their systems also provide operating-system features and store services under their own policies. See Apple’s privacy policy, App Store privacy information, Apple Location Services privacy information, and Google’s privacy policy.

Lottery-data providers process requests under their policies: New York’s privacy policy and the Texas Lottery privacy statement. Links opened in your browser are governed by the destination’s policies.

4. Information you send to support

If you email support@refractedforge.com, we receive your email address, any name your email includes, the message and attachments you choose to send, and ordinary email metadata. We use this information to respond, troubleshoot problems, handle feedback and privacy requests, and maintain the correspondence needed to resolve your issue. Our email is provided through Zoho Mail; see Zoho’s privacy policy.

We cannot remotely inspect your local ledger. Please do not send passwords, payment details, unredacted ticket images, claim barcodes, or other information that is not needed for your request. If you voluntarily send a screenshot or image, it becomes part of the support correspondence we receive; the app’s no-upload behavior does not apply to email attachments you send yourself.

5. Website visits and cookies

Cloudflare hosts and delivers refractedforge.com. To deliver pages and protect the service, Cloudflare processes connection and request information, which can include IP address, requested URL, browser or device information, time, and security events. We may receive traffic summaries or security information through Cloudflare’s dashboard. See Cloudflare’s privacy policy.

We do not add advertising trackers, marketing cookies, analytics scripts, or a mailing-list form to this website. Cloudflare may use cookies or similar mechanisms for essential security functions. Email links open your own mail application; they do not automatically send a message or upload app data.

6. Why we use information and when it is disclosed

We use information to provide the features you request, respond to you, maintain purchases and support, diagnose issues, secure the website, and meet legal obligations. We do not sell personal information, use it for targeted advertising, or track your activity across other companies’ apps and websites.

Information may be processed by the service providers described above for their stated functions, by people authorized to handle support, or by professional advisers when necessary. We may disclose information we hold if required by law or reasonably necessary to protect users, investigate abuse, or establish or defend legal rights. These situations do not give us access to the ledger on your device.

Where applicable data-protection law requires a legal basis, we rely on providing the service you request, consent for optional processing where required, legitimate interests in support and security where those interests do not override your rights, and compliance with legal obligations. Device permissions can be withdrawn as explained below.

7. Retention, backups, and deletion

App data

Your saved ledger, photo copies, favorites, settings, and cached results remain in the app’s local storage unless removed or replaced. The iOS build also keeps a last-good ledger copy for recovery. There is no app-level cloud sync or export, and we do not hold a server backup of your tickets.

Deleting one ticket on iOS: swipe left on its list row or use the ticket’s delete button, then confirm. This removes the ticket from the active ledger and updates its notifications. Saved photo files are not automatically erased when a ticket is deleted, and the previous ledger can remain in the local recovery copy until a later save replaces it.

Deleting one ticket on Android: open the ticket, choose Delete ticket, and confirm. The app removes the saved ticket folder and its associated photo and updates notifications. On both platforms, favorites and cached drawing results are kept separately.

Deleting all local app data: on iOS/iPadOS, use Delete App in Settings. Removing the Home Screen icon or choosing Offload App keeps the data. On Android, uninstall LottoPrism or use its Clear storage / Clear data control in system app settings; clearing only the cache is not enough. Deleting local data does not delete original images in your photo library, copies held by photo-backup services, existing device backups, Apple or Google purchase records, or support emails.

Backups: iOS app data may be included in your configured iCloud or computer backup; manage those copies separately through Apple’s backup controls. Restoring a backup can restore app data. The Android build is configured to disable cloud backup of app data. Original images may still be backed up by your chosen photo service. We cannot delete copies stored on your device or in backups controlled by you or another provider.

Information held by us or providers

We keep support correspondence only as long as reasonably necessary to address the request, follow up on related issues, resolve disputes, and meet legal obligations. The period depends on the issue and any applicable recordkeeping requirement. You may request deletion sooner; we will delete information we no longer need and explain any applicable exception. Provider backup copies may persist through their normal retention cycles.

Apple, Google (including ML Kit and Google Play), lottery-data providers, Cloudflare, and email providers retain the information they process according to their own applicable policies and service settings. We do not set a single retention period for their independent records. Purchase-related records needed for entitlement, accounting, or legal requirements may remain after app deletion.

8. Your choices and privacy rights

  • Photos and camera: choose which images to import. Manage LottoPrism’s camera permission on iOS, or your camera app’s permissions on Android, through system Settings. Manual ticket entry is available on both platforms.
  • Location: on iOS, change LottoPrism’s access under Settings → Privacy & Security → Location Services. Android does not request location access. You can enter or edit the purchase jurisdiction on either platform.
  • Notifications: turn options off in LottoPrism’s Settings → Notifications or change system notification permissions. Your device also controls background refresh or background activity and battery restrictions.
  • Local information: review or edit saved tickets, remove tickets or favorites, and follow the deletion instructions above. No LottoPrism account exists to close.
  • Correspondence: choose whether to contact us and what to include. Email us to ask about or request deletion of information we hold.

Depending on where you live and applicable law, you may have rights to access, correct, delete, or obtain a copy of personal information; restrict or object to processing; withdraw consent; or complain to a data-protection authority. To make a request, email support@refractedforge.com. We may ask for information reasonably necessary to verify the request, without asking you to send your ticket ledger. We will respond as required by applicable law and explain any limitation. Withdrawing consent does not affect processing that was lawful before withdrawal.

9. Security and processing locations

LottoPrism stores saved ticket data and photos in private app storage on both platforms, with iOS file protection on Apple devices and Android’s app storage protections on Android devices. Its external lottery-data requests and this website use HTTPS; Google documents HTTPS protection for ML Kit metrics. Access to support information is limited to its support and operational purposes. No storage or transmission method is completely secure; protect your device, backups, and email account.

Local app data stays on your device except for backups you configure and information you choose to send. External service requests, Android diagnostic metrics, and support messages may be processed in the United States and other countries where the named providers operate, whose privacy laws may differ from those where you live. Where applicable law requires safeguards for transfers of information under our control, we use the relevant provider arrangements and legally required safeguards.

10. Children

LottoPrism is intended for adults who are legally old enough to purchase lottery tickets in their jurisdiction. It is not directed to children under 18. We do not knowingly collect children’s personal information through support or this website. If you believe a child has provided information to us, contact us so we can investigate and delete it as appropriate.

11. Changes to this policy

We will update this page and its “last updated” date when our practices change. If a change materially affects how personal information is used, we will provide additional notice or request consent where required. This policy will be reviewed as LottoPrism develops and before public release.

12. Contact us

Refracted Forge LLC
LottoPrism support and privacy inquiries
support@refractedforge.com

For help using the app, visit LottoPrism Support & Contact.