Privacy

Your account. Your email address, and — if you sign in with GitHub — the name and avatar GitHub returns. We use a password-less sign-in link, so we never hold a password.

What you set up. Your product description, target audience, the terms you track, any forum or RSS addresses you add, and your reply guidance. Scoring depends on this text, so it is sent to our analysis provider (below).

Public posts we find. For each match we store the author's public username, the post title and body, its address, timestamp and public engagement counts. We only read content that is already public, or — for Telegram groups — content in a group whose admin added our bot.

What we derive. An intent label, a 0–100 score, a one-sentence reason, and an optional reply draft.

How you work. Which posts you marked relevant or irrelevant, lead stages and notes, saved views, and replies you sent through us.

Your settings. Notification channel and threshold, digest hour and time zone, and — if you connect them — your Telegram chat, Slack channel, and network accounts.

Billing. A customer and subscription identifier and your plan. Payments run through Polar as merchant of record; card details never reach our servers.

If you connect Bluesky, Mastodon, GitHub, YouTube or a Discourse forum, we store an access credential for that account, encrypted at rest with AES-256-GCM. We never ask for your account password.

We request the narrowest permission each network offers for posting. Some networks describe that permission more broadly than we use it — YouTube's only write scope is worded to cover editing and deleting your videos, but Earlyn only ever creates a comment.

A connected account is used for exactly one thing: publishing the reply you press send on. Disconnecting it in Settings deletes the stored credential immediately.

If you connect a YouTube account, Earlyn's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We request youtube.force-ssl solely to post a comment as you. We do not read your videos, analytics or subscriber data, we do not use Google user data to train models, and we do not transfer it to anyone except as needed to publish the comment you send.

Anthropic — post content and your product description are sent to Claude to classify intent and draft replies. Sent under Anthropic's commercial terms; not used to train their models.

Railway — hosting and the Postgres database, in the Amsterdam region.

Resend — sign-in links, alerts and daily digests.

Polar — payments and invoicing, as merchant of record.

Sentry — server error reports. We do not run any browser tracking or analytics script.

Telegram and Slack — only if you connect them, and only to deliver your alerts.

Source platforms — we call the public APIs of the networks you track in order to find posts.

We do not sell or rent your data, we run no advertising, and we place no analytics or tracking cookies. The only cookie we set is the one that keeps you signed in.

We never post anything without you pressing send. There is no autopilot.

We keep your data while your account is open. Deleting your account in Settings removes your projects, tracked terms, found posts, analyses, leads and connected credentials.

Notification emails carry an unsubscribe link that turns off alerts without deleting anything.

To ask for a copy of your data or to have it deleted, write to hello@earlyn.app and we will act within 30 days.

We will update this page when what we do changes, and move the date at the top. Material changes will also be emailed to you. Last updated 6 September 2026.