Privacy policy

Reather turns public GitHub README files into creator-controlled technical stories.

Data we process

We process your Clerk account identity, GitHub username and avatar, GitHub App installation metadata, selected public repository metadata, root README revisions, generation activity, and published story content. We do not request access to private repositories.

How we use it

We use this information to authenticate you, detect root README changes, generate drafts with Eve, publish stories you approve, enforce plan limits, prevent duplicate jobs, and operate and secure the service.

Service providers

Reather uses Clerk for authentication, GitHub for repository access, Neon for product records, Sanity for story content, Vercel for hosting and operational analytics, PostHog for product analytics and client error reporting, and Vercel AI Gateway and Eve for generation. Preview billing tests use Stripe sandbox data; live billing is not enabled for the Starter launch.

Product analytics and session replay

We use PostHog to understand product usage and diagnose client-side errors. Reather identifies signed-in users with an internal Clerk ID, not an email address, and our custom analytics events do not include repository names, README content, GitHub tokens, or billing details. Session replay is off by default and starts only if you choose “Allow replay.” Replays mask all form input and on-page text, and remove query strings from captured URLs. You can decline replay without affecting use of Reather.

Retention and deletion

Deleting your account removes stories from public view immediately, disables automation, and schedules permanent deletion after 30 days. Provider security logs and backups may persist for their normal limited retention periods.

Your choices

You can unwatch repositories at any time, change repository access in GitHub, or delete your Reather account from the account deletion page. Questions can be sent to mustaphaliaichi@gmail.com.