Privacy and data use

Privacy, with clarity.

This notice explains the data Taggz uses, why we use it, and the controls available to you, including for face matching and optional analytics.

Effective August 16, 2026Face matchingAnalytics controls

Face matching is specific to events

A face enrollment creates a face template used to look for you in photos uploaded to relevant Taggz events.

Analytics are optional

You can allow or decline optional analytics. They do not include names, emails, face data, event codes, or private links.

You keep meaningful control

You can skip face enrollment, remove a saved face profile, and request access, correction, or deletion of personal data.

1. Who we are and what this notice covers

Taggz is an event-photo platform operated by The Mok Company. In this notice, “Taggz”, “we”, “us”, and “our” refer to the people and systems operating the Taggz platform.

This notice explains how we handle personal data when you visit taggz.app, create or join an event, upload or access event photos, use payment features, or choose to use face matching. An event host may make their own choices about an event and its access settings. Where a host independently determines why attendee or event data is used, their own privacy information may also apply.

2. Personal data we may collect

We collect the data needed to run the service and protect it. What we collect depends on how you use Taggz.

  • Account and event information, such as your name, email address, phone number, role, event details, invitations, and access settings.
  • Event media and related information, such as photos you upload or access, file and upload details, event association, and access activity needed to operate galleries.
  • Face data, only when you use face enrollment or face matching. This can include your enrollment selfie and a derived face template or embedding used to compare your face with faces detected in relevant event photos.
  • Payment and billing records, such as payment status, transaction references, and receipts. Card details are handled by the payment provider during checkout and are not intended to be collected as full card details by Taggz.
  • Technical and security information, such as browser, device, IP-address, log, and error information needed to secure, operate, and diagnose the platform.
  • Optional analytics information, only if you allow it through the analytics controls. Our optional analytics implementation is designed to exclude names, email addresses, face data, event codes, and private links.

3. Why we use personal data

We use personal data to provide the platform, set up and manage events, authorize access, deliver galleries, support customers, process payments, prevent misuse, maintain security, meet legal obligations, and improve the service where optional analytics has been allowed.

Depending on the activity, processing may be necessary to provide the service you request, meet a legal obligation, protect our legitimate operational interests, or rely on your consent where consent is the appropriate basis. We do not use consent as a shortcut where another lawful basis is required.

4. Face matching and face data

Face matching may be available for an event when the host has enabled that feature. When you choose to enrol, Taggz uses the enrollment image to create and maintain a face template or embedding for photo matching. The matching feature is intended to help you find relevant event photos, not to make decisions about employment, credit, insurance, housing, identity verification, or advertising.

Face enrollment is a distinct feature. You can choose not to enrol where the feature is optional, and you can remove a saved face profile from the face-enrollment area. Removing it stops future matching that depends on that profile. It does not by itself delete your account or event photos you may otherwise be entitled to access.

This privacy notice is not itself a face-data consent request. Where consent is required for face-data processing, Taggz should request it separately, clearly, and for the specific matching purpose before the enrollment is submitted. We do not send face data through optional analytics.

5. When we share personal data

We do not sell personal data. We share data only where it is needed to provide Taggz, meet a legal obligation, protect rights and security, or complete a corporate transaction such as a reorganization.

  • Event hosts, photographers, attendees, and other authorized participants, according to the access controls and settings for the relevant event.
  • Service providers that help us run Taggz, including hosting, storage, communications, security, technical support, and payment processing providers. They may process data only for the services they provide to us and subject to appropriate contractual or legal safeguards.
  • Authorities or other parties where disclosure is required by applicable law, a valid legal process, or is necessary to protect people, rights, property, or the integrity of Taggz.

6. How long we keep data

We keep personal data only for as long as it is reasonably needed for the relevant service, event access, security, legal obligation, dispute, or recordkeeping purpose. There is not one universal retention period for every event photo or account record because hosts, event settings, and service plans can differ.

  • Account information is generally kept while your account is active and for a limited period afterwards when needed for support, security, accounting, or legal purposes.
  • Event photos and associated metadata are kept according to the applicable event settings, host arrangement, and service purpose. We may delete or de-identify them when they are no longer needed.
  • A face profile is kept until you remove it, your account is deleted, or it is otherwise no longer needed for the matching purpose. Technical backups and security records can persist for a limited additional period before expiry or overwrite.

7. Your choices and rights

Subject to applicable law, you may ask to access, correct, update, delete, or receive information about your personal data. You may withdraw consent for a consent-based activity at any time. Withdrawal does not affect processing that was lawful before the withdrawal, and it may mean that a feature such as face matching can no longer operate for you.

You can decline optional analytics in the analytics controls. You can remove a saved face profile in the face-enrollment area. For another privacy request, contact us using the details below and include enough information for us to safely identify the account or event involved.

8. Analytics and cookies

Taggz asks separately before enabling optional analytics. You can choose Allow analytics or Decline, and you can reopen those settings at any time using the analytics-control button on the site. Essential technical storage may still be used to remember your privacy choice, keep the platform secure, and deliver requested features.

9. Security and international processing

We use technical and organizational measures intended to protect personal data, including access controls and security monitoring. No online service can guarantee absolute security, so please use a strong password and contact us promptly if you believe your account has been accessed without permission.

Taggz and its providers may process data in Egypt and in other countries where our service providers operate. Where a transfer is required, we take steps intended to apply the safeguards required by applicable law.

10. Children’s data

If you are under 15, do not submit face data unless your parent or legal guardian has provided the consent required by applicable law. Hosts and guardians should contact us if they believe a child’s data has been provided without the required authorization.

Privacy requests

Need help with your data?

Email us with “Privacy Request” in the subject line. We may ask for enough information to protect your account before acting on a request.

info@taggz.app

We may update this notice when our services or processing change. The latest version will always appear on this page with its effective date.