Privacy
ImmiCA Privacy Policy
Effective and last updated: October 29, 2026
Overview
ImmiCA is an iOS document-preparation app from Let’s Moyu. You do not need an ImmiCA account. Case information and documents are stored primarily on your device, but some optional features transmit selected information to remote services, and the app includes Google Mobile Ads. This policy describes those flows; it does not claim that all processing happens on-device or that no information is transmitted.
Case information and documents on your device
Answers, profile details, case progress, selected documents, generated reference PDFs, and package files are kept in the app’s local Application Support storage. Document assets use iOS file protection. ImmiCA does not require an account and does not operate a cloud case database, case synchronization, cloud backup, or case migration service.
Apple device backups and iCloud settings are separate from an ImmiCA-operated backup service. Depending on your device and backup settings, iOS may handle app data under Apple’s backup services. Let’s Moyu cannot restore a case from an ImmiCA server because no such case backup is provided.
For a camera scan, the app creates a processed image copy for use in the case after you confirm it. You may also choose images or files through iOS pickers. The app only uses the items you provide to the workflow.
Optional remote document recognition and organization
If you choose an AI-assisted recognition action, the selected document image or images are sent over HTTPS to an ImmiCA Cloudflare Worker. Depending on the workflow, this can include a selected passport image, both sides of a PR card, or a selected Canadian status-document image, along with document/workflow and language hints. The app sends the image content selected for recognition, not an automatic upload of every file in your case. You review and correct any returned suggestions.
An optional address-history organization action sends the narrative you submit, the selected language, and the required start and end dates. That request also carries a case identifier and an entitlement token so the service can authorize the feature. Do not use this feature unless you are comfortable sending that narrative for remote processing.
The Worker validates requests and sends the selected content to OpenAI’s Chat Completions API using the gpt-4o-mini model. The Worker does not maintain an ImmiCA case database or document bucket; it handles request content for processing and returns results to the app. OpenAI’s API data handling applies to content sent to OpenAI.
Cloudflare and OpenAI logs and retention
The production Worker configuration enables persistent structured logs with 100% head sampling and disables invocation logs. The Worker code logs operational fields such as request ID, route, success or failure stage, status, whether OpenAI was called, and an observation count. It does not intentionally write image bytes, filenames, address-history text, or extracted field values to those logs. No Worker Logpush destination is configured in the Worker configuration we reviewed.
Cloudflare’s published Workers Logs retention is 3 days on Workers Free and 7 days on Workers Paid. We have not verified the Cloudflare account plan or whether separate account-level log exports are enabled, so we cannot state which period or any separate export policy applies to this account.
OpenAI states that API data is not used to train models by default unless a customer opts in. Its standard abuse-monitoring logs may contain prompts, responses, and derived metadata and are retained for up to 30 days by default; eligible Zero Data Retention or Modified Abuse Monitoring controls can change this. We have not verified the ImmiCA API project’s retention-control or opt-in settings. Do not assume a shorter or zero-retention arrangement for ImmiCA.
References: Cloudflare Workers Logs and OpenAI API data controls.
Camera, photos, files, and speech permissions
Camera access is requested when you choose to scan a document. When you import through an iOS photo or file picker, you choose the items to provide to ImmiCA; the app does not need continuous access to your whole photo library for that selection.
Optional address dictation requests microphone and speech-recognition access. ImmiCA asks Apple’s Speech framework to use on-device recognition when the selected recognizer supports it. When on-device recognition is unavailable, Apple may process captured speech on its servers. The raw speech audio is not sent to the ImmiCA Worker; a transcript can be used in the local address form. Apple’s Speech recognition documentation explains this service.
Advertising, consent, and tracking
ImmiCA includes Google Mobile Ads interstitial advertising and Google’s User Messaging Platform (UMP). The app requests consent information, provides a privacy-options flow when required by UMP, and requests ads only when UMP reports that ads may be requested. Google says its iOS Mobile Ads SDK may collect IP address, device identifiers, advertising data, app interactions, performance data, and diagnostic information. Which data is processed can depend on SDK behavior, region, consent, and ad configuration.
In the iOS release configuration reviewed, we found no NSUserTrackingUsageDescription and no app-side App Tracking Transparency authorization request. This means the reviewed build does not present an ATT prompt; it is not a claim that the advertising SDK collects no data or performs no measurement. The final SDK configuration and App Store privacy disclosures must accurately describe the SDK’s behavior.
References: Google’s iOS Mobile Ads data disclosure, AdMob privacy guidance, and Apple’s App Tracking Transparency documentation.
Firebase Analytics and crash reporting
In the iOS release candidate reviewed, GoogleService-Info.plist is not bundled, and the app configures Firebase only when that file is present. Firebase Analytics code and linked frameworks remain in the project, but Analytics is not configured in that candidate. No Firebase Crashlytics integration was found. If Firebase is enabled in a later release, its event collection must be reflected in the applicable privacy disclosures. See Firebase privacy and security information.
Purchases
For the iOS release, in-app purchases are handled by Apple through StoreKit. Apple processes the payment; ImmiCA does not receive your payment-card number. The app receives purchase transaction information and stores a case-bound consumable entitlement locally. ImmiCA does not use Google Play billing in this iOS release.
There is no ImmiCA account or server-side entitlement recovery service. A case and its consumable entitlement may be lost if you delete the case or remove and reinstall the app. Apple’s Privacy Policy and applicable App Store terms cover Apple’s processing.
Generated documents, exports, and deletion
Prepared PDF references and ZIP packages are created in app storage and are not sent to IRCC by ImmiCA. If you export or share a package, the file goes to the destination you select and is then handled by that destination and its provider. You are responsible for protecting and deleting exported copies.
You can remove a case and its associated local data using the in-app case deletion control. If the device cannot remove some files, the app can leave deletion pending and ask you to retry. Deleting the app also removes its local app data, subject to any Apple backup you control and any copies you exported. ImmiCA cannot recover deleted or reinstalled local cases or consumable entitlements.
Diagnostics and support messages
The app may show local error and workflow status information. For remote-recognition diagnostics, the Worker logs the limited operational fields described above. Google Mobile Ads may collect SDK diagnostics and performance information. If you email support, Let’s Moyu receives the email address and whatever details you choose to include; please do not attach unredacted immigration documents.
Third-party privacy information
Contact and related pages
Questions about this policy can be sent to [email protected]. See the ImmiCA product page, Support, and Terms.