as it should.As It Should, Inc.
Sheet 2Enquire

Your connections belong to you.

Sheet 3 of 4Specification — WhomEffective 30 September 2026As It Should, Inc.

Whom is designed around a local-first business-card library. This policy explains what stays with you, when a limited feature contacts an external service, and the controls available to you.

1.0Your card library

Your saved cards are stored on your device. When iCloud sync is available, contact fields, tags, original card images, recognized text, and each card's review status also sync through your private CloudKit database under your Apple account. As It Should, Inc. cannot browse that private database or use it to build a contact graph.

Person grouping, relationship notes, follow-up reminders, and meeting history stay on this device. Whom does not sync them through iCloud. Whom's iCloud sync can restore your saved cards on another device, but it does not restore this relationship information. Deleting the app can remove this local information; iCloud card sync is not a backup of it.

Whom may access the iOS Contacts library only after you grant permission and only to perform the contact actions you request. Whom does not upload your Contacts library to As It Should, Inc.

2.0Connected features

2.1AI recognition fallback

Cloud recognition is off by default. Only after you enable it in Settings and confirm the disclosure, if on-device recognition produces a concrete quality failure, Whom may send a temporary reduced-size card image or OCR text and layout to an App-Attest-protected AWS service using Amazon Bedrock. The request is used to return recognition results and is not retained as a saved card library. Requests are rate- and quota-limited.

2.2Recognition improvement

If you separately enable this setting, Whom may send OCR text from a reviewed card together with the corrections you saved. Card images and internal database identifiers are rejected. Submissions are encrypted at rest and deleted after 30 days.

2.3Company logos

Whom may use a company website or work-email domain, or a printed company name when no domain is available, to locate a company logo. Brandfetch may process the lookup, and curated fallback assets may be delivered through our AWS content service. Whom does not send the person's name, card image, phone number, address, notes, or tags for this purpose. Logo files are cached on the device.

2.4Product analytics

Product analytics are off by default. If you enable “Share usage analytics,” Whom sends a limited set of screen names, feature outcomes, and coarse workflow categories to Mixpanel. The event interface does not accept names, companies, contact information, card text, images, contact identifiers, or search terms. Mixpanel adds random app/device identifiers to link events over time. This is pseudonymous usage data, not identifier-free data. Automatic event collection and IP-based geolocation are disabled. You can turn collection off at any time.

2.5Social-profile import

LinkedIn or another supported provider is contacted only after you choose that import method and authorize it. Whom receives only the fields made available through the provider's supported authorization flow.

2.6Apple Wallet

The selected personal card is sent to Whom's signing service only to create the Wallet pass you request and is not retained by that service.

2.7Exchange

The universal QR payload is a vCard. Optional Whom-to-Whom rich exchange uses an unguessable, short-lived capability in CloudKit's public database. The publisher removes superseded records and retries removal of its expired records on later launches.

2.8In-app purchase

The one-time Whom Unlimited purchase is made through Apple's App Store. Whom receives only Apple's signed confirmation of the purchase and stores no payment details. The number of cards added is counted on your device.

3.0Your choices

You can disable cloud recognition, product analytics and recognition-improvement sharing at any time in Whom Settings. You can revoke Contacts access in iOS Settings. Deleting a card removes it from the library. On this iPhone the card, including its original scans, stays in Recently Deleted for 30 days and can be restored during that window. After 30 days the local copy and those scans are removed. The deletion is sent through private iCloud, so the card leaves your other devices as well.

“Erase all cards everywhere” deletes every card in the library on this iPhone and waits until private iCloud confirms those deletions. Those cards follow the same 30-day Recently Deleted window on this iPhone. Provider authorization can be revoked through the relevant provider. See Whom support for recovery and export guidance.

4.0Retention and security

Recognition-improvement submissions expire after 30 days. Authentication challenges and public exchange records are short-lived. Operational logs are configured for 14-day retention and are designed not to contain card text, contact data, images, or service credentials.

Whom uses Apple App Attest for protected service requests, encrypted transport, encryption at rest for retained feedback, strict request-size limits, and least-privilege service roles. No system can guarantee absolute security, but Whom is designed to minimize both the information collected and the consequences of failure.

5.0Children

Whom is a professional contact-management tool and is not directed to children. We do not knowingly collect personal information from children.

6.0Changes and contact

We may update this policy when Whom's features or service providers change. The effective date above will be updated with material revisions. Questions can be sent to hello@asitshould.co.