Effective on publication.
Bits Cards is provided by BITS Blackrock IT Solutions LLC, Commercial Registration No. 191833, Alexandria Investment Registry Office. Its published registered office is 8 Ali Basha Zulfakar St, Mostafa Kamel, Sidi Gaber, Alexandria, Egypt. Contact the operator through the BITS contact page for privacy, access, correction, or deletion requests. Identify your Bits Cards account so the request can be verified. Do not send passwords or authentication codes.
Bits Cards is currently an internal service for users with a provider-verified bits-solution.com email address. It lets eligible users manage digital business cards, contact records, email signatures, and meeting backgrounds. Company administrators manage company templates, assigned company cards, and explicitly shared company contact records. They do not receive access to another person's private notebook solely because they are administrators.
Information used by the service
Clerk manages registration, sign-in, sessions, and organization memberships. Bits Cards checks your provider identity, verified email addresses, current organization membership, and role to authorize access. If you choose Google sign-in, Google and Clerk process your Google account identifier, name, email address, and profile image for authentication and account linking. The connection requests only OpenID, email, and basic profile permissions. It does not request access to Gmail messages, Drive files, or calendars.
Bits Cards stores the professional information, profile images, logos, custom backgrounds, contact records, notes, encounter history, and follow-up details that you or an authorized company administrator save. These records are used to provide the selected card, contact, signature, background, and export features. Company-owned records and personal records have different access rules. Organization membership changes can remove access to company assets without deleting every company-owned record.
The service maintains aggregate daily card-request, file-request, and accepted-exchange counts where the relevant sharing functions are enabled. These counts do not identify unique visitors or prove an address-book import. Infrastructure providers may process connection information and service logs to operate and secure the service. This notice does not promise that infrastructure logs or backups disappear immediately after a request.
Sharing and external copies
Private drafts and notebooks require authorized access. Public card publication is currently disabled on the internal production service. If publication is enabled in a later release, only the explicitly published profile is shared through its card URL. A recipient's voluntary contact submission becomes an owner-scoped or company-owned contact according to the displayed destination and consent flow. Submitting a contact is not consent to marketing.
Downloading or copying a vCard, signature, QR image, or background creates a separate copy. Sending or installing that copy shares the included information with the recipient, mail client, or meeting service you choose. Updating or removing a record in Bits Cards does not recall those external copies. Prepared offline card copies remain on the device until the user removes them or clears the relevant browser storage.
Providers and storage
Bits Cards uses Clerk for identity, Google when you choose Google sign-in, and the existing Hetzner infrastructure for the application and PostgreSQL database. Provider processing and storage may occur outside your location. Their own notices apply to their services: Clerk privacy notice and Google privacy policy. The use of Google user data is limited to the identity purposes described here, including the applicable Google API Services User Data Policy requirements.
The current application has no advertising integration, contact enrichment provider, conversation recording, AI transcription, or CRM synchronization. A later feature that changes data use requires an updated notice and its own authorization where applicable. Google account data is not used by the current application for advertising or AI model training.
Your controls and retention
You can edit your saved professional details, remove individual records through the available controls, and export supported card/contact data. The in-app whole-account erasure action is currently disabled while its provider and operational acceptance is completed. Request whole-account deletion through the operator's contact page. Identity verification and review are required; the present release does not offer a verified automatic completion time or a finalized backup-expiry period.
Saved records are retained until removed or handled through the applicable verified deletion process. Previously downloaded files, browser-held offline copies, other people's received contacts, company-owned records, provider records, security records, and recovery backups may require separate handling. Ask the operator for the scope and status of a specific request. This notice will be updated when those operating limits change.
Authentication uses provider-managed cookies and session mechanisms. Prepared offline cards use browser storage after a user action. The current application does not install an advertising tracker.