Privacy Policy
Last updated: 2026-10-31
What the plugin uploads
The FairShot Proof plugin never uploads your code, diffs, file contents, tool output or file paths. For each session in a repo you chose to track, it uploads:
- Your own prompts, with secrets removed and cut to 400 characters each. Fenced code in a prompt is replaced by a placeholder.
- Numeric stats such as turns, edits, test runs, retries and duration.
- Commit SHAs, so we can check them against your public GitHub history.
Run tally preview any time to see exactly what the next upload contains. Run tally pause to stop it, or add a .tallyignore file to a repo to exclude it. Nothing from a repo leaves your machine until you track that repo.
What we collect otherwise
- Your email, and your name and email from Google or GitHub if you sign in with one of them. For GitHub we also keep your login.
- Public GitHub data about you: repositories, languages and commit metadata. We read it with our own read-only token; we do not store your GitHub access token.
- The preferences you set: location, work mode, pay floor, work authorization, stack and role types.
- Product analytics (pages visited, buttons used) through PostHog and Google Analytics.
FairShot: your CV, your jobs and your contacts
This part covers what it does with the CV and details you give it.
- Your CV. It is stored only in a private bucket and opened through short-lived signed links. Before any text reaches a language model, we remove your email, phone number and address.
- Who sees you. Your profile is private by default. An employer or founder sees you only after you apply, or after you accept an intro. They see your contact details only after you say yes.
- Sending. We prepare applications, drafts and messages. You press send. We never submit an application or send an email or message for you.
- Contacts you find. People you save while looking for a way in live in your own private tracker. There is no shared people database and no export. Email addresses we guess are labelled as guessed, and we do not probe mail servers. Our servers do not collect contacts from LinkedIn. To have a person removed, email us and we will remove them.
- Jobs. We list jobs from public sources that allow it, and every job links back to the original posting.
- Emails from us. At most one nudge email a day. Each one says why you got it and has a one-click unsubscribe. We do not send an empty digest.
Hidden jobs from open posts
Some people announce a job in a public post on Mastodon or Bluesky. If it fits you, we show it as a hidden job. For each post we keep only the company, role, place, skills and a link to the original, never the post text, and we delete it after 30 days. If you wrote a post or you are named in one and want it gone, email founder@berelentless.dev with the link or your handle. We remove it and do not bring it back.
Applications and response scores
Each seeker has a limited number of applications, so an application means something. That limit is not for sale and nobody can pay to bypass it. Employers are expected to answer every application. If one does not answer within the time we state, the application closes automatically and counts toward that employer's response score. We do not edit or bypass these scores by hand.
How we use it
A nightly job sends your uploaded prompts and stats to a language model to score how you work. The result is your skill profile: an overall score, six habit scores and a short summary. We keep raw prompts for 30 days, then delete them. Scores and stats stay until you delete your account.
What founders see
Only if you turn on open to work. Before you accept an intro, a founder sees your first name and last initial, city, score, habit scores, stack, and a brief written from your stats. They never see your full name, contact details, employer or raw prompts. Your pay floor is used only to filter and is never shown as a number.
If you accept an intro, the founder gets your full name, email and GitHub profile for that role. You can decline, and you can turn off open to work at any time.
Your public card
Off by default. Once your profile has 10 sessions over 2 weeks, you can turn on a public card at a link with your GitHub username. Anyone with the link, founders included, sees your GitHub username, first name and last initial, score, habit scores, stack, session counts and public GitHub stats. It never shows your prompts, code, location, pay, work authorization or contact details. Turn it off on your profile page and the link stops working.
Who processes your data
- Supabase: sign-in and database.
- Vercel: hosting.
- DeepSeek: scoring and written briefs. Receives redacted prompts and stats, not your name.
- NVIDIA: turns summaries into numeric embeddings for matching.
- Resend: intro emails.
- PostHog and Google Analytics: product analytics.
We do not sell your data.
Your control
On the settings page you can export everything we hold about you as JSON and delete your account. Deleting removes your profile, sessions, scores and device tokens. Your local ~/.tally folder stays on your machine until you delete it. If you are in the UK or EU you have the usual GDPR rights, including access, correction and withdrawing consent.
Contact
Questions? Email founder@berelentless.dev.