Checkame Privacy Policy

1. Where things are stored

Screenshots, plans, numbers and memos (such as receipts) that Checkame reads are stored only on your iPhone and in your own iCloud (private database). iCloud sync can be turned off in Settings. We cannot see any of it (except what is sent under section 3).

2. Permissions

• Photos: used only to read screenshots and ticket photos.
• Calendar and Reminders: used to write the plans and deadlines you register and to check for duplicates.
• Notifications: used to remind you the day before and on the day of a deadline.
• Face ID / Touch ID (optional): used only to unlock the app when you turn on App lock in Settings. iOS handles the biometric data itself; the app and we never receive it.

You can use Checkame from the share sheet without granting any of these.

3. Improving recognition (what we store on our server)

To improve the reading rules, when the confirm card reads a screenshot, when you check it with AI, and when you register or skip, the app sends the following to our server (Google Cloud), where it is stored.

• The screenshot that was read. The following are blacked out on your iPhone before sending: names that carry an honorific or label (such as 様, MR, "Name", "Passenger"), phone numbers, email addresses, postal codes, card numbers, lines labeled as an address, and barcodes/QR codes in the image. Because this is done by automatically recognizing text, it is done as far as possible; names or addresses without an honorific or label may remain.
• The recognized text (with personal information masked as far as possible), the reading result (dates, type, place, amounts, booking numbers, including the results of "Check again with AI"), the values you corrected, actions such as register or skip, the app version and display language.
• A random number generated by the app per installation. No account, device identifier or name is included, so we cannot tell whose data it is.

Not sent: account or device identifiers, other photos in your library, calendar contents, location. Names and contact details are masked as far as possible before sending, as described above. Booking numbers, dates, places and amounts are not masked and remain as learning material. The data is used only to improve the reading rules and check quality, and is never sold or passed on to third parties. You can turn this off any time with "Help improve recognition" in Settings; when off, nothing is sent. To request deletion, contact support.

When you correct a date, small learning fragments (date wording, type, before/after values) are also received via Apple iCloud (public database) as before. Because of how iCloud works, these records automatically carry a creator ID assigned by Apple (one per iCloud account). We cannot learn your name or email address from this ID. The same setting turns them off.

3b. Cloud re-read (optional) and trip suggestions (optional)

When you tap "Check again with AI" on the confirm card, or—while "Double-check with AI automatically" in Settings is on (on by default; you can turn it off anytime)—each time a confirm card opens, that single image is sent to our reading server (on Google Cloud) and read with Google's generative AI (Vertex AI). The reading server does not store the image; it returns the result to your iPhone. The image is not used for AI training and we do not store it. Caching is turned off on Google's side (Google may keep logs for a limited period for abuse monitoring under Google Cloud's terms). When "Help improve recognition" is on, the AI reading result is also stored as section 3 data (with the image masked as far as possible). With the automatic check off, nothing is sent unless you tap.

(Not currently offered.) Only if you turn on "Trip suggestions" in Settings, your trip's destination, dates and party size are sent to the same server to return information near your hotel. Screenshots, booking numbers and names are never sent, and the server stores nothing.

4. Google integration (optional)

Only if you sign in to Google in MY and turn on "Save deadlines to Google Tasks", the title and date of a deadline you register are sent to your own Google account. Sign-in credentials are stored only on this iPhone and deleted when you sign out. Saving to a Google Calendar added to your iPhone goes through the iOS Calendar feature, with no direct communication with Google.

How we handle Google user data: When you sign in to Google, the app (1) reads your email address to show which account is signed in, (2) reads the names of your Google Tasks lists so you can choose where to save, and the tasks due on the same day so the same deadline is not added twice, and (3) creates tasks in Google Tasks for the deadlines you register. This data and your sign-in information are stored only on your device and are never sent to our servers. We do not share or sell it to third parties, and we do not use it for advertising or to train AI. Signing out in MY deletes it from the device. You can revoke access at any time in your Google Account settings. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

5. Sign in with Apple (optional)

This only displays your name on this iPhone. Signing in does not change where data is stored and nothing is sent to us.

5b. Kept only on this iPhone

• Favorite places (home and work address): stored only on this iPhone and used only in the URL handed to the iOS Maps app when you open directions. Never sent to us. When you search for an address or pick one on the map, Apple Maps services receive what you type or the map position (not us).
• App lock PIN: stored only in this iPhone's keychain and not synced to iCloud.

5c. File backup

The file you export from MY › Backup / Restore (events, trips, memos and corrections) leaves your iPhone only when you choose where to share it. We do not receive it. Screenshot images are not included.

5d. The Android version

• Where data is stored: events, numbers and memos are stored only on your Android device. There is no sync equivalent to iCloud, and the app is excluded from Android Auto Backup (Google Drive). To move to a new device, use the file in MY › Backup / Restore.
• Permissions: Photos and videos (to read screenshots and ticket photos), Calendar (to write the events and deadlines you tap to add, and to check for duplicates; deadlines are written as all-day events), Notifications, and biometrics (only when App Lock is on; Android handles biometric data and neither the app nor we receive it).
• Text recognition: done on your device with Google ML Kit; images are not sent. ML Kit may send diagnostic information such as usage statistics to Google to maintain quality (it does not include images or recognized text).
• Google Calendar: saving to calendars of a Google account added to your device goes through Android's calendar system; the app does not talk to Google directly.
• Google Tasks: sign-in information is stored on this device, encrypted with the Android Keystore. What is sent is the same as in section 4.
• Favorite places: addresses are stored only on this device. When you search for an address, Android's geocoder sends what you type to Google (not to us). There is no pick-on-map option.
• App Lock PIN: never stored as-is; it is kept as a one-way hash, encrypted on this device.
• Reading improvement and "Check again with AI": same as sections 3 and 3b. The date-correction fragments sent to iCloud's public database are not sent by the Android version.

6. What we don't collect

• Accounts or passwords
• Third-party SDKs such as analytics or crash reporting
• Advertising or tracking
• Location

7. Contact

Please use the support page.

© 2026 株式会社CIZMO