Security
What we do, in specifics rather than adjectives, and what we have not built yet. Both halves matter if you are deciding whether to trust us with your bookings.
Last updated 16 November 2026.
The short version
- Guest money is a direct charge on your own Stripe account. We never hold it, so there is nothing of yours for anyone to take from us.
- Card numbers never touch our servers. Payment happens in Stripe Checkout.
- Passwords are hashed with PBKDF2-HMAC-SHA512 in two chained rounds of 100,000 (200,000 iterations), and wrong passwords are limited per email address and per IP address.
- Sessions are HttpOnly, Secure, SameSite=Lax cookies, revocable server side. Every signed-in form carries a CSRF token.
- Every Stripe webhook signature is verified and every event is deduplicated.
- We keep the exact terms and cancellation scale a guest agreed to, with the time and the IP address, which is what protects the campsite in a dispute.
- Data sits in Cloudflare D1 in Western Europe, over TLS, backed up with point in time restore.
- We have no two-factor authentication, no penetration test and no SOC 2 yet. That list is below, in full.
This box is the headline. The sections below are the detail, including the uncomfortable one.
Your money does not pass through us
This is a security property, not just a commercial one. Guest payments are Stripe direct charges on your own connected account, with no application fee. We never hold a balance for you, so there is no PitchDesk float to steal and no PitchDesk account for someone to redirect a payout from. If we were compromised tomorrow, the money already in your Stripe account would still be in your Stripe account.
Card numbers never reach our servers. Payment happens in Stripe Checkout, on Stripe's own pages, so the card details go from the guest's browser to Stripe. We store Stripe's identifiers and the amount, nothing more. That keeps the whole product out of PCI DSS scope beyond the simplest self assessment.
Passwords and logins
- Passwords are hashed with PBKDF2-HMAC-SHA512 in two chained rounds of 100,000, so 200,000 iterations, with a fresh 16 byte random salt for every password. OWASP suggests 210,000 for a single round, and our platform caps one round at 100,000, so we run two. We cannot read your password and neither can anyone who steals the database.
- Password comparison is constant time, so the response cannot be timed to guess a hash.
- Password reset links are single use, random, and expire after an hour. Changing your password, or the email address you log in with, cancels any that are still waiting.
- After five wrong passwords for one email address in 15 minutes, that address cannot try again until the 15 minutes are up, whether or not it has an account. One IP address gets 30 wrong passwords in 15 minutes. A reset link goes to the same address at most three times an hour.
- Changing the email address you log in with needs your current password, and we tell the old address it has changed.
- We do not email you your password, because we do not have it.
- When you sign up, we email you a link to confirm your address. You can set your site up straight away, but your booking page takes no bookings, and your guests get no emails from PitchDesk, until you have pressed the button it opens. The link works once and lasts 7 days.
Sessions and forms
- Your login session is an opaque random identifier in an HttpOnly, Secure, SameSite=Lax cookie. HttpOnly means a script cannot read it. SameSite=Lax means another website cannot ride on it.
- Sessions are stored server side, so logging out really does end them, and we can revoke one.
- Every signed-in form that changes something carries a double submit CSRF token, compared in constant time. Logging out is one of them, so another website cannot log you out.
- Output is escaped by default by the templating layer. Somebody has to deliberately opt out to inject raw HTML, which makes cross site scripting a decision rather than an accident.
- Owner written text, such as your arrival instructions, is escaped and turned into paragraphs rather than trusted as HTML.
- Every database query is parameterised. No SQL is built by joining strings.
Webhooks and payment integrity
- Every Stripe webhook signature is verified with HMAC-SHA256 against the endpoint secret before we act on it, using a constant time comparison.
- Signatures older than five minutes are rejected, so a captured webhook cannot be replayed later.
- Webhook event identifiers are recorded and deduplicated, so a retry cannot confirm a booking twice or take a payment twice.
- Payment requests carry idempotency keys, so a network retry does not become a second charge.
- Prices are always recalculated on the server from your own rates. The browser never tells the server what something costs.
What we store to protect the campsite
One record exists purely so that a campsite can prove what happened. It is worth describing on a security page because it is the difference between winning and losing a dispute months later.
- The terms snapshot, including the cancellation ladder. We store the campsite's terms as they read at the moment of booking, together with the structured ladder that was in force then. A campsite changing its policy next season cannot change what an existing guest agreed to, and the refund a guest receives is computed from the same ladder they were shown in pounds and dates at the checkout. What was displayed and what is enforced are the same object.
The snapshot is written once and not edited afterwards.
PitchDesk also does not take a balance off a stored card automatically. Every card payment on a booking is one the guest made themselves, in Stripe Checkout, while they were there to see it.
Where the data lives
- Everything runs on Cloudflare Workers, with the database in Cloudflare D1 in the Western European region.
- TLS everywhere, with HTTPS enforced.
- Encryption at rest is provided by the platform.
- Backups are automatic, with point in time restore.
- Every query is scoped to the campsite that owns the row, so one account cannot read another's bookings.
- Booking management links use a long random token, not a guessable booking number.
- The calendar feed a campsite can publish carries guest surnames, so it has its own private key, sixteen random bytes per site, appearing on no public page. It is deliberately not the public key that identifies the booking widget, because that one is visible in the code an owner pastes into their own website. Asking for a feed with the widget key returns nothing. The residual risk, stated rather than glossed: the URL is an address and not a login, so anyone an owner gives it to can read it until the key is rotated.
- Pages and API responses carry
X-Content-Type-Options: nosniffand a strict referrer policy. - Every page carries a
Content-Security-Policythat lets only the scripts we serve, and the few we write into our own pages, run. A script that found its way into a page any other way would not run. It does not yet restrict styles or images. - Holding a pitch while a guest pays is limited per connection (an IPv6 network counts as one), and unpaid holds can never take more than half of a campsite at once, so nobody can take a site off sale without paying.
- Channel calendar import reads only public HTTPS addresses, never a private network or one a redirect points at, cuts off any calendar over 4MB as it arrives, and caps how many feeds one site can have, so one account cannot slow down everyone else's.
- Pages refuse to be shown inside another website's frame (
frame-ancestors 'none'andX-Frame-Options: DENY), so nobody can lay our buttons under theirs. The exceptions are your public booking page and the booking form the widget puts on your own website, which are built to be framed. Your dashboard, logging in, and a guest's own booking and payment pages are never framed. - Browsers are told to use only HTTPS for pitchdesk.co.uk for six months
(
Strict-Transport-Security). - The dashboard, the API and embedded booking pages are excluded from search engine indexing.
How it is built
- Almost no third party runtime dependencies. There is no npm supply chain of any size to compromise, because the application code is the application.
- No analytics script, no advertising pixel, no tag manager, no font CDN. Fonts are served from our own domain. Nothing third party executes in your browser on our pages. The one thing a booking page may load from elsewhere is an image the campsite has linked to, such as its logo, which must be HTTPS.
- The booking widget you embed in your own website is a small script that we serve, and it sets no cookies.
- Secrets are held in the platform's secret store, never in the repository.
What we have not done yet
A security page that only lists strengths is marketing. Here is the honest other half, current at 3 October 2026.
- No two-factor authentication on owner logins yet. It is the next security feature we will build. Today, a strong unique password is your protection.
- No independent penetration test yet. The application has been reviewed internally and built to a checklist, which is not the same thing as somebody being paid to break it.
- No ISO 27001 and no SOC 2 report. Those cost more than this product makes at the moment. If your own compliance process requires one, PitchDesk is not the right choice for you today, and we would rather tell you now than at renewal.
- No bug bounty programme. We will still thank you properly and credit you if you want it.
- Rate limiting is simple. Logging in, reset requests and new accounts have fixed limits per email address and per IP address, and the platform protects the edge. There is no account lockout that needs us to undo it, no CAPTCHA and no check of passwords against known breaches yet.
- No audit log you can read. We record booking events internally, but there is not yet a screen where you can see who changed what and when.
- Restores are tested, but not on a published schedule. We have restored from backup and know that it works. We do not yet run drills to a documented calendar.
- Small team. There is no 24 hour on-call rota. Out of hours, a serious problem gets attention when it is seen.
When one of these changes, this list changes with it and the date at the top of the page moves.
Reporting a vulnerability
Email hello@pitchdesk.co.uk with the subject line "security". Tell us what you found and how to reproduce it. You will get a human reply within one working day and we will tell you what we are doing about it.
Please do not run automated scanners against the live service, do not access or change data that is not yours, and do not degrade the service for the campsites using it. Test against your own trial account. If you report something in good faith and stay within those lines, Coreter Limited, which runs PitchDesk, will not take legal action against you.
The rest of the small print
Questions about any of this go to hello@pitchdesk.co.uk and a person will answer.