What we collect,
and why.

Your email address (required — that's how we reach you). The tier you chose on the signup card — Free, Pro, or Team — so we know which signup segment you're on. Optionally, a first name (so pre-launch emails can read like a person wrote them) and an optional company or role field (so the Team signup has a real signal about who's behind a request). Server-side, we also log standard request metadata at submit time — IP address and user agent — which we use only for spam and duplicate-signup prevention.

Anonymous analytics events (page views and which tier card got clicked on /pricing) so we can see which copy and which tier is pulling weight during the signup phase. Cookies are limited to a single anonymous visitor ID and an A/B-test variant cookie used only on the homepage.

We do not collect your payment details — there is nothing to pay for until Loudify launches. We do not collect location data beyond what your IP address reveals. We do not sell or rent your data, and we do not run third-party advertising trackers.

To know who we've already emailed so you don't get the same launch announcement twice, and to remove you cleanly when you unsubscribe. Without this we'd be guessing, and you'd get duplicate messages.

Each tier on /FAQ gets a different pre-launch email cadence. Pro and Team subscribers get more detailed product updates; Free subscribers get less frequent, broader updates. We match cadence to tier choice — that's the only reason we ask.

The numbers shown on the homepage and /pricing ("220 on Free, 88 on Pro, 14 on Team") are computed from your tier choice at signup. The count is anonymous — no individual is identifiable from a tier total.

Server-side request metadata (IP, user agent) plus a uniqueness check on email lets us block duplicates and obvious scripted abuse of the signup endpoint. We do not profile you from this.

Your account and email rows are kept while your account is active. They're deleted when you unsubscribe via the link in any email we send, or within 90 days of you closing your account or asking us to delete it. Encrypted backups age out within an additional 30 days.

Page-view and click events are kept for 13 months from collection, then deleted in the next monthly purge. They never carry your email or any identifying field — only the anonymous visitor ID described above.

When you use Loudify to generate a launch tweet, your project URL leaves Loudify and is sent to OpenAI's API for analysis and tweet generation. OpenAI processes the request under their own data-use policy; we send only the URL and the relevant context — never your email or account data.

If and only if you click Publish on a generated tweet, that tweet text is sent to X via the Twitter MCP for posting under our verified handle. We do not post without an explicit click.

Account rows, analytics events, and generated-tweet history are stored in a Neon-hosted Postgres database. Neon is the storage layer; only Loudify reads and writes those rows.

Pre-launch mail is sent through a transactional email provider (the specific vendor is a deployment-time configuration — counsel can name the exact one in this section before launch). The vendor receives only your email address and the rendered email body.

One click from any email we send. The link takes you to a single-step unsubscribe page that removes your row immediately. No "are you sure," no re-engagement sequence, no follow-up "we miss you" mail.

Email the address at the bottom of this page and we'll send you a JSON export of every row we hold that's tied to your email — account entry, tier choice, named fields, and any signup-time metadata we still have. Typical turnaround is a few business days.

Same channel. Reply to any email or write to the contact address and your row is removed from production. You won't get a confirmation marketing email afterward — just the deletion confirmation you asked for.