Skip to page content
BEHINDTHE SHOWLive Production,
Explained.

Behind The Show / Information

Privacy Policy

What information the website uses, what happens when you contact us, and how your production brief is handled.

Last updated / 2 October 2026

Who this policy concerns

Behind The Show is a live-production knowledge platform created by Vinay Sharma. This policy describes information handling on behindtheshow.live, including contributions, production enquiries and the Brief Builder.

For a privacy question or a request concerning information you have submitted, use the About page contribution form, choose Other contribution and identify your request in the subject. You can also reply to an acknowledgement email you received from us.

When you contact us

The contribution form collects your name, email, contribution type, subject and message. The production enquiry form also collects the event details and contact information you choose to provide, including optional organisation and telephone details.

We use this information to review the submission, send an acknowledgement and respond where appropriate. Submission does not subscribe you to a newsletter. Contributions are not automatically published.

Messages are delivered through Amazon Simple Email Service (SES) to the relevant BTS inbox. The website does not create a database or CRM record of submissions. Email copies and replies can remain in the receiving mailbox and email-provider systems.

Your production brief

The Builder requires no account. Drafts are saved in this browser on this device, not in a cloud draft database. Each save gives the draft a 30-day expiry. Expired drafts are removed when the Builder next checks them; browser storage does not erase itself while the site is closed.

Use the Builder’s clear/start-new action or clear this website’s browser storage to remove a draft. Other people using the same browser profile may be able to access it.

Generating a PDF sends your answers to the BTS server for validation and document generation. The document is generated in memory and returned for download; the application does not permanently store the brief or PDF. Downloaded copies remain wherever you save or share them.

Avoid passwords, payment details and unnecessary confidential or personal information in a brief.

Analytics and browser storage

The production site uses Google Analytics for public-page measurement. This includes page URLs, which can include search or other query parameters, page titles, browser/device information and interactions. Do not put confidential information into URLs or website search queries.

Google Analytics can use first-party cookies to distinguish visits and sessions. See Google’s cookie explanation and Google’s Privacy Policy. Your browser can block or clear cookies; Google also offers an Analytics opt-out browser add-on.

Builder workflow events record actions such as reaching review or generating a PDF, not brief answers. Form messages, names, email addresses and production descriptions are not deliberately included in those events. Admin and Article preview pages are excluded from the public-page tracker.

Clearing cookies is different from clearing a locally saved Builder draft. Browser site-data controls can remove both.

Hosting, security and providers

The site uses Amazon Web Services for hosting and transactional email, and Google for Analytics. Providers process information needed to deliver their services under their own arrangements. We do not promise that all provider processing occurs in one country.

Requests include technical information such as IP addresses and headers. Server-side rate limiting uses a request identity to reduce abuse. Operational diagnostics may include error information; handlers are designed not to log complete form messages or brief payloads. This does not mean infrastructure or providers retain no technical records.

See AWS SES data protection for provider information.

Retention and your requests

The application has no permanent brief store or enquiry database. Mailbox correspondence has no automatic website-controlled deletion schedule. Analytics and infrastructure records have separate provider/configuration retention settings; the Builder’s 30-day rule does not apply to all site data.

You may contact us about access, correction or deletion of information you supplied. Identify the relevant submission or reference where possible. The response depends on the information held, applicable requirements and what can be verified; this policy does not promise a particular deadline or unconditional deletion.

External links and updates

Linked websites, including Instagram and technical sources, have their own privacy practices. This policy applies to BTS, not those destinations.

We may update this page when practices change. The date above identifies the latest revision.