Privacy policy: Camp & Class Registration
Last updated: 21 November 2026
This policy explains what data the Wix app “Camp & Class Registration” (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. The app is on the Wix App Market; this policy describes the app as built.
What the app does
The app lets the owner of a Wix site (a camp, club or school) let parents register several children for several sessions in one checkout, give each child’s details, medical notes and consents, and pay in full, with a deposit or in instalments. Orders and payments stay in the Wix checkout and Wix Orders; the app keeps the registration records.
Roles
The site owner who installs the app is the controller of the families’ and children’s data: the owner decides which programmes are offered, which questions are asked and who may see the answers. Kayabyte acts as a processor that handles the data only to run the widget and dashboard, keep the registration, payment-schedule and waitlist records, send the emails listed below and support the owner. Wix.com Ltd. hosts the owner’s site and holds the orders and payments.
Sub-processors
- Cloudflare, Inc. runs the app’s service and database (Cloudflare Workers, the D1 database) and sends the app’s emails (Cloudflare Email Service).
- Resend (Resend, Inc.) is our fallback email provider. Emails go through it only if sending through Cloudflare fails. We also use it to send a few help emails to the site owner during a free trial (the owner can unsubscribe with one click).
We will update this page before any other sub-processor is used.
What is stored
- About each family (the parent or guardian who registers): first and last name, email address, phone number, address if the owner asks for it, a second guardian’s name, phone and email if given, the language they used, and a note the owner may add.
- About each child: first and last name, date of birth or grade, gender if the owner asks for it, and a photo consent choice.
- Medical and care notes about each child: allergies, medical notes, medication, dietary needs, doctor, swimming level, emergency contacts (name, phone, relation) and the people allowed to pick the child up.
- Answers and consents: answers to the owner’s own questions, and each consent the parent accepted, with the typed name, the time and a fingerprint (hash) of the consent text shown.
- Registrations and money: programmes, sessions, seats, prices, the payment schedule, payments received and offline payments the owner records, with the Wix order, cart and payment ids, the email used at the Wix checkout (encrypted; it is not used to sign in) and the Wix visitor or member id of the order. We store no card or bank details and no passwords.
- Waitlist and check-in: waitlist entries and offers (answers given when joining a waitlist are kept until the entry is accepted, removed or expires); on Pro and Business, check-in and check-out times per day.
- Sign-in: a hash of each one-time email code (codes expire after 10 minutes) and a hash of each sign-in session (it ends 7 days after sign-in at the latest, or after 3 days without use). Codes and sessions are not stored in plain text.
- Emails: the recipient address (encrypted), type, time and status of each email, and the text of each email.
- About the owner: Wix site and app instance ids, site and business name, time zone, currency, the owner’s email address for notices, plan, settings, programmes, sessions and price rules.
- Audit records: who in the dashboard viewed or printed medical data (see below). They hold ids and counts, not the medical text.
How it is protected
Every child and parent field (names, email, phone, address, date of birth, medical and care notes, answers, typed consent names, owner notes), the recipients and text of sent emails, and payment-request links are encrypted one by one before they are stored, with AES-256-GCM and keys held as secrets of the service. Search by name or email uses keyed hashes, not the plain text. Data is sent over HTTPS. Medical text is never put into lists, search results, CSV exports, emails, the Wix cart or payment requests, or our logs; it appears only on the screens and printouts described next. We make no claim that the app is certified or compliant with any standard.
Who can read it
- The family: a parent can see and edit their own children’s details after confirming a code sent to their email. A family cannot see another family’s data.
- The site: the site owner and anyone the owner has given access to the site’s dashboard can open the app’s dashboard. Only they can read a child’s medical and care notes, through three views: the child’s medical page, the roster (on screen and printed: allergies, pickup people and emergency contacts) and, on Pro and Business, the medical print. Registration lists, family pages, orders and CSV exports contain none of it.
- Every such read is recorded: the dashboard keeps an audit list with the time, the person (their Wix user id) and which child or session was opened or printed.
- Kayabyte does not read registrations or medical notes in the course of normal operation. Where the owner asks us for help, we ask for the minimum needed.
Where
On Cloudflare’s network. The database is not pinned to one region, so data may be processed outside the EU/EEA under Cloudflare’s data processing terms.
Emails
Emails are sent from a Kayabyte address in the name of the owner’s business, with replies going to the owner. Families get: sign-in codes, registration confirmations, payment requests and payment confirmations, reminders for balances and instalments (with a one-click unsubscribe; payment requests themselves still go), waitlist and offer notices, and cancellation notices. Owners get a daily digest, a notice for each registration on Business, and operational alerts. Emails contain no tracking pixels from us. Sent emails are removed after 90 days.
Retention
- Medical and care notes, and custom answers: deleted automatically a number of days after the child’s last registered session ends. The owner sets the number, from 30 to 730 days; the default is 180. If the child has a later session, the clock starts after that one. The owner can also use “Purge medical now” for the whole site or one programme. After a purge the family page shows empty fields and asks again at the next registration.
- Names, contact details, consents and the payment ledger: kept while the app is installed, until the family is deleted.
- Families that verified an email but never registered or joined a waitlist are deleted after 30 days.
- Short-lived records: sign-in codes are deleted after one day, rate-limit counters (keyed hashes of the email or IP address, no plain values) after two days, and processed Wix event ids after 30 days.
Erase on request and on uninstall
- On request: the owner can delete a family at any time in the dashboard. This removes the family’s and children’s names, contact details, medical and care notes, answers, typed consent names, notes and queued emails, and their sign-in codes, sessions and waitlist entries. Orders, lines, schedules and payments stay with amounts only, shown as “Deleted family”. Open payment requests are voided first. If you are a parent, ask the camp or school first; if you cannot reach them, write to support@kayabyte.dev.
- If the app is removed: the widget stops at once, and all of the site’s data in our database is deleted 30 days after removal. A reinstall within those 30 days keeps the data. We keep a small install record (site id, install and removal times, plan changes) for our own install counts; it holds no family or child data.
Browser storage
After a parent signs in, the widget keeps a sign-in token in the browser tab’s session storage. It ends when the tab is closed, 7 days after sign-in at the latest, or after 3 days without use; “Sign out” revokes it, and the owner can sign a family out everywhere. No email, child, medical or answer data is kept in the browser. The dashboard keeps no medical data in the browser’s storage. The app uses no analytics or advertising.
Children
Registrations are for children, so the app stores children’s data. It is entered by the parent or guardian who registers, and the owner decides which questions are asked and needs a lawful basis, and where required the parent’s consent, for them. The consent boxes in the app are a record of the typed name, time and text version; they are not a legal e-signature.
Logs
Our service logs hold job outcomes and ids, not names, email addresses, dates of birth or medical text. Cloudflare may still process network metadata (such as IP addresses) to deliver and protect the service, under its own terms. Install, removal and plan events that Wix sends (site id and plan) and one “first paid registration” event with the app instance id are copied to Kayabyte’s private usage statistics.
We do not sell data
We do not sell or rent data, and we do not use families’ or children’s data for advertising, for our own marketing or for any purpose other than running the app. Data is shared only with Wix and the sub-processors named above.
Your rights
If you are a parent, contact the camp or school first: they hold your record and can export or delete it. We help them with such requests. For questions about this policy, or to exercise rights under the GDPR, contact support@kayabyte.dev.
Changes
We will update this page if the app’s data handling changes, including before any new sub-processor is used. The date at the top shows the latest version.