Privacy policy: Copy Bookings to Another Site

Last updated: 12 November 2026

This policy explains what data the Wix app “Copy Bookings to Another Site” (the app), published by Kaya Byte, org.nr 938 851 883, trading as Kayabyte, 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.

What the app does

The app copies a Bookings setup (services, categories, booking policies, staff members, working hours and class and course sessions) from one Wix site to another Wix site, when the owner of both sites asks it to by showing a pairing code on the first site and entering it on the second.

Roles

The site owner is the controller for the data in their Wix sites. Kayabyte acts as a processor that handles the data only to carry out the copy the owner asked for. Wix.com Ltd. hosts the sites and the app’s dashboard page. Cloudflare, Inc. hosts the app’s copy service and its database and is a sub-processor.

Data the app reads

From the site that shows the code: services, categories, booking policies, staff members (name, email, phone, description, photo, working hours), the sessions of classes and courses, and service images. From the site the setup is copied into: the names of its existing categories, policies, staff and services (and staff emails), to skip what is already there, its working-hours entries (to avoid duplicates), its plan and payment currency. The app does not read or copy bookings, customers, contacts, members or payments.

Data the app stores

The copy service keeps these records: - Pairing codes, with the app instance IDs and site IDs they belong to and when they expire. - For each copy: the two app instance IDs and site IDs, the target site’s name, its status and counts, the last check’s summary (counts, and the names and reasons of services that cannot be copied) and how long the link between the sites lasts. - For each item in a copy (category, policy, staff member, service, hours, sessions): the ID on both sites, its name, whether it was copied, with the reason or a note if something was left out. While a copy is running, the source record of a booking policy or staff member (including the staff email and phone) is held so the copy uses one consistent snapshot; it is removed when that item is finished, and at the latest 30 days after the copy last changed. - For each image of a service in a copy: the image’s address on the first site and its file ID on the second. - Per site, for as long as the app is installed or longer: the number of services copied into it (so plan limits stay correct), the last plan we saw for it, and whether the one-time review note was answered. - Failed pairing attempts (instance ID and time), kept one day.

Service descriptions, prices and other content pass through the service during the copy. Images are imported by Wix into the second site’s Media Manager.

Retention and deletion

Copy records are deleted 30 days after the copy last changed. Pairing codes are deleted 7 days after they expire, whether or not they were used. The per-site counter, last plan and review-note answer described above are not deleted by this clean-up; email us to have them deleted.

Logs

The copy service writes technical log lines (the app instance ID, the request path, the outcome, and for a failed item its ID and the error). Logs contain no customer data and are kept by Cloudflare for a short time.

Plans and payments

Paid plans are sold and billed by Wix. We never receive card details.

Cookies, tracking and third parties

The app sets no cookies on the site and uses no analytics, advertising or tracking services. No data is shared with third parties other than Wix and Cloudflare, as described above.

Your rights

For questions about this policy, or to exercise your rights under the GDPR, contact support@kayabyte.dev.

Changes

We will update this page if the app’s data handling changes. The date at the top shows the latest version.