EN ES FR PT-BR HI 简中 繁中 RU AR TR
Privacy

Privacy Policy

How AsylumTracker handles account, subscription, community, AI analysis, EOIR case lookup and tracking, and public EOIR/USCIS data.

Last Updated: September 22, 2026

Overview

AsylumTracker provides immigration court, judge, USCIS asylum office, community, purchase, and AI-assisted analysis features. We limit personal data collection and use data only to operate, secure, and improve the app.

Information We Collect

We may process favorites, preferences, language, appearance, onboarding status, and AI usage counters stored locally on your device. If you sign in or use community features, we may process your account identifier, display name, avatar, applicant role, posts, comments, reports, blocks, and moderation records. If you submit attorney verification details, we may process information such as bar state and bar number.

When you purchase Premium, Pro, lifetime access, or AI analysis credits, Apple App Store or Google Play Billing provides entitlement and purchase status. We do not directly collect or store credit card numbers.

On iOS, our backend stores verified App Store transaction details—including transaction and product identifiers, purchase, expiration, and revocation status, price, currency, storefront, and a random per-install UUID used as the app account token. If you opt in to refund-information sharing, we also store your consent choice, policy version, and timestamp. We do not use the UUID for advertising or cross-app tracking.

If you turn on Judge Data Update Alerts, our server stores your device's push-notification token (an Apple Push Notification service token on iOS, or a Google Firebase Cloud Messaging token on Android) together with the judge code and court code of the case you track, solely to deliver those alerts when new monthly data is published. No name, A-Number, nationality, or tracked case record is uploaded with it. Turning the alerts off, or deleting your tracked case, removes the token and those codes from our server.

On Android, community posts can be translated on your device using Google ML Kit. The text you translate is processed on your device and is not sent to us or to Google, but ML Kit sends Google limited diagnostic and usage information—such as device model and OS version, app package and version, a per-installation identifier, performance metrics, and the languages involved—which Google uses to operate and improve ML Kit.

For Android AI-credit purchases, our backend stores your account-linked remaining balance, the Google Play order ID, and a one-way hash of the purchase token so credits can be restored and the same purchase cannot be granted twice. The raw purchase token is used transiently to verify the purchase with Google Play and is not stored.

If you request AI-powered case analysis, we process the case factors you choose to submit so that our backend can generate the analysis.

On Android, we send a randomly generated installation identifier and basic in-app interaction events, such as an upgrade screen being shown or a purchase completing, to our first-party backend to measure and improve the upgrade experience.

On Android, we send a one-way SHA-256 hash derived from a device identifier with AI analysis requests to enforce usage limits, prevent duplicate abuse, and protect the service. We do not receive the underlying device identifier.

Web Report Account and Sync

If you sign in to the web report builder, we store the client profiles and report workspace data you choose to save, which may include client names, case numbers, notes, report settings, and export history. This information is linked to your account so you can resume work and access it across sessions. It is processed through Supabase using encrypted connections and access controls, is not sold or used for advertising, and is retained until you delete the relevant records or your account, subject to limited security, fraud-prevention, and legal retention needs.

Individual EOIR Case Lookup and Tracking

When you submit or refresh an individual EOIR case lookup, your A-Number and nationality are sent directly from your device to the U.S. Department of Justice EOIR Automated Case Information System. These lookup inputs do not pass through AsylumTracker servers.

EOIR case lookup uses hCaptcha. hCaptcha processes your verification response and anti-abuse network and device signals, such as IP address and device or browser characteristics, to provide the challenge and help prevent automated abuse.

If you track a case on iOS, its tracked case record may include an A-Number, nationality, name, case status, asylum clock information, and hearing dates. Historical snapshots store normalized case state and do not duplicate the name or A-Number. This data is stored locally using iOS file protection and is not synced to AsylumTracker servers. The app marks its CaseTracking storage directory to be excluded from device backups, although iOS ultimately controls storage and backup behavior.

Information We Do Not Collect

We do not track precise location, access contacts, read photos, use the microphone, sell user data, or use third-party advertising SDKs.

How We Use Information

We use information to provide judge, court, USCIS asylum office, case lookup, community, purchase, and AI analysis features; save preferences; manage Premium, Pro, lifetime, and AI analysis entitlements; moderate community content; handle reports and blocks; and improve reliability.

Public Data Sources

Immigration data shown in the app comes from public datasets, including EOIR FOIA immigration court records, USCIS asylum office aggregate reports, and other public sources where noted in the app. These public statistical datasets are not personal user account data.

Storage and Third Parties

Authentication, community features, certain synced app data, and backend synchronization are processed through Supabase using encrypted connections and access controls. Purchases are processed by Apple App Store or Google Play Billing. AI analysis is processed through our backend when you request it. Individual EOIR lookups are sent to DOJ/EOIR, and hCaptcha processes verification and anti-abuse signals as described above.

User-Initiated Sharing

If you tap Share Redacted Summary, the app creates a redacted case summary and opens the iOS share sheet. Only the content you choose to send is provided to the app, service, or person you select, subject to that recipient's privacy practices. AsylumTracker does not automatically share tracked case records.

If you explicitly enable Share Refund Information with Apple, then after you request a refund from Apple we may tell Apple whether the purchase was delivered and whether free or trial content was available, to assist Apple's refund review. No tracked case record, A-Number, name, or nationality is shared. This setting is off by default and can be withdrawn at any time; after withdrawal, we stop sending future consumption information.

Account Deletion and Your Rights

You may delete your community account inside the app or request deletion by email. Instructions are available on the Account Deletion page. You may also contact us to request access, correction, deletion, data export, or analytics opt-out where applicable.

To access or delete consumption information already sent to Apple, submit a request directly to Apple at privacy.apple.com.

Government Affiliation and Legal Disclaimer

AsylumTracker is not affiliated with EOIR, USCIS, DHS, DOJ, or any other government agency. Information in AsylumTracker is for informational purposes only and is not legal advice. Consult a qualified immigration attorney about any individual case.

Changes

We may update this policy from time to time. The latest version will be posted on this page with the updated date.

Contact

For privacy-related questions, contact [email protected].