# Privacy Policy for Moose Diag
Effective date: 2026-09-26
Moose Diag is an Android vehicle diagnostic and reference application. This Privacy Policy explains what information Moose Diag uses, why it is used, where it is stored, who may receive it, how long it is kept, and what choices you have.
Moose Diag is published by Diki Software Solutions in Bulgaria. You can contact us about privacy at dikisoftwaresolutions@gmail.com.
This policy applies to the Android app with package name `com.moosediag.app`.
## Summary
Moose Diag does not require an account. We do not ask for your real name, email address, phone number, contacts, photos, camera access, microphone access, SMS messages, call logs, payment information, health information, or precise GPS location.
The app stores vehicle profile choices, downloaded reference databases, profile history, cached catalogue/service results, diagnostic trouble code searches, and optional application logs locally on your device. Moose Diag does not operate its own user account server or cloud database for this information.
Moose Diag uses Google Play services, Google Play Asset Delivery, a Moose Diag database-download service hosted through Cloudflare Workers and R2, and Google AdMob. AdMob may use mediated advertising providers, including Meta Audience Network and InMobi, to fill the same advertising placements. These providers may process information such as IP address, approximate location inferred from IP address, app and ad interactions, diagnostics, advertising identifiers, device identifiers, and app information for advertising, measurement, analytics, fraud prevention, security, compliance, and service delivery.
## Who We Are
For this policy, "Moose Diag", "the app", "we", "us", and "our" mean the Moose Diag Android application and its developer.
Developer name: Diki Software Solutions
Country: Bulgaria
Privacy contact: dikisoftwaresolutions@gmail.com
Moose Diag is an independent application. It is intended for vehicle reference, parts catalogue, service information, and diagnostic reference workflows.
## Information Stored On Your Device
Moose Diag stores the information needed for the app to work. This may include selected vehicle profile values, vehicle profile history, cached table-of-contents results, cached parts catalogue results, cached service information results, downloaded database packs, diagram database packs, DTC search state, app settings, and optional application logs.
If you enter or decode a VIN, select a vehicle configuration, browse parts, open service documents, search DTCs, or download optional database packs, that activity may be reflected in local app state, local cache, or local logs. This information is used to make the app faster, restore prior selections, avoid repeated database queries, and help troubleshoot problems.
Application logging is intended for diagnostics. In release versions, logging is off by default where the app provides that setting. If you enable logs, they may include technical events, database loading status, selected profile identifiers, document identifiers, part identifiers, DTC identifiers, errors, and timing information. Logs remain on your device unless you choose to export, copy, or share them.
Live-parameter CSV captures are stored in the shared `/sdcard/MooseDiag` folder. Files in this shared folder can remain after Moose Diag is uninstalled and must be deleted separately if you no longer want them.
You can remove private local Moose Diag data by clearing the app's storage in Android settings or uninstalling the app. If you imported database files or created CSV files or other exports in `/sdcard/MooseDiag`, you must delete those shared files yourself.
## Downloaded Reference Databases
Moose Diag uses local SQLite database files for vehicle data, parts catalogue data, diagnostic reference data, service information, repair information, and optional diagram data. Some databases may be delivered with the app and some may be downloaded later through Google Play Asset Delivery.
These database files are reference data used by the app. They are stored on the device so the app can work offline and so large optional content, such as diagram data, does not have to be included in the base download. Depending on the app version and migration state, database content may be delivered through Google Play or downloaded in signed chunks from the Moose Diag database-download service hosted through Cloudflare Workers and R2.
Google Play may process technical information needed to install the app, deliver asset packs, resume downloads, verify integrity, and manage updates.
When Moose Diag contacts the database-download service, Cloudflare and the service may receive ordinary network and delivery information such as your IP address, request time, requested manifest or chunk path, response status, user agent containing the Moose Diag version, and security or abuse-prevention information. The request does not include your VIN, diagnostic readings, vehicle profile history, application logs, or CSV contents. Cloudflare processes this information under its own privacy terms: https://www.cloudflare.com/privacypolicy/
## Ads
Moose Diag uses Google AdMob to show anchored banner ads, an interstitial after an eligible DTC readout completes, and an explicitly selected rewarded ad that grants a temporary ad-free period. After you finish and explicitly close eligible fullscreen EPC diagram or service-document content, the app may show a frequency-capped interstitial at that completed-content break. The requested content opens immediately; an interstitial is not shown before it, is not shown on every close, and is not triggered by Android Back or document-to-document navigation. AdMob mediation may ask Meta Audience Network or InMobi to supply an ad for the configured banner, interstitial, or rewarded placement. The app does not send vehicle diagnostic data, VINs, locally stored database contents, CSV captures, or application logs to these advertising providers.
According to Google's AdMob disclosure documentation, the Google Mobile Ads SDK may automatically collect and share information such as IP address, approximate location inferred from IP address, app interactions, app launch and ad interaction events, diagnostic information, device or advertising identifiers, app set identifiers, and account-related identifiers where applicable.
Google and mediated advertising providers may use advertising-related information for advertising or marketing, measurement, analytics, fraud prevention, security, compliance, and service operation. Their SDKs and ad content may use advertising identifiers, app set identifiers, IP addresses, cookies or comparable local storage, pixels or web beacons, and similar technologies to provide and measure ads, apply privacy choices, and prevent abuse. Google states that data collected by the Google Mobile Ads SDK is encrypted in transit using TLS. Each mediated provider processes information under its own privacy terms.
Where required, Moose Diag uses Google's User Messaging Platform to request and store advertising privacy choices before the app initializes advertising or requests an ad. Consent and opt-out signals may be made available to Google and configured mediation partners using applicable industry consent strings. The available choices and whether a privacy-options entry point is required depend on your location and the messages configured in AdMob. Withdrawing consent prevents new ad requests when the consent platform reports that ads may no longer be requested, but it does not delete information already processed by an advertising provider under its retention policy.
You can use Android and Google ad privacy controls to reset or delete your advertising ID, limit ad personalization where available, and manage consent choices where those controls are presented.
For more information about Google's privacy practices, see:
Google Privacy Policy: https://policies.google.com/privacy
Google AdMob: https://admob.google.com/
Google AdMob data disclosure information: https://developers.google.com/admob/android/privacy/play-data-disclosure
How Google uses information from sites or apps that use Google services: https://policies.google.com/technologies/partner-sites
Meta Privacy Policy: https://www.facebook.com/privacy/policy/
InMobi Privacy Policy: https://advertising.inmobi.com/privacy-policy
## Network Access
Moose Diag may use network access for Google Play Asset Delivery, direct database manifest and chunk downloads, Google Play services, AdMob ads and mediation, app integrity or delivery features, and related platform services. The app does not require a Moose Diag account and does not upload your VIN, diagnostic values, local vehicle profile history, local parts browsing history, local service document cache, CSV captures, or local application logs to the Moose Diag database-download service.
If you choose to share logs, screenshots, copied text, exported files, or other information with us or with another party, that sharing is initiated by you.
## Permissions
Moose Diag requests permissions needed for app operation, vehicle-adapter access, database delivery, network access, ads, Android system requirements, and shared file storage. On Android 11 and later, Moose Diag requests all-files access so it can read imported database files and create and manage live-parameter CSV captures at the exact shared path `/sdcard/MooseDiag`. On older supported Android versions, it requests the corresponding external-storage permission. This storage access is not used to upload unrelated files or provide files to advertising SDKs.
Moose Diag does not request access to contacts, photos, videos, microphone, camera, SMS messages, call logs, calendar, precise GPS location, or payment information.
Depending on the Android version and build type, local database files may be stored in app-specific storage or imported from a user-accessible folder. Android may restrict direct access to app-specific folders. If the app provides an import, download, or database status feature, it is used to help place or verify the required local database files.
## Sharing
Moose Diag shares advertising-related and service-delivery information with Google AdMob, Google Play, Cloudflare, and related service providers as described above. When mediation is enabled for an ad request, Google may share the request with Meta Audience Network or InMobi, and the selected provider may process advertising-related device, app, network, interaction, and diagnostic information.
We may disclose information if required by law, to comply with a valid legal process, to protect rights and safety, to prevent fraud or abuse, or to enforce applicable terms and policies.
We do not sell personal information for money. Advertising-related disclosure to Google, Meta, or InMobi may be treated as a "sale," "sharing," or targeted advertising under some privacy laws even when no money is exchanged for the information. Where required, the app and the providers offer consent or opt-out choices as described above. We do not operate a Moose Diag user account database or user profile server.
## Security
Moose Diag stores app data locally on your device using Android app storage and local database files. Google service communication, including AdMob communication, is handled by Google's SDKs and platform services.
No app, device, storage system, or network transmission can be guaranteed to be perfectly secure. You should protect your device with Android security features and avoid sharing exported logs or screenshots if they contain information you consider sensitive.
## Retention And Deletion
Local app data remains on your device until you clear app storage, uninstall the app, delete imported files, or use an in-app delete or clear feature where available.
Application logs remain on your device until they are cleared by you, cleared by the app, or removed by clearing app storage or uninstalling the app. CSV captures and other files written to `/sdcard/MooseDiag` remain until you delete them; uninstalling Moose Diag does not necessarily remove them.
Google, Meta, InMobi, Cloudflare, and their services may retain advertising, delivery, diagnostics, and security-related data according to their own policies and legal obligations.
Because Moose Diag does not require accounts and does not operate its own cloud user database, we usually cannot access or delete local app data from our side. You can delete local data directly on your device.
## Your Choices
You can choose which vehicle profile to select, whether to download optional database packs, whether to enable application logging, whether to clear logs, and whether to share exported logs or screenshots.
You can clear app data or uninstall Moose Diag to remove local app data stored by Android for the app.
You can use Android permission settings, Android app storage settings, Google Play settings, and Google ad privacy controls to manage platform-level choices.
## Children
Moose Diag is not directed to children. The app is intended for vehicle owners, technicians, enthusiasts, and other users who need vehicle reference or diagnostic information.
We do not knowingly collect personal information from children through a Moose Diag account or Moose Diag server. If you believe a child has provided personal information to us, contact us at dikisoftwaresolutions@gmail.com.
## International Users And Privacy Rights
Depending on where you live, you may have privacy rights such as access, correction, deletion, restriction, objection, portability, or the right to withdraw consent where consent applies.
For local data stored only on your device, the practical way to access or delete it is through the app, Android app settings, exported files, or uninstalling the app.
For advertising-related information handled by Google, Meta, or InMobi, use the provider privacy controls and policies linked above. Where required, Moose Diag provides an in-app privacy choices entry point backed by Google's User Messaging Platform.
You can contact us at dikisoftwaresolutions@gmail.com with privacy questions or requests. Because Moose Diag does not require accounts, we may need enough information to understand and respond to your request, and in many cases we may not be able to identify local app data that exists only on your device.
## Changes To This Policy
We may update this Privacy Policy when Moose Diag changes, when data practices change, when third-party SDK behavior changes, or when legal or platform requirements change.
The effective date at the top shows when this policy was last updated.
## Contact
If you have questions about this Privacy Policy, contact:
Diki Software Solutions
Bulgaria
dikisoftwaresolutions@gmail.com