Privacy Policy

KMSTRY is operated by Bright Minds Hub Marketing Management LLC, Office 2703, Concord Tower, Dubai Media City, Dubai, United Arab Emirates. In this policy, “KMSTRY”, “we”, “us” and “our” refer to that company.

For privacy questions or requests, contact adops@brightmindshub.net. Our contact telephone is +971 4 494 1211. Please do not send passwords, verification codes or unnecessary identity documents by email.

This policy covers the KMSTRY app, personal and venue accounts, and our associated account, invitation, support and legal-document web pages. A venue may separately be responsible for information it obtains and uses for its own business purposes. Its independent activities are not made lawful simply by using KMSTRY.

KMSTRY is for adults aged 18 or older. An adult-only service still needs safeguards against child abuse and exploitation; see our Child Safety Standards.

The information collected depends on the features you use.

We do not import your address book or read your device calendar as part of these features. Adding an event to a calendar does not give us general access to that calendar. We do not receive Face ID or fingerprint templates.

Public video uploads and venue-verification video submission are not currently available. This does not mean that private messages, document uploads or any pre-existing records cease to be personal information. If we introduce materially different processing, we will update the relevant notice and obtain permission where required before it starts.

We use information to create and secure accounts; provide profiles, venue discovery, check-ins and messaging; manage venue teams and events; deliver requested notifications; investigate abuse and enforce our rules; answer support and privacy requests; and maintain and improve reliability.

Location is used for nearby discovery and to check whether a check-in is eligible at a venue. KMSTRY does not continuously track your location in the background. Previously received coordinates and check-in history can remain stored after location permission is withdrawn; stopping future collection is different from deleting existing records.

Account-linked venue discovery analytics is a separate, optional choice, off by default. If enabled, it can connect discovery activity to your account. Turning it off removes account identifiers from retained search-event records; unlinked records and aggregate results may remain. “Unlinked” does not mean that every record is necessarily anonymous under every law.

Marketing email enrolment is not currently available. Account verification, security, team invitations, requested exports and other necessary service emails are distinct from marketing communications. We do not sell personal information.

We process personal data in accordance with applicable data-protection laws, including the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) where it applies. The legal basis depends on the processing and the law that applies. It may include your consent, steps necessary to provide a service you request, compliance with a legal obligation, or another exception expressly available under the applicable law. We do not treat acceptance of our Terms as blanket consent to every use of personal information. Any legitimate-interest basis under a law that recognises it requires a separate assessment; it is not assumed to apply to all users or all processing.

Personal profiles and activity

Profile details and approved content can be visible to other users eligible to access the relevant discovery, profile, check-in or story feature. Do not put confidential information in a public-facing profile or upload content you do not have permission to share.

Your full date of birth is private account information used for age eligibility and your own account setup. Other-user profile, discovery, check-in and notification responses provide age where needed, not your full date of birth. Access to private account information by authorised administrators is restricted to their account-management and safety responsibilities.

An active check-in can reveal your presence at a named venue, with profile information, interests and Moments as the feature permits. Eligible connections can access personal stories in supported circumstances without being physically at the same venue. Precise GPS coordinates are not ordinary public profile or venue-guest display fields, but the venue and time can still reveal where you were.

Anonymous Mode changes visibility in supported features. It does not make you anonymous to KMSTRY, erase your history or conceal information you deliberately disclose in a message or other content.

Venue accounts and staff

We keep registration names separately from public profile names to identify account holders, support venue team membership and prefill profile setup. Authorised members of a venue's team can see a member's registration name; the member's date of birth is not shown in team lists. Prefilling a personal profile does not itself publish that name.

Accepting a venue team invitation does not itself submit public content to AWS. Safety-check permission is requested when the account holder first chooses a feature that needs that processing. It applies to that person's personal and venue activity on the same account, not to other team members. Deferring personal-profile setup does not complete or activate that profile; the person can return to their venue account and resume setup later.

Venue profiles, approved venue stories, gallery images and event information can be visible on public-facing venue surfaces. Authorised venue staff can access guest and business information according to their role. This can include non-anonymous active guest profile details and eligible stories, rather than only totals. Staff may access authorised venue functions remotely.

Venue activity and staff access controls are separate from the optional account-linked discovery analytics setting. A venue operator must use information obtained through KMSTRY appropriately and must not attempt to identify anonymous guests or use guest information for unauthorised outreach.

Messages and private documents

Messages and attachments are shared with their intended recipients, subject to applicable service and safety access. Private venue-verification documents are restricted to authorised processing and review, not published as venue photos. These services are not end-to-end encrypted. Authorised personnel may access relevant information when necessary for support, security, moderation or lawful requests.

Recipients may keep screenshots or copies. Deleting content from KMSTRY cannot guarantee removal of copies already made outside our control.

We use Amazon Web Services (AWS) to assist with safety checks of public-facing content. Amazon Rekognition analyses submitted image data for visual safety signals and detects text in images. Readable extracted text, supplied text overlays and text fields routed through public-text moderation are evaluated using Amazon Bedrock Guardrails. This can include profile names and bios, check-in text, venue descriptions, and event or offer text. A sign-in provider's display name may also be processed when it is used to create a public profile.

These checks send the relevant content to AWS. The content itself may contain personal information; sending image bytes without an account name does not make an image anonymous. We associate the resulting decision and safety signals with the relevant content in KMSTRY. This public-content pipeline is not a statement that all private conversations or entire private business documents are routinely submitted to the same AWS checks.

Automated results may approve content, prevent its publication, or send it for human review. Unreadable text, an uncertain result or a processing failure can delay publication without establishing a policy violation. A preview visible only to its uploader is not evidence that other people can see it. For an initial check-in, a required Moment must pass the relevant checks before the check-in provides room access.

Authorised reviewers can inspect relevant content and safety information to make or review a decision. You can ask us to reconsider a restriction through the available reporting or support route. Automated tools are not infallible, do not prove that an image is lawful, and do not reliably determine a person's age or detect every instance of child sexual abuse material.

Your permission and choices

Before content is first sent to AWS for these checks, we explain the content involved, the provider and purpose, and ask for explicit permission. Declining does not require you to surrender access to account management, privacy requests or deletion. Features that require the affected public-content processing cannot complete without that permission. If you later choose such a feature, you can reconsider then; permission is not requested for every subsequent upload. You can withdraw permission through the available privacy controls or contact us for help. Device camera, photo-library and location permissions remain separate. Withdrawal stops subsequent processing covered by that permission, including queued work not yet sent, but cannot recall data already transmitted or undo processing lawfully completed. Separate legal obligations, including responding to a valid safety or legal request, are not cancelled by withdrawing an optional permission.

Provider retention and secondary use

We have configured our AWS account to opt out of the use of our content for improvement of supported AWS AI services, including Rekognition. This is separate from processing necessary to provide the requested service. It is not a promise that every operational record is immediately deleted or that every provider operation occurs in one country. The safety checks described here are not a KMSTRY face-recognition or identity-matching service.

We use providers to operate the functions described in this policy. Depending on the environment and enabled features, these include:

We may also disclose information to authorised professional advisers, an authority where legally required or justified, or parties to a business reorganisation with appropriate safeguards. A report can require sharing relevant information with authorised safety personnel or an appropriate authority. It does not authorise unrestricted public disclosure of a reporter's identity.

Provider photos remain third-party content. A request to hide a Google-sourced photo in KMSTRY is not a request that automatically deletes it from Google Maps.

Google Maps and Places features are also subject to the Google Privacy Policy, incorporated here for those features. Google describes the information it receives and how it uses it in that policy. This does not replace KMSTRY's responsibility for its own processing.

We operate from the UAE. Our current primary media-storage configuration uses Frankfurt, and the AWS moderation requests described above are directed to the Frankfurt region. Providers' support, delivery networks and subprocessors may process information in other countries, including the United States. These regional settings do not mean that all information stays in Europe.

For international processing, we apply the transfer requirements that govern the information involved, including appropriate contractual safeguards or another permitted transfer basis where required. You may contact us for information about the arrangements relevant to your data. A destination's privacy laws may differ from those in your country; no part of this policy makes every provider's activities identical to KMSTRY's own processing.

Visibility, expiry, deletion from active systems, and backup expiry are different processes.

• Account and profile information is generally kept while needed to provide the account, then removed through the applicable deletion process, subject to justified legal or safety exceptions.
• Check-ins normally expire after three hours and can end earlier. Personal stories are linked to their check-in lifecycle; venue stories normally expire from viewing after 24 hours. Expiry does not itself promise immediate physical erasure of every related record or copy.
• Historical check-in records, including their venue, timestamps and coordinates, are deleted from active systems through scheduled daily cleanup after 12 months from the check-in's creation. Last-known location is replaced when a new location is received and otherwise cleared through scheduled daily cleanup after 12 months from its last update. These records are removed earlier when you delete your account, subject to the limited safety and legal exceptions described below. A check-in needed for an open safety case or a valid preservation requirement may be retained with restricted use until that need ends; the cleanup then rechecks it. Deletion also removes the check-in from personal history and may affect historical venue statistics. Backup expiry is separate.
• Deleted messages and chats hidden by both participants are removed through scheduled cleanup after the applicable 30-day retention period. For messages, the period starts when the message is deleted; for chats, it starts when both participants have hidden the chat. A message still retained by another participant or a copy outside KMSTRY is a separate matter.
• Generated export archives expire after 96 hours, or 48 hours when precise location history is included. Minimal export-request audit records can be retained for up to 24 months, subject to earlier deletion in applicable account-deletion paths.
• Moderation records are distinct from the underlying media. Media decision records become eligible for scheduled cleanup 90 days after the source is removed. Text-decision records become eligible 90 days after their creation. Relevant open cases or legal obligations may justify longer retention with appropriate access limits. The timer for a media decision does not begin while its source remains in use.
• Deleting an account detaches it from retained safety reports without creating a copy of its name, email or date of birth in those reports. Reports and the selected evidence can still contain information relevant to an investigation; they are not necessarily anonymous. Open reviews remain protected. Detached reports become eligible for scheduled cleanup 90 days after both account deletion and case closure, unless an authorised, reasoned preservation period remains active. Reports supporting an active content restriction are retained while needed to manage that restriction. Evidence files are deleted only after checks confirm that no live content or retained report still needs them.
• Where we use our temporary AWS storage for moderation inputs, those copies are subject to a one-day lifecycle-expiration rule. Scheduled storage deletion is not a promise of physical erasure at exactly 24 hours, and this rule does not describe every operational record held by AWS or the original content stored by KMSTRY.
• Venue-verification, support, security, legal-acceptance and business records are kept for the purpose and applicable obligations involved. Deleting a personal profile is not necessarily the same as deleting an entire account or a venue's legitimate business records.
• Backup copies are separate from live service data and are retained only for the recovery cycle and applicable obligations. Information removed from live systems is not immediately removed from every backup. Access is restricted, and a recovery must respect previously completed deletion requests.

If information must be retained for a specific legal obligation or justified safety case, we limit access and use to that purpose and review continued retention. Such an exception is not permission to retain every part of an account indefinitely. An account or content deletion request does not override a valid preservation requirement; unrelated information remains subject to the applicable deletion process.

Depending on the applicable law, you may request access, correction, deletion, a copy or transfer of your information, restriction of processing, or object to particular processing. Where processing depends on consent, you may withdraw it without making earlier lawful processing unlawful. Some requests require proportionate identity checks; we do not need your account password or email verification code by email.

Available app controls include supported visibility and notification preferences, the optional account-linked analytics choice, and personal or authorised venue data exports. Device settings control operating-system permissions. Turning off a device permission may prevent the corresponding feature from working without preventing unrelated account functions.

Self-service exports are scoped to the requesting person's account and venue authority. They exclude credentials and information that would expose another person's private data or a reporter's identity. A self-service message export is not necessarily a complete copy of all received messages. Contact us for a manual access request where necessary; we may need to redact other people's information.

Use the app's account-deletion function to delete the whole account, or the account-deletion page linked from our website and store listing if you cannot use the app. The web process uses email confirmation. Removing a personal profile, leaving a venue team and deleting the whole account have different consequences. If these routes are inaccessible, contact our privacy address.

We respond within the time required by applicable law, explain an applicable limitation or permitted extension, and provide the relevant review or complaint route. You may also have a right to complain to the UAE Data Office or another authority competent under the law applicable to your information. No contractual term removes a mandatory privacy right.

We do not offer KMSTRY to people under 18. If you believe an account belongs to a minor or content involves child abuse or exploitation, use the in-app report function or contact our safety channel described in the Child Safety Standards. Do not send or download suspected illegal images to make a report; provide the account or content reference and a description instead.

We may restrict access while investigating age or safety concerns. Any collection or retention associated with that investigation must have an appropriate purpose and legal basis. An adult-only rule does not mean that automated moderation can guarantee that no harmful content will be encountered.

We use access controls, encrypted network connections and other safeguards appropriate to the services involved. Secure links or restricted storage are not end-to-end encryption, and no system can guarantee absolute security. Where an incident triggers a legal notification obligation, we will address it under the applicable requirements.

Our app and associated account pages use storage needed for sessions, preferences, security and caching. This statement is not a guarantee that an independently operated third-party site, map, sign-in page or our separate corporate website uses no cookies or analytics. Their own notices apply to their processing.

We will publish the effective date and keep relevant legal versions identifiable. Material changes will be brought to your attention through an appropriate service notice. If a change requires fresh permission, we will request it before the affected new processing rather than treating continued use as blanket consent. Acknowledging that you have read this policy is separate from accepting our Terms of Service and from giving a specific optional permission.