SECURITY CENTER
Practical safeguards. Clear boundaries.
This page describes this website’s implementation, not a certification of GingerClick or a promise that every risk has been eliminated.
Content Security Policy
The site sends a CSP restricting resources to this origin, with data images permitted. It allows inline scripts and styles for the generated Next.js interface. Objects are disabled; base URLs are restricted to self; form actions are restricted to Cal.com; frame-ancestors is none. The inline allowances are a limitation, not a claim of maximum hardening.
Transport and browser controls
Configured response headers include Strict-Transport-Security (max-age=63072000; includeSubDomains), X-Content-Type-Options: nosniff, Referrer-Policy: strict-origin-when-cross-origin and Permissions-Policy disabling camera, microphone and geolocation. HSTS is a browser HTTPS policy; it has no effect on an initial plain HTTP local development request.
Static pages, no application database
Pages are prerendered with Next.js. There is no site-operated submission backend or application database. Hosting and network providers still process technical connection information to deliver and secure requests.
Booking and diagnostics
Email fields open Cal.com with an email prefill. The diagnostic runs in browser memory and does not fetch or scan the website you enter. At the result, you can opt to include a summary in the external booking URL. Cal.com then applies its own policies.
No analytics or security badge
No analytics SDK or tracking cookies are installed. We do not claim an independent audit, certification or guaranteed protection. Headers address particular browser risks and do not replace secure application design.
Report a concern
Contact andy@gingerclick.com with the affected URL and a concise description. Please do not send secrets or personal data and do not test beyond systems you are authorized to assess.