Skip to content
Sign inRequest access

The fine print, plainly

Privacy: whose data this is, and where it goes.

Hot Cues holds three kinds of people's information: the companies who run it, the couples they work for, and the guests who request songs. This page walks through all three.

Draft · September 2026

Draft — pending legal reviewThis is a working scaffold, not a finished policy. The factual statements about how the product handles data are accurate; the sections marked for our attorney are placeholders awaiting reviewed language, and nothing here should be read as legal advice or a binding commitment until this notice is gone.

§1What this covers

This policy covers the Hot Cues application: the public site, the console DJ companies work in, the client portal couples plan in, and the public guest-request pages. It is written for all three audiences at once, because the honest answer to “who can see what I typed” depends on which one you are.

§2What we collect

  • Account information. Name, email address, and sign-in records for people who work at a company using Hot Cues.
  • Event and client records. Whatever a company enters to run its events: clients and their contact details, timelines, songs, venues, services, prices, invoices, and payouts.
  • Portal answers. What couples fill in while planning — questionnaire answers, song choices, uploaded images, and the contact details of people they list (wedding party, vendors).
  • Guest requests. On a public request page: the song, the name the guest gives, and an optional note. No account, no email.
  • Messages and calls. Email threads a company routes into Hot Cues, and — when a company records a consultation — the recording's transcript.
  • Screenshots given to Agent Cue. Images a company uploads for intake are read to draft an event and stored with it.

§3Where it can go

Data leaves Hot Cues only to services a company has switched on, and only the slice each one needs:

  • Hosting and database — the infrastructure the app runs on.
  • Stripe — payments and subscription billing. Card numbers never touch our servers.
  • Email delivery — to send the messages and reminders a company writes.
  • Anthropic — when AI features are used, the text or image being read (an email, notes, a screenshot) is sent for extraction. Results are staged for human review, never applied on their own.
  • Apple Music and Spotify — search queries and playlist links, to look up song metadata. We store references to songs, not audio.
  • Google — only when a company connects its own Google account, for its calendar and mail.
  • Call infrastructure — when in-app consultations are used.

Insert the formal subprocessor list with legal entity names, locations, and data-processing terms; confirm whether a company-facing DPA is required for the client-data relationship.

§4What we don't do

  • We don't sell anyone's data, and there are no ads.
  • One company can never see another's data. That isolation is enforced by the database itself — every query runs inside the asking company's walls — not just by application code.
  • AI features never act alone: anything machine-read becomes a suggestion a person approves or discards.

§5Couples and guests

If you're a couple planning in a portal or a guest requesting a song, your information belongs to the event you gave it to. The DJ company running your event controls it; Hot Cues processes it for them. Questions about your data go to that company first, and this section will name the mechanics once reviewed.

Define the controller/processor split, the data-subject request path for portal clients and guests, and the applicable-law scope (state privacy statutes; GDPR only if it turns out to apply).

§6Export and leaving

A company can export everything it has put into Hot Cues — events, clients, songs, answers, money records — as a single file, from Settings, at any time, on any plan. No lock-in is a product decision, and it's also this policy's enforcement mechanism: if you don't like how we handle data, you can take it and go.

§7Retention and deletion

Set the retention windows: how long records live after a company closes its account, the deletion SLA, what survives in backups and for how long, and the invoice-record carve-out tax law requires.

§8Cookies and sessions

Hot Cues uses cookies to keep you signed in — session cookies, not tracking ones. There is no third-party analytics or advertising script on any page.

§9Changes and contact

When this policy changes materially, companies are told before it applies to them — the same rule the product follows for pricing.

Add the notice mechanism and period, the contact address for privacy questions, and the effective date once reviewed.

Privacy · Hot Cues