Cookie policy

These are what keep you signed in and keep your work from disappearing. They're not optional.

• Sign-in session. When you log in, Supabase (the service that handles accounts) stores your session in your browser's local storage, so you stay signed in between visits.
• Guest pattern draft. If you start designing at /try without an account, your in-progress pattern is kept in local storage so it survives a page reload, and is claimed into your account if you sign up.
• Your cookie choice. Whatever you pick below is itself remembered in local storage, so you're not asked again every visit.

Heddle uses Google Analytics to see which pages get used and where people get stuck, so I know what to work on next. It's off by default. If you accept the cookie banner, Google Analytics loads and sets its own cookies to recognize repeat visits; if you decline, none of that runs, and nothing is sent to Google.

Beyond page visits, a few specific actions are recorded, so I can see where people drop off rather than just how many pages loaded: reaching the guest sign-up prompt, completing sign-up, and exporting a PDF. None of these include your name, email, or anything you've designed.

You can change your mind at any time:

Billing is handled by Stripe's own hosted checkout page, not by Heddle directly. While you're there, Stripe may set cookies under its own domain to process the payment and prevent fraud. Heddle never sees your card details.

The site's typefaces load from Google Fonts, which means your browser makes a request to Google's servers to fetch them. That request doesn't set an analytics cookie, but it does mean Google can see that a request came from your IP address, the same as it would for any external image or font.

If any of this is unclear, or you want your data handled differently, email me directly at hello@heddledesign.com — it comes straight to me. You can also reach the contact page.