Your research. Clear data boundaries.

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

Check your app version. Version 3.0 is currently available on the App Store. Version 3.1 is in development. The optional measurement switch, encrypted cases and other controls described under “3.1” are planned for that version; they are not controls available in 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.

Current 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 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. An unavailable or unmatched response is kept as unknown rather than treated as 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 removes the local measurement queue. 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. StoreKit determines current purchase access. If the separate purchase-verification service is configured, it receives signed transaction information and a random purchase token to verify entitlements, restores, expiry and refunds. It stores transaction identifiers, product, dates, environment, entitlement status and payload hashes. These records are separate from optional usage measurement and are not subject to its 45-day limit. They support access recovery and purchase disputes; contact us with a deletion request so we can explain which records can be removed and which must remain for the purchase service or 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 static website does not add advertising pixels, analytics scripts or tracking cookies. Hosting still 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 maigret@txyou.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.