withSeismicBook a seatBook a seatLet’s goLet’s go

The short version

I run a small business. I collect the least I can get away with: your name and email when you buy a seat, what you bought, a device id and some page events so I can see which parts of the site work, and the marketing tags that were on the link you first arrived through.

Card numbers never touch my servers. You type them into Stripe's own form, inside Stripe's own frame. All I ever hold is a set of Stripe reference ids.

There is no Google Analytics here, no advertising pixel, no session replay, no fingerprinting, and no data sold or shared with advertisers. Ever.

This policy was last updated on 20 August 2026.

Who is responsible for your data

The controller is [registered company name], registered under company registration number [company registration number], registered address [registered postal address]. Doug Silkstone runs the weekends and answers the email.

For anything in this policy — questions, requests, complaints — write to doug@withseismic.com. There is no separate data protection officer; the business is too small to need one, so that address reaches a person directly.

What I collect, and where it sits

I will be specific, because vague privacy policies are usually hiding something.

When you buy a seat or a digital product. Checkout asks for exactly two things: your name and your email address. Those go into the orders table, along with the weekend you picked, the order status, the amounts, my Stripe reference ids (customer, payment intent and payment method), the access token that opens your order page, and the attribution data described below. What you bought sits in order_items. Every charge attempt, including failed ones and their failure reasons, and every refund, sits in payments. Which post-purchase offers you were shown, and whether you took them, sits in upsell_events.

When you sign up for an account. Your name, email, a hashed password, and — on each session — your IP address and browser user-agent string. Sessions expire after thirty days.

When you use the site. A short list of product events: page viewed, event viewed, seat added, cart opened, checkout started, contact submitted, payment succeeded, upsell viewed, upsell accepted, upsell declined, receipt viewed, portal viewed, lead captured. That is the whole list; anything else is rejected. Each event is stored in the funnel_events table with a random device id, the path, and — once you have told me your email at checkout — your email address alongside it. Order access tokens are stripped out of recorded paths on both the browser and the server, so the credential is never written into the analytics table.

When you give me your email for the newsletter or a lead magnet. That email, where you gave it, and the attribution data go into the leads table.

Emails I send you. Every message is written into an emails outbox table before it is sent — and that row holds the recipient address, the subject, and the full rendered body. A receipt therefore contains your name, your email, the venue address and everything you bought, and it stays in that table. I can read that table through an admin route. Nobody else can.

Attribution. On your very first page view, before you click anything, the site writes two things into your browser's localStorage: a random device id (seismic.anon.v1) and a first-touch attribution record (seismic.attribution.v1) holding any utm_* values, ref, gclid or fbclid on the link, the referring site, the page you landed on, and the time. It is written once and never overwritten. It is sent with analytics events and copied onto your order when you buy. There is currently no consent prompt in front of it. I think that is a fair thing to tell you plainly rather than bury; see Cookies and storage for the full list of what is stored on your device and how to clear it.

Rate limiting. IP addresses are held in the server's memory for a few minutes to stop abuse of the login and order-lookup forms. Nothing is written to disk.

What I never collect

No card numbers, expiry dates or security codes. No special-category data. No location beyond what an IP address implies. No cross-site tracking, no ad networks, no data brokers. No purchase of lists. No profiling that produces an automated decision with a legal effect on you.

Why I am allowed to hold it (lawful bases)

  • Contract. Your name, email, order, payments, entitlements and the emails that service the order. I cannot sell you a seat without these.
  • Legal obligation. Transaction records kept for tax and accounting.
  • Legitimate interests. Product analytics, first-touch attribution, the outbox, the abandoned-checkout email and fraud prevention. My interest is running a very small business well; the counterweight is that the data is minimal, never sold, and never used to make automated decisions about you. If you object, I will stop — see below.
  • Consent. Marketing emails you asked for by giving me your address. Withdrawn any time, with no effect on anything before.

Who else touches it (processors)

  • Stripe — payments. You enter card details directly into Stripe's hosted fields; the card never reaches my servers. Stripe receives your email and the amount, sets its own cookies on its own domain for fraud detection, and acts as an independent controller for its own fraud and compliance purposes.
  • Resend — email delivery. Receives the recipient address, the subject and the full body of each message.
  • My own PostgreSQL database and application servers, run on hosted infrastructure at [hosting provider and region].

That is the complete list. No analytics vendor, no CRM, no ad platform.

International transfers

The weekends happen in Prague, prices are in US dollars, and the processors above are US-headquartered with global infrastructure. Where data leaves the UK or the European Economic Area it does so under the standard contractual clauses in each processor's data processing agreement, together with the UK addendum where it applies. Hosting region is [hosting provider and region].

How long I keep it

I will be honest here too: the system has no automatic deletion. There is no purge job, no expiry timer, no anonymisation routine. Every row described above is kept until a person — me — deletes it.

The policy I hold myself to:

  • Order, payment and invoice records: kept for [retention period for tax records, e.g. seven years] because tax law requires it.
  • Analytics events and lead records: deleted on request, and reviewed and cleared out at least once a year.
  • Outbox message bodies: deleted on request; otherwise pruned annually beyond the records tax law requires.
  • Account and session data: deleted when you close your account.

If you ask me to erase something, I do it by hand, and I will tell you what I removed and what I had to keep.

Security

Passwords are hashed, never stored in plain text. The session cookie is httpOnly and same-site. Downloads are served with no-store caching and only after checking that the person asking has actually paid. Card data is out of scope entirely because it never arrives.

One thing you should know: the access token in the link to your order page is a credential. Anyone holding that link can view the order and can add a post-purchase offer to the card you used, with one click. It sits in the URL of your thank-you page and in your browser's storage. Treat it like a password — do not forward the link, and clear your browser storage on a shared machine.

Your rights

If you are in the UK or the EEA you have the right to: access a copy of your data; rectify anything wrong; erase it, where I am not required to keep it; restrict or object to processing, including the analytics and attribution described above; portability of the data you gave me, in a machine-readable file; and to withdraw consent to marketing at any time.

There is no self-service export or delete button — I would rather say so than pretend otherwise. To exercise any right, email doug@withseismic.com from the address you used, and if it concerns an order, quote the order number from your receipt. It looks like SEIS-4F9K-2M7Q. I will reply within thirty days, usually much sooner, and I will not charge you for it.

If I get it wrong, you can complain to your national supervisory authority — in the UK, the Information Commissioner's Office; in the EEA, the authority for the country you live in. I would appreciate the chance to fix it first.

Children

The weekends and the material are for people running businesses. The site is not intended for anyone under 18, and I do not knowingly collect data from children.

Changes

If this policy changes materially, the effective date above changes with it and I will email anyone with an active order. There is no version history on this page — only the effective date and the last-updated date the site records.

Related pages