Privacy policy
This is a translation provided for convenience. The Korean text is the binding version; if the two differ, the Korean text applies.
CardKeep (“the app”) is built not to store card information on CardKeep operator servers. This policy explains what the app actually handles and where.
1. What the operator collects
The operator does not collect or store on any server the personal data of users or the data printed on their cards. There is no sign-up, login, advertising SDK, or operator-run usage analytics. The Google ML Kit technical diagnostic traffic is explained in section 4. Payments are handled by Google Play or Apple in their store UI; the operator never receives card or payment-method details.
2. What is stored on the device
Original card photos, names, companies, job titles, phone numbers, emails, notes, labels, places, reactions, important marks and follow-up appointments are stored only in the app’s own storage on your device.
If you enable Android Google Backup or iPhone iCloud device backup, the operating system may include app data in the backup for your Google or Apple account. The CardKeep operator cannot access or keep a copy of that backup.
Usage counts (for example how many cards were saved) record only an event name and a time, never linked to card contents. You can read and clear them in Settings. They are never sent anywhere.
3. When data leaves the device
Data leaves the device only when you choose to send it: sharing card details, sharing a photo, exporting CSV or vCard, saving a backup file, sharing an iCalendar file, opening the phone, messaging, mail or maps app, and adding an event to your calendar.
If you enable your operating system’s device backup, the operating system may also send app data to that account’s backup service for device transfer and recovery.
You pick the receiving app or service in the operating system share sheet, and what happens after that follows that app or service’s own policy.
4. Text recognition and Google ML Kit
Card text is recognised by Google ML Kit running on the device. Card images and recognition results are not uploaded to an OCR server.
ML Kit may however contact Google servers for model and compatibility updates and for performance and usage metrics. This traffic may include device and app information, an installation-specific identifier, recognition events and performance metrics, but never card images or recognised text. It is encrypted in transit with HTTPS.
5. Permissions
Camera: requested when you take a photo of a card.
Photos: requested when you choose a card photo from your album.
Calendar: on iPhone, write-only access is requested when you add an event. On Android no calendar permission is requested; a calendar file is shared instead.
Contacts, call logs and the microphone are never requested.
6. Other people’s information on a card
A business card is usually someone else’s personal data. Keep it for the purpose it was given to you, and check the recipient and the service before you export or share it.
7. Retention and deletion
Data stays on the device until you delete it. Deleting from a card removes that card and its photo; “Delete all cards and photos” in Settings removes everything. Uninstalling the app also removes the app’s storage, as the operating system deletes it.
The operator keeps no server copy, so data deleted from the device cannot be recovered for you.
8. Your rights
You can read, edit, export and delete your data inside the app at any time. These are not turned into paid features.
9. Changes to this policy
If a feature that changes how data is handled is added, such as login or cloud backup, this policy is updated and announced inside the app before it takes effect.
10. Contact
For anything related to personal data, please get in touch below.
Operator: 세일즈 코파일럿 팀
Email: salescopilot.team@gmail.com