Privacy Policy

1. Data we do not collect

The app does not ask for your name, phone number, or payment information, and does not read contacts, precise location, photos, or device advertising identifiers. A full link you choose to report may itself contain personal information; review it before sending or share only its domain. Camera frames are used only to recognize QR codes on your device and never leave the device.

2. Data stored on your device

To provide scan history and preferences, the app stores the following information locally on your device:

• scanned QR code content, scan times, and routing outcomes;
• settings such as automatic routing and the default opening method; and
• downloaded routing rules and cached app names, webpage titles, and icons.

This information is not synchronized to the developer's servers. You can delete history and caches inside the app. Uninstalling the app also removes its locally stored data.

3. Network access

Lenskip's only developer-operated backend distributes cryptographically signed URL-routing rules and a small number of destination icons. Rule-distribution requests do not include scanned content, scan history, or personal information stored on your device. The hosting provider may process standard connection information, such as an IP address, for delivery and security purposes; the backend does not record IP addresses.

Depending on the features you enable, the app may also communicate directly with:

• the scanned link's website and Apple's public lookup services to determine which app can handle a domain; only the domain or app identifier is used for this lookup, and the complete link is not sent to the developer's backend;
• the webpage represented by a scanned link to retrieve its title and site icon; the destination website receives a normal web request; and
• a third-party app or browser that you choose to open. Those services handle information under their own privacy policies.

4. Routing reports

When a QR code opens in the wrong place, you can submit a report from your scan history telling us where it should have opened. This is the only feature that sends scanned content to the developer, and it happens only when you personally choose to send each one — no other scan records are automatically reported. If delivery fails, a report you submitted is queued locally and retried when the app launches or returns to the foreground, for up to seven days.

Before sending, the app shows you the full address it is about to send, verbatim. You can choose to send only its domain. A report contains:

• the link you are reporting (the full address, or just the domain if you chose that);
• the destination you picked — WeChat, Alipay, the code's own app, or staying in the browser — and, if you picked the code's own app, an app name you may optionally type;
• what the routing actually did: which rule matched, how the app tried to open it, the outcome, and whether the destination app is installed; and
• the routing-rules version, the app version, and your major iOS version.

A report contains no device or installation identifier, and nothing else from your scan history. A full link may itself contain account, order, or other personal identifiers, so reports are not guaranteed to be anonymous. We do not associate reports to identify users, build profiles, or reconstruct their scan history.

Reports are used only to improve URL-routing rules. They are not used for advertising, cross-app tracking, or profiling, and are neither shared nor sold. Submitting one does not change how your device routes codes — it takes effect in a later rules update.

To withdraw a report you have submitted, contact us at the address in section 8.

5. Camera permission

The app requires camera permission to scan QR codes in real time. If you deny permission, camera scanning will be unavailable. Camera frames are neither uploaded nor saved.

6. Children's privacy

The app is not directed to children and does not knowingly collect personal information from children.

7. Changes to this policy

If the app's data practices change, we will update this page and the date shown above. Material changes will be disclosed where appropriate.

8. Contact us

If you have questions about this policy, email thoamsy2@gmail.com.