Skip to main content

Privacy policy

Last updated: 12 November 2026

We process personal data to provide, secure, and improve Ticket Window. Payment card details are handled by payment providers and are not stored directly by Ticket Window.

1. Data we collect

  • Account data, including name, email address, and phone number.
  • Transaction and booking records needed to provide the service.
  • When you book a medical appointment, we collect the name and contact details associated with the booking, the selected service, the appointment date and time, and any optional notes you choose to provide. These details may reveal information about your health.
  • Usage data, including visits and interactions with the platform.
  • Device data, including browser type, operating system, and IP address.

2. How we use data

  • Provide and improve platform services.
  • Process bookings and payments.
  • Send booking confirmations and important account notices.
  • Support accounts and respond to requests.
  • Analyze platform use and protect service security.

3. Data sharing

We do not sell personal data. Data is shared only with the relevant merchant, service providers needed to operate the platform, when legally required, or with user consent. We make your medical appointment details and any notes you provide available to the merchant providing the service so they can manage your booking.

4. Security

  • Encrypted connections using TLS.
  • Access controls and security monitoring.
  • Operational backups and recovery procedures.
  • Payment processing through approved payment providers.

5. Your rights

  • Request access to your personal data.
  • Correct inaccurate account information.
  • Request deletion where applicable.
  • Opt out of marketing communications.

6. Cookies

We use cookies and similar technologies for essential sessions, preferences, security, and service improvement. Browser controls can be used to manage optional cookies.

7. Customer sign-in with Google and Apple

When you choose customer web sign-in with Google or Apple, we receive the provider account identifier and available name and email address to sign you in and link your customer identity. We protect identity links and necessary authorization credentials, retaining them and handling deletion requests under the existing account-deletion policy. This option is for customer accounts.

8. Adding tickets to Apple Wallet and Google Wallet

When you choose to add a ticket or booking to Apple Wallet or Google Wallet, the selected Wallet provider receives the fields needed for the pass, such as booking or event details, its QR code and the ticket-holder details shown on it. The copy saved with the provider is subject to its privacy policy and your account settings with that provider.

Data used by the customer and merchant apps

App data-practices clarification dated 31 October 2026.

This clarification covers the Ticket Window customer and merchant apps and service pages opened within them. The data involved depends on the account, feature, merchant settings and permissions in use.

Email may be used to send marketing campaigns, and the name may be used to help select recipients according to the campaign settings. You can unsubscribe or stop promotional messages through the available controls, or contact support to request that they be stopped.

Accounts, bookings and messages

We process account contact details and identifiers to provide sign-in and account services. Booking, ticket, sales and payment records support the transactions you use. When you use an available in-app conversation, its text, participants and read/time information are processed and stored by the service. A booking or conversation addressed to a merchant makes the related details available to that merchant.

Devices and notifications

The apps use Firebase Cloud Messaging and installation/device identifiers for messaging and service operation. Messaging can initialize before sign-in. An account device registration can include a notification token, app version, language and time zone. Your device settings control notification display; that control is separate from all installation and technical data processing.

Payment information and submitted files

Supported checkout flows use payment services. The service can receive transaction identifiers, status, amount and limited payment-method information, such as a card’s last four digits. An optional saved-method feature can retain a provider token and masked method details. Available bank-transfer flows can ask for a reference and a proof image or PDF. Authorized merchant pages can accept event images and bank-account details. These data are associated with the relevant account, transaction or business feature.

Automatic translation

Merchants can manage automatic translation in language settings. When enabled, an uncached translation can send the text and language context to DeepSeek for processing. Translation dictionaries and service request/response logs can retain related text. This describes selected translation content; it does not state that every chat, payment or uploaded document is sent to that service.

Service providers and security

Operating the features can involve hosting, messaging, transactional communications, payment and translation providers. Processing by a provider is subject to the applicable service terms and privacy information. We use account and technical information to operate and protect the service. The type of data involved and the recipient depend on the feature used.

Account deletion and retained invoices

The account-deletion policy effective 29 October 2026 below sets a 10-business-day fulfillment period after receipt of a request, with ownership verification before action. Invoices and evidence required to support them are retained for at least 10 years from issue, with restricted access; a specific legal requirement or documented hold can require longer retention. This invoice rule is not a ten-year retention rule for every account, message or uploaded file. Request receipt and confirmed deletion are separate states.

Account deletion and invoice retention

This account deletion policy applies from 29 October 2026 and supplements the privacy information on this site.

When deletion is completed, sign-in access is disabled and existing sessions and notification device registrations are revoked or removed. Personal profile and contact details, including your name, email address, phone number and profile image, are deleted or irreversibly anonymized. Retained invoice data is handled separately below.

We complete account deletion within 10 business days of receiving your request. Account ownership must be verified before deletion is carried out.

Business days are Sunday, Monday, Tuesday, Wednesday, Thursday, excluding announced public holidays, in Asia/Riyadh time. The day we receive the request is not counted.

Invoices and the information required to substantiate them are retained for at least 10 years from the invoice issue date for accounting and legal obligations, with restricted access. A specific legal obligation or documented legal hold may require longer retention. This does not keep your personal account active or permit sign-in.

Deleting a merchant user’s personal account does not by itself close the merchant business or delete other staff or customer accounts. For a business owner, ownership transfer or business closure requires a separate authorized process.

Submitting a request does not mean the account has already been deleted. We confirm completion only after processing and explain any data that must be retained under the policy or a specific legal requirement.

How to request account deletion

Have questions?

Contact us if you need help understanding this page.

Contact us