Set up a booking contact without exposing private details

Define the public role

Decide whether enquiries go to the artist, manager or another authorised representative. A role address can separate public booking from private correspondence, but only publish an address that exists and is monitored. Do not invent a manager or promise a response time the team cannot support.

Ask only for useful information

A simple initial enquiry can identify the event, proposed date, location, broad requirements and contact route. Avoid collecting payment credentials, identity documents or excessive personal information at first contact. Keep public form labels and the actual handling consistent.

Map the data flow

Record where messages go, who can read them and what services store them. If a form or bot is used, check its actual processing and retention before writing a privacy statement. Do not assume a role email or a noindex tag makes submitted information private.

Test the real workflow

Through an authorised test, verify delivery, routing and any confirmation before launch. Protect account credentials and define how suspicious or irrelevant enquiries are handled. Applicable privacy obligations need review for the actual operator and audience. This guide creates no mailbox, form, booking calendar or automated reply.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

• ICO privacy-information requirements: UK context
• DistroBolt artist privacy checklist

Continue your release planning

• Build a useful public page for a music release
• Keep one verified register of your official artist links
• Privacy choices for artist websites and fan forms

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.