What we collect and why

Google sign-in supplies your name, email address, and email verification status, plus a stable account identifier, and may supply a profile image URL. Makeable uses those account details to keep you signed in, show your profile, and connect saved builds to your account. New waitlist records contain your name and email, but not your Google account identifier or profile image.

How we use it

We store your email address in Makeable's waitlist storage so we can manage the waitlist and send pilot-access communications. The hosted deployment uses Netlify Blobs. If you join through Google sign-in, we may also keep your name to personalize the invitation. We deduplicate by normalized email address and never store your Google credential token.

Analytics

We use PostHog to understand visits and actions such as opening a preorder, starting checkout, submitting a build idea, and completing Google sign-in. PostHog receives an anonymous browser identifier and, after sign-in, a one-way pseudonymous Makeable account identifier so activity can be counted across visits. PostHog receives event details, not your email address, name, Google account identifier, or Google credential. Inputs are masked in session recordings.

Remembering your signup

After a verified sign-in, Makeable stores a random, HttpOnly browser session cookie so the same browser can recognize your account. The cookie is not a Google credential, contains no email address, cannot be read by page JavaScript, and expires after one year. Removing browser cookies means you may need to sign in with Google again.

What we do not do

• We do not sell your email address or Google profile data.
• We do not use Google sign-in data for ad targeting.
• We do not ask for more Google data than we need for sign-in, saved builds, and the waitlist.

Retention and removal

We keep waitlist records until they are no longer needed for pilot access or product communication. You can ask us to remove your record at any time.