Security & Accessibility

Last updated November 12, 2026

  • Security at Hanwell Studio is treated as an ongoing practice, not a checkbox. We aim to build systems that protect user data by design: minimal data collection, strong access controls, and clear separation between user-facing operations and administrative infrastructure. This page describes the technical and organisational measures currently in place.

  • All data transmitted between your browser and hanwell.studio is encrypted using HTTPS (TLS 1.2 or higher). Data stored in our database is encrypted at rest by Supabase on AWS infrastructure. File uploads (site images and media) are stored in Supabase Storage, which also encrypts data at rest. Authentication tokens are transmitted only over HTTPS and are never exposed in URLs.

  • User authentication is handled by Supabase Auth, which implements industry-standard JWT-based session tokens. Passwords are hashed using bcrypt and are never stored or transmitted in plain text. We implement row-level security (RLS) policies on all user data tables in our database — your data is accessible only to your own account, enforced at the database level regardless of application-layer logic. Administrative database access uses a separate service role key that is never exposed to client-side code.

  • Hanwell Studio is hosted on Vercel, which provides global CDN delivery, DDoS mitigation, and automatic TLS certificate management. Our database and storage infrastructure is managed by Supabase, running on AWS in the United States. Neither Vercel nor Supabase employees have routine access to user data. We use environment variables and secrets management to keep API keys and credentials out of source code.

  • API endpoints that accept user-submitted data (such as contact forms) are rate-limited by IP address to prevent abuse. Authentication endpoints are rate-limited by Supabase's built-in mechanisms. We monitor for unusual traffic patterns and may temporarily block IP addresses that display abusive behaviour.

  • If you discover a security vulnerability in Hanwell Studio, we ask that you report it to us privately before disclosing it publicly. Email your findings to hello@hanwell.studio with a description of the issue, the steps needed to reproduce it, and the potential impact. We will acknowledge your report within 2 business days and work to resolve confirmed vulnerabilities promptly. We do not operate a formal bug bounty programme at this time, but we are grateful for responsible disclosures and will acknowledge your contribution if you wish. Our machine-readable security policy is at hanwell.studio/.well-known/security.txt.

  • In the event of a confirmed security incident affecting user data, we will: contain the incident and assess its scope; notify affected users by email as soon as reasonably practicable, and in any event within 72 hours of confirmation; notify relevant data protection authorities as required by applicable law; and publish a post-incident summary once the investigation is complete. We maintain internal runbooks for common incident types and conduct periodic reviews of our security posture.

  • We do not store payment card numbers, CVVs, or bank account details — all payment processing is delegated to Polar. We do not store passwords in plain text or reversibly encrypted form. We do not sell user data. We do not provide third parties with access to user data except as described in our Privacy Policy and sub-processor list.

  • Hanwell Studio is committed to making hanwell.studio accessible to everyone. We aim to meet WCAG 2.1 Level AA across the application. Measures in place include: semantic HTML with correct heading hierarchy; ARIA labels and roles on modals, accordions, and navigation; full keyboard navigability; visible focus indicators; colour contrast meeting WCAG AA requirements; alt text on informational images; and responsive layouts usable at 200% zoom. The site builder canvas (drag-and-drop section editing) involves direct-manipulation interactions not currently fully accessible via keyboard or screen reader — we are working to improve this. All other areas of hanwell.studio are intended to be fully accessible. If you encounter an accessibility barrier, email hello@hanwell.studio with the page and a description of the issue. We aim to respond within 5 business days.

  • For security concerns, privacy questions, or accessibility issues, contact Hanwell Studio at hello@hanwell.studio.