Your research. Clear data boundaries.

Maigret is provided by Jiuhong Deng (App Store seller: 就洪邓). This policy explains the app and maigretapp.com. For privacy questions or requests, email support@maigretapp.com.

Check your app version. The sections below describe the 3.1 release and the earlier 3.0 app separately. Controls described for 3.1 do not apply retroactively to installations of 3.0.

Public-source requests

Entering a username or another supported public identifier causes the app to request the relevant public websites. The identifier and ordinary network information, including your IP address, therefore reach those sites. Their privacy policies and access conditions apply. Maigret does not provide access to private accounts or bypass authentication. Opening an original result or sharing a report also sends information to the destination you choose.

Earlier version 3.0

Version 3.0 uses Firebase for app analytics and diagnostics and RevenueCat for subscription management. These services can process app or installation identifiers, app and device context, interactions, diagnostic information and, for purchase management, transaction and entitlement information. Apple processes payments. A statement that every part of using the app stays on your phone would not describe these network services accurately.

Provider information: Firebase privacy and security, RevenueCat privacy policy, and Apple privacy policy. The new 3.1 measurement controls below do not retroactively apply to 3.0 or delete information already processed by those providers. Contact us for questions about the version you use or a data request.

Local research data in 3.1

Scan history and encrypted saved cases are stored in the app’s local storage until you delete them. Optional search-session credentials use the device-only Keychain. Support provides separate controls for history, cases and credentials, plus Delete All Local App Data. Exported or shared files exist outside the app’s storage and must be deleted separately wherever you saved or sent them.

Optional local review reminders in 3.1

Review reminders are off unless you choose to enable one for a saved case. Notification permission is requested only after that action. Your device’s notification system stores the time you select and a local case reference; the notification uses a generic reminder without case names or search content. This reminder information is not sent to our servers. Tapping the notification opens the case for you to review; it does not start a scan or background monitoring. You can change or cancel the reminder from the case, including after a subscription expires. Deleting a case or all local app data also removes its pending and delivered reminders; the app reports an error if it cannot confirm that cleanup.

Optional usage measurement in 3.1

“Share usage diagnostics” is off until you enable it in Settings. When enabled and a measurement service is configured, the app sends a limited set of event categories, count ranges, app version and build, event times rounded to the minute, and Apple Ads attribution. It does not send search inputs, result or profile URLs, extracted profiles, case names, notes, reports, cookies, credentials, receipts or Apple-signed purchase payloads through this measurement channel. Firebase analytics and crash collection are not enabled in the 3.1 implementation.

A random app-only measurement ID groups activity for up to 45 days. A separate random session ID is created when the app returns to the foreground, and random event IDs prevent duplicates. These are pseudonymous identifiers: they can connect actions during that period. They are not IDFA or a device fingerprint. The server hashes the measurement and session identifiers with a service secret. We do not join these identifiers to purchase-service records or track activity across other companies’ apps or websites.

If you opt in, the app can request an Apple AdServices token and send it directly to Apple to resolve Apple Ads attribution. The token is temporary and is not stored in our event database. The measurement service receives only attribution status and, when Apple supplies them, campaign, ad group and keyword identifiers, country or region, conversion type and click/view classification. We do not receive the search text you entered in the App Store. Unavailable or invalid responses remain unknown. An explicit no-match response is recorded separately; neither establishes an organic install.

Measurement retention and your choice

The local measurement ID rotates after 45 days. The local queue holds at most 500 events and is excluded from backup. Turning the switch off cancels pending sending and attribution work and attempts to remove the local measurement queue. If local cleanup fails, the app displays an error and sharing remains off. Late callbacks cannot reactivate collection. Re-enabling it starts a new measurement ID.

Switching off cannot recall a request that was already received. Server events expire 45 days after the event and are deleted at the next scheduled hourly cleanup; cohort records older than 45 days are also removed once no retained events reference them. Deleting all local app data also disables measurement. The service intentionally has no email, name or purchase-token lookup for these event records, so we may not be able to identify an old measurement record from a support email. The retention limit still applies.

Purchases and rule downloads in 3.1

Apple handles payment details; Maigret does not receive your payment-card information. Verified StoreKit transactions on the device determine current Pro access, including eligible historical lifetime purchases. The 3.1 app does not send transaction signatures to Maigret’s server or request a server entitlement. Separately, Apple may send signed App Store server notifications to Maigret for purchase statistics and analysis. After verification, the service records notification type, product and transaction identifiers, relevant dates, environment and signature hashes; it does not use those records to unlock the app. These records are separate from optional usage measurement and are not subject to its 45-day limit. Contact us with a deletion request so we can explain which records can be removed and which must remain for applicable obligations.

The app may download signed public-site checking rules. Rule-download requests include normal network and cache information, not a scan history. Service security checks may transiently use a keyed hash of a network address to limit abuse. Cloudflare processes network requests to deliver the site and configured services. See Cloudflare’s privacy policy.

This website and support

This website uses Google Analytics to understand visits and improve its pages. Google Analytics uses cookies and processes information such as pages visited, referring websites, browser and device information, and website interactions. Website measurement is separate from the app’s optional usage diagnostics and its 45-day retention limit. You can restrict cookies in your browser or use Google’s Analytics opt-out browser add-on. See Google’s privacy policy for information about its processing.

Hosting processes normal connection information needed to serve pages. External links lead to services with their own policies. Emailing support sends us your email address, message and any attachments you choose to include. A diagnostic package is optional. Avoid sending search inputs, passwords, cookies, full receipts or complete research reports. We use support messages to respond and resolve the request, and can review deletion requests by email.

Requests and policy changes

Contact support@maigretapp.com to ask about access, correction or deletion of information associated with your support or purchase request. Tell us which app version and service your request concerns; do not send credentials. Rights and retention obligations depend on the applicable law. We will update this page when the product’s data practices change and keep the version boundaries explicit.