Privacy policy: Tour Booking & Timed Tickets
Last updated: 15 November 2026
This policy explains what data the Wix app “Tour Booking & Timed Tickets” (the app), published by Kayabyte, the trading name of Caner Kaya, Stasjonsveien 64, 0771 Oslo, Norway (we, us), processes when it is installed on a Wix site. It adds to the privacy policy for Kayabyte apps for Wix, which also applies. Made by Kayabyte.
What the app does
The app lets a tour operator or attraction sell tickets for departures on their Wix site. Guests choose a date, time and tickets, pay at the site’s Wix checkout, and receive a QR ticket by email and on a tickets page. The operator’s staff check guests in with a link on a phone.
Roles
The tour operator who installs the app is the controller of its guests’ data. Kayabyte acts as a processor that handles the data only to take, confirm, remind, check in and support the bookings the operator receives. Wix.com Ltd. hosts the site, its checkout and its orders and is the source of order data. Cloudflare, Inc. hosts the app’s service and database (Cloudflare Workers and D1). Resend sends the app’s emails. Cloudflare and Resend are sub-processors. Brevo would be added here the day it is switched on; it is not used today.
Data about guests
- Collected by the booking form on the operator’s site: name, email address, optional phone number, optional note, answers to the operator’s own questions (up to 3, Pro), the chosen pickup point, tickets and seats, the time the terms were accepted and which version, a booking code and a ticket link token, the payment status and the Wix order ID and number.
- Passed to Wix: the guest’s name, email and phone are also passed to Wix to create the checkout.
- Not stored: card or bank details. Payment is taken in the operator’s Wix checkout.
- Waitlist (Pro): name, email and seats wanted for a departure. The guest is emailed at most twice, and the entry is deleted 7 days after the departure.
- Check-in records: the booking, the time, how many people arrived and which check-in link (its label) was used. The log itself holds no names.
- Technical data: a keyed one-way hash of a visitor identifier and of the network address is stored with a booking and in short-lived counters for rate limits and abuse protection (not the address itself). Counters are deleted after 2 days, webhook ids after 14 days, the activity log after 90 days and alerts after 60 days.
Data about the operator
Wix site ID and app instance ID, site name and address, currency, time zone, plan and trial state, the owner or business email address (from Wix), the settings and tour content the operator enters, and the staff and guide email addresses the operator enters.
Check-in links and the guide email
A check-in link shows names, seats, phone numbers, pickup points and notes to anyone who holds it, for departures from the previous day to the next day. Links are random and secret, can be revoked at once and can have an expiry date. The Business plan can email a passenger list (name, seats, phone, pickup point, notes) to the guide’s email address the operator enters. The operator chooses who receives the link and the list.
Emails
Emails are sent through Resend from tickets@kayabyte.dev in the operator’s business name. Guests receive a booking confirmation with the QR ticket, a reminder (Pro), a cancellation or move notice, a “seats freed” message (waitlist) and a “tickets again” message. Replies go to the operator’s contact email. The operator receives a digest of new bookings, alerts, cancellation requests and refund tasks; replies to those go to support@kayabyte.dev. Emails contain no tracking pixels. Resend sees the recipient address, subject and body to send them, under its own privacy policy.
Retention and deletion
- Unpaid holds and expired bookings are deleted after 30 days.
- Guest name, email, phone, note and answers are blanked 12 months after the departure. The booking code, counts and amounts stay. The keyed hashes are removed at the same time.
- Waitlist rows are deleted 7 days after the departure.
- Erasure: the operator can erase one booking’s personal data, or all bookings of an email address, in the app at any time. A Wix data removal request for an order erases that booking’s personal data.
- If the app is removed: the site’s data is deleted 30 days after removal and at least 7 days after the last confirmed departure ended, so guests keep their tickets. Refunds made in that time are not applied, because the app can no longer read the shop’s orders. If the app is reinstalled within that time, the data is restored. We keep a small install record (site ID, install and removal times, plan changes) for our own install counts; it holds no guest data, and you can ask for it to be removed.
- Orders and contacts that Wix holds belong to the site and are not touched. A duplicated site starts with no tours or bookings.
Cookies and tracking
The pages on tours.kayabyte.dev (tickets page and check-in page) set no cookies, use no analytics or advertising and load nothing from other sites. Ticket pages are not indexed by search engines and send no referrer. The booking widget keeps the guest’s selection in the browser’s session storage. The privacy link in the widget, the tickets page, the check-in page and the dashboard opens this page.
Logs
Our service logs contain ids and outcomes, no names, email addresses or phone numbers, and link tokens are masked. Cloudflare keeps request logs for a limited time, and they may include the page address and network metadata. Install, removal and plan events that Wix sends (site ID and plan) are copied to Kayabyte’s private usage statistics.
Security
Dashboard calls need a Wix owner or co-owner access token, checked on every call. Calls from the widget carry the site’s Wix instance token. Ticket pages use a random 128-bit link, check-in pages a revocable secret link, and Wix webhooks are verified with the app’s Wix public key. Every query is scoped to one site. Data is encrypted in transit (HTTPS) and stored encrypted by Cloudflare D1. Anyone who has a ticket link can open that booking’s tickets page, so guests should treat it like a ticket.
We do not sell data
We do not sell or rent data, and we do not use guest data for advertising, for our own marketing or for any purpose other than running the app. Data is shared only with Wix, Cloudflare and Resend, as described above.
Honest limits
A QR code identifies a booking and is not an anti-fraud product. Refunds are made by the operator in Wix Orders; the app never refunds money. Guest data that the operator exports (CSV, printed passenger list, guide email) is the operator’s responsibility.
Your rights
Guests should contact the tour operator first about their data. For questions about this policy, or to exercise rights under the GDPR, contact support@kayabyte.dev. We support erasure and export requests from operators.
Changes
We will update this page if the app’s data handling changes. The date at the top shows the latest version.