What happens to your salon's data.

Where the data is stored

Kammzeit runs on InstantNode's own servers in the data centre of Skylink Data Centers B.V. in Eygelshoven (Kerkrade), Netherlands. The database, backups and email sending run on our own systems in the EU. Administration takes place from the EU or the EEA.

Tube-Hosting filters incoming traffic with PletX technology to protect against overload attacks. Only connection data such as IP addresses is processed for this, never content. Stripe only processes the billing data for your Pro plan and never data about your customers.

Who has access

Only we as the operator have access to the servers, database and backups. Other people only if they have first been bound to confidentiality in writing. We only look at content if you ask us to, if it is technically necessary for operation, backups or fixing a fault, if there is a specific suspicion of abuse or a security incident, or if the law requires it.

We don't pass data on to third parties and we don't sell anything. We don't keep access logs. The server's error logs are deleted after 14 days.

Separation between salons

All salons share one database, and the separation happens in the application: every record belongs to exactly one salon, and every query in the dashboard is limited to the salon that is logged in. A salon account can only see its own data. Every booking page has its own subdomain. The program runs as a separate, restricted system user that can only write to its own data directory.

Roles in your salon

With Pro, the salon owner can give staff their own logins. Every login has its own email address and logs in by itself with a link. There is no need to share one login.

• Staff see the calendar, customers with their notes and the queue, and keep their own working hours up to date.
• They have no access to the plan, settings, services and team, the data export, the CSV export of customers, deleting customers or deleting the account. The server checks this on every request, not just the menu.
• When the owner removes an access, all sessions of that login end immediately. If a staff member is inactive or Pro ends, the login can no longer be used.

How this works in the dashboard is described in Invite your staff.

Login and cookies

• No password: to log in, we send a link to your email address. It is valid for 15 minutes and works only once.
• We store login links and session IDs only as SHA-256 hashes, never in plain text.
• The session cookie kz_session cannot be read by scripts (HttpOnly), is only sent over encrypted connections (Secure), is only valid for the site you logged in on, expires after 30 days and becomes invalid as soon as you log out.
• The cookie kz_queue is set by the queue on the phone of a customer who joins. It only remembers their place for today, is only valid for that salon's queue, can't be read by scripts and expires after 12 hours.
• Kammzeit sets no other cookies, none for statistics or advertising either.
• Changes in the dashboard are only accepted from forms whose origin is checked. A Content Security Policy prevents scripts from other sources from being loaded. Login, booking, the queue and uploads are rate-limited against mass requests.

Encryption

All connections to the website, the booking pages and the dashboard are encrypted with TLS. We administer the servers via SSH. Kammzeit does not additionally encrypt notes in your customer records. Health data such as allergies should only go into the records with explicit consent, see Customer records.

App and device storage

The dashboard can be installed as an app, see Install the app. The app's service worker only stores fixed files on the device, such as the stylesheet, font, images and the offline page. Pages with appointments, customers, login or session data are always loaded from the network and never kept in the device's storage. So no customer data is left behind on a front desk computer or a shared tablet.

In the browser's storage, Kammzeit only remembers two small things: that you closed the install notice and that you have already seen the dashboard tour. Neither contains personal content.

Uploaded images

We only accept the logo, cover image and gallery photos as PNG, JPEG or WebP, no SVG, because SVG files can contain scripts. Every image is checked, resized and saved anew. This removes all metadata: camera details, the time it was taken and the GPS location from the EXIF data. The images are stored in the database, belong to exactly one salon like all other data, are backed up with it and removed when the account is deleted. They are publicly visible on your booking page, so only upload what should be shown there.

Backups and deletion

The database is backed up regularly on InstantNode systems in the EU, and each backup is kept for 30 days at most. If you delete your account, we immediately remove all of your salon's data: customer records, appointments, staff and their logins, services, images, login links and sessions. It disappears from the backups no later than 30 days afterwards. Expired sessions are deleted automatically, queue entries the following day.

Your control

• All your data as a file at any time: Export and delete.
• View, change, export (CSV) and delete customers, for example when a customer asks for access to or erasure of their data: Customer records.
• Remove your staff's access at any time: Invite your staff.
• Delete your account for good, at any time, in the dashboard.

Data processing

You are the controller for the bookings on your page, and we process the data only on your behalf (Art. 28 GDPR). You accept the data processing agreement when you sign up. Annex 1 lists the technical and organisational measures, Annex 2 the sub-processors. Our privacy policy applies to your own account. The English versions are translations; the German versions are legally binding.

Verifiable

Kammzeit's code is public. You, or someone with IT skills, can read exactly how login, separation between salons, export and deletion are implemented. See Open source.

What we don't promise

Kammzeit has no certification such as ISO 27001. We don't promise a specific availability, for example as a percentage. No system is completely secure. We do what is described above, and we tell you if your data is affected by a data breach.

Reporting a vulnerability

Write to kontakt@kammzeit.de, please with:

• a short description of the vulnerability and the affected address,
• the steps we can follow to reproduce it.

Please don't publish anything before we have fixed it. Don't access other salons' data, and avoid tests that disrupt the service. We don't pay bug bounties, but we answer every report.