Privacy Policy

How we collect, use, and protect your data on Brand Card

Introduction and Scope

This Privacy Policy explains how the Brand Card platform collects, uses, shares, and retains your data when you use our website and app, and what rights you have over that data and how to exercise them.

This policy applies to everyone who uses Brand Card, whether you register with an email and password, sign in with an external account such as Google, Facebook, TikTok, or Snapchat, or verify a phone number through Firebase Phone Authentication.

This document covers privacy only. The rules for using the platform and account responsibilities are set out in a separate Terms of Use document, and requests to delete your account or data are covered in a separate Data Deletion page.

Who We Are

Brand Card is a digital platform for selling top-up cards and digital products, along with an associated wallet and payment system, a loyalty/cashback level program, and an optional agency (referral commission) program.

When you use the platform, you are interacting with the operator of this store under the name Brand Card, which is responsible for processing your data as described in this policy.

Effective Date, Last Updated, and Version

This section states when the current policy took effect and when it was last revised, so that any user or external reviewer (such as a login-provider review team) can confirm they are reading the currently approved version.

Data You Provide Directly

When you create or complete your account, you may provide the following data yourself:

  • The display name on your account.
  • Your email address (when registering with email and password, or when an external login provider agrees to share it).
  • Your phone number, which also doubles as your WhatsApp contact number when needed.
  • Your password, stored hashed using the Argon2 hashing algorithm — no staff member or system can ever read it as plain text.
  • The country and currency you select when completing your account details; your currency is locked after your first choice and only changes through a specific administrative process under defined conditions.
  • Your gender, and a profile photo and cover photo if you choose to upload them.
  • A referral code or agency code, if you used one at registration.

Accounts created purely through social login or phone verification may hold no stored password at all, since sign-in in that case relies on the external identity provider rather than a password we store.

Data Collected Automatically

While you use the platform, a limited set of technical and security data is collected automatically, including:

  • Your IP address and browser/app identifier (User-Agent) with every login attempt.
  • A log of successful and failed login attempts, used to detect intrusion attempts and repeated password-guessing.
  • A log of phone verification attempts through Firebase, used only to detect abuse.
  • An administrative audit log of actions taken on your account by the store's admin team (such as cancelling an order or adjusting a balance), which records the IP address and browser used at the time of the action.
  • A hash of your session refresh token and its expiry date, used to manage login/logout across devices, without ever storing the token itself in a readable form.

The platform does not currently use any third-party analytics, advertising, or marketing-tracking tool (such as Google Analytics or Meta Pixel). Any future addition of such a tool will be explicitly disclosed here before it is enabled.

Orders, Wallet, and Financial Transaction Data

To fulfill your purchases and manage your balance, we collect and generate the following data:

  • Details of each order: the product and selected quantity or tier, price, order status, and a unique reference code.
  • Any additional information a specific product requires to complete delivery, such as an account ID inside a particular game or app.
  • The delivery response shown to you (whether from an external supplier or typed in manually by the store's team).
  • Your wallet balance and its complete transaction history: deposits, purchases, transfers between users, refunds, and coins redemptions, each with the balance before and after the transaction.
  • Cash deposit requests: the amount, the payment method chosen, and any text fields required as proof of payment (such as a transfer reference number).
  • Your coins balance and its history (earned from purchases, redeemed, or adjusted by an admin), your account level, and your cumulative purchase total, which determines that level.

Images, Documents, and Payment Proofs

When you make a cash deposit that requires proof of payment, you may upload a receipt image. This image is stored privately and is only ever displayed through a short-lived, signed link when reviewed by the store team or by you, the requester, yourself.

You may also upload an optional profile photo and cover photo for your account, and attach an image as evidence when submitting a report about another user.

No image you upload is ever used for any purpose other than the one it was uploaded for (displaying your profile, reviewing a deposit, or reviewing a report).

Account Verification (Optional)

If you choose to verify your account, we first ask for your explicit consent, then collect only the following:

  • Your full name as it appears on your identity document, the document type and its issuing country. We do not ask for your ID number or date of birth.
  • A photo of the front of the document, and of the back when the document has one.
  • A live capture of your face from the front camera: three frames, and a short clip when your device can record one, while you follow random movements we ask for.
  • When you consented, the version of the consent text, and the IP address and browser used at that time.

The only purpose of this data is to confirm that you own the account before showing the verification badge next to your name. It is reviewed by hand only by Brand Card staff who hold the verification-review permission, and every view and decision is logged. We do not use automated face recognition, do not send these images to any outside provider, never show them or your legal name to other users, and never send them by email or notification.

The images, the live capture and the name are stored encrypted in private storage that is not publicly reachable, and the images are deleted automatically after a set retention period following the decision. If you cancel a request before sending it, or do not finish it within 24 hours, its files are deleted at once. After an approval we keep the verified name and the decision record for as long as the account stays verified.

Verification is entirely optional and not verifying does not affect how you use the store. You can ask for your verification data to be deleted through support or the data deletion page.

Customer Service, Reports, and Complaints Data

Direct customer-service conversations currently take place through the social channels published on the in-app Support page (such as WhatsApp or Telegram, depending on what is enabled). Those conversations are subject to that platform's own privacy policy to the extent they are stored outside our application.

The in-app reporting feature lets you report another user. In that case we store: the reason for the report, an optional text note, and an evidence image if you attach one, linked to both your account and the reported user's account.

Agency, Invitations, and Commission Data

This section applies only if you choose to use the agency (referral-commission) feature, or if you join an agency through an invite link or code.

  • When applying to activate an agency: the proposed agency name, the proposed code, and a snapshot of your name, country, and phone number at the time of application are saved.
  • If you join an agency through an invite code or link, your account is permanently linked to it for commission-calculation purposes.
  • The agency's full balance-movement history (commissions earned, withdrawals, admin adjustments) is kept in full for accounting and audit purposes.
  • External agency withdrawal requests include whatever data the chosen withdrawal method requires (such as an e-wallet number or bank account details).

Signing In With External Accounts

You may choose to sign in or create an account using one of the following identity providers, depending on what the store admin has enabled: Google, Facebook, TikTok, Snapchat, or your phone number via Firebase Phone Authentication. Using any of these methods is entirely optional — email and password remain available as an alternative for as long as it is enabled.

Each provider passes us only the minimum data needed to create an account and recognize you when you return, based on the exact scopes our system actually requests:

Google

  • Your unique Google account identifier (sub).
  • Your email address, only if verified by Google.
  • The display name on your Google account.

We request the "profile" scope, which may include access to your Google profile photo, but Brand Card never reads, stores, or displays that photo anywhere.

Facebook

  • Your unique Facebook account ID.
  • The display name on your account.
  • Your email address, only if Facebook agrees to share it (not always available).

We only request the "email" and "public_profile" scopes — we never access your posts, friends list, or pages.

TikTok

  • Your TikTok open identifier (open_id).
  • The display name on your account.

TikTok's API never provides an email address under this scope, so a technical, non-real internal email is generated for your account for purely technical purposes — we never access your videos or followers.

Snapchat

  • Your unique Snapchat external identifier.
  • The display name you set on Snapchat.

We do not request access to your Bitmoji, profile photo, friends list, chats, or any private content, and we never attempt to reconstruct your Snapchat friend graph in any way. Snap Kit does not provide an email under this scope, so a technical, non-real internal email is generated for your account, exactly as with TikTok.

Phone Number via Firebase

  • Your phone number in international format, after you confirm it with the SMS verification code.
  • Firebase's internal identifier for that verification.

The verification code is sent and validated entirely through Firebase's infrastructure (a Google service) — the code itself never passes through our servers at any point.

  • We never obtain your password on the external provider — we cannot see or store it, because it is never shared with us at all under how these protocols are designed.
  • We do not store the access token or refresh token issued by any external provider after sign-in completes; the token is used momentarily to verify your identity and is then replaced with our own platform session token.
  • Your account with the external provider remains governed by that provider's own privacy policy, independently of this one.
  • You can stop using a given login method at any time, or request that it be disconnected from your account or its associated data deleted, as described in the "Deleting Your Account or Disconnecting a Login Provider" section below.

How We Use Data and Our Legitimate Purposes

We use the data described above only for the following purposes:

  • Creating and operating your account and verifying your identity when you sign in.
  • Fulfilling your orders and processing your wallet transactions.
  • Calculating coins, level, and commissions according to the rules published within the platform.
  • Protecting your account and other users' accounts from fraud, abuse, and intrusion attempts.
  • Contacting you about your account, orders, or transactions when needed.
  • Complying with genuine legal or accounting obligations, when they apply.

Sharing Data With Service Providers and Suppliers

A digital platform like Brand Card does not operate in isolation from every external party. Some data is processed by the technical and operational entities necessary to deliver the service, only to the extent required for each entity's specific purpose, and no further:

  • Hosting and cloud infrastructure providers that run the website, backend server, and database.
  • Login and identity-verification providers (Google, Facebook, TikTok, Snapchat) and the phone-verification provider (Firebase), only when you choose to use one of these methods.
  • External suppliers required to automatically fulfill certain digital products, who receive only the data necessary to complete delivery (such as the account ID required inside the target service), never your full identity or wallet data.
  • Fraud-prevention, security, and technical error-logging services, where used to keep the platform secure.
  • Legal or regulatory authorities, where a genuine, binding legal obligation to disclose exists.

Brand Card does not sell your data to any third party for marketing or advertising purposes, and does not share your data with anyone outside the scope described above.

Cookies and Local Storage

We use only the cookies needed to run and protect sign-in, and we do not use them for advertising or to track you across websites. A login session has two tokens: an access token, valid for 15 minutes, and a refresh token that renews it. Where they are kept differs between the website and the app, as follows.

On the website:

  • Refresh token: kept in an HttpOnly, Secure, SameSite=Strict cookie. The page's scripts cannot read it, and it is sent only to the sign-in paths of Brand Card's server.
  • Access token: kept in the browser's storage, which is local storage (localStorage) normally, or session storage (sessionStorage) when "Remember me" is unticked. It is sent with your requests to Brand Card's server only.
  • The "Remember me" option: shown for email sign-in when the store has it switched on. When unticked, the cookie and the access token end when the browser closes. With the other sign-in methods, the session stays saved on the device until you sign out or it expires.
  • Accounts saved on the device: their sessions are kept in a separate cookie of the same kind for 30 days, sent only to the account-switching paths.
  • Remembering a device for ID sign-in: a cookie of the same kind for 45 days, sent only to the ID sign-in paths.

In the app:

  • Refresh token: kept in the secure storage provided by your device's operating system, not in the app's local storage.
  • Access token: kept in the app's local storage, and sent with your requests to Brand Card's server only.
  • The app does not use cookies to manage your session.

On our servers we keep only a hash of the refresh token, never the token itself. A session ends no later than 30 days after your last full sign-in. When you sign out, we ask the server to end this device's session and clear its data from your device immediately; if the connection fails, we ask again automatically once it returns, and the session stays active on the server until that request succeeds or the session expires.

Local storage is also used to remember your personal preferences, such as your chosen language and light/dark appearance, so you don't have to reselect them on your next visit.

Some external login providers (such as Google or Facebook) may set their own cookies while their own sign-in page is displayed, as may reCAPTCHA by Google during phone verification; those cookies are governed by that provider's privacy policy, not ours.

Data Retention Period and Criteria

How long we keep each type of data differs depending on its purpose and any obligations attached to it:

  • Core account data: kept for as long as your account remains active — that is, until it is deleted at your request or by an administrative decision.
  • Order, financial transaction, and wallet records: kept for as long as necessary for operations, accounting, dispute resolution, and any applicable legal obligation, which in some cases continues even after account deletion.
  • Security records (login attempts, administrative audit logs): kept for a period appropriate to detecting and investigating fraud and abuse when needed.
  • Once a specific piece of data is no longer needed and no legal obligation requires keeping it, it is deleted or anonymized.

This policy does not commit to a single fixed numeric period for every category of data, because that genuinely differs by data type as described above.

Data Protection Measures

We apply a set of concrete technical measures to protect your data, including:

  • Hashing passwords with the Argon2 algorithm before storage, so no password is ever stored as plain text at any point.
  • Temporary account lockout after a defined number of failed login attempts, to block automated password-guessing.
  • Refresh-token reuse detection, which immediately invalidates the session when suspicious reuse behavior is detected.
  • Short-lived, signed links for accessing sensitive files such as deposit receipts, instead of permanently accessible static links.
  • Encryption of sensitive credentials for login providers and external suppliers (such as connection keys) before they are stored in the database.
  • Per-user data isolation, so no request can ever access or act on another user's data.

We do not claim any system is absolutely immune to every risk; the above is an accurate description of the measures actually in place, not an unverifiable general claim.

Your Rights and Choices

As a user, you have the right to:

  • View the core data linked to your account through the account, wallet, and orders pages within the platform.
  • Correct inaccurate personal data.
  • Request a copy of your data, or further clarification about it, through the Support page.
  • Stop relying on a given social login method, as long as another valid sign-in method remains available for your account.
  • Request deletion of your account and data, as described on the separate Data Deletion page.
  • Object to your data being used for a purpose beyond those described in this policy, and contact us about it.

How to Correct Your Data or Request a Copy

You can edit some of your data directly from within your account (such as your name, profile photo, or password), based on what is actually available on the Account and Settings pages.

For data that cannot be changed directly from your account (such as correcting your country or currency after it has been locked, or requesting a full copy of your data), submit a request through the in-app Support page. We will ask you to verify that you are the account holder before acting on any such request.

Deleting Your Account or Disconnecting a Login Provider

The process for deleting your account and data, and for disconnecting a specific login method from your account, is described in detail on the separate Data Deletion page, including what is deleted and what we may retain temporarily for legal or accounting reasons.

Data Transfer and Operating Services Across Countries

Your data may be processed or stored on cloud infrastructure run by hosting and technical-service providers whose data centers may be located in a different country than your own, and likewise when you use global login providers such as Google, Facebook, TikTok, or Snapchat, which may process data on their own infrastructure.

In these cases, we rely on the contractual and technical safeguards those providers offer to protect the transferred data, to the extent available for the type of service provided.

Children's Privacy and Minimum Age

Brand Card's services involve real payments and management of a financial balance, and are therefore intended for people aged 18 and over. The platform does not currently collect a date of birth or any dedicated technical age-verification mechanism at registration; meeting this requirement remains the user's own responsibility when creating an account.

The platform does not knowingly target children. If we determine that an account belongs to a person under the legal age in their country and was created without appropriate parental consent, we will act to delete or restrict that account once this is confirmed through a verified request.

Changes to This Policy

This policy may be updated from time to time to reflect a change in the service, in login-provider requirements, or in applicable law. The last-updated date and version number will always appear at the top of this page, and we will notify you within the platform of any material change that affects your rights.

How to Contact Us About Privacy

For any question or request related to this policy or your personal data, you can reach us through the in-app Support page, or by email at:

privacy@brandcard.online