TallyJobs

Privacy policy

Last updated 2026.

Who this covers

This policy describes TallyJobs at tallyjobs.app, operated by jacobandrewbarton@gmail.com. It is the account you sign in to, not a separate analytics product.

What we store

• Account: email address, optional name, and a Google account id if you use Google sign-in.
• Job search content you enter: companies, roles, notes, contacts, interview notes, saved jobs, tags, links, and dates.
• The background you save for Role Fit (resume text or a summary you paste) and any analysis you choose to file on a record.
• Billing: Stripe customer id, subscription id, plan name, and the date access runs until. Card numbers stay at Stripe.
• Role Fit usage: when a read ran, and the input and output token counts Anthropic reports. The usage row does not store the posting.
• A session id and a CSRF token in cookies so you stay signed in and so another site cannot submit changes as you.

Role Fit sends text to Anthropic

When you run Role Fit, two things leave this server: the job posting you pasted, and the background saved on your account (or, if the operator has turned on a server-wide profile file, that file). They are sent to Anthropic's API to generate the read, along with the instructions that ask the model to stick to that background. Anthropic's privacy policy and terms apply to that processing. We do not send your data to Anthropic for any other feature. If you do not run Role Fit, nothing is sent.

Other processors

• Stripe, for checkout, subscriptions, and the customer portal.
• The email provider the operator configured (for example Resend), which receives your email address and the sign-in link.
• Google, only if you choose Google sign-in. We receive your email, whether Google says it is verified, your name, and the Google subject id.

Cookies

The session cookie is HttpOnly. A second cookie holds the CSRF token so the app can send it back on changes. Both are SameSite=Lax. They are not used for advertising.

Export

The app's export downloads a JSON file of your applications, contacts, interviews, activity, saved jobs, dismissed suggestions, and saved background. It does not include anyone else's data. Import replaces your records only.

Deletion

The Account page deletes the account when you type DELETE. That removes your user row and, through database cascades, your applications, activity, interviews, contacts, saved jobs, background, sessions, and Role Fit usage. Magic links for that email are deleted too. If you have a Stripe subscription, we ask Stripe to cancel it. Stripe still keeps payment records under its own policy.

A lifetime purchase leaves a sale row so the 50-seat cap cannot be reset by deleting an account. That row keeps the email and the Stripe checkout id. The job-search content is still deleted. Ask jacobandrewbarton@gmail.com if you need that sale record removed and understand the cap may then be wrong by one.

How long

Content stays until you delete it or delete the account, or until the operator shuts the service down. Server logs may keep an IP address and a request line for a short operational window. Sign-in links are discarded about an hour after they are created.

Security

Each table of job-search data is stored with your user id, and the API reads and writes only that id. This is a single SQLite database on the server, not a separate database per customer. Isolation is enforced in the queries, not by a physical split.

Contact

Privacy requests: jacobandrewbarton@gmail.com.