Privacy Policy

Last updated 2 October 2026

1. Who we are

rightaiforthejob.com ("the Site") is operated by Right AI For The Job LLC, a limited liability company based in Osceola, Indiana, United States. Our full postal address is available on request. For any privacy question, or to exercise any right described below, contact support@rightaiforthejob.com. We answer to that address and it is the fastest route to a person.

2. The short version

There are two different things on this Site and they are treated differently, so the distinction is worth stating plainly before anything else.

What you type or attach in the tool-matching box is processed locally in your browser and is not uploaded to our servers. That has not changed and is not part of any account. Try & compare, further down that page, is a different box with a different answer; it is described below.

An account is optional. If you choose to create one, your email address, the tool lists you save, your answers to “did this work?” and any note you choose to write with one are stored by our service providers, because storing them is the only way they can sync to your other devices. Everything else on the Site works without an account, and if you never create one we store nothing about you beyond the server logs described in section 6.

3. Local processing

Certain features of this Site are designed to process information locally in your web browser.

When a feature is identified as local processing, task inputs and uploaded files used by that feature are processed on your device and are not uploaded to rightaiforthejob.com's servers.

The matching box compares your text against a set of keyword rules held in the page itself. That comparison runs entirely on your device. Your text is never transmitted, stored, or logged.

Try & compare is the exception, and it is not local processing. That section sends the task you type into it, together with the text of any file you attach to that section, to the AI models you tick, through this Site's server so that the API keys are never exposed to your browser. Every one of those models is reached through OpenRouter or Venice, gateways that receive what is sent and pass it to whichever host is serving that model, so the gateway and that host both see it. It sends nothing until you press the compare button, and the providers you did not tick receive nothing. Each provider receives it under its own terms and privacy policy, which govern what it does with the text; this Site does not store the task, the file contents or the answers, and closing the tab discards them. If you would not send a piece of text to an AI provider directly, do not put it in that box and do not attach a file containing it.

The two file buttons are not the same button, and the difference matters. Files attached to the tool-matching box at the top of the home page are opened and read by code running in your browser, and they never leave your device: nothing is uploaded, and the Site's servers never receive the file, its contents, or anything derived from them. Files attached inside Try & compare are read in your browser too, but their text is then sent, because sending it is what that section is for — asking several AI models the same question about the same material. A PDF, Word, PowerPoint or Excel file attached there is opened in your browser and the words are taken out of it; the file itself is never uploaded, but those words are. A picture attached there is treated the same way: any text in it is read out by code running in your browser, and that text is what is sent, never the picture. The one exception is the image row, where a picture is the material itself: there the picture is sent to the image tools you ticked, and the section names them beside the button before you press it. The section says all of this beside the button before you press it.

What that reading takes is a measurement, not the text. For each file the Site records only: its name, its size, the browser-reported type, and counts it can establish by looking — the number of pages in a PDF, slides in a presentation, sheets in a spreadsheet, rows and columns in a CSV, words in a document, the pixel dimensions of an image, and whether a text file contains an error trace. Those counts are used to choose which AI tools to recommend and are shown back to you beside the file. Nothing else is extracted, and no part of a file's content is stored, logged or transmitted.

The reading is bounded: large files are read only up to a fixed limit, and a fact is recorded only when the file states it unambiguously — a PDF whose page count cannot be read with confidence is simply reported without one. Everything is held in the page's memory for as long as the tab is open. Closing or refreshing the page discards the files and the counts together.

Account information, saved tool lists and your answers to “did this work?” are separate from this local-processing functionality and may be transmitted to and stored by our service providers so that account features can function across devices. An answer carries the tool it is about and nothing about the question that produced the recommendation. If you write a note with an answer, that note is stored as you typed it — see section 4, which explains what to keep out of it.

4. Accounts, saved lists and feedback

Creating an account is optional. If you create an account, rightaiforthejob.com may collect information such as your email address, account identifier, authentication information provided by our authentication provider, the AI tools or lists you choose to save, whether you told us a recommended tool worked for you, and any note you chose to write alongside that answer.

We use this information to authenticate your account, synchronize saved tools, lists and feedback across devices, maintain account security, and provide requested account features.

rightaiforthejob.com does not store task inputs, prompts, uploaded files, folders, PDFs, documents, spreadsheets, slides, audio, code, or other materials processed through features specifically identified as operating locally in your browser. Nothing you type into those features is ever copied into an account record. The single exception is text you deliberately type into the note box described in section 4a, which is stored because writing it is a choice you make knowing that.

A saved tool is stored as the identifier of the tool and nothing else — the short name that appears in its web address. We do not store a copy of the tool's details, and we do not record which pages you visited to find it.

Feedback is stored the same way: the identifier of the tool, whether you said it worked, and — only if you pick one after saying it did not — a reason chosen from a fixed list of six. The task you asked about, anything you attached, and the requirements read out of your question are not sent with an answer and are not stored with it. Your feedback is private to your account: it is shown only to you, on /my-feedback/, and it is not published, aggregated, or used as a public rating.

4a. The note box, and the one thing to keep out of it

You can add a short note to an answer. It is optional, it is the only free-text box on this Site whose contents we keep, and it is stored in your account exactly as you type it, up to 500 characters.

Because it is stored as typed, please do not put anything in it that you would not want stored — not the task you asked the matcher about, not the contents of a file you attached, not client names, and not personal or confidential information about yourself or anybody else. Everything you type into the matcher and every file you attach stays in your browser, as section 3 describes. A note does not: it is sent to our service provider and kept until you change or delete it.

The box is empty every time it opens. Nothing prefills it, and nothing in it is derived from your question, your files or the requirements read out of them — the code that saves a note has no access to any of those, and our build refuses to publish if it ever gains any.

A note is private to your account in the same way the rest of your feedback is: it is shown only to you, it is never published or shown to another visitor, and it is never used as a public review or rating. You can edit or remove a note at any time from /my-feedback/, and deleting your account deletes it.

Information associated with your account is stored only as reasonably necessary to provide account functionality, maintain security, comply with applicable legal obligations, and resolve disputes.

5. Google Sign-In

If you choose “Sign in with Google,” Right AI for the Job receives information from Google necessary to create and authenticate your account, such as your email address, Google account identifier, name, and profile image where provided. We use this information only to authenticate your account and provide account functionality. We do not use Google account information for advertising, sell it, or share it except with service providers necessary to operate authentication and account features. Account-associated information may be deleted through your account settings.

6. Information collected automatically

Like any website, requests to the Site reach a web server operated by Cloudflare, Inc.. That provider may automatically log technical information including IP address, browser type, referring page, and time of request, for the purposes of delivering the site and protecting against abuse. We do not use these logs to build profiles and we do not combine them with anything else. Retention is governed by our hosting provider's own policy.

Analytics. Every page on this Site also loads Google Analytics, which measures how the Site is used: the pages you open, the page or search that sent you, the approximate location derived from your IP address, your device and browser, and whether you are a first-time or returning visitor. It sets cookies in your browser to recognise a returning visit. It runs on every visit, whether or not you have an account and whether or not you ever sign in. Section 8 names what it is and how to refuse it, and the Cookie Notice says which cookies it sets.

Advertising measurement. The same tag also carries a Google Ads conversion tag. Its job is to tell us whether somebody who arrived from one of our adverts went on to do something useful here, and to let Google attribute that back to the advert they clicked. It sets an advertising cookie, and where audience features are switched on in our advertising account it can also let Google include this visit in a remarketing audience — which means seeing our advert again elsewhere. It is refused by exactly the same means as the analytics, and the Cookie Notice names its cookie.

Your IP address therefore reaches two parties: our hosting provider, which is unavoidable for any website, and Google. Google states that it uses the address to derive an approximate location and does not log or store it in Analytics. We never see your IP address ourselves in either case.

7. Cookies and local storage

The Site sets analytics cookies on every visit. They belong to Google Analytics, they are described in the Cookie Notice, and they are set whether or not you have an account. They are not strictly necessary: the Site works identically without them, and the Cookie Notice says how to refuse them.

If you sign in, your browser also stores the session that keeps you signed in between pages. That storage is strictly necessary to provide a feature you asked for, and it holds your session only — never anything you type or attach. Signing out removes it.

When you leave the home page to sign in, or for your account pages (My AI Tools, My feedback, Account), the home page keeps what was on it in your browser tab’s own session storage so it is there when you come back: the task you typed, what was read from the files you attached, the AIs you ticked, and any answers already on screen. It never leaves your browser and is never sent to us. It is deleted as soon as the home page puts it back, it expires after two hours, and closing the tab deletes it.

The Site also sets one advertising cookie, for the Google Ads tag described in sections 6 and 8. It is not strictly necessary either, it is named in the Cookie Notice, and the same three ways of refusing it apply.

8. Service providers

We may use third-party service providers to support functions such as authentication, database hosting, infrastructure, and email delivery. These providers may process limited information on our behalf as necessary to provide their services. We seek to limit information shared with service providers to what is reasonably necessary for the applicable function.

Accounts, saved lists and feedback. Authentication and storage of saved lists and feedback, including any note you write with an answer, are provided by Supabase. If you sign in, your browser connects to Supabase directly, and Supabase receives your IP address and the information needed to authenticate you and return your lists. If you never sign in, your browser makes no request to Supabase at all.

Signing in with Google. Google is the authentication provider for signing in, and receives the information necessary to perform it, under Google's own privacy policy. What Google returns to us, and what we do with it, is section 5. If you never sign in, your browser makes no request to Google.

Web fonts. Typefaces are served from this domain rather than from Google Fonts or any other font service. No request leaves your browser to fetch them, and no font service learns your IP address from visiting.

Outbound links. Links to AI products lead to sites we do not control. Once you leave, that site's privacy policy applies, not ours. We add no tracking parameters to any outbound link.

Analytics. The provider is Google, through Google Analytics 4. The tag loads from googletagmanager.com on every page of this Site and sends what section 6 describes to Google, who process it as our processor and under their own policy. We use it to see which pages and categories people actually use, and nothing in it is combined with an account, with anything you type into the tool matcher, or with any file you attach — those never leave your browser and are not available to the analytics code. We do not sell what it collects.

Advertising. The provider is Google again, through Google Ads. One tag serves both: a single gtag.js configured for the analytics property and for the advertising one, which is the arrangement Google's own instructions ask for rather than two tags on a page. What it is for is measuring our own advertising — whether a click on an advert of ours led anywhere — and, where audience features are switched on in that account, building remarketing audiences, which is advertising use of your visit and is described as such here rather than buried. If you are in California, enabling those audience features is "sharing" for cross-context behavioural advertising under the CCPA/CPRA; the ways to refuse it below are open to everybody, in every jurisdiction, without asking us.

Neither tag ever receives anything you type into the tool matcher, any file you attach, or anything held in an account. That code and this code have no connection to one another, and the build refuses to publish if they ever gain one.

You can refuse both. Blocking cookies for this Site in your browser's settings, or using any content blocker, stops both tags — they load from the same place. Google's own opt-out add-on stops the analytics everywhere, and Google's ad settings are where personalised advertising is turned off across Google's own products. The Site works exactly the same way after any of them. A previous version of this policy said the Site ran no analytics and promised to name the provider here before that changed; these paragraphs are that notice, and they name the advertising one too.

Forms. If you send us a message through the contact or ticket form, the contents are delivered by Formspree, a third-party form processor, and are handled under their privacy policy as well as ours. Nothing is sent to them unless you press Submit.

9. Account deletion

You may request deletion of your account through the account settings available on the website, at /account/.

Deleting your account will remove your saved lists, your feedback and its notes, and account-associated data from active systems, subject to limited retention that may be required for security, fraud prevention, legal compliance, dispute resolution, or backup processes.

10. Your rights

Depending on where you live, you may have rights to access, correct, delete, or port personal data held about you, to object to processing, and to complain to a supervisory authority. These include rights under the UK and EU GDPR and, for California residents, under the CCPA/CPRA, including the right not to be discriminated against for exercising them.

If you have never created an account, the only personal data connected with your visit is what Google Analytics collects, described in section 6 — we hold none of it ourselves, it is not linked to your name or your email, and we have no way to find your visit in it or to single you out. If you want it gone at the source, the opt-out routes in section 8 stop it being collected at all. If you have an account, the data we hold is your email address, your account identifier, the dates the account was created and last changed, the names of your lists together with the tool identifiers in them, and any answers you have given about whether a tool worked together with any notes you wrote. You can see all of it on /my-tools/, /my-feedback/ and /account/, and delete all of it yourself from /account/. If you have emailed our support address, we hold that correspondence and will delete it on request. Write to support@rightaiforthejob.com.

We do not sell personal information, through user accounts or otherwise, and we never have. What we do do is measure our own advertising, which section 8 describes in full: where audience features are switched on in our Google Ads account, that counts as "sharing" for cross-context behavioural advertising under the CCPA/CPRA. Nothing from an account, and nothing you type or attach anywhere on this Site, is part of it — and section 8 says how to stop it without writing to us.

11. Children

The Site is not directed at children under 13, and we do not knowingly collect information from them. Several tools listed here have their own minimum age requirements set by their providers.

12. International visitors

The Site is hosted on infrastructure that may serve content from servers in several countries. Google Analytics is a service of a company based in the United States, so the measurement data described in section 6 may be processed outside the United Kingdom and the European Economic Area under Google's own transfer safeguards. If you do create an account, the account information described in section 4 is stored by our service providers and may be processed in the country where that provider hosts the project.

13. Changes

If this policy changes materially, the date at the top will change and the substance of the change will be described here.