How AfterScan handles data

Account and profile details, such as your name, email address, company details, profile image, booking URL, and authentication identifiers when you sign in with email, Apple, or Google.

Workspace content and settings, such as event names, campaign names, capture form fields, booking links, follow-up settings, and other configuration you save in the product.

Lead and scanner information submitted through QR capture pages, such as name, company, email address, phone number, consent choices, and custom form answers.

Connected-service data and tokens for integrations you choose to enable, including providers such as Google, Microsoft, Calendly, Cal.com, LinkedIn, HubSpot, and Salesforce.

Device and app data needed to operate the mobile experience, such as secure session state, push notification tokens, and media library access when you choose to save QR assets to your device.

To authenticate users, create and deliver QR capture flows, and route captured leads into booking and follow-up workflows.

To send or prepare follow-up content, including email, SMS, push reminders, and AI-assisted drafts when those features are enabled by the account owner.

To maintain integrations you connect, troubleshoot support requests, protect the service, prevent abuse, and comply with legal obligations.

If you choose to sign in with Google, AfterScan uses basic profile scopes such as openid, email, and profile to identify your account and display your name, email address, and profile image.

If you choose to connect Gmail, AfterScan requests Gmail Send so it can send follow-up emails to leads from your Gmail account. AfterScan does not request permission to read, list, modify, or delete your Gmail messages.

If you choose to connect Google Calendar, AfterScan requests Google Calendar Events for calendars you own so it can create or manage booking and follow-up events related to captured leads. AfterScan does not request broad calendar read/write scopes or Google Contacts access.

AfterScan uses Google API data only to provide the user-facing features you enable, does not sell Google user data, and does not use Google user data for advertising.

If you connect an email account using an app password, AfterScan sends that credential to your email provider over a TLS-encrypted connection to verify access. The connection check does not send an email.

After a successful check, AfterScan stores your email address, sender name, server settings, and an encrypted copy of the app password on its servers. The saved password is used to send the follow-up emails you enable and is not returned to the mobile app.

SMTP setup in the mobile app does not enable inbox reading or reply synchronization. If reply synchronization is configured separately, it uses its own saved settings.

You can remove the saved SMTP password from Settings > Email connection. You can also revoke the app password in your Google or Microsoft account security settings.

AfterScan uses three third-party AI services, only for the features below. The AfterScan apps ask for your permission before each feature first sends data, and you can turn each one off at any time in Settings > Privacy.

OpenAI: when you scan a badge or business-card photo that has no QR code, the photo is sent to OpenAI to read the name, title, company, email address, and phone number printed on it. QR codes are read without AI.

Anthropic: when AI drafting is turned on, each new lead's name, company, email address, phone number, and form answers, together with your profile and event details, are sent to Anthropic to write the follow-up email, text, and recap.

Exa: when AI research is turned on, each new lead's name, company, and email domain are sent to Exa to look up their company and public professional profile on the web.

These providers process the data to return results to AfterScan for the feature you turned on. AfterScan does not send your data to them for advertising.

With vendors and infrastructure providers that help us operate the service, such as hosting, authentication, messaging, notification, and AI or enrichment providers acting on our behalf.

With third-party tools a workspace owner intentionally connects, such as calendar, email, scheduling, CRM, and messaging providers, so the requested workflow can run.

When required by law, to protect rights or safety, or as part of a merger, acquisition, financing, or asset transfer.

AfterScan does not describe itself as selling personal information or using app data for cross-app advertising tracking.

We keep information for as long as needed to provide the service, maintain reasonable business records, enforce agreements, and satisfy legal obligations.

Workspace owners can remove some content inside the product, and users can request access, correction, or deletion by emailing hello@qrwizard.app.

If you submitted your information to a seller through an AfterScan capture page, you may also need to contact that business directly because it controls the lead workflow it created.

You can disconnect integrations, sign out, disable notifications in device settings, and choose whether to grant photo-library permissions when saving QR assets.

If you have an AfterScan account, you can delete it from Settings in the AfterScan app (iPhone, iPad, Mac, or Android) or send a deletion request to hello@qrwizard.app.

Privacy questions, access requests, and deletion requests can be sent to hello@qrwizard.app.

AfterScan is built for professional lead capture and is not directed to children under 13.