# Privacy Policy

_Last updated: October 26, 2026_

This policy explains how we handle information on **boppr.me**, in the Boppr mobile app and App Clip, and through our related profile, account, and API services (the “Services”). It covers account holders, people visiting public profiles, and people sharing contact details with them.

Purchases and browsing on our separate Shopify store at boppr.com are covered by the [store privacy policy](https://boppr.com/policies/privacy-policy). This policy describes the digital Services; it does not replace the store’s disclosures about shopping and advertising.

## 1. The short version

- Your published profile and links are public. Share only what you want other people to see, save, or forward.
- Opening a profile does not give its owner access to your phone’s contacts, photos, or messages. We do receive ordinary web request information and generate visit statistics.
- If you submit a contact form, the profile owner receives the details you enter and can save, export, or send them to an integration they configure.
- Profile analytics show aggregated visits, approximate locations, referring sources, and device categories. They do not give the owner a named list of visitors.
- Boppr getting-started texts are a separate, optional choice on the contact form. Older forms used a pre-selected checkbox; see section 3.
- AI scanning and writing features send the content needed for your request to Google’s AI services. Review the results before using them.
- You can contact [support@boppr.com](mailto:support@boppr.com) about privacy or deletion. Reading this notice is not consent to every possible use of your information.

## 2. Information we receive

### Information you provide

**Accounts and profiles.** Account identifiers, sign-in information handled by our authentication provider, email address, name, username, biography, business details, profile images, links, and settings. Information you publish can appear in a public profile, contact download, QR destination, sharing image, or Wallet pass.

**Contacts and leads.** Details entered in a profile’s contact form, contacts an account holder saves or imports, business-card images submitted for scanning, and associated notes, tags, and follow-up content. The exact fields depend on what you or the profile owner enter.

**Purchases and support.** Subscription status, product and transaction identifiers, purchase history provided by the billing platform, and messages you send to support. App-store payment credentials are handled by Apple or Google; we use RevenueCat to manage subscription entitlements.

**Profile imports.** If you ask us to import a profile from a service such as Popl or Dot, we retrieve the page you identify and process its profile details and links.

**Connected services.** Configuration and credentials you supply for integrations, and the data those integrations exchange at your direction. Do not put secrets in public profile fields.

### Information collected when you use the Services

Our infrastructure receives IP addresses, request times, browser and device information, URLs requested, and other connection or diagnostic information needed to deliver and protect the Services. Hosting providers may keep request and security logs separately from our profile analytics.

The app can receive push-notification tokens and permission status. Features such as taking a photo, choosing an image, scanning a code, or saving a contact use the relevant device capabilities and permissions. A permission request does not mean that your entire photo library or address book is uploaded.

## 3. Public profiles and contact sharing

A profile marked private uses an access link or token. Anyone you give that link to may be able to access and forward it; it is not a promise that recipients cannot copy the content.

Public profile information can be viewed without an account and may be indexed by search engines, copied, downloaded, or shared. Removing it from Boppr cannot recall someone else’s saved contact, screenshot, exported file, or search-engine cache.

When you submit your details to a profile owner, that owner decides how to use them for their own activities. They may receive notifications and sync the lead to their own systems, including Klaviyo or a webhook destination. Their privacy practices also apply. Sharing a contact is not, by itself, permission for unlimited marketing.

If you separately opt in to Boppr getting-started marketing texts, we process your phone number, opt-in choice, and related contact details for that purpose and may pass them to messaging or automation providers used to deliver the messages. This is optional and separate from sending your details to the profile owner. Message frequency varies; message and data rates may apply. Contact [support@boppr.com](mailto:support@boppr.com) to withdraw that opt-in or get help. Older versions of the contact form pre-selected the text-message checkbox. A stored selection from those versions does not by itself establish that you actively agreed to marketing. Contact us if you received an unwanted message or want us to review a historical selection.

Contact the profile owner about their copies and communications. You can also contact us about information held in Boppr; we may need the profile link and approximate submission date to locate it. Account holders must have a lawful basis to upload or use other people’s information.

## 4. Profile analytics

We count profile visits and link interactions to help owners understand how their profiles perform. Our web-profile analytics aggregate counts by day, approximate country, region or city, referring website category, device type, browser, operating system, and visitor-local weekday and hour. Location comes from IP-derived hosting information, not precise GPS access. Approximate coordinates may be stored with location aggregates.

The custom web-profile counter does not store raw IP addresses, full user-agent strings, or full referring URLs in its analytics records and does not use a visitor cookie or visitor ID to recognize a person across visits. This describes that counter, not all infrastructure logs, account storage, or third-party SDKs.

Owners see summaries for their profiles, not the raw connection information or a named visitor history. These summaries are not guaranteed to be anonymous in every context: small counts and approximate locations can still reveal information when combined with other knowledge. Visits are not unique people; bot filtering and location estimates can be wrong. Some older counters and link totals cover different periods from the web-analytics date selector.

**The 7-, 30-, and 90-day filters control the report you see. They are not deletion deadlines.** Daily aggregate analytics currently have no automatic age-based deletion schedule. Contact us about deletion requests; we do not promise that deleting an account immediately removes every historical aggregate or provider log.

### Public activity map

Our public activity globe can display recent, grouped city-level activity from a connected Google Analytics property, including approximate timing, platform, and counts. This is separate from an owner’s private profile dashboard. It does not display names or contact details, but small counts can still reveal information when combined with other knowledge. Which activity appears depends on the websites and app versions connected to that property.

## 5. How we use information

We use information to provide accounts and public profiles, deliver contact-sharing and lead-management features, manage subscriptions, send service messages and requested notifications, provide support, measure performance, investigate abuse, secure the Services, and meet legal obligations.

Where European or UK data-protection law applies, the basis depends on the purpose: performing our agreement with you for the service you request; legitimate interests in operating, improving, and protecting the Services where those interests do not override your rights; legal obligations; or consent where required. You may object to processing based on legitimate interests and withdraw consent without affecting earlier lawful processing.

### AI features

If you use business-card scanning or AI follow-up drafting, the image, text, and relevant contact information included in that request are sent to Google through Firebase AI services. These features involve cloud processing, not only processing on your device. Avoid submitting sensitive information that is unnecessary for the task. AI can misread details or invent content; review its output before saving or sending it. Provider processing is subject to the applicable Google service terms; this notice does not promise zero provider retention or blanket exclusion from every form of model improvement.

## 6. Providers and other recipients

We disclose information needed for the relevant function to:

- **Google / Firebase, Google Cloud, and Google Analytics:** authentication, database, file storage, backend hosting, AI processing, and aggregate activity reporting.
- **Vercel:** web and API hosting, request delivery, and IP-derived location information.
- **RevenueCat, Apple, and Google Play:** purchases, subscription verification, and app distribution.
- **Expo, Apple, and Google:** app delivery and push notifications.
- **Resend, SendGrid, and Klaviyo:** service email or communications and list features, depending on the feature and client version.
- **Messaging and automation providers:** delivery of optional Boppr getting-started texts when you opt in.
- **Meta:** app advertising measurement where its SDK is configured; see the next section.
- **Profile owners and destinations they configure:** contact submissions, integrations, and exports as explained above.

We may also disclose information when legally required, to investigate fraud or protect rights and safety, to advisers supporting those purposes, or in a business transaction such as a merger or sale, subject to applicable protections. We may share information at your request. Linked websites and services have their own policies; we do not control what happens after you leave Boppr.

## 7. Cookies, device storage, and advertising measurement

Authentication and other features use browser or device storage to maintain sessions and preferences. Clearing or blocking that storage may sign you out or prevent features from working.

Some app builds include Meta’s SDK configured to initialize and log app events automatically, including installs, launches, and supported purchase events; the app may also log registration and purchase events explicitly. Depending on the build, platform, and permissions, Meta may receive device identifiers and app-event information. On iOS, advertising-identifier access is subject to Apple’s tracking permission. On Android, configured builds may collect the advertising ID without an in-app tracking prompt; available controls to delete or reset it, or limit advertising, are in your device’s privacy or ads settings and vary by Android version. Denying iOS permission does not necessarily stop every non-identifier event or essential diagnostic request. See [Meta’s privacy policy](https://www.facebook.com/privacy/policy/).

Advertising measurement may fall within legal definitions of “sharing,” “sale,” or targeted advertising in some jurisdictions even when money is not exchanged. We do not make a blanket “no sharing” claim for that processing. Use your device’s tracking and advertising controls and contact us to exercise applicable opt-out rights. These Services do not currently provide a universal in-app advertising opt-out switch or a guaranteed automatic response to every browser privacy signal. The Shopify store has separate controls described in its policy.

## 8. Retention and security

Retention depends on the record and its purpose. Account information supports an active account; purchase, support, security, and legal records may be needed longer for obligations, disputes, or abuse prevention. Provider logs and backups have their own retention cycles. Aggregate analytics currently remain until removed rather than expiring automatically, as explained above.

You can request account deletion through the app or support. Some uploaded images, a record that the account was deleted, historical analytics, subscription or integration-provider records, backups, and independently exported copies may remain after the primary account is removed. Tell us if your request concerns those records so we can assess it under applicable law. We will explain relevant exceptions rather than promise complete or instantaneous erasure.

We use measures such as authenticated access and encrypted network connections to protect information. No system is perfectly secure. Contact support if you suspect unauthorized access; do not email passwords or full payment details. We will provide legally required notices about qualifying security incidents.

## 9. Your choices and rights

You can edit your profile, remove published details, manage device permissions and notifications, disconnect integrations, and use unsubscribe options in marketing communications. Disconnecting an integration does not delete copies already delivered to it. Service and security messages may still be necessary.

Depending on your location and the laws that apply, you may request access, correction, deletion, a portable copy, restrictions on processing, or an opt-out of sale, sharing, or targeted advertising. You may also withdraw consent, use an authorized agent, appeal a denied request where available, or complain to your data-protection authority. We will not unlawfully discriminate against you for exercising these rights.

Email [support@boppr.com](mailto:support@boppr.com) with your request. We may need proportionate information to verify identity or authority; do not send identification documents unless we request them through an appropriate channel. We respond within applicable legal time limits and explain if an exception applies. For an appeal, reply with “Privacy appeal.”

## 10. Children and international processing

Boppr is not directed to children under 13. Do not submit information about a child under 13. If you believe a child has provided information, contact us so we can investigate and address it. Account eligibility is explained in our [Terms of Service](https://boppr.me/terms).

Boppr operates from the United States, and providers may process information in the United States and other countries with different privacy laws. Where applicable law requires transfer safeguards, those requirements apply to our processing; contact us for information about safeguards relevant to your data.

## 11. Updates and contact

We will update the date above when this policy changes. For material changes, we will provide additional notice through the Services or an appropriate communication channel, and obtain consent where required before a new use begins.

For privacy questions or requests, contact **Boppr** at [support@boppr.com](mailto:support@boppr.com).
