ByShare
BYSHARE · PRIVACY & TRANSPARENCY

Privacy Policy

How your information is handled when you use ByShare on the web and iPhone.

Effective date: October 25, 2026

1. About ByShare and this policy

ByShare provides digital business cards, optional public and unlisted card pages, QR and contact-file sharing, account and membership features, and support services through its website and iPhone app. This notice explains the types of information ByShare processes when you use these services, why the information is needed, when it may be shared, and your available choices.

The current operator and privacy contact information are listed at the end of this page. This notice applies to the ByShare website, account portal, and iOS app where they use ByShare services. If a feature is not used or enabled, data associated with that feature may not be collected.

2. Information you provide

  • Account and identity: Your name, email address, account credentials, and information needed to verify your email, sign in, recover your account, and secure it with optional two-factor authentication. Passwords are stored as one-way hashes, not plaintext.
  • Business-card information: Information you add to a card, such as your name, job title, company, phone number, email, website, address, biography, social links, design choices, and profile image. These details may identify you or people whose details you choose to add.
  • Connections and leads: Contact details you save or import, and details people submit to you through your public card form. An iPhone contact picker may be used to select individual contacts with your permission.
  • Messages: Contact Us requests, email-verification requests, support tickets, follow-up messages, and other information you send to the ByShare team.
  • Membership details: Your selected plan, membership status, activation history, and payment-related identifiers needed to verify entitlement. Payment card details are handled by the payment provider rather than entered into ByShare's own purchase forms.
  • Content and preferences: Public web-card visibility choices, share settings, account preferences, and other content you voluntarily submit.

3. Information processed automatically

To deliver and protect the service, ByShare may process website sessions, security events, login attempts, device or account identifiers used for app connections, and technical request information such as IP addresses, dates, browser or device details, and error records. When a web card is viewed or its links are used, ByShare records profile-view and related interaction events to provide the card owner with analytics. Technical logs may also be held by the hosting and infrastructure providers used by the service.

The iPhone app may keep cards, images, selected contacts, and some activity information locally on your device. This information is not automatically published to a ByShare web page solely because it is saved on your iPhone. Signing in, explicitly importing or publishing a card, restoring membership, or requesting a server-generated Wallet pass may send relevant information to the portal or a service provider.

4. How we use information

We use information to:

  • Create accounts, verify email addresses, authenticate users, secure sessions, detect misuse, and respond to support and privacy requests.
  • Store, render, and share business cards according to the privacy and visibility options you choose.
  • Sync account identity, linked cards, and membership eligibility between the ByShare portal and the iOS app when you use those features.
  • Process purchase status, apply membership benefits, and handle refunds or access changes notified by a payment provider.
  • Provide card-view analytics and improve reliability, performance, and security.
  • Deliver service-related emails, such as email verification, recovery codes, ticket updates, and account notifications.
  • Meet legal obligations and respond to valid requests where required by law.

5. Public pages, QR codes, and shared cards

If you enable a public directory listing, the selected card fields can be discovered through ByShare's directory and may be indexed by search engines. An unlisted card is not shown in the directory, but anyone who receives or forwards its link may access the page. QR and NFC links can also be passed to others. A contact file, image, screenshot, or saved copy may remain outside ByShare's control after another person receives it.

Your iOS app lets you choose between direct contact sharing and a web link where a web version is available. You may disable a linked card's web page through supported privacy controls. Disabling the page prevents ByShare from serving that page, but it cannot erase information already downloaded, forwarded, cached by third parties, or copied into someone else's contacts.

Only publish information that you have the right to share. In particular, obtain permission before publishing another person's personal contact details.

6. iPhone permissions and on-device content

ByShare uses relevant iOS permissions only when needed for features you choose. For example, the app may ask you to select contacts through Apple's contact picker or save a QR image to Photos. You can review or change permissions through iOS Settings. The app's direct QR, vCard, and image-sharing functions may transmit the information you choose to the recipient or sharing service; the recipient's handling of that content is outside ByShare's control.

Apple Wallet passes are created only when you request the feature. Generating a pass may require submitting selected card artwork and business-card fields to ByShare's Wallet generation infrastructure. Once added to Apple Wallet, Apple's handling of the pass is subject to its own policies and device controls.

7. Payments and membership

For iPhone in-app purchases, Apple processes payment and provides purchase and subscription transaction information to the app. ByShare may transmit signed transaction evidence to its portal to verify access across your account. For web purchases, Stripe processes payment information and sends payment and subscription status to ByShare. ByShare uses that information to assign benefits, show valid membership status, support account management, and retain required transaction records.

ByShare does not need your full payment-card number to provide these features. Your payment provider's privacy notice also applies to its own processing. Cancelling a subscription does not itself erase your ByShare account or legally required billing records.

8. When information may be shared

Information is available to other people when you choose to publish or directly share a card, and to card owners when someone voluntarily submits contact information through their profiles. ByShare also uses service providers for functions such as:

  • Apple: App Store purchases, purchase verification, and Apple Wallet functions.
  • Stripe: Hosted web checkout, billing, and subscription notifications, when web payments are enabled.
  • Hosting and email providers: Secure operation of the portal, delivery of verification and support messages, backups, and infrastructure support.
  • Wallet infrastructure: A configured pass-generation service, which may include Google Cloud/Firebase components, when a Wallet pass is generated.
  • Optional security services: For example, Cloudflare Turnstile when an administrator enables it for anti-abuse checks.

Service providers must be selected and configured with appropriate protections for personal information. ByShare may disclose information when legally required or necessary to prevent serious security abuse. We do not describe customer business-card data as publicly available unless you publish or share it through the relevant feature.

9. Cookies, sessions, and security

The website uses login-session cookies and other security measures needed for account authentication, CAPTCHA checks, and protection against unauthorized requests. These cookies are not optional advertising cookies. ByShare uses technical and organizational measures to protect stored information, such as password hashing, access controls, and HTTPS where configured. No internet or storage system can guarantee absolute security.

10. Retention, deletion, and your choices

Account data and saved portal content are generally retained while the account is active and needed to provide the service. Specific records may need to be retained longer for billing, fraud prevention, support disputes, security investigations, backup recovery, or applicable legal obligations. Verification codes and certain temporary requests expire according to the feature's security rules. Deleting the app from an iPhone does not automatically delete portal records or cancel an App Store or Stripe subscription.

Depending on the feature, you can edit or delete saved cards, stop publishing a web card, change web visibility, remove imported contacts or local analytics, revoke optional iPhone permissions, and sign out. If you want to access, correct, export, or request deletion of account data, use the privacy contact method listed below. A deletion request may require identity verification, and some information may remain where retention is legally required or needed to resolve security or billing issues. Copies held by other people or services are outside ByShare's direct control.

11. Children and international use

ByShare is intended for professional identity and networking. It is not designed as a children's social network. If you believe a child has provided personal information improperly, contact the operator to request review or removal. Depending on your region and where the hosting or service providers operate, information may be processed in another country and subject to that country's rules.

12. Updates to this notice

The operator may update this notice when features, providers, or legal obligations change. The date displayed above indicates the version currently published on this page. Material changes should be communicated where required by applicable law.

13. Contact and privacy requests

To ask a question, exercise a privacy choice, or request data removal, use the contact options shown beneath this policy. For account-specific issues, a signed-in user may also use Support Tickets when enabled. Include enough information to identify the relevant account, but do not send passwords, verification codes, or full payment-card details.