BirthdaySmile
LEGAL

Privacy policy

BirthdaySmile uses information to provide personalized digital birthday cards, keep the service secure, support payments, and improve how the service works. We do not sell or rent personal information, and we do not use card content for advertising.

Information we use

We use this information to provide the features you request, maintain and improve BirthdaySmile, communicate about your account or order, and protect the service. Never send us your bKash or Nagad PIN, account password, or one-time verification code.

Cards, links, and passwords

Your card is stored so you can create, manage, and share it. When sharing is enabled, the card link or QR code opens the card for its recipient. Anyone who has the link may be able to access it unless you use the optional password protection. A password adds a layer of protection for recipients; keep it private and send it separately from the link. Do not include information in a card that you would not want its intended recipients to receive.

Product analytics

First-party product analytics records page views and selected actions, including card creation starts, completions and failures; template selections; sign-in and sign-up starts; card openings and sharing; QR downloads; and checkout, order-creation and payment-submission milestones. These events measure usage and milestones; they do not record every button click.

Analytics uses a random, HttpOnly session identifier that expires after 30 minutes. It does not associate events with an account identifier. Page-view data may include a normalized page or landing-page path, referring site hostname, limited campaign values, and country-level information when supplied by Vercel. Advertising click identifiers, full URLs, and unrelated query parameters are not stored. Analytics does not collect card messages, names, photos, passwords, authentication tokens, payment credentials, or transaction references. Events are retained for up to 13 months.

Meta Pixel

When the site operator enables Meta tracking, BirthdaySmile sends PageView events on selected public pages and ViewContent events when you select a birthday-card design. Meta Pixel may also receive the page location, referrer, IP address, browser and device information, and other technical data described in Meta's own policies. The operator must keep tracking disabled unless an appropriate legal basis and any required permission have been established. A configuration switch is only a technical control; it does not establish legal authorization.

Meta's Events Manager can have automatic event collection settings that are separate from this code. The site operator should review those settings before enabling tracking. Disabling tracking in BirthdaySmile stops future code-managed Pixel events but does not remove cookies already stored by Meta or erase information Meta may already have received.

Meta Purchase measurement

If Meta tracking and its matching-data setting are enabled after the operator has established an appropriate legal basis and any required permission, a server-side Purchase event may be sent after a bKash or Nagad payment is verified. It includes the verified amount in BDT, payment timestamp, a stable order-based event identifier, and a generic product identifier. Where appropriately authorized and available, matching fields can include SHA-256 hashes of normalized email, the order's verified wallet phone, and account identifier; valid Meta browser cookies; and a trusted platform-provided IP address and browser User-Agent. Matching fields are optional and are omitted when unavailable or invalid. Card content and payment credentials are not sent.

Purchase matching data is kept only for the delivery window (up to 30 days from order creation) and is removed earlier after delivery or terminal failure. A payment verified after that window is not eligible for a Purchase event. Meta may process received information under its own terms and privacy policies. This site cannot independently determine whether a visitor's data may lawfully be sent; enabling a server setting does not itself create that permission or legal basis.

When information is shared

We share information only as needed to run BirthdaySmile. Supabase provides authentication, database, and storage services; Vercel hosts and delivers the site; Resend delivers transactional emails; and, only when Meta tracking is enabled, Meta receives the events described above. If you choose Google sign-in, Google processes the information needed for that sign-in. These providers handle information under their own terms and privacy policies. Card information is made available to recipients when you enable sharing. We may also disclose information when required by law or when reasonably necessary to protect users, investigate abuse, or secure the service. BirthdaySmile does not sell or rent your personal information.

Retention and your choices

We keep account, card, order, and payment information for as long as needed to provide and protect the service, maintain sharing access, resolve support or payment issues, and meet applicable record-keeping needs. Card availability follows the expiry date shown in the service. Some order or payment records may remain after a card expires. You can disable browser storage or use browser privacy controls; doing so may limit analytics attribution and does not erase events already recorded.

BirthdaySmile does not currently provide an automated account-deletion feature. To request account deletion or ask about your information, email birthdaysmile.official@gmail.com or syedshadnanmozammel@gmail.com. We will review the request and explain any steps needed. Some records may need to be retained for payment history, security, or other legitimate record-keeping purposes; cards linked to payment history may be archived rather than erased. We do not promise a specific completion deadline or permanent deletion of all copies.

Contact and updates

For privacy questions, email birthdaysmile.official@gmail.com or syedshadnanmozammel@gmail.com. We may update this policy as BirthdaySmile changes. The current version will be posted on this page.