Effective date: October 23, 2026
Agent Card Draw is developed by Oscar Sanchez. This policy explains how the app handles information when you create a professional card, organize contacts and events, draw a card, share information, use Apple Wallet, view advertising, or choose to share usage analytics.
Contact: [email protected]
Agent Card Draw stores your professional profile, e-cards, contact and lead details, lead notes and status flags, selected images, event information and history, and app preferences locally on your device. The current app does not require an Agent Card Draw account and does not provide cloud synchronization of this locally stored contact collection.
Your device and any backups you enable are also subject to Apple's settings and privacy practices. Removing information from the app does not remove copies you have already exported, sent to someone else, added to another app, or retained in a device backup.
You decide when to share card or contact information through QR codes, Nearby Exchange, CSV export, AirDrop, Messages, email, Apple Wallet, or other iOS sharing destinations. Nearby Exchange requires a user-initiated session and an acceptance choice before an incoming card is added. Sharing destinations and recipients handle the information under their own terms and privacy practices.
The current interface offers CRM-ready exports for you to import or share; it does not offer direct CRM account sign-in or automatic CRM synchronization. Saved contacts, notes, and images are not supplied to advertising or analytics as contact-field values or artwork.
Please collect or share another person's information only when you have permission to do so.
When you choose Add to Wallet, the app sends the selected business-card fields and generated Wallet artwork to our configured pass-signing service over HTTPS. Depending on your card, this may include your name, company, title, phone number, email address, website, license number, social links, office address, headshot, logo, and QR artwork.
The service uses this information to generate and return the signed Wallet pass. Readable card content and artwork are processed for that request rather than stored as a developer-hosted contact collection. Responses instruct clients not to cache them. The signing private key remains on the service and is not included in the app. You can review the resulting pass before choosing whether to add it to Wallet.
To protect the service from replay and abuse, security controls use short-lived information such as a request digest, a one-time challenge's expiry and used status, and limited request/IP information for rate limiting. These security values are not used to build a contact profile or target advertising.
Apple controls the handling of a pass after you add it to Apple Wallet, including any Apple services and synchronization you enable. Remove a saved pass through Apple Wallet if you no longer want it there.
Usage analytics are off by default. You can enable or disable Share Usage Analytics in More > Privacy Choices without losing app features or changing the price of a plan.
If you enable it, Google Analytics for Firebase processes app-instance identifiers, general location derived from network information, device and app information, navigation and feature interactions, scanning and sharing flow events, draw events, advertising interactions, purchase-flow events, and diagnostic information. Google Analytics also measures app lifecycle and in-app purchase/subscription events, including product information, through its standard SDK functions.
App analytics events use feature states, counts, choices, lengths, product information, and diagnostic details. They do not send the actual names, phone numbers, email addresses, lead notes, captured card images, or Wallet artwork saved in your contact collection as analytics parameters. We do not set an Agent Card Draw account/user ID in Analytics. Firebase advertising storage, advertising user data, advertising personalization, and Firebase IDFV collection are disabled in this version.