Privacy policy

Information you give us

When you call or email, we collect what you choose to tell us: your name, company, email address and phone number, and the details of the event — date, venue, room, headcount, agenda or run of show, and any drawings or floor plans you attach.

The contact form

The form on the contact page asks seven things and records seven things: your name, your email address, your phone number if you give one, the event date or that it is not set yet, roughly how many people, the venue or city if you know it, and what you need. It asks nothing else — no company field, no budget band, no marketing consent, and nothing about how you found us.

One thing travels with it that you do not type. If you reached this site by clicking one of our Google advertisements, the link you followed carried an identifier for that click, and the form sends it back to Google so that we can tell which advertisement produced an inquiry. It identifies the click, not you — we are never told who you are from it, and nothing you typed in the form is sent to Google with it. Section 05 describes where it is held in the meantime. If you did not arrive from an advertisement there is no identifier and nothing is sent.

What happens to it is short. The submission is checked and emailed to us, and that is the whole of the journey — there is no database behind the form, nothing is written to the web server, and nothing you send is ever stored anywhere this site can serve it. Two things are looked at in passing and neither is kept: a hidden field that only an automated script would fill in, and the number of submissions from your IP address in the last ten minutes, both of which exist to stop the form being used to send spam. Your inquiry then lives in email, under section 04.

Information the site collects on its own

Nothing. There is no account, no login and no payment taken on this site, and no page collects anything unless you fill in the form. Like every website, the service that delivers it processes standard request data — IP address, browser user agent and the page requested — in order to serve the page and to block abuse. We do not build anything on top of that data and we do not have a visitor-level view of it.

Information we do not want

Do not send payment card details or identity documents by email; we will never ask for them that way. If a project means we handle a guest list or registration data on your behalf, that is covered by the contract for that project rather than by this page.

• To reply to your inquiry, and to ask the questions a scope needs.
• To prepare a scope and an estimate for your event.
• To plan and produce the event itself — the load-in schedule, the rigging drawing, the power calculation, the crew call.
• To keep the records that come with the work: estimates, invoices, certificates of insurance, permit applications.

That is the whole of it. We do not profile you, we make no automated decisions about you, and we do not sell your information.

We do not sell your personal information, and we do not share it for anyone else's advertising. It reaches four kinds of recipient, and no others:

• Our own people. The producer, estimator and crew leads on your job.
• All On Stage Productions, our parent company, whose staff and systems handle production and back-office work for our projects.
• Service providers we use to run the business: Google Workspace for email, Cloudflare for hosting and delivering this site, Resend for delivering the contact form's mail to our inbox, and — for measuring our own advertising only — Google Ads and a call-tracking service (see section 05).
• Venues and suppliers, only where delivering the job requires it, and only the part they need — a venue needs a name to expect at the dock and a load-in window; a fabricator needs a drawing and a date.

We will also disclose information where the law requires it, which in practice means a valid legal request or a permit or licensing authority asking a question about a build.

An inquiry sent through the form arrives as an email, so everything below applies to it too. Mail sent to an address at our domain is hosted in Google Workspace. Internally it may be forwarded — including to staff at All On Stage Productions — so that it lands with the person who will scope or produce the job rather than sitting in a shared inbox. It stays in our mail archive for as long as the record is useful to the work and to the accounts.

Email is not a secure channel. If something in your inquiry is commercially sensitive, say so on the phone and we will find a better way to move it.

This site sets no cookies. There is no advertising pixel, no Google tag, and no consent banner to click away. The typefaces are served from this domain rather than from a font service. Five things are worth disclosing:

Counting visits

We use Cloudflare Web Analytics to count how many people read each page. It sets no cookie and builds no profile of you: it records the address of the page, roughly where in the world the request came from, and how quickly the page loaded, and it does not follow you between sites or between visits. There is nothing here that could be used to work out who you are, which is why there is no banner asking your permission for it.

The network a request arrives on

Every request that reaches any website carries the name of the network that carried it. For most visitors that is a broadband or mobile company — Comcast, AT&T, Verizon — which tells us nothing about them, and we discard it. When it is instead a business that runs its own network, we keep that name together with the page that was requested, the rough location and the time. The purpose is commercial and worth stating plainly: it tells us which companies are reading about corporate event production, so that we know who to follow up with.

What is kept is the organisation and never the person. Your IP address is not stored, your browser and device are not stored, and nothing in that record distinguishes you from anyone else at the same employer — there is no identifier that could tell two of you apart. That is a constraint built into the database rather than a promise we are asking you to take on trust. No cookie is involved, no script runs in your browser for it, and nothing is sent to or bought from a data broker or an identity-matching service. These records are deleted after ninety days.

Most of what reaches a website is not a person at all, and we keep those records too: requests from hosting companies, datacentres, scanners and the like, from anywhere in the world, so that we can tell them apart from the real ones and check our own filtering. There is nobody behind those to describe. A request from a home or mobile connection is in neither group — it is discarded as it arrives and no record of it is written anywhere.

The advertising click identifier

When you arrive from one of our Google advertisements, the address of the page carries a short identifier for that click. If it is there, the site keeps it in your browser's session storage — the tab's own scratchpad, which is emptied the moment you close the tab, is not a cookie and is never sent anywhere on its own. Its only use is that if you go on to send the contact form, that identifier goes to Google Ads with the time of the submission, so that the advertisement can be credited with the inquiry. Your name, your email address and everything else you wrote stay out of it.

We do this from our own server rather than by putting Google's tracking code on the page, which is why there is no script here to block and nothing about your visit is reported to anyone unless you actually send the form. If you did not arrive from an advertisement, nothing is stored and nothing is sent.

Call tracking

A call that arrives from one of our advertisements may be routed through a call-tracking service, so that we can tell which advertising produced an inquiry. That service records the number you called from, the time and the length of the call, and which advertisement it came from. It is used to measure advertising, not to build a profile of you, and if you call the number published on this page directly you are not in it.

The form's confirmation page

Sending the contact form takes you to a short confirmation page. Nothing is different about it: no script runs there, nothing is written to your browser, and it is exempt from none of what this section says. What tells us an inquiry was sent is the inquiry arriving, not your arrival on that page — which means what we count is a message we actually received, not a page view.

These pages are built once and served as flat files over HTTPS. There is no database behind them, no login, no stored submission and no customer record on the web server — so the ordinary risk of a brochure site holding a copy of your data does not apply here.

The contact form is the one exception to "flat files", and it is a narrow one. It posts to a small piece of code that runs on Cloudflare's network, checks the submission and emails it. It keeps no copy. There is nothing for it to read back, nothing for it to leak, and no URL on this site that will show anybody an inquiry — because none was written down in the first place.

Inquiries themselves live in email and in our estimating and project files, and access to those is limited to the people who need them to quote and produce the job. No system is perfect, and we will not pretend otherwise: if something goes wrong with data you sent us, we will tell you what happened.

Depending on where you live you may have the right to ask what personal information we hold about you, to have it corrected, or to have it deleted. You do not need to cite a statute to use this: email, call or write to us at the address in section 11 and say what you want.

Where we have to keep something — an invoice, an insurance record, a permit application, anything a tax or licensing obligation attaches to — we will tell you what we are keeping and why rather than quietly keeping it.

This site links out rarely. Where it does — most often to a venue's own published room specifications — that page belongs to someone else and this policy does not cover it. Read theirs.

We produce corporate events, and nothing here is directed at children. We do not knowingly collect personal information from anyone under 16. If you believe we hold something about a child, tell us and we will delete it.

We update this page when what we do changes — a new service provider, a form, self-hosted fonts. The date under the headline is the date of the last change, and the change is made on the page rather than announced by email.