Privacy Policy

Updated 14 September 2026

majlis helps you share a digital contact card. This page explains what is stored, what becomes public, and the choices available to you.

Information used to run your account

Google sign-in provides an account identifier, name, email address and, when available, a profile picture. majlis does not receive your Google password. We store your account status, invitation redemption and the details you add to your Professional and Personal cards, including contact details, social links, photos and sharing choices.

We use this information to sign you in, manage invitation access, save your cards, generate QR codes and contact downloads, and respond to support requests. Authentication and hosting services may also process technical logs such as IP addresses, request times and errors to operate and protect the service.

What other people can see

A new card is private until you publish it. Anyone with a published card’s link or QR code can view its name, photo and fields you have enabled for sharing. Downloaded contacts contain those shared details. A public card does not offer a switch to your other card.

Hidden contact fields are excluded from public card responses and contact downloads. The signed-in editing workspace uses account ownership rules. People with administrative access to the underlying services may access stored information to operate and support majlis.

Photos and copies already shared

Uploaded card photos currently use public file links. Anyone who has a photo link can view it, including while the card is private. Unpublishing a card does not disable an existing photo link. Upload only a photo you are comfortable making public; contact us to request removal of an uploaded file.

You can edit or unpublish either card. This changes future access through majlis, but cannot remove contacts, QR images, photos or screenshots already saved by other people.

Services that process information

Google provides sign-in, and Supabase provides authentication, database storage and photo storage. Their processing may occur outside your country, depending on the services and project region. The website’s hosting service also processes requests to serve the app. Links to social profiles open services with their own privacy practices.

Your optional welcome email

If you choose the welcome email when signing up, we share your verified email address with beehiiv to send one message with tips for your new account. beehiiv keeps it as a subscriber record in a separate majlis publication and processes email delivery and engagement information. We do not share your card details with beehiiv or enroll you in general newsletters or conference updates.

The choice is optional and does not affect access to your account. A short-lived cookie carries your choice through Google sign-in and is cleared when sign-in returns. We keep a private account-linked processing record to prevent duplicate welcome requests. You can unsubscribe using the email footer or contact us to request deletion of your beehiiv record. Deleting your majlis account does not automatically delete the separate beehiiv record.

Trying a card before sign-up

The demo builds your card and QR preview in your browser. Selecting Continue keeps a temporary draft in that browser tab so it can follow you through sign-in and invitation activation. It expires after 12 hours and is cleared when you discard it, save it to your account, or sign out. The demo QR contains no entered contact details and links back to the demo. Your details are added to your account only when you save the card.

Cookies and this device

Essential session cookies keep you signed in. The app saves QR images and their card links on your device so you can present them offline after opening the dashboard. Signing out clears those app-stored QR codes on this browser. QR images you download separately remain in your files.

Optional Google Analytics loads only when it is configured and you choose to allow it. It records page types and clicks on card tabs, QR downloads, contact downloads and sign-up invitations. We replace individual card addresses with a generic card page and do not include card names, contact details or social links in these events. Google also processes technical information and analytics identifiers to measure visits. Your choice is stored on this browser. You can change that choice below. Essential authentication and service logs do not depend on analytics consent.

With the same optional analytics choice, majlis also counts public card visits and Save to contacts clicks in hourly totals. These totals distinguish QR-marked links from other links and signed-out visits from member visits; they do not store names, card addresses, account IDs or visitor identifiers. The card address is used briefly to check that the card is published and exclude signed-in owners, then discarded from these counters. We separately retain aggregate account and card creation totals to operate the service. Aggregate totals can remain after an account is deleted.

Retention and your choices

Account and card information remains stored while your account exists; unpublishing hides a card rather than deleting its data. Replacing a photo does not automatically remove earlier uploads. You can request access, correction, export or deletion by emailing us from your account address. We may need to verify your request. Service logs and backups follow the relevant provider’s retention settings; deletion from active records may not immediately remove backup copies.

Contact for support.