1. Who operates the services
The website and Eureka DMV are operated by Eureka Apps. Public business or contact details: info@eureka.top.
In this policy, “we,” “us,” and “our” refer to that operator. Eureka Apps and Eureka DMV are service and product names.
2. Website information
The website has no account system, contact form, newsletter, advertising, or analytics. We do not add analytics or advertising cookies.
The website itself does not set cookies.
When you request a page, Railway and network providers receive ordinary connection and security data needed to deliver and protect the site. This may include an IP address, requested URL, host name, browser or user-agent information, timestamps, and security events.
3. Study information stored on your device
Eureka DMV does not require a learner account. The app stores onboarding and jurisdiction choices, settings, practice attempts, answers, results, reading confirmations, and cached study content locally on the device.
We do not upload or sync practice attempts, answers, results, or reading confirmations to Eureka Apps services. A jurisdiction-specific reset removes that jurisdiction’s attempts and reading confirmations, but it does not remove settings, other jurisdictions, cached content, purchase identity, saved report drafts, or outbox records. Operating-system device backups may still include local app information.
4. Content delivery
The app requests catalogs, releases, study content, and media from our content service hosted on Railway. Those requests expose ordinary connection information to Railway and network providers. We do not attach a Eureka Apps learner account to those requests.
5. Purchases and subscriptions
Apple processes App Store payments, billing details, and the Apple account used for a purchase. We do not receive or store payment-card details.
RevenueCat helps validate purchases and provide subscription entitlements. The app is configured without a Eureka Apps sign-in, and RevenueCat creates a random anonymous app user ID that is cached on the device. RevenueCat processes App Store receipt and transaction data, purchase history, and entitlement information for purchase validation, app functionality, and its subscription service. Its SDK requests also include default technical metadata such as the operating-system and platform version, generic device model, app version, build and bundle identifier, locale and storefront, and a vendor-scoped Apple device identifier (IDFV) where available. Each request also exposes the source IP address and ordinary connection and security data to RevenueCat and network providers. The launch configuration disables automatic device-identifier collection for attribution integrations; that setting does not suppress the default SDK request metadata just listed.
Read the Apple Privacy Policy and RevenueCat Privacy Policy for their practices.
6. Reports you choose to send
You can report a study-content issue or app problem. A report may include:
- the chosen report category, your report text, and an optional reply email;
- a random client-generated submission identifier used to submit and retry the report safely;
- the product, jurisdiction, content, release, revision, or PDF page involved;
- content and interface language;
- app and build version, operating-system version, generic device model, originating screen, and a safe error code where available.
The report flow is designed to exclude study history, screenshots, attachments, secrets, and persistent device fingerprinting. Do not include passwords, payment details, government identifiers, or information you do not want us to receive in free text.
A saved report or outbox record is stored locally until the server acknowledges it, you remove it where the app allows, or the app’s data is removed. The server stores the submitted fields, submission and receipt identifiers, a normalized-request hash, receipt time, workflow status, routing and resolution information, and relevant content-reference snapshots. Report versions may also be stored for operational history.
The report endpoint does not place the raw network address in the report record. It creates a keyed network digest in a separate rate-limit record with an expiry value. Cleanup is periodic, so the expiry value is not a promise of physical deletion at an exact minute. Railway and network providers may separately process connection and security data.
7. Support and privacy emails
If you choose to email us, we receive the sender and recipient addresses, subject, message, standard email headers, and any attachments you add. We use that information to respond, provide support, handle privacy requests, and operate the services.
Your email provider and the provider that receives our mail process the message for delivery, security, and storage. Do not email passwords, payment-card details, government identifiers, or other information that is not needed for your request.
8. Optional analytics and advertising
AppsFlyer and Amplitude are excluded from the launch version. The launch configuration does not include advertising, cross-app tracking, or optional product-analytics SDKs. User-initiated reports and RevenueCat purchase processing are separate from advertising analytics.
9. Service providers and disclosure
We use Apple for App Store distribution and payments, RevenueCat for anonymous purchase identity and entitlements, and Railway for website and content-service hosting. These providers process information for their respective services under their own terms and privacy commitments.
We confirm that third parties receiving user data from us or processing it on our behalf will provide the same or equal protection described in this policy and required by applicable App Store rules.
We do not sell personal information or use it for targeted advertising. We may disclose information when required by applicable law, to protect the services, or to respond to a valid legal request.
Railway’s practices are described in its Privacy Policy.
10. Retention and deletion
Server-side report retention starts when the service receives the report. The retention period is until it is no longer reasonably needed to investigate, respond to, or document the issue. Exceptions: longer retention may apply for security, fraud prevention, disputes, or legal obligations.
Report backups: Deleted report data may remain in routine backups until those backups are overwritten through normal rotation.. Report versions: Stored report versions follow the same retention and deletion approach as the underlying report..
Report access, deletion, and privacy requests: Email support@eureka.top. Eureka Apps reviews and handles verifiable requests subject to legal and operational limits.. Responsible role: Eureka Apps support.
Support correspondence retention starts when the support mailbox receives the message. The retention period is until it is no longer reasonably needed to respond, provide support, or resolve the request. Exceptions: longer retention may apply for security, fraud prevention, disputes, or legal obligations. Backups: Deleted correspondence may remain in routine backups until those backups are overwritten through normal rotation..
Support correspondence access, deletion, and privacy requests: Email support@eureka.top. Eureka Apps reviews and handles verifiable requests subject to legal and operational limits.. Responsible role: Eureka Apps support.
Local app information remains on the device until it is reset, removed by the app or operating system, or the app’s data is deleted, subject to device backup behavior.
11. Privacy requests
To ask about report or support information, request access or deletion, or raise a privacy concern, use support@eureka.top. Include the optional reply email used with a report and details you remember, such as the approximate submission time, jurisdiction, content, release, revision, or page. The app does not currently display a report receipt. Because there is no learner account, a report sent without a reply email may not be reliably identifiable. Do not send identity documents unless we specifically explain why they are needed.
Privacy rights differ by location. We will handle verified requests as required by applicable law.
12. Younger users
Age and minors approach: No special age threshold is stated; use must comply with applicable law and the App Store age rating..
Eureka DMV is a driving-knowledge study tool and does not require a learner profile. Reports accept free text and an optional email only when a user chooses to provide them. Do not submit personal information about another person without authority.
13. Changes to this policy
We may update this policy when the services, providers, or legal requirements change. We will post the revised policy here and update its effective date.
14. Contact
Operator: Eureka Apps
Public business or contact details: info@eureka.top
Privacy contact: support@eureka.top