Questions, answered

Backdating commits in your own repository is a normal git feature and isn't named in GitHub's policies. The Acceptable Use Policies do prohibit "automated excessive bulk activity" and "inauthentic interactions", so we keep volumes human-scale, write only to the one new repo you name, keep every commit readable by anyone who opens it, and never touch other accounts. GitHub could change its rules; we can't control that.

Anyone can open the repo, and we don't hide it. With the realism engine and real-looking files it won't scream "generator", but it is generated activity. Don't present it as evidence of specific work — treat it like a green lawn, not a résumé line.

Sign-in is read-only (read:user and user:email). Pushing is separate: before your first fill you create the repo on GitHub and install RetroFill on that one repository, and GitHub blocks everything else — a write to another repo is refused, a private repo you did not pick is invisible. Later fills reuse it, and each push uses a key that lasts an hour and reaches one repository. Change or remove it at github.com/settings/installations.

Your GitHub id, login, name, avatar and primary email; an encrypted OAuth token; the plans you paint; job logs; product events like sign-in, fill and undo; your purchases and a Stripe customer id if you buy something; and, if you came through an invite link, the inviter's code. No repo contents beyond what we write. "Delete account" in Settings removes all of it immediately.

Each commit is a real change to a small project (notes, a utility and its test, a journal entry) with varied messages and timestamps at working hours in your timezone. It is still generated activity, and anyone who opens the repo can see it was created on one day.

We keep volumes human-scale with hard caps per day and per fill, write only to a new repo of yours, and warn accounts under 30 days old. GitHub's rules don't mention backdated commits, but GitHub can change its rules or how it counts contributions; if that makes a purchase unusable, we refund it.

Commits stop at the end of the period you already paid for, and you keep the Time Machine features until then. Commits already pushed stay unless you use Undo on the Autopilot repo. Cancel in one click from Billing; "Keep Autopilot" undoes it any time before the period ends.

Yes. Any purchase is refundable within 14 days while it's unused: press Refund on the receipt in Billing and it's issued on the spot, no ticket. If you already used it, the same button files a request and we answer within two business days. If a fill fails, the credit comes straight back and the purchase stays refundable. Autopilot renewals are not refundable, but you can cancel any time before they happen.

No. Previewing on your real graph is free and needs no sign-in. Your first fill is free too if it covers at most 7 days and 20 commits — enough to watch a real push land on your profile before you buy anything.

Any 365-day window you choose: a calendar year, or the rolling year shown on your profile. A Coffee credit pays for one such window; a fill that spans two windows uses two credits. Time Machine removes the limit entirely, forever, for one payment.

Payments go through Stripe's Managed Payments, so Stripe's Link service is the seller of record. Your statement reads LINK.COM* RETROFILL and the receipt email comes from Link, not from us. Prices are in US dollars; where sales tax or VAT applies it is added at checkout and shown before you pay, and refunds include it.