๐Ÿ” Security

Built for professionals who handle sensitive data

Cloudymonkey is a B2B platform used by travel professionals to manage client bookings and financial data. We treat security as a core product requirement, not an afterthought.

๐Ÿ”’ TLS 1.2+ everywhere
๐Ÿ›ก๏ธ Passwordless auth
๐Ÿฆ ISO 27001 infrastructure
๐Ÿ‡ฌ๐Ÿ‡ง UK/EU data residency
โš™๏ธ Zero password storage
๐Ÿ”‘

Authentication

Cloudymonkey uses magic link (OTP) authentication only โ€” there are no passwords to store, hash, breach, or forget. Every login is a one-time, expiring token sent to your verified email address.

  • No password database โ€” eliminates the most common breach vector
  • Magic links expire after 10 minutes
  • Each link is single-use
  • Sessions are JWT-signed and automatically expire
  • Powered by Supabase Auth (SOC 2 Type II certified)
๐Ÿ”’

Encryption

  • In transit: TLS 1.2+ enforced on all connections โ€” no HTTP fallback
  • At rest: AES-256 encryption on all stored data (AWS/Supabase)
  • HSTS: HTTP Strict Transport Security enforced with 1-year max-age and preload
  • API keys: Never stored in client-side code โ€” all third-party API credentials live exclusively in server-side environment variables
๐Ÿ›ก๏ธ

Application Security

  • Content Security Policy (CSP): Restricts script and resource origins to an explicit allowlist
  • X-Frame-Options: DENY: Prevents clickjacking attacks
  • X-Content-Type-Options: nosniff: Prevents MIME-type sniffing
  • Referrer-Policy: Strict origin control on all outbound links
  • Permissions-Policy: Camera, microphone, geolocation, and payment APIs disabled by default
  • Row-level security: Database queries are scoped to the authenticated user at the database level โ€” not just application logic
๐Ÿ—๏ธ

Infrastructure

Cloudymonkey is built on infrastructure providers that hold independent security certifications:

ProviderRoleCertification
Supabase (AWS eu-west-1)Database, auth, storageISO 27001 ยท SOC 2 Type II
ResendTransactional emailSOC 2 Type II
DuffelFlight data & bookingISO 27001 ยท PCI DSS

All data is stored and processed in the UK or EU (Ireland). We do not transfer personal data outside of the UK/EEA.

๐Ÿ“‹

Access Control

  • The agent dashboard requires a valid authenticated session โ€” unauthenticated users are immediately redirected to login
  • The admin panel is restricted to a single authorised email address
  • All API endpoints require a valid JWT bearer token โ€” no anonymous access to agent data
  • Third-party API calls (flight search, bookings) are server-side only โ€” your clients' data never passes through browser-side code to external APIs
๐Ÿ“ง

Email Security

  • SPF: Authorised sender policy in DNS
  • DKIM: Cryptographic email signing on all outbound mail
  • DMARC: Policy enforcement to prevent spoofing
  • All login emails sent from @cloudymonkey.com via Resend (EU region)
๐Ÿ’พ

Data & Backup

  • Automated daily database backups via Supabase
  • Point-in-time recovery available
  • Saved quotes are stored in your local browser storage โ€” they never leave your device and are not held on our servers
  • Passenger booking data is passed directly to the airline fulfilment provider and is not stored on Cloudymonkey's servers
๐Ÿ”Ž

Monitoring & Incident Response

  • Platform and edge function logs retained for security review
  • Suspicious access patterns trigger session invalidation
  • In the event of a confirmed data breach affecting your account, we will notify you within 72 hours in accordance with UK GDPR Article 33
  • To report a suspected security incident: security@cloudymonkey.com

๐Ÿ› Responsible Disclosure

If you discover a security vulnerability in the Cloudymonkey platform, we ask that you report it to us privately before public disclosure. We are committed to working with security researchers in good faith.

Contact: security@cloudymonkey.com

Please include: a description of the vulnerability, steps to reproduce, potential impact, and your contact details. We aim to acknowledge reports within 2 business days and provide a resolution timeline within 5.

We will not pursue legal action against researchers who act in good faith and follow responsible disclosure principles.