What we do with your data

Published, not something you are asked to agree to. What you agree to is the authorization and the free-tier promise, on the way in.

What we do with your data

Version 2 · 2026-08-31

The short version

Fried Mango works your job search out of a mailbox you made for it. It holds what you tell it, what it finds in that mailbox, and what it writes on your behalf. It does not sell any of that, does not advertise against it, and does not put it into a model that serves anybody but you.

What you sign in with

Google sign-in. We receive your email address and a Google-issued identifier for your account. We never see your Google password, and we do not store one.

What you give Google permission for

Two things, and they are the whole list:

  • Reading your job-search mailbox (`gmail.readonly`)
  • Sending mail from it, as you (`gmail.send`)

When you sign in, we get the number of messages in your email account. That is the whole of it: one request, one number. Nothing opens, lists, or downloads a message.

We use it to check that you have signed in with a mailbox made for your job search rather than the account you have used for fifteen years. If it is the second one, we turn you away and keep the number that decided it, so we can tell you why.

Reading your mail is now something the product can do, and here is exactly what that means today. One task exists — it looks at messages that arrived in the last day and writes a line saying who each one was from and what its subject was, so you have a record. It does not reply, does not decide anything, and does not act on what it read.

Mail can now go out, and only an application you approved. One task sends: it attaches the resume you opened and the letter you read, to an address for an employer you said yes to. It sends nothing else, to nobody else, and it cannot send anything you have not approved. That was asked for first — authorization version 3 — which is the promise that matters.

Nothing reads your mail unless you have connected the mailbox, and you can disconnect it at any time from your Google account's permissions page.

The permission is requested at sign-in because Google asks for permissions once, up front, rather than at the moment they are first used.

Our use of what we receive from those two permissions follows the Google API Services User Data Policy, including its Limited Use requirements. In plain terms that means we use your mail to run your job search and for nothing else — in particular, it is never used to build or improve anything that serves another person.

What we store

Things you tell us. Your display name, pronouns, timezone, the area you are looking in, and how far you are willing to travel. Answers you give about your work history and what you are looking for.

Your prospects — the jobs you are pursuing. Postings, employers, where each one stands, your notes, and a record of what changed and when. We say prospect rather than application because most never become one: a prospect can be a lead you are still weighing up, or a conversation with somebody you already know rather than a form to fill in.

Things written for you. Resumes, cover letters, application answers and the text of emails — each version kept, so it is always possible to say exactly what you approved.

Contact details for people at employers. Names, roles, email addresses and phone numbers of recruiters and hiring managers connected to your prospects. These are people who have not agreed to anything with us; we hold what is necessary to correspond with them about you, and nothing more.

Bookkeeping. When you signed in, whether you were admitted or turned away and why, the mailbox size described above, and which version of which document you accepted and when.

Who else can see it

Fried Mango runs on infrastructure other companies operate, and each of them can technically reach the part it holds. They are all in the United States, and they are:

A managed database and sign-in providerwhere everything described above is stored
A web hosting providerserving the dashboard you are looking at
A cloud compute providerrunning the work behind it
Anthropicwhich runs the model your Search Team thinks with

The first three are suppliers who hold your data because they run the machinery. None of them may use it for their own purposes. Ask us who they are and we will tell you — this is a description of roles rather than a secret, and the list changes as infrastructure does.

Anthropic is named rather than described, because it is the one that reads rather than stores, and the next section is about that.

The model, and what reaches it

Your Search Team is a set of language models. Those models are made and run by Anthropic, a company in the United States, and reaching one means sending it text.

What goes to them:

  • Your profile answers — your work history, what you are looking for, what you will not take.
  • The job postings being considered for you, and what we know about the employers.
  • The messages in your job-search mailbox, where a task needs to read one to do its job.
  • Drafts written for you, while they are being written.

What never goes to them: the key to your mailbox, your passwords, or anything else that would let somebody holding it sign in as you. That is not a policy, it is how the system is built — the part of Fried Mango that talks to a model is refused those credentials outright, and there is a test that fails if that ever stops being true.

What Anthropic may do with it:

  • They do not train models on it. Their commercial terms for the interface we use say so directly, and that is the basis on which we send anything at all.
  • They delete it within thirty days. That is their standard retention. It is not zero — we have no arrangement with them for zero — so for up to a month a copy exists on their systems as well as ours.
  • One exception, which we would rather you heard from us. If something we send trips their abuse detection, they may keep it for as long as two years while they look into it. We do not expect that to happen to a job search. We are telling you because a promise of thirty days with a footnote is worse than a plain description of both.

They are the only one. No other model company receives anything, and adding a second would be a new version of the [authorization](authorization.md) and a fresh acceptance — not a notice, and not a quiet edit to this page. That is why they are named: a name is something you can look up, and "an AI provider" is not.

What goes to employers, which is the point

The companies above hold your data because they host us, or read it because they run the model. Employers are different: they receive it, because putting your application in front of them is what you are here for.

When Fried Mango applies for a job or writes to a recruiter on your behalf, what goes out is what you would send yourself — your name, your contact details, your resume, your answers, and the text of the message. It goes from your mailbox, as you, to the employer you chose.

Nothing goes out until you have read the exact words and said yes. Not a summary, not "an email like this one" — the actual text that will be sent. That is the promise in the [authorization](authorization.md), and it is the one that governs everything in this section.

Once something is sent, it is theirs. An employer holds your application under their own practices, for as long as they keep it. We cannot recall it, delete it from their systems, or tell you what they do with it. That is true of any job application; it is worth saying plainly because here something else did the typing.

Applications can now be sent, by email, one at a time, each one approved by you. What goes is the exact resume and the exact letter you read; the file is made once and stored, so what an employer opens is the document you opened rather than a fresh version of it. Filling in employers' own forms is still not built — when it is, you will be asked again, because a new verb is a new version of the authorization and a fresh acceptance.

What we do not do

  • No person here reads your mailbox — not for support, not for debugging, not out of curiosity.
  • Nothing you give us trains a model that serves anybody else. What we hold makes your own search better and nothing wider than that: it does not go into a general model and it does not improve another candidate's Search Team. Anthropic does not train on it at all.
  • Nothing is sold, rented, or shared with advertisers. There are no advertisers. You are the customer, or you will be; that is the whole point of charging you rather than an employer.
  • We do not touch any mailbox but the one you signed in with.

Keeping it separate is the protection

We ask you to make a Gmail account for your job search rather than using your everyday one, and that request is the largest privacy measure here. A mailbox made two months ago for this contains this. Your real account contains your life, and we would rather not be able to read it.

That got more important with version 2, not less: what we can read is now also what we can send to a model, and the smallest mailbox is the smallest version of both.

How long we keep it

While your account is open. If you ask us to delete it, everything belonging to you goes, and it takes what is under it with it — your prospects, your documents, your notes.

Two things survive that, deliberately: the record that an email address signed in and was turned away, so a refusal does not have to be re-derived, and the record of which terms you accepted, which is the evidence that we asked. Ask for those to go as well and they will.

Deleting your account here does not reach back into what was already sent. Anthropic's thirty days run from when we sent it, not from when you ask us; an employer keeps what you applied with under their own practices. Both are described above so that "everything goes" is not read as more than it is.

You can revoke our access to your mailbox at any time from your Google account's permissions page, without asking us. It takes about thirty seconds and everything stops.

Getting a copy

Ask, and we will give you a copy of what is yours in a form you can read.

If this changes

We will publish a new version. Where a change is about something new being done on your behalf, you get asked again rather than told — that promise lives in the [authorization](authorization.md) and it is the one that matters.

Asking us something

support@friedmango.com. A person reads it.

The terms you are asked to accept · Back to sign in