Heybuck · Updated September 16, 2026

Privacy

Development preview. This page describes the current local preview of Heybuck. Stripe sandbox payments are enabled for testing; no real money is charged.

Information you enter

The quiz stores your answers in your browser so you can continue where you left off. Your saved quiz email address and answers are stored in Supabase. When you open checkout, Stripe receives your checkout email, account reference, and selected offer. Payment details are entered directly in Stripe’s secure form; Heybuck does not store card numbers or security codes. Heybuck stores Stripe customer, checkout, subscription and invoice references, payment amounts, and membership status to manage access and billing. Use only test payment details in sandbox checkout. The separate no-charge preview does not request payment details.

Your subscriptions and requests

Information you add to your dashboard, including subscription details, cancellation and refund requests, and their correspondence, is stored with your account. It is used to show your subscriptions and carry out the requests you authorize.

Connected email

Connecting a mailbox requires a separate authorization. If enabled, Heybuck uses Composio to connect to your email provider and OpenRouter to process relevant mail content, identify subscriptions, and assist with cancellation and refund correspondence. Those providers process the information required for these features under their own terms.

Connecting email does not authorize a cancellation. You review and authorize each request. You can disconnect your mailbox in Settings to stop future scans; disconnecting does not remove requests and information already saved in your account.

Login and browser storage

Heybuck uses a session cookie to keep you logged in. It also stores quiz progress in your browser. Login links are time limited and can be used once. Account and application data is stored in Supabase.

Product analytics

When analytics is enabled, we use PostHog EU to understand where people leave the quiz, whether they find subscriptions, and whether cancellation and refund requests reach a confirmed result. We send specific actions, basic browser/device information, safe campaign labels, and an anonymous browser identifier or internal account ID. PostHog stores separate browser identifiers for the public website and the application in local storage. Earlier application actions are linked when you open your account. Campaign labels can carry from the website into the application.

We do not send your name, email, quiz answers, mailbox contents, merchant names, amounts, payment references, refund reasons, or sign-in tokens to analytics. Automatic click capture and session recording are disabled. Browser analytics respects Do Not Track. Development and test analytics stays off unless explicitly enabled for testing.

Before a public launch

The operating company, support contact, retention periods, and privacy request process will be published before this service accepts real customers. This preview is for product development and review.