What We Collect, And What We Don’t.

If you are only reading this site

Nothing is collected and nothing is stored on your device. This site sets no cookies. It writes nothing to local storage. There is no analytics running, no advertising pixel and no social-network widget. The fonts, the map library and every image are served from this domain.

There is one exception, and it is worth naming precisely. The coverage map draws its background tiles from Esri’s ArcGIS service, so opening that page asks Esri’s servers for images — which necessarily tells them your IP address and which browser you are using. That happens only on the coverage map, and only while it is open. Apart from it and the two form pages described below, no page on this site contacts anyone else.

Links out to Facebook, Instagram, LinkedIn and Google are ordinary links. Nothing is shared when the page loads; once you click one you are on their site, under their terms, not ours.

If you send us a form

There are two, and this is everything each one asks for.

Advertiser inquiry

• Your name, and your email address
• Business name, phone number, preferred city or market
• Campaign goal, venue type you are interested in, budget range
• Whatever you write in the message box

Venue partner application

• Business name and contact name
• Email address, phone number, city
• Type of business, and whatever you write in the message box

Both forms also carry a hidden field that is invisible to you and left empty by a real browser. Automated spam scripts fill it in, which is how they are recognised. If it arrives filled in, the submission is dropped.

The automated-visitor check

The two form pages also load a check from Cloudflare, called Turnstile, that tells people apart from automated scripts. It is the only third-party script on this site, and it runs only on those two pages. It works in your browser while the page is open, so Cloudflare’s servers receive your IP address and details of your browser and how it behaves. Most visitors see nothing; occasionally it shows a checkbox. Cloudflare states that it does not read what you type into the form.

The check leaves a one-time code in the form. When you send it, the program described below passes that code and your IP address to Cloudflare to confirm the check was passed, and Cloudflare answers yes or no. The code is not included in the email we receive. Cloudflare offers an optional setting that would add a cookie of its own to this domain; it is switched off. What Cloudflare’s check does with what it receives is governed by Cloudflare’s Turnstile privacy addendum, not by us.

If the check cannot run, because JavaScript is off or a blocker stops it, your message still reaches us. It is marked for a person to look at rather than thrown away.

Where a submission goes

It is sent to a small program we run in our own Amazon Web Services account. That program formats your submission into an email and sends it to our business inbox. It sets the reply address to the email you gave, so that answering you is a single click and your message is not separated from your address.

It is not written into a database, a customer-relationship system, a mailing list or an advertising platform. There is no such system behind this site. Your enquiry becomes an email, and an email is all it becomes.

Two things are checked on the way through. Every submission is scored automatically for spam; a few recognisable attack shapes are discarded without ever reaching the inbox, and borderline ones are delivered with a note on them rather than thrown away, so that a real enquiry is not lost to a false alarm. When a submission is discarded as spam, or when the email fails to send, a copy of what was submitted is written to our server log — deliberately, so that a genuine enquiry caught by mistake can still be found and answered. A submission that is delivered normally is not copied there: for those, the log records only that the message was sent, the names of the fields it contained, and the domain part of the email address. The published policy will say how long those logs are kept.

Who else can see it

Four companies are involved in getting your message to us, and none of them is given it for their own purposes.

• Amazon Web Services hosts this site, runs the program described above, and delivers the email.
• Cloudflare runs the automated-visitor check on the two form pages and confirms it when you send a form. It is not sent your message.
• Esri serves the background tiles on the coverage map, and receives nothing but the ordinary request for an image.
• Google, because the inbox your message arrives in is a Google account, so your message sits there as any email would.

Beyond those, nobody. Your details are not sold, rented, traded, or passed to an advertising network, a data broker or a lead-buying service.

Tracking across other websites

This site does nothing to help anyone build a picture of what you do on other websites over time: it sets no cookies and carries no advertising pixels, no cross-site identifiers and no third-party analytics. The one third-party script, Cloudflare’s check on the two form pages, is there to stop spam, and works under the Cloudflare terms linked above.

Because of that, a Do Not Track signal from your browser has nothing to switch off, and this site does not act on one. If that ever stops being true — if analytics is switched on, or a pixel is ever added — this page is updated before the change goes live, not after.

Seeing or removing what you sent

Write to brad.digitalwave@gmail.com, or call (617) 304-8777, and ask. What we hold is the message you sent us, in an inbox, so telling you what that is and deleting it are both straightforward. The published policy will set out formal rights and the timescales that go with them; until then, ask and it gets done.

What this page deliberately leaves out

You will not find a retention period in days here, or a postal address. Both are real decisions that have not been made yet, and printing a number or an address that nobody has settled on would be inventing policy on a public page — which is worse than admitting the gap. They belong in the published policy, and that is where they will appear.

When this page changes

The effective date below changes whenever the page does. There is no mailing list to notify, because we do not keep one. If you want to know whether anything moved, this page is the record. When the lawyer-drafted policy is published, it takes the place of this page entirely.

Effective 21 September 2026 · Digital Wave Marketing Solutions