Privacy

What the site stores in your browser

The Music Planner saves your draft on your own device as you go, so you can close the tab and pick it back up. That draft sits in your browser's local storage. It's yours. Clearing your browser data removes it, and until you press Send to Justin I've never seen it.

The homepage remembers which kind of event you were looking at so the page doesn't reset on you. That's a preference, and it stays on your device.

If you start the planner and then go to make an account, the name, email and date you already typed ride along in your browser's session storage so you don't type them twice. That clears itself when the account is made, and when you close the tab.

If you create an account, the site sets one cookie named dje_s. It holds a random session token and nothing else: no name, no email, no event details. It's marked HttpOnly, Secure and SameSite=Lax, it lasts 30 days, and signing out deletes it. That cookie is what keeps you signed in, so the site can't work without it while you're logged in.

Those are all the cookies there are. There's no advertising cookie, no analytics cookie and no third-party cookie on this site, which is why you aren't being asked to click through a consent banner to read the page.

If you send me the booking form

The booking form on the weddings page asks for your name and your email, and optionally your phone number, event date, event type, venue or city, and anything you want to tell me about the night.

It gets saved so I can answer it, and it comes to me as an email with your address set as the reply-to so I can write straight back. It is saved first and mailed second on purpose: if my email provider has a bad day, your enquiry is still sitting there waiting for me instead of disappearing.

I keep it while I'm answering you and for a short while after, and I delete it once the enquiry has gone cold or your event is over. Ask me to delete it sooner and I will.

Sending it doesn't create an account and doesn't book anything. If you'd rather not use a form at all, the text and email buttons do the same job from your own phone.

If you write about your night

The page at /words sends me what you write: your name, the night, how it went and your own words. It's stored on my server and emailed to me, the same way as the booking form.

If you choose to share it, I may put one sentence of yours on my homepage. It runs with your first name, or a plain label if you chose to leave your name off ("A couple", "A corporate client", "A private client", or "An event coordinator" or "A venue we work with" for someone writing from the trade), then the month, and the place if you named one and it's fine to name. Your surname, email and Instagram stay with me. If you choose "Keep it between us", it stays between us.

Two small things about that line under your words. I may tidy how a place is spelled, and I may fill in the month when you left it blank, because a card is mine to set. I never change a word of what you wrote. A card from someone in the trade often carries no month at all, since it was not their own night.

One thing works the other way round. If you write to me as a planner, a coordinator or a venue, I may name you the way you'd want to be named in your own trade: your name, your role and where you work. A recommendation from a professional is worth reading because everyone can see who wrote it. Tell me to leave your name off and I will.

Ask me and I'll take it down. The homepage updates within about a week.

If you create an account

An account is optional. You can browse the site, fill in the Music Planner and book me without ever making one.

When you do make one, I hold your name, your email address, and whatever event details you give me: phone number, event date, event type and venue. I also hold your Music Planner, any notes you write me, my own notes about your event, and a copy of your countersigned agreement once there is one.

Your password never reaches my server. Your browser stretches it with PBKDF2-SHA256 over 200,000 rounds and sends only the derived key, which the server salts and hashes again before storing. I can't read your password, and I can't recover it. If you're locked out, text me and I'll issue you a one-time reset link that expires in 24 hours.

While you're signed in, the site records the IP address and browser name attached to that session, and a short activity log of the kind "planner saved" with a timestamp. That's there so I can tell a real sign-in from someone else's, and so I know whether your planner is current before your event.

Your event agreement

The agreement page is built so that your booking never touches a server at all. Everything in the document rides in the part of the link after the #, and browsers are required to keep that part on your own machine. It's never sent with the request, so it can't be logged, cached or read in transit.

That means when you open your agreement, read it and sign it, your name, phone, venue and address stay on your device and travel back to me only in the link you send.

After I countersign, I can file a copy of the finished agreement to your account so you can pull it up later. That copy is stored, and it's the only part of the agreement flow that is. If you'd rather I didn't file one, say so and I won't.

The Music Planner and song search

When you search for a song, the planner asks my server, and my server searches my own music library. That search never leaves my site, so nobody outside it hears what you typed.

I own a lot of music, but not everything. If my library comes up empty for what you typed, and only then, your browser asks Apple's public music catalogue directly. Apple can see your IP address for that one search, the same way it can for any picture or video you load from anywhere on the web.

Album artwork and the 30-second previews come straight from Apple, because that's where those files live. Results from my own library have neither, so a search I can answer myself asks Apple for nothing at all.

All of it is optional. Typing a song title in by hand runs no search at all. The planner works exactly the same either way.

My server keeps one number out of all this: how many song searches happened each day, added up across everybody. It's a running total and nothing else. It doesn't record who searched, what you typed, or which searches belong together, and it's the only way I can tell whether anyone is using the planner, since the site runs no analytics script.

When you press Send to Justin, your planner comes to me and I get an email telling me it arrived. I keep it until your event is over and my records are settled.

Email

The site sends email through Resend, and it only ever sends it to my own business inboxes: mine, and my CFO's, who handles the books and gets the same alerts. There's no mailing list, no newsletter and no automated email to you from this website.

When you press Send to Justin, sign up, leave me a note, or send the booking form, Resend handles delivering that alert to my inbox with your email address set as the reply-to, so I can answer you directly. Resend processes that message to deliver it.

The Text and Email buttons on the site open your own phone or mail app with a message already typed. The site doesn't send those. You do, and you can edit or cancel before you hit send.

Analytics

There is no analytics script on this site. Nothing measures you in your browser: no tracking pixel, no Google Analytics, no Facebook or Meta tag, no advertising tag and no remarketing of any kind.

That also means I have no visitor count at all. I can't tell you how many people read this page, or which country they read it from, because I can't tell myself. My domain sits with a different company from the one that serves the site, so the report a host usually gives you isn't there to read.

The one number my server keeps is the one described above: how many song searches happened each day, added up across everybody. It uses no cookie, sets no identifier, and can't follow you to another website. It can't tell me that a particular person read a particular page. I get one total a day.

Hosting and security logs

The site runs on Cloudflare Pages. Cloudflare sits in front of it and handles delivery, HTTPS and blocking attacks, and in doing that it processes ordinary request data including IP addresses. That's how any website on the internet works, and it's covered by Cloudflare's own privacy terms.

My own code counts requests per IP address on the sign-in, sign-up, password-reset, booking, /words, song-search and homepage-quotes endpoints, so somebody can't sit there guessing passwords or flooding my inbox. Signing in is counted per email address as well, so a flood aimed at one account is caught wherever it comes from, and leaving me a note or sending your planner is counted per account instead of per address. Those counters hold a key and a number, they reset on a timer between a minute and a day long, and they're used for nothing else.

Most of those keys have your address in it, so a row is deleted once its window has passed. That happens as later requests come through rather than on a clock, so on a quiet stretch a row can sit well past its window, and on a week with no visitors at all it waits for the next one.

Who else sees any of this

Me, and my CFO, who handles the books for the business and can sign in to the admin side. That's the list.

I don't sell your information, I don't rent it, and I don't hand it to marketers, lead brokers, venues or vendors. The companies named above (Cloudflare for hosting, Resend for my email alerts, Apple for the songs I don't own and for artwork) process the narrow slice described in each section because the site needs them to work, and they're bound by their own terms.

The one exception is the ordinary one: if a court ordered me to hand something over, I'd have to comply.

How long I keep things

Planner drafts in your browser stay until you clear them. A session lasts 30 days from the time you sign in, and using the site inside the last week of that pushes it out another 30, or immediately when you sign out. An expired session stops working straight away, and its row goes when you sign out or when the account does. Rate-limit counters reset within a day, and the row that held one is deleted the next time the site is busy enough to sweep it.

What you write about your night is kept while it's on the site and for a reasonable period after, and it goes whenever you ask. A booking enquiry is kept while I'm answering it and cleared out once it has gone cold or the event is over. The copy that reaches my inbox as email I clear the same way.

Account records, planners, notes and filed agreements I keep while we're working together and for a reasonable period afterward, because a signed agreement is a business record and I need to be able to produce it. Ask me to delete your account and I'll delete it, along with your planner, your notes and your sessions. Your signed agreement stays on file with your name removed from the account link.

What you can ask me to do

Ask me for a copy of everything I hold about you and I'll send it. Ask me to correct something and I'll correct it. Ask me to delete your account and I'll delete it.

Text or email me and I'll handle it myself, usually the same day. There's no request form and no ticket queue for this, because it's a two-person business and I'm the one who answers.

If you're in California, the CCPA gives you those rights by statute and adds the right not to be discriminated against for using them. Since I don't sell or share personal information for advertising, there's nothing here to opt out of. If you're in the EU or UK, the GDPR gives you equivalent rights, and my basis for holding your information is performing the contract you've booked me under.

Children

This site is for adults booking entertainment. I don't knowingly collect information from anyone under 13. If a child has created an account here, text me and I'll remove it.

Changes to this page

If I change how any of this works, I'll change this page and move the date at the top. The current version is always the one you're reading.