Privacy Notice
You are asked to acknowledge this notice, not to agree to it. It describes what we do.
What we collect when you create an account
Your email address, and either a password or a Google sign-in.
Passwords are handled by our authentication provider and are stored only as a cryptographic hash. We never receive or store your password. If you sign in with Google we receive your email address and a Google account identifier; we do not receive your contacts, your calendar, or your Google password.
We also record which version of these documents you were shown and the moment you accepted, so that what you agreed to can be produced later.
Applications you track
The employer, the role title, the location, the date you applied, where you applied, and any outcome you record.
Alongside each application we keep its history: the kind of each thing that happened, when it happened, and where we learned it. For anything learned from a forwarded message we also keep the sending domain and the employer and title as that message wrote them.
Your notes
A note you write on one of your applications is stored with its text, the tag you chose, whether you pinned it, and when you wrote and last changed it. Notes are yours to read, change and remove. We do not read them to build anything we publish.
The files you attach
You can attach a file to an application: a CV, a cover letter, or any other document you sent. We store the bytes in a private bucket, and alongside them a record of the file name, its size, its type, the label you gave it and which application it is attached to.
The bucket is not public and has no public address. The bytes are reachable only by you, through a link we create at the moment you press to open the file and which stops working sixty seconds later. We never serve the bytes ourselves, the file name never reaches a log line, and our public read credential has no access to the file or to its record at all.
Copies of postings you save
When you save a posting you applied to, we keep your own copy of it: the title, the employer, the location, the address it was at, the moment you captured it, and the text of the posting as it stood. The text is stored in the same private bucket as your files, under the same rules.
If the posting changes while you are waiting, we keep the earlier text as well, so that your copy can show what moved. These copies are yours. Nothing we publish is built from them, and our public read credential cannot see them.
When you ask us for help
If you report a problem from the extension or from a page, we store what you typed, the address of the page you were on, which posting it was about, a fixed set of facts about what the extension was showing you at the time, the version of the extension, and an install identifier. If you were signed in we store your account identifier with it, so we can answer you.
The install identifier names the installation and not the person. A report can be filed without being signed in, and one filed that way carries no account identifier.
A report you filed while signed in is deleted with the rest of your rows when you delete your account. A report filed while signed out names no account, so there is nothing for a deletion to match, and we keep it.
What the extension reads and sends
The extension runs only on the job boards it asks permission for when you install it, and on this site. It reads only the pages you open yourself, and it sends what it reads to us and to nobody else.
Sharing the listings you see is a separate agreement you can give or refuse, and it can be withdrawn. While it is on, the facts of the listings on a page you open are sent to us: the board, the posting identifier on that board, the address, the title, the employer and location as written, the pay, the employment type and the work arrangement if stated, a content hash of the description, the date the board displayed, and the day you saw it. Where you open a listing, the address you opened is sent with it. Each batch carries a random identifier and no account identifier, and nothing stored with it maps back to you. Refusing costs you nothing else in the product.
The address of a board we do not watch is recorded as a bare domain name when you meet a posting on one, with the days it was seen and how many pages carried structured data. A domain is all that can be stored: the column refuses any value containing a path, a query or a space, so no part of the address of a page you opened can be kept there.
A small count of what the extension could read is sent under its own separate agreement, so that we notice when a board changes its pages. It carries numbers, the board, the version, the day, and a random identifier for the installation. No page content is included and no account identifier is sent.
Forwarded mail
The product has a design for forwarding application-related email to a private address we would generate for you. It is switched off, no part of the interface offers it, and the route that would set it up sends you back to your applications. No address has been generated and no message has been received.
If it is ever offered, it will be its own separate agreement, and what would be stored is written down now so that it can be checked against what happens later: the sending domain, a salted hash used only to notice the same message arriving twice, what kind of message it was, and whether we could read it. What would deliberately never be stored is the subject, the body, any snippet, the sender's full address, the recipient, or the raw message identifier. There are no columns for them.
Addresses and abuse controls
We record a salted hash of your IP address so we can rate-limit abuse: when you check a posting, when the extension sends us anything, when you submit a report or a signup, when you tell us why you removed the extension, and when a sign-in fails. We do not store raw IP addresses for these purposes.
For most of those the hash is a counter key and nothing else: it goes into a rate counter, which is kept for two days and then deleted, and it is written on no row described anywhere else in this notice.
A report you submit is the exception, and the hash is on the report itself. The limit on reports is not a counter: it is a count of your own earlier reports about the same employer, so the rows have to be comparable to each other, and the hash is what makes them so. Nothing reverses it to an address and we hold no table that maps one back. It stays on the report for as long as the report does, which has no end date: nothing prunes reports, and deleting your account does not withdraw them.
Reports you send us about an application
You can report what happened with an application without an account. What we store is the employer and role title as you wrote them, the location, the address of the posting, the kind of claim, the dates, and your account of it with personal details removed before anything is written down.
A report carries no account identifier, no name and no email address. There is no column for any of them, and we provide no way to retrieve or recall one. That is why a report cannot be individually withdrawn, which the terms say in their own section 7.
What it does carry is a salted hash of your IP address. It is what lets us limit how many reports about one employer arrive from one place, and it is the only thing on the row that could group two reports together. It is not an address, nothing turns it back into one, and the abuse section above says how long it stays.
Before a person reads a report, it is sent to an AI provider to screen, which is named in the processors below. What is sent is the employer, the role title and your account of what happened. The hash is not sent, and neither is anything else.
What we collect about employers
Nothing about you. Our employer records come from public sources: job postings published by employers on their own hiring systems, state layoff notices, SEC filings, Form 5500 filings, federal court dockets, and OSHA data. Nothing you do creates or changes an employer record, except that aggregated applicant outcomes may contribute to published statistics once enough people have reported, and never in a form that identifies you.
Selling your data
We do not sell your personal data, and we do not share it with advertisers. We do not run advertising on this service.
The early-access and legislative signup lists
Two forms on this site take an email address before there is any account: one for early access and one for legislative offices. What we store is the address, the name you gave, the office if you gave one, which list it was, the version of the one-sentence agreement the form showed you and the moment you agreed, and, if the link you arrived by carried them, the campaign tags in it and the host of the page that linked to you. We also store a hash of the confirmation token we email you, when it was sent and when it expires, and the moment you confirmed.
A confirmation email goes to the address, sent through our outbound email provider from the mail subdomain. Once you confirm, your address, your name and your office are sent to our mailing-list provider so the list can be mailed from there. Nothing else reaches it: not the campaign tags, not the referring host, not the token.
The signup is not an account. No password, no session, and no row in anything that an account reaches. The one-sentence agreement the form shows is recorded on the signup's own row rather than with the agreements an account makes, so what you agreed to is answerable from the row.
The emails carry an unsubscribe link, which stops the mailing-list provider sending to you. It does not remove the row we store, and we have no automatic way to remove one: write to privacy@hiringrecord.com and we will. We do not delete these rows on a schedule.
When you tell us why you removed the extension
If you remove the extension, the page we send you to offers a reason you can tap and a box you can type in. What we store is the reason, what you typed if you typed anything, and the version of the extension.
Nothing on that row identifies you. There is no account identifier, no email address, no install identifier, and not even a hashed IP address: the hash is spent on the rate limit and dropped. We cannot tell two of these apart by who sent them, so there is nothing here for a deletion to match and nothing to ask us to remove.
Cookies and what is stored in your browser
We set three things and no others.
A time-zone cookie, `hr_tz`, holding the name of your browser's time zone, so dates read in your own zone. It is not an identifier and it is read only to format a date.
Sign-in cookies, set by our authentication provider, which are what keep you signed in. Signing out clears them.
One value in your browser's session storage, `hr.record.bar.dismissed`, set when you dismiss the sign-up bar on a record page so it does not come back in that tab. Session storage is cleared when you close the tab and never leaves your browser.
There is no analytics, no advertising and no tracking cookie of any kind, and no third-party script that would set one. The one check that runs in your browser against somebody else is our bot-protection provider's, on the sign-in, account and signup forms; we set no cookie for it and we receive nothing from it but a yes or no.
Who processes data on our behalf
Our database, authentication and file storage provider; our hosting provider for this site and its API; our own server, which runs the nightly retention and deletion passes; our email routing and bot-protection provider; our outbound email provider; the mailing-list provider that holds the early-access list; and an AI provider that screens a submitted report before a person reads it.
How long we keep things
Our crawl telemetry is kept 30 days, and forwarded-mail records are kept 90 days. Your account data is kept until you delete your account.
Your files and your saved copies of postings are kept while the application they belong to is still open, and for six months after it is resolved. A nightly pass sets that date, and when it passes the stored bytes are deleted.
The counters behind our rate limits, which is where the salted hash of an IP address is held, are kept for two days and then deleted.
Deleting your account
Deleting your account happens in two stages, and the first one cannot be undone.
On the next nightly run after you ask, we delete the stored bytes of every document you uploaded and of every posting you saved.
Seven days later we delete the rows: your account record, your applications and their history, your notes, the links between your files and an application, the records of your saved postings, your consent record, and your forwarding address and its receipts if you had one. The seven days are there so that a deletion somebody did not mean can be undone while they last.
Deletion does not remove statistics already computed, and does not withdraw reports you submitted. A report carries no account, so there is nothing on it for a deletion to match.
Your rights
You can ask for a copy of your data, ask us to correct it, or ask us to delete it. Write to privacy@hiringrecord.com.
Children
This service is not intended for anyone under 16.
Contact
Cotter Hill LLC, 46 Shopping Plaza, Unit #5046, Chagrin Falls, OH 44022. Privacy questions: privacy@hiringrecord.com.
This is the version currently in effect. Each version is stored separately and is never edited, so the exact wording anybody agreed to can be produced. Corrections to the record itself are published at hiringrecord.com/corrections.