How is this site secured?
Every page of BookBlume Publications is served over HTTPS with HSTS, an enforced Content-Security-Policy and hardened response headers. It keeps only what you choose to send it, protects it with row-level security, and never sells it or shares it for advertising. It sets no optional cookies or trackers.
Last checked 5 November 2026 · security score 99/100
What this site collects
BookBlume Publications keeps only what you choose to give it:
- a message you send through the contact form, with the name and email address you give
It is never sold or shared for advertising. You can ask what is held about you, and ask for it to be removed, using the contact details on this site.
Consent
This site sets no optional cookies or trackers. Its visitor statistics come from Cloudflare Web Analytics, which uses no cookies.
How the site is secured
- Every page is served over HTTPS, with HSTS on the live domain so browsers refuse an insecure connection.
- A Content-Security-Policy is enforced, so the browser runs only the code and connects only to the services this site actually uses.
- Hardened response headers: no MIME sniffing, a strict referrer policy, and camera, microphone and location access switched off.
- The information you send is protected by row-level security in the database, so the public can read only what is meant to be public.
- Public forms are protected against automated spam.
- The platform that builds and publishes this site scans its own code for leaked secrets and known vulnerable dependencies.
Who processes data for this site
- Cloudflare serves the site and protects it at the edge.
- Supabase stores the information you send, in its London (United Kingdom) region.
- Resend delivers the emails this site sends you.
Reporting a concern
Security researchers can find our contact details and policy at/.well-known/security.txt. For anything else, use the contact details on this site.