Privacy
Last updated 5 September 2026
Jobsy is a job-discovery app. You swipe on real job listings and it learns what you want. The data that makes that work is yours, it works only for you, and this page says where all of it is.
What we hold, and where
This is the whole list. It is kept in step with the code: the two buttons under Your data in ✨ Personalize walk exactly this inventory, and a test fails the build if a store is added without a bullet here.
- Your profile state — your setup answers, every swipe and its date, the model Jobsy has learned about you, your interest threads, what each role you liked is marked as, any note you typed against one, how well Jobsy thinks you fit it and — for each gap it named — the one line it suggests you could say about that in an interview and the one thing it suggests you build next, your résumé text and, if you wrote one, the paragraph about the work you're proudest of. Held in our database (Supabase), and cached in your own browser.
- A second copy of that same profile state, in Jobsy's own Notion — this is where profile state was kept before Jobsy had a database of its own, and it is still the standby: where Jobsy runs without that database set up, this is what your setup and your swipes are saved to instead. Where one exists it holds the same list as the bullet above, as it stood when it was last written — nothing extra. Both buttons below reach it: it is in the download, and deleting your profile clears it out. One honest detail about that last part — Notion's API cannot erase anything, so what the delete does there is archive it, which takes it out of the database and leaves it in the trash of that workspace, which is ours and not yours.
- Where your likes go — the delivery setting for your profile, and, if you connected your own Notion database, the integration token you gave us, what we read about that database's columns so a like can fill them, which of those columns you chose for each piece of a like, and Notion's own message when it last refused one. Held in our database.
- Liked roles waiting to be emailed — if you chose the daily email, the roles you liked sit in a queue until the next email that carries them, each with the fit analysis Jobsy worked out for it, if AI mode was on. If you've set that email to Off they wait there until you turn it back on; they are also always in your Liked list in the app.
- Roles already sent — one line per role you liked saying it was already delivered, so a dropped connection can't send the same one twice. It goes when you undo the like.
- Which account may open which profile — one line linking your sign-in to your profile, the name your profile is shown under, and your email address. Both of those come from the Google account you signed in with. We take the address from there rather than asking you to type one because a draft CV is your whole career history in one document, and one wrong character in a typed address would send it to a stranger with nobody ever finding out.
- How much you used — a count of AI batches and job searches per day, so a busy day can't run up a surprise bill. A count, not the contents.
- Requests of yours that failed — when Jobsy's own server breaks, it writes down which part of it broke, what the error said and when, so we find out without you having to tell us. It is attached to your account, which is why it is in the list — but it records nothing about what you were looking at: no search terms, no swipes, no résumé.
- Anything you told us was wrong — if you use the Something wrong? link at the bottom of ✨ Personalize, we keep what you typed, the email address you gave if you gave one, and a few small facts about what was on screen at the time: which tab you were on, where your likes go, whether AI mode was on, and the id of the job you were looking at along with the location printed on it. The same applies if you use ⚑ Report this job on a card, which also keeps the details of that listing — its title, the employer, the link, where we found it and the category we gave it. Those are facts about a job advert rather than about you. Never your résumé, your swipes or anything from your browser beyond that. It is attached to your profile, so it is in the download and in the delete below.
- Your invitation — the email address that was invited, and the Google sign-in itself, which Supabase holds on our behalf.
- A place on the waitlist — if you signed in while Jobsy was full, we keep the address you signed in with and when you asked, so we can let you in when there's room. That's the only thing it is used for. We delete waitlist entries a year after they were made, and deleting your account removes yours straight away.
- Refused sign-in attempts, and reports sent — when a password or a sign-in is refused, the internet address it came from and a count of how many times, so nobody can sit and guess the password; and the same count of reports sent through Something wrong? or ⚑ Report this job, so nobody can flood them. Both are attached to no account and no name — a count and an address, never what was in the report — which is why neither is in the two buttons below. Getting the password right clears the first.
- Your browser — a copy of your profile state lives in this device's local storage so the app works instantly and offline.
Who else sees it
- Anthropic. Jobsy sends Claude a summary of your preferences, the roles it is choosing between, and — this is the one worth reading twice — your résumé text and the paragraph about the work you're proudest of. Choosing which roles to deal you, building a plain-language profile of you, working out how well you fit the roles you liked and what you could say or build about the gaps, and — when you fast-track a role — writing you a draft CV and cover letter all happen only when AI mode is on. Find my keywords is the exception, and it is the earliest point your résumé leaves this device: it sends your résumé as soon as Jobsy has an Anthropic key — including from the setup screen, where AI mode cannot be on yet because you have no profile, and while you are in Browse mode, where the rest of the AI is off. With no Anthropic key configured, neither your résumé nor the paragraph ever leaves your device, and your keywords are found here instead.
- Supabase hosts the database and runs the Google sign-in.
- Notion, if you chose it: your likes are written into the applications database you connected, using the token you gave us.
- Resend delivers our email: the daily digest, if you chose it, and the draft CV and cover letter Jobsy sends you when you fast-track a role. Those drafts go to you and to nobody else — Jobsy never sends anything to an employer, and never applies on your behalf.
- Job sources. Searching for roles sends the search terms — your fields, keywords, pay floor and location — to the job APIs. It never sends your résumé or your swipes.
Nobody else. Your data is never sold, never shown to recruiters, and never used to rank one employer above another. That is written into Jobsy's constitution and it survives any acquisition.
Cookies
One, called jobsy_session. It records that you signed in, and
nothing else. There is no tracking and no analytics, which is why there is
no cookie banner — adding one would imply we do something we don't.
Getting a copy, and getting rid of it
Open ✨ Personalize and scroll to Your data.
- Download my data gives you a JSON file containing everything in the list above. Your Notion token is reported as stored rather than copied into the file — it is a password to your own workspace, and downloading it would create a hazard for you, not remove one.
- Delete my profile removes every item in that list, ends your session and clears this browser's copy. When the profile you delete is the last one on your account, the account, your invitation and your sign-in go with it. It cannot be undone and there is no backup we can restore from.
One thing deletion does not touch: your own Notion workspace. If you connected an applications database, those pages are in a workspace that belongs to you. We wrote into it; deleting out of it is not ours to do. Delete those pages yourself, and remove Jobsy's integration from your workspace while you're there.
One partial exception, stated because the alternative is pretending: if your likes go to the daily email, a like that has already been mailed is in an email we can't unsend.
Asking us
If anything here is unclear, or you want something done that the buttons don't do, reply to any Jobsy email.