Pocket Card: Digital Business Card — Privacy Policy
Last updated: 2026-10-04
This privacy policy applies to the mobile app "Pocket Card: Digital Business Card" (shown in the app as "Pocket Card") for Android:
- Google Play: package com.moon.businesscard, developer "janey-moon"
The app is developed and operated by Heekyung Moon (Google Play developer name: janey-moon).
Contact: ansgml2100@gmail.com
OVERVIEW
Pocket Card does not require an account, and we do not sell personal information. The app lets you create your own business cards, show them as a contact QR code, export them as files or images, and keep a log of contact details you receive from other people together with where and when you met. Cards, received contacts, photos, and files the app creates are kept in the app's storage on your device. The app also uses Google services for analytics, crash reporting, remote configuration, and advertising.
CAMERA, PHOTOS, CONTACTS, AND SHARED CARDS
Camera: the app asks for camera access only when you tap "Allow camera" on the Scan contact QR screen. The back camera runs only while that screen is open and is used to read QR codes; the code is decoded on your device by Google's barcode-scanning component included in the app. The app does not save camera images. When a contact QR code is read, its text is shown for review, and a contact is stored only if you open it and tap Save. If you decline camera access, you can still paste contact text or open a .vcf file.
Photos and files: "Choose photo" and "Open .vcf" use the Android system file picker, which needs no storage permission; the app reads only the file you pick. A picked photo is copied into the app's storage, and a photo embedded in an imported vCard is copied there when you save that contact. The app does not browse your gallery.
Phone contacts: the app does not read or write your phone's contacts (contact permissions are blocked). On a received contact, "Open phone contact editor" hands its name, organization, job title, phone, email, website, address, and shared contact note to your phone's contacts app; whether that contact is saved, and where it syncs, is controlled by that app.
What a shared card contains: the contact QR code contains, in vCard text, only the fields ticked under "Fields in QR" (from full name, given and family name, organization, job title, phone, email, website, address, and shared contact note); it never contains the photo, card label, or meeting details. Anyone who scans or receives your QR code gets those details. The card image shows the card label, photo, name, job title, organization, phone, email, and website. The QR image and QR wallpaper show the card's name, organization, and QR code; the contact pass image also shows the phone number (or the email if there is no phone). A .vcf export contains the vCard fields and the photo, but not the meeting place, meeting date, or private meeting note. A CSV export contains the card label and all text fields, including the meeting place, meeting date, and private meeting note, but no photos.
Sharing: when you tap "Share file", the file is passed to the Android share sheet, and the app or person you choose receives it. The app does not upload your cards, contacts, photos, or exported files to the developer or to any analytics or advertising service.
INFORMATION STORED ON YOUR DEVICE
For each card or received contact the app saves: card label, full name, given and family name, organization, job title, phone numbers, emails, websites, address, shared contact note, an optional photo, the time it was created and changed and when an image of it was last exported, and, for received contacts, where you met, the meeting date (a new received contact starts with today's date, which you can change), and a private meeting note. These are kept as files in the app's documents storage. The app does not set a maximum number of cards or contacts. When you delete a card or contact, the app keeps a deletion marker (its internal ID and deletion time) so that importing an older backup does not bring it back.
The app also keeps files you create or open in its documents storage: exported .vcf, CSV, image, and raw-record files; backups you create; copies of the .vcf and backup files you open (opened backups are kept so missing parts can be added later); and files recovered from a backup that could not be fully restored. Each time the app starts, it removes older files so that it keeps the five newest files in each of its export and opened-file folders, the three newest complete backups you created, and the three newest complete backups you opened; backups you created that did not finish writing and other temporary files are removed once they are more than a day old. Files created after that start remain until a later start. Incomplete opened backups and recovered files are not removed by this cleanup, and the cleanup is skipped while the app's index or a saved record cannot be read. The app may also store cached advertising settings and a cached More Apps list.
The developer does not run a server that receives your cards or contacts. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not write to Firestore. The More Apps list loads app icons from internet addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches and sessions, the launch screen, the launch ad step, opening the privacy policy, More Apps, or the review option in the menu, ad revenue events (ad format, value, currency, and precision), app version, device type, and app-instance identifiers. No event parameter includes names, contact details, notes, photos, or other text you enter.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob: an app-open ad at launch and when you return to the app, an interstitial ad that may appear after you save a new card or contact and return to the home screen, a banner ad, and a native ad in the exit dialog. Google may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location. Banner ads are shown only on the My cards and Received tabs of the home screen. The app does not start a full-screen ad (app-open or interstitial) while the QR scanner or the card editor is open.
PERMISSIONS AND ADVERTISING CHOICES
Feature permissions: camera, for QR scanning. The app also uses Android's vibration permission for short haptic feedback on some buttons and after saves and exports; it is granted at install, is not a runtime prompt, and gives no access to your data. The app does not request microphone, location, contacts, storage or photo access, Bluetooth, health data, or notifications.
At launch, Google's consent message (UMP) is shown where required (for example in the EEA and UK). If the consent step completes and your choice does not allow ads to be requested, the app does not request ads. Personalized ads are requested only where consent is not required or your choice allows personalized advertising; otherwise ads are non-personalized. If the consent step fails (the consent information, the consent message, or your recorded choice cannot be loaded), the app requests non-personalized ads only.
Where Google reports that a privacy options entry is required, the menu (Settings tab, "More") shows "Privacy choices", which reopens the consent message so you can change your advertising choice. Ad requests are paused while it is open; if it cannot be shown, the app stops requesting ads until it is restarted. You can change the camera permission in your device Settings at any time.
STORAGE AND YOUR CONTROL
You can edit a card or contact, remove its photo, or delete it from its detail screen. Deleting removes the card or contact and its saved record file from the app's storage, and photo files that no saved card, contact, or unsaved draft still uses are removed; if a damaged record is found, the app keeps photo files until it can be read. The deletion marker described above remains. Single-card .vcf, CSV, and image exports are linked to their card or contact when created and are removed when you delete it, or at a later app start; this does not happen while a saved record cannot be read. Other files (exports of all contacts, raw-record exports, older unlinked exports, backups, and copies of opened files) are not removed by deleting a card and follow the startup cleanup described above. Files you pick pass through the app's cache; the app does not delete the file picker's cache copies itself, and Android may clear its cache. Clearing the app's data in Android settings or uninstalling the app removes the app's storage on the device, including these files, but may not remove an older system backup. Files you shared or saved elsewhere are controlled by the app or person that received them.
"Create full backup" on the Settings tab writes a backup that includes every readable card and received contact, their photos, private meeting notes, and the deletion markers, plus the raw text of any record that cannot be read. Importing a backup merges it: newer versions replace older ones, and contacts the backup marks as deleted are also removed from this device.
Local data may be included in a Google or device backup depending on your backup settings (the Android app does not opt out of system backup). Uninstalling normally removes the active copy but may not remove an older backup.
Because we do not receive your cards or contacts, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google, or to ask us for help with a privacy request, contact us at the address below.
We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy. Data processed by Google is retained according to its service settings and policies:
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
SECURITY
Your cards, contacts, photos, and app-created files are kept in the app's private storage, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Backup, .vcf, CSV, and image files are not encrypted or password-protected, and backups and CSV files include private meeting notes, so share and store them with care. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app handles to what is described in this policy.
IMPORTANT NOTICE
Pocket Card does not verify who created a QR code or contact file. Check scanned or imported details before saving or calling, emailing, or visiting them. Exported images and files are snapshots and do not update after you edit a card. When you store details about other people, respect their wishes and the laws that apply to you.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Heekyung Moon (Google Play developer: janey-moon)
Email: ansgml2100@gmail.com