Privacy Policy

MeCode is designed to keep your data on your device and to use as little of it as possible. This policy explains which permissions MeCode uses, where your data is stored, and when the app goes online.

What we don’t do

• You can use MeCode without signing up or signing in. We don’t create accounts or collect personally identifiable information.
• MeCode includes no advertising, third-party analytics, or tracking SDKs. We don’t sell or share personal data, and we don’t track you across apps.
• We don’t run servers that store your data. Your codes, history, favorites, collections, tags, and scan sessions are never uploaded to us.

How MeCode uses permissions

• Camera: MeCode uses the camera to scan codes. The camera is active only while the scan screen is open. Frames are recognized on device and are never recorded or saved.
• Photo library (add only): MeCode requires access to your photo library to save generated code images. It writes only when you tap Save and never reads other photos in your library.
• Recognize from photos: You pick photos with the system photo picker, so MeCode receives only the photos you select and needs no photo library read permission. Photos are recognized on device and never uploaded.
• Face ID / Touch ID: MeCode uses Face ID to secure your saved code data, for App Lock and history protection. The system performs authentication; MeCode receives only the result and never has access to biometric data.
• Files and sharing: PDF recognition uses the system file picker or share sheet and reads only the file you choose or share. The Share Extension handles only the text, links, images, or PDFs you share to MeCode.

You can revoke any permission in Settings at any time. The related feature stops working; everything else keeps working.

Data storage

• On device: Code assets, history, favorites, collections, tags, scan sessions, style templates, and logos are stored in MeCode’s App Group container, shared by the app, the Share Extension, and widgets, and protected by iOS Data Protection.
• iCloud sync: After you unlock Pro and turn on iCloud sync, code assets, favorite status, collections, tags, and scan sessions sync to your own private iCloud database. Only devices signed in to the same Apple Account can access it; we cannot read it.
• Spotlight: When Spotlight search is on, history records that are not deleted are added to the on-device system search index and never uploaded. Turning the setting off, turning on history protection, or deleting records removes the related index entries.
• Widgets: Home Screen and Lock Screen widgets read only snapshots in the on-device shared container.
• Exports: Exported code images and data files are written to the system temporary directory and handed to the share sheet; you decide where they go.
• Secrets: Scan Hook HMAC secrets are stored in the on-device Keychain and are never included in data exports.

When MeCode goes online

Scanning, recognition, generation, and management all happen on device. MeCode connects to the network only in these cases:

1. iCloud sync: When turned on, data syncs to your private iCloud database through Apple CloudKit.
2. In-app purchases: Buying or restoring Pro goes through the App Store. Apple processes payment information; we never receive it.
3. Scan Hooks: Off by default. Only after you create and enable a Hook does MeCode send saved scan results to the address you entered. The request is built from your template and never passes through our servers.
4. Opening links: MeCode visits a website only when you tap to open a scanned link.
5. Help and policy pages: MeCode loads pages from the MeCode website only when you open the user guide, privacy policy, or terms of use.

Logs

Diagnostic logs are written only to the on-device system log for troubleshooting. Logs never include code content, links, Hook addresses, or request bodies.

Contact us

If you have questions about this privacy policy, contact us from More > Feedback in MeCode, or email mecode@yycc.dev.