Visiting Cards Privacy Policy
Visiting Cards is designed to keep your business-card catalogue under your control. Android and iOS card recognition and catalogue browsing work on your device without signing in. Optional Google sign-in, Sign in with Apple on iPhone and iPad, or email/password sign-in for invited accounts creates a Visiting Cards account for AI credits and, with separate approval, cross-device catalogue sync; the web trial requires approved sign-in. The app has no advertising. Online services and technical SDK diagnostics are described below.
Request deletion of your account or cloud data — no app installation is required.
Information handled by the app
Depending on the features you use, the app may access and store on your device:
- photographs of business cards;
- text recognised from cards, including names, job titles, companies, phone numbers, email addresses, websites, postal addresses, GSTIN/PAN details, and other printed information;
- scan location, place name, date, and event information;
- voice-note audio and text you attach to a card;
- follow-up reminders, tags, interaction notes, and app settings;
- the contact details, layout, and visual background you choose for “My Card”; and
- an optional API key that you provide for an AI service.
How information is used
The app uses this information to read cards, let you review and correct them, organise your catalogue, search it, group cards by company, place, event, or type, set reminders, and create exports or backups that you request.
Optional services that can receive data
Account sign-in and Firebase catalogue sync
When you choose Google sign-in or Sign in with Apple, your chosen sign-in provider and Firebase Authentication process your sign-in and assign an account identifier. Invited email/password accounts authenticate directly with Firebase Authentication; the app does not store the account password in the catalogue. For those accounts, account deletion asks you to confirm your account password. Apple sign-in on iPhone and iPad supports Hide My Email; the app then receives a private relay address instead of your real address. Visiting Cards stores the name, email address and profile-photo URL supplied by your provider (when available), account identifier, approval status, and related timestamps in Firebase to manage your account and closed-trial access. A request for trial access can be stored even if access is not yet approved. Firebase Authentication also processes IP addresses and technical request information for authentication, security, and abuse prevention.
If you approve catalogue sync, Google Cloud Firestore and Cloud Storage for Firebase receive your catalogue and associated media: card/contact/company details, postal addresses and phone numbers, scan locations and place names, event and follow-up information, interaction notes, private text notes, voice recordings, card photographs, logos, and My Card data. Sync also stores revision information, timestamps, content hashes, and a generated device identifier used to coordinate changes. Previously linked, signed-in devices can sync automatically. The app retains a working local copy for offline use.
Firebase is a service provider for this account and sync functionality. Catalogue sync is protected by encrypted network connections and account access controls, but is not end-to-end encrypted: it is distinct from the password-encrypted backups and key vault below. Private notes are included in account sync and full backups even though contact sharing excludes them.
Encrypted API-key vault
If you choose cross-device access to your AI key, the app encrypts that key on your device with a separate password before saving it in your account's Firestore key vault. The vault stores the encrypted key, random salt/nonce, authentication tag, encryption-version information, owner account identifier, and update time. The vault password and unencrypted key are not sent to Firebase by this feature. Your password is required to unlock the key on another device; the developer cannot recover it. When you use an AI provider, the app separately sends the unencrypted API key to that selected provider over HTTPS to authenticate the request.
Google Drive recovery backups
Google Drive backup is separate from Firebase account sync. If you connect Drive and enable backups, the app stores password-encrypted recovery files in a backup folder in your Google Drive, using Google's sign-in and file APIs. Full backups can include the catalogue, notes, and media. Restoring an encrypted backup on another device requires the original backup password. Google processes the account and file metadata needed to provide this service. Older unencrypted ZIP backups, if present, are not made encrypted retroactively. Disconnecting Drive does not delete files already backed up.
Other optional services
Core card reading works without an AI service. If you enable AI-assisted reading and save your own provider key, relevant card text is sent directly from your device to the provider you select: OpenRouter, Anthropic, OpenAI, or Google Gemini. A card photograph is included only if you separately enable “Also send the card photo.” Your selected provider processes that request under its own terms and privacy policy.
AI backgrounds and credit purchases (optional). On iPhone and Android, you can sign in and buy prepaid AI credits through the App Store or Google Play. No personal API key or catalogue-sync trial approval is needed for backgrounds. The store processes your payment; we do not receive your card number or banking details. The Visiting Cards AI service, hosted on Railway, verifies your Firebase sign-in and store receipt, stores an account-linked credit ledger, purchase identifiers and tokens, product identifiers, transaction dates and available store price/currency information, and processes refunds. Credits are associated with your sign-in account, do not expire, and are separate from PartLens credits and the Supporter purchase. One completed background preview or regeneration spends one credit, even if you discard it; failed generation releases the reserved credit.
After you agree to AI generation and ask for a background, your device sends a company/design brief (company name, industry, products, city, brand colour and your design instructions) and any chosen logo or card reference to this service. Printed card text is blanked out on your device first; recognition can miss text, so avoid selecting a sensitive reference or including private information in design instructions. The service sends the brief and references to OpenRouter and its OpenAI image provider to generate the background. It checks the result for unwanted lettering and may make one technical correction within the same credit. These providers process data under their own terms and privacy policies. Your phone does not send your catalogue, private notes or contacts list for background generation.
The AI service does not save the brief or reference images in its database. It stores a one-way request fingerprint, generation status, cost and timestamps to prevent duplicate charging, and keeps a private completed image for up to 24 hours for interrupted-request recovery. Images are then removed automatically. Saved backgrounds remain on your device and are included in backups or account sync if you enable those features. On the web, optional background painting continues to use your own selected provider key and its charges.
AI writing help (optional). If you have connected your own AI key and agree when the app first asks (you can switch this off under Settings → AI assistant), asking for a follow-up draft or a pre-meeting brief sends details about that one contact directly to the AI provider you selected: their name, salutation, job title, company, its business type and products, city, when and where you met, lead ratings and interests, your typed notes and voice-note transcripts about them, your last contact with them and any open reminder note, plus your own name, title and company for the signature. Their phone numbers and email addresses are not sent. Nothing is sent until you ask; without AI, drafts and briefs are written on your device.
Sending contacts to your CRM (optional). If you connect Zoho CRM, HubSpot, a Google Sheet, or a web address you choose (for example Zapier or Make), the contacts you choose to send go directly from your device to that service using your own sign-in or key. That includes their name, job title, company and its products, email addresses, phone numbers, website, postal address, GSTIN/PAN, when and where you met, lead rating and interests, and your typed and voice notes only if you switch notes on for that connection. Zoho and Google sign-in happen on their own pages in your browser; the resulting tokens and keys are kept in secure storage on your device. The developer runs no server in between and does not receive this data. The receiving service handles it under its own terms, and deleting a contact in the app does not delete it there.
If you choose to connect OpenRouter from the app, OpenRouter’s own sign-in page opens in your browser and, once you approve, returns a key for this app directly to your device. The developer does not receive it.
If you enable company lookup, the app may open the public website printed on a card to identify what that company does. It does not send your catalogue to that website.
If you ask the app to record where a card was scanned, the app obtains a device location and may use the operating system’s geocoding service to turn coordinates into a place name. That service may process the coordinates under the platform provider’s privacy terms.
If you enable My Card exchange, your contact fields and layout recipe are placed in the QR shown or shared by you. The app uploads the selected visual background over HTTPS to the Visiting Cards exchange service backed by Vercel Blob so the receiving phone can download and cache it. For a card created in the app, that blob contains no structured contact fields. If you choose an existing card image, the image itself may visibly contain the text printed on that card. The service stores no account, original filename, contact database, or QR payload. A one-way hash of the app installation identifier is used only to enforce the upload rate limit.
Exports and contact saving occur when you request them. Backups can also run automatically after you enable scheduled backup. The selected destination app or service handles the information under its own privacy terms.
Recognition SDK diagnostics
Android and iOS text recognition and barcode scanning use Google ML Kit on the device. This local recognition does not require uploading your card photograph to Google. The ML Kit SDK does collect technical information such as device and app versions, installation identifiers, feature events, configuration, input/output sizes, error codes, and performance measurements for diagnostics and usage analytics. These technical transmissions use HTTPS and do not require Firebase catalogue sync to be enabled. The app does not offer a separate switch to turn off this SDK telemetry. See Google's ML Kit disclosures for Android and iOS and Firebase privacy information.
Storage, retention, and deletion
You can delete cards, contacts, and companies inside the app. Deleted records remain recoverable in the app's Trash for 30 days unless you delete them permanently sooner. Clearing app storage or uninstalling removes local app data, not cloud copies. Keep an export or backup of anything you want to retain before deleting it.
Firebase retains account/trial records, synced catalogue snapshots and media, and an optional encrypted key vault until they are removed or you request cloud-data/account deletion. A successful sync can propagate record changes and attempt to remove media no longer referenced by the current catalogue; earlier catalogue revisions and files whose cleanup failed can remain. Deleting a record locally is therefore not a guarantee that every historical cloud copy has been erased. Signing out stops that session but does not delete the cloud account or its stored data. Removing an API key from local settings does not remove its encrypted cloud-vault copy.
Google Drive recovery files, local backup/safety copies, exports, contacts saved to the phone, and copies sent to other people have separate lifetimes and must be deleted at their destinations. Cloud-account deletion does not remotely erase those copies. In-app account deletion stops cloud writes for the deleted account, including other linked devices. Signing in again can create a new account; uploading retained local cards requires a new sync preview and your confirmation.
Each exchanged background is stored under an unguessable address. A separate deletion secret stays in secure storage on the uploading phone and is never placed in the QR. The one-way installation hash and rate counter are automatically deleted within 48 hours. A receiving phone may retain its downloaded copy until its owner deletes that card or app data.
An optional API key is stored using Android Keystore-backed secure storage or the iOS Keychain. Network requests to optional providers and websites use encrypted HTTPS connections.
AI account deletion. Delete account in the app also removes recoverable AI images and disables the credit wallet. Minimal purchase, refund and credit-ledger records and a pseudonymous account marker are retained for payment reconciliation, duplicate-purchase prevention, security and applicable record-keeping obligations. Store purchase history remains with Apple or Google. Verified deletion requests by email cover this AI service as well as Firebase. Sign-out alone does not delete your credits or service records.
Delete your account or request data deletion
In the current iOS app, open Settings → Sync between devices → Delete account. After your confirmation, the app asks your sign-in provider to verify your identity, stops account sync, removes your Firebase catalogue revisions and media, profile and trial records, and encrypted key vault, then deletes your Firebase Authentication account. Apple authorization is revoked for Apple sign-in accounts. This action cannot be undone. If a connection fails, use Delete account again to finish; the app does not report completion until the operation succeeds. Cards stored on this device stay available offline. A minimal security marker containing only the former random account identifier and the deletion-request timestamp is retained to prevent old signed-in devices from recreating deleted cloud data. It contains no contact fields, email address, catalogue or media.
To request deletion of your Visiting Cards account and associated Firebase data, email bhupendrafire@gmail.com from the sign-in email address used for the app (or explain that you used Apple Hide My Email), with the subject “Visiting Cards account and data deletion.” You can do this without installing or opening the app. You can also reach this page through Settings → Privacy policy.
We verify control of the account before acting. Do not send passwords, API keys, your vault password, or your catalogue. If you cannot access that email address, contact the same inbox for identity-verification help. Verified requests are completed within 30 days. Account deletion removes the Firebase Authentication account, profile, trial request/access records, all associated Firestore documents (including the encrypted key vault), and the user's Cloud Storage catalogue revisions and media. You can instead request deletion of only the cloud catalogue/media or only the key vault while keeping the account; specify that scope in your email.
We confirm when deletion is complete. We do not keep the deleted catalogue or vault for advertising or analytics. Support correspondence necessary to process and document your request is separate from app catalogue storage. Your Google or Apple account itself is not deleted. Google Drive files, local copies, exports and copies received by others are not automatically deleted by this request; remove them at their destinations.
To delete data handled by the developer-operated exchange image service:
- Edit or delete My Card in the app. The app uses its device-held deletion secret to remove the previous hosted background and its server metadata.
- If the app or deletion secret is no longer available, email bhupendrafire@gmail.com with the public background URL from the saved or shared QR/card and ask for deletion.
Manual requests are completed within 30 days. The hosted background and its server metadata are deleted. Rate-limit records expire automatically within 48 hours. Copies already downloaded by another user cannot be remotely removed; that user can delete the received card or clear the app's data. Local catalogue data can be deleted inside the app, by clearing Visiting Cards storage in Android settings, or by deleting the app in iPhone or iPad Settings.
Sharing and sale
The developer does not sell, rent, or use your catalogue or exchanged backgrounds for advertising or behavioural analytics. The app contains no advertising SDK or Firebase Analytics integration. The technical diagnostics performed by Google's SDKs are described above. Data goes to the service providers and optional services described here, or to destinations you intentionally choose for export or sharing.
Permissions
The app may request camera, microphone, location, contacts, and notification permissions to provide the corresponding feature. It uses NFC only when you choose to write your own card onto a sticker. You can deny or revoke these permissions in Android or iOS Settings. The app uses the system photo picker for gallery selection; iOS also requests photo-library access when needed for import or export. Optional app lock uses the device authentication screen, including Face ID on supported iPhones; the app never receives biometric templates or your device passcode. iPhone NFC sticker writing requests access only when you choose it and requires a supported, NDEF-formatted tag.
Children
Visiting Cards is a business productivity tool intended for adults and is not directed to children under 13.
Changes
This policy may be updated when the app’s data practices change. The effective date above will be revised when that happens.