S SiteSums
PrivacyTermsData processingCookiesSecurity

How your data is kept safe

You are putting your clients' details, your prices and your bank account into SiteSums. This page explains how that data is protected.

Last updated 8 November 2026 · SiteSums is operated by Nikita-Jade Hancock, 124 City Road, London EC1V 2NX. Questions: info@sitesums.co.uk

Where it lives

Your data is stored in a UK data centre (London), operated by Supabase on Amazon Web Services. It is encrypted on disk and encrypted in transit. Backups are encrypted too.

Your account can only see your account

Every table in the database carries rules (called row-level security) that the database itself enforces before returning a single row. So a bug in our application code can't get round them. Your account can read and change only rows marked as yours. We test it by creating two accounts and confirming neither can reach the other's data through any route.

How you sign in

You sign in with Google or with a link we email you. There is no SiteSums password to be guessed, reused or leaked. Your Google account or email account is your key. Protect it the way you would your bank login, with a strong password and two-step verification on that account. You can also switch on two-step sign-in for SiteSums in Settings, so a code from an app on your phone is needed as well.

The links you send clients

Every quote, portal or approval link has a long random code in it, so nobody can guess one or work through them one by one. You can regenerate any of them at any time from the document, which instantly kills the old one. A deleted document's link stops working.

Money

Card payments are handled entirely by Stripe: card numbers never reach SiteSums. When you take a card payment from a client, they type their details into Stripe's page, not ours. Your own bank details (which you enter so clients can pay you by transfer) are stored encrypted at rest and appear only on the documents you produce.

Files

Receipts and template masters are in private storage, readable only by the account that owns them. Two things are deliberately public: your logo and your project cover images, because they appear on the pages your clients open. Treat a cover image the way you'd treat a photo on your website. A house exterior is fine; a floor plan with an alarm code on it isn't.

What we can see

Administrative access to the live database is limited to named people at SiteSums and used only to keep the service running or to help you when you ask. We do not read your documents for any other reason. We never sell your data, and we share it only with the providers listed in the privacy policy.

When something goes wrong

Errors are logged with the account they affected and reviewed. If we ever discover a breach affecting your data we will tell you within 48 hours with everything we know, so you can meet your own duties. Details are in the data processing terms.

Your controls

  • Export everything, any time: Settings → Export.
  • Delete your account and everything in it yourself: Settings → Delete account. Immediate, irreversible, and backups age out within 30 days.
  • Regenerate any share or portal link from the document it belongs to.

What we'd ask of you

  • Secure the Google or email account you sign in with. It is your SiteSums key.
  • Don't forward a client's document link to anyone other than that client.
  • Tell us straight away if you think your account has been accessed: info@sitesums.co.uk.

Reporting a security vulnerability

If you believe you have identified a security vulnerability in SiteSums, please report it to info@sitesums.co.uk and allow us the opportunity to investigate before disclosing it to anyone else. We will acknowledge your report within two working days and treat any confirmed issue as a priority.

© 2026 SiteSumsPrivacy · Terms · Data processing · Cookies · Security · ContactSiteSums is a trading name of Nikita-Jade Hancock, 124 City Road, London EC1V 2NX.