commad

Privacy

Commad stores what it needs to run your account and write the ads.

Account

Supabase Auth stores the account. A password stays with Supabase. Continue with Google sends you to Google, then Supabase keeps the email Google shares. We store that email on your profile, along with the pages you run.

Pages you run

When you click Commad on a page, the extension sends us the page address, its title and the comments or reviews shown on it. We store them with the hooks and primary texts we return. The comments are sent to OpenAI to write that pack. Do not run Commad on a page you are not willing to send to them.

Try it on the page

The homepage demo sends the comments you paste to OpenAI to write the hooks. We do not store that paste. We store the hooks for up to 48 hours so we can email them, then they expire. If you leave an email, we store it with the campaign tags from your visit (utm parameters and fbclid) and send the full set from francesco@commad.app. We store a hash of the network address, not the address itself, to limit how often the demo can run.

Payment

Stripe processes the card. We store a Stripe customer id, the subscription status, and when the current period ends. We never see the card number.

How you found us

When you land on Commad, we store the campaign tags from that link (utm parameters and fbclid) in a first-party cookie named commad_ft. If you create an account, we copy those tags onto your profile so the sign-up can be tied to the ad. This cookie is not the Meta or Google measurement cookies below.

Cookies and measurement

Nothing below runs until you press Accept in the cookie banner. If you press Reject, or do nothing, none of these tools load and they set no cookies.

Google Tag Manager loads our Google tags. Google Analytics counts page views, signups and checkouts, and stores the _ga cookies. Meta Pixel sends the same events to Meta and stores the _fbp cookie. When you sign up or pay, our server also tells Meta directly (Conversions API), with your email and account id hashed. That is how we see whether ads lead to an account or a payment. We never send your email to Google.

PostHog (hosted in the EU) records product analytics and session replays to help us understand how the app is used and where errors occur. Replays mask all text inputs and generated output, so your thread content is never recorded. PostHog identifies you only by your account id, never your email. PostHog sets ph_ cookies only after you accept.

We also keep a first-party event log (product_events table in our database) for operating the service, which records product events for all users. This is stored on our own infrastructure and is not shared with any third parties.

We also keep the campaign tags from the link you arrived on (utm parameters, fbclid, gclid) in this browser, so a signup can be credited to the ad that brought you.

We store your choice in this browser for up to 12 months, and log it on our server under a random id, with no email or IP address, so we can show what you agreed to. To change it, use here or in the homepage footer. If you withdraw, we remove the cookies above and reload the page.

Deletion

Delete the account from Account inside the app. That removes your login, your profile and every thread and pack stored with it, and deletes your Stripe customer, which stops any subscription. Stripe keeps its own payment records as the law requires. If you cannot log in, email the address on your Stripe receipt from the address you signed up with.