HireWebs

Using the site without an account

Browsing, searching, filtering, and saving jobs does not require an account. Without an account, your saved jobs and resume stay in your own browser (local storage) and are not sent to us. Your browser also remembers when you dismiss the sign in reminder.

When you search or filter jobs, your search words, place, and filters are sent to our server so it can find matching jobs. We do not link them to your name or account, and we do not keep a history of what you search for. Our hosting provider may record basic technical data about the request (see Netlify below).

Usage counts and analytics

We count what visitors do in total, such as visits, jobs opened, Apply clicks, saves, and resumes saved. These counts have no cookies and are not tied to your name, email, or resume.

Some links to HireWebs carry a tag that says where they were shared, such as hirewebs.com/?ref=threads. If you arrive through one, your browser remembers that tag for 90 days so we can count, in total, how many visits, Apply clicks, and sign ups each place brings. If you create an account, we save the tag (or "direct" if there was none) and when you last used the site with your account ID. It is never tied to your name, email, or resume, and it is only used for these totals.

If you choose Accept on the notice at the bottom of the page, we also use Google Analytics (through Firebase) to see where visitors come from, which countries they visit from, and how the site is used. It uses cookies or similar storage and sends usage data to Google. If you choose No thanks, it is not loaded. Your choice is remembered in your browser, and you can clear your browser's site data to be asked again.

The same Accept also turns on the Meta Pixel, which tells Meta (Facebook and Instagram) when someone who saw a HireWebs ad visits, searches, creates an account, opens checkout, or subscribes, so we can tell which ads work. It uses cookies. For those events our server may also send Meta the same event with your IP address, browser type, and, if you are signed in, a scrambled (hashed) copy of your email address and account ID. We never send your resume, your searches, or the jobs you look at. With No thanks, nothing is sent to Meta.

Information we collect when you sign in

• Google account basics. When you sign in with Google, Google and Firebase share your name, email address, profile photo, and a unique account ID with the sign in. We never receive your Google password. Firebase keeps the sign in account record. On our own servers we keep your account ID and your plan, and we do not store your name or photo in our own data. We do not keep your email address in our own data.
• Saved jobs and resume. Signed in users have their saved jobs (up to 200) and resume stored on our servers so they follow you across devices.
• Matches data. If you use Matches (jobs that fit your resume), we store a short profile read from your resume (job titles, experience level, key skills, years of experience, and the cities it mentions, but not your name or contact details, and a few roles your background leads to), the result of each job check (including short phrases from your resume that the AI pointed to as evidence), and any jobs you mark Not a fit along with the reason you chose.
• Messages you send us. If you send feedback or a message from the site, we receive its subject and text, the email address you give (or your account email if you are signed in), and your account ID if you are signed in. We use it only to read and answer your message. It is delivered to our email inbox through Resend.
• Saved resume versions (Pro). If you are on Pro, the optimizer saves the rewritten resume, summary, and suggestions for each field you optimize, so you can come back to them. Free plan results are shown once and not saved.
• Field summaries. The first time anyone asks about a field, we save a short list of what recent public job postings in it ask for. It is shared across everyone's searches and contains no personal information.
• Daily usage counts. How many times each tool has been used on your account today, so we can apply daily limits. These are counters only. They do not contain what you sent to a tool.
• Where you found us. For accounts made after October 2026: the link tag that first brought you (or "direct"), when the account was made, and when you last used the site, so we can count sign ups and active people per source.
• Sign in session. Firebase keeps a sign in session in your browser so you stay signed in.

What the AI tools receive

When you use a tool, the information it needs is sent to an AI service (Anthropic) to produce the result:

• Fit check, cover letter, and interview prep send your resume text and the job you picked.
• Searching for a job title we have not seen before may send those search words, and only those words, to the AI service to find related job titles. The answer is saved and reused for everyone's searches, and it is not linked to you or your account.
• The resume optimizer sends your resume text and the field you choose to the AI service, together with a short summary of what recent public job postings in that field ask for.
• Matches sends your resume text to the AI service to build your profile, and again together with the full text of each job it checks for you. This happens when you open Matches or change your resume.
• Interview practice also sends the question and the practice answer you typed.
• Interview prep, interview practice and the resume optimizer can take longer than a normal request allows, so the request (including your resume text) is held on our server while the AI service works on it, and deleted as soon as your browser has picked up the answer, or after a few minutes if it never does.
• Follow ups and outreach messages (Pro) send your resume text, the job you picked, and the name and date you enter, if any.
• Offer negotiation sends the details you enter in the form, such as pay, location, and experience. These details are not saved to your account.

We do not store the results of the fit check, cover letter, interview prep, follow ups and outreach messages, or offer negotiation on our servers, or interview practice results on the Free plan. They are shown in your browser, and they are gone when you close them unless you copy or download them yourself. Matches is an exception: its profile and job check results are saved to your account so they do not have to be worked out again each time. Saved resume versions for Pro are another. On Pro, interview practice saves each answer you have reviewed, with its stronger version, under that job (up to 12 answers for each of your 30 most recent jobs), so you can read them again before the interview. Your use of the AI service is also subject to Anthropic's own terms and privacy policy.

Please do not enter anything you are not comfortable sharing with an AI service. If you upload a PDF resume, it is read in your browser and only the text you review and save is kept.

How we use information

• To sign you in and keep your saved jobs and resume on your account.
• To run the AI tools and Matches, and enforce daily limits.
• To keep the site secure and working.
• To reply if you contact us.

We do not sell your personal information, and we do not use advertising trackers.

Services that handle your data

• Google and Firebase handle sign in. Their scripts load from Google when you open the sign in option.
• Anthropic processes the text you send to the AI tools.
• Turso hosts the database of public job listings. It holds listing details only, such as title, company, location, pay if listed, and a link, and no information about you.
• Resend delivers the emails you ask for, such as a refund receipt or a reply to a message you send us. The email address and the message are sent to Resend for delivery.
• Netlify hosts the site, the server code behind it, and the storage for saved data. It may record basic technical data such as IP address, pages requested, and error logs.
• Cloudflare (cdnjs) serves the PDF reader used only when you upload a PDF resume.

These providers have their own privacy policies and handle data under their own terms.

Job listings

Listings come from public company job boards. Each listing links to the original posting. Applying happens on the employer's site, under their privacy practices. Job categories shown on the site are guessed from the job title and may be wrong. The job list contains public listing details only, such as title, company, location, pay if listed, and a link. It contains no personal information about you. Listings older than about 45 days are removed from the site.

How long we keep information

• Saved jobs and resume stay on your account until you delete them or ask us to.
• Saved resume versions stay until you delete your saved data. A new run for the same field replaces that version, and at most 12 are kept.
• Matches data stays on your account until you delete it. Your profile is replaced when your resume changes, and a job check result is replaced when the same job is checked again.
• Your account ID and plan stay until you ask us to delete your account record.
• Daily usage counters are tiny records of how many times a tool was used on a given day.
• Service providers such as Netlify keep their own technical logs under their own schedules.

Your choices

• Use the site without signing in.
• Open the Account sheet and choose Delete my saved data to remove your saved jobs, resume, Matches data, saved resume versions, and saved interview practice answers from your account and your browser. This does not remove your account ID, plan, or usage counters.
• Email us to ask for your account record, including your account ID and plan, to be deleted.
• Remove this site's access from your Google Account security settings at any time.

Children

HireWebs is not intended for children under 13, and we do not knowingly collect information from them.

Changes to this policy

If this policy changes, the date at the top of this page will be updated.

Contact

Questions or deletion requests: hirewebs@outlook.com