Privacy Policy

Kadens (“we”, “us”) is a booking and event-execution platform for DJs, promoters, and the people who work with them, operated from Melbourne, Australia. We are the data controller for the personal information described here. You can reach us at support@getkadens.com.

Account data — name, email, phone number, country, password hash or OAuth identity (Google or Apple), and your account preferences.

Profile data — your handle, stage name, bio, photos, links, genres, and anything else you choose to publish on your public page.

Booking and event data— gigs, bookings, run sheets, availability, crew, equipment, and the client details you enter to manage an event (a client’s name, email, phone, and event information). For that client data, you are the controller and we process it on your instructions.

Messages and enquiries — booking requests, in-app messages, contact-form and support enquiries.

Payment data — handled by Stripe. Card numbers never touch our servers; we keep your Stripe customer reference, plan, and invoice history.

Usage data — pages viewed, features used, device and browser type, and approximate (country-level) location, subject to the consent rules below.

Kadens can capture a booking from content you share into it — a screenshot, a forwarded text, an email, or a DM. When you share content for capture, we process it solely to extract the booking details (who, when, where, what) and create the booking record you then review. The shared content can include messages written by a third party (the person who messaged you); we process it only on your instruction, only for that extraction, and we do not use it to build profiles of the sender, for advertising, or to train models. The original shared artefact is kept while the capture is waiting for your review, retained for up to 90 days after you confirm or dismiss it (so you can check what was captured against what was said), and then deleted — what remains is the structured booking you confirmed and an audit reference to when it was captured.

Where capture connects to a third-party platform (for example WhatsApp or Instagram via Meta’s APIs), our use of data received from those platforms complies with the platform’s developer policies, is limited to providing the capture feature you invoked, and is never sold or transferred except as needed to provide that feature.

To run the product (bookings, calendars, run sheets, notifications you asked for), to bill you, to keep the platform safe (rate-limiting, abuse and spam prevention), to answer your enquiries, to improve the product from aggregate usage, and — only with the lawful basis described in the analytics section — to measure marketing. We do not sell personal information, and we do not use your event data for advertising.

Named services that process data on our behalf, and what they hold:

• Supabase — our database, authentication, and file storage. Hosted in Sydney, Australia.
• Vercel — application hosting and delivery (Sydney region for compute; a global CDN for public pages).
• Stripe — payments, subscriptions, and tax. Stripe is a global processor and holds your card and billing details under its own certified controls.
• Zoho (CRM and Desk)— when you contact us through the website, submit a support request, or join a waitlist, your enquiry (name, email, what you wrote, and the routing details you chose) is transmitted to and stored in Zoho’s Australian data centre. We keep enquiry records in Zoho for as long as the conversation is active and up to 24 months after it closes, then delete them. Self-serve product signups are not synced to the CRM.
• Loops — transactional and lifecycle email (the emails the product sends you). Holds your email address and message history.
• Twilio — SMS and WhatsApp notifications, where you enable them. Holds the phone numbers messages are sent to.
• Pusher — realtime presence and broadcast on live events. Transient; holds connection metadata, not your content.
• Sanity — the content system behind our marketing pages. No user data.
• Google Analytics 4 and Meta (Pixel and Conversions API) — marketing measurement on the public website only, governed by the consent section below.

Some of these providers store data outside Australia (notably Stripe, Loops, Twilio, Google, and Meta). Where they do, the transfer is covered by the provider’s standard contractual safeguards.

The public website uses Google Analytics 4 and the Meta Pixel (with server-side Conversions API) to understand where visitors come from and whether the site works. In the EEA, the UK, and Switzerland these are off by default and only activate if you consent (Google Consent Mode v2); elsewhere they run with consent assumed, and you can decline. Strictly necessary cookies (your session, your theme, your consent choice) are always on. The authenticated product is not ad-tracked.

Account and event data stay for as long as your account exists. Delete your account and we delete or de-identify your personal data within 30 days, except records we must keep (billing and tax records, kept 7 years under Australian law) and minimal abuse-prevention logs. CRM enquiry records follow the Zoho retention above. Backups age out on a rolling schedule within 35 days.

You can access, correct, export, or delete your data — from the app where possible, or by emailing support@getkadens.com. We handle requests under the Australian Privacy Principles, and where the GDPR or UK GDPR applies to you, under those rights (access, rectification, erasure, restriction, portability, objection). If you’re not satisfied, you can complain to the OAIC (Australia) or your local supervisory authority.

We’ll post changes here and bump the date at the top. Material changes get an email or in-product notice before they take effect. Questions → contact us.