Heavyfeather
PricingLive demo
Log inCreate account
ExplorePricingLive demo
Log inCreate account

Security at HeavyFeather

Built with deliberate safeguards.

The practical controls HeavyFeather uses today, the boundaries of those controls, and how to report a concern responsibly.

AboutPrivacy PolicyTerms of ServiceSecurityContact
01

Security approach

HeavyFeather uses layered controls appropriate to an actively developed web application. Security is treated as ongoing engineering work, not as a certification claim. This page describes controls currently implemented and does not claim that any system is risk-free.

02

Hosting and transport

  • The production application is hosted on Cloudflare and served over HTTPS.
  • HTTP Strict Transport Security instructs compatible browsers to use encrypted connections for the domain and its subdomains.
  • Production data is stored in a tenant-scoped Cloudflare D1 database.
03

Accounts and access

  • Passwords are stored as one-way hashes rather than recoverable plaintext.
  • New accounts currently require manual early-access review before they can enter a workspace.
  • Application routes enforce account, workspace, and staff authorization boundaries.
  • Sessions use secure cookie-based authentication controls.
04

Connected-service credentials

Provider credentials, OAuth refresh tokens, and integration secrets are encrypted at rest with AES-256-GCM, masked by default in the interface, and used on the server. HeavyFeather requests provider permissions that support visible product features and documents the current Google Ads data scope in the Privacy Policy.

05

Browser and application protections

HeavyFeather sends security headers that restrict embedding, object content, form destinations, referrer disclosure, sensitive browser capabilities, and MIME-type interpretation. Policies are kept compatible with the application's legitimate Shopify and Google authorization workflows.

06

Analytics and public forms

Google Analytics is consent-gated and limited to public pages. It does not load in private customer or staff workspaces. Public contact and signup endpoints use validation and abuse controls, and submitted messages are reviewed in the private staff interface.

07

Report a security concern

If you believe you found a security or privacy issue, use the Contact form and begin the subject with “Security report.” Include the affected URL, the behavior you observed, and a safe way to reproduce it. Do not access another person's data, disrupt the service, or perform destructive testing. HeavyFeather does not currently operate a public bug-bounty program or claim a formal security certification.

Heavyfeather
ProductPricingLive demo
Get startedCreate accountLog in
CompanyAboutPrivacyTermsContact
© 2026 Heavy Feather. All rights reserved.