Privacy

Privacy Policy

This site is run by one person. This page describes exactly what it collects, why, and how to have it deleted — in plain language rather than legal boilerplate.

Last updated 21 August 2026

Who runs this site

AdamBossin.com is operated by Adam Bossin. Questions about anything on this page go to hello@adambossin.com.

What gets collected

Only what you type into a form. The contact, entrepreneur programme and AI programming forms ask for a name, a way to reach you (email or phone), optional details about your business, and whatever you write in the message field.

There is no advertising tracking on this site, no third-party analytics, and no cookies used to profile you. If you sign in to the private admin area, a session cookie is set so the server knows who you are — that is the only cookie the site sets itself.

Why it is collected

To reply to you. A form submission is stored so the enquiry is not lost, and an email notification is sent so it gets read. Nothing is used for marketing lists, and nothing is sold or rented to anyone, ever.

Who it is shared with

These services handle data on the site's behalf, and nobody else does:

  • Vercel — hosts the site and serves every page.
  • Supabase — the database where enquiries and correspondence are stored.
  • Resend — sends notification emails and replies.
  • Cloudflare Turnstile — checks that form submissions come from a person rather than a bot.
  • Calendly — powers the booking calendar. Booking a call is subject to Calendly's own privacy policy.
  • Google Fonts — delivers the typefaces the site uses.

Google user data

The private admin area of this site includes internal automation tools that connect to Google services — Google Tag Manager and Google Ads — using the site owner's own Google account.

These tools are used solely to administer properties the site owner owns and operates. Data retrieved from Google is used only to audit and manage those properties. It is never sold, never shared with third parties, never used for advertising or profiling, and never used to train machine-learning models. Credentials are stored encrypted and are accessible only to the site owner.

These tools are not available to visitors and do not process visitor data. Access can be revoked at any time from the Google account's third-party app permissions page.

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How long it is kept

Enquiries are kept while there is a reason to — an active conversation, an ongoing engagement, or a record of work done. Anything with no continuing purpose gets deleted.

Having your data removed

Email hello@adambossin.com and ask. You can request a copy of what is held about you, a correction, or deletion, and it will be handled — there is no form to fill in and no process to navigate.

Changes to this policy

If this page changes materially, the date at the top changes with it. There is no version history worth keeping; the current page is the policy.