Privacy Policy
Last updated 8 November 2026
hirly finds job postings that fit you, writes a résumé and cover letter for each one, and fills the employer’s application form — in your own browser, or for you if you allow it. Doing that means handling your résumé and your contact details. This page says exactly what is collected, why, who receives it, how long it is kept, and how to get rid of it.
hirly is operated by Insihts, Corp., a US company whose registered address is 1111B S Governors Ave STE 21416, Dover, DE 19904, United States. It is the controller of the personal data described on this page: wherever the page says “hirly”, “we” or “us”, it means Insihts, Corp.
Personal data we collect
These are the categories of personal data hirly collects. Most of it you give us yourself; some is created as you use hirly, and some is collected automatically.
| Category | What it includes |
|---|---|
| Account and sign-in details | Your email address, and your name and profile picture if you add them or your Google account supplies them. Passwords and passkeys are held by our authentication provider, not in hirly’s own tables. Source: You, or Google if you sign in with Google. |
| Résumé and career profile | The text of your résumé and its file name (the uploaded file itself is not stored), phone number, contact email, location, LinkedIn URL, headline, current title and company, work history, education, certifications, skills, years of experience, target roles, salary range and work preferences. Source: You. hirly reads the details out of the résumé you upload. |
| Answers to application questions | Your answers about work authorisation and visa sponsorship, the countries you may work in, notice period, earliest start date, willingness to relocate or travel, references, and answers you have given to employers’ screening questions, saved so you do not retype them. Source: You — in onboarding, in settings, or when a form asks. |
| Optional self-identification | Gender, race or ethnicity, veteran status, disability status and criminal record, only if you choose to give them. Each one starts as “decline to answer”. See “Sensitive information” below. Source: You, and only if you choose to. |
| Jobs and matches | The postings hirly matched to you or that you opened with the extension (title, company, location, description, URL), how well each fits and why, and the jobs or companies you skipped or blocked. Source: Public job postings, scored against your profile. |
| Documents hirly writes for you | Tailored résumés and cover letters (as text and as PDF files), résumé versions you or a connected assistant save, and the career notes hirly derives from your résumé: strengths, skill gaps and suggested roles. Source: Generated from your résumé and the job posting. |
| Application records | Which jobs you applied to and when, the status of each application, which form fields were filled, the questions an employer’s form asked and your answers to them, the confirmation or error the employer’s site showed, and a screenshot of the filled form when one was taken. Source: Created as hirly fills or submits an application. |
| Records of your consent | If you allow hirly to submit applications for you: when you allowed it, the IP address and browser user agent it was allowed from, and whether it was allowed on the website or through a named AI assistant. Source: Recorded at the moment you give consent. |
| Plan and payment records | Your plan, subscription status, order amounts and the customer reference our payment provider gives us. Card details are entered on the payment provider’s form and never reach hirly. Source: You and our payment provider. |
| Email records | Which emails hirly sent you, the delivery events our email provider reports (such as delivered, bounced or marked as spam), and whether you unsubscribed. Source: Created when an email is sent. |
| Usage, device and network data | Pages you view and what you click, recordings of your sessions on our sites, your IP address, browser and device details (user agent), the page that referred you, advertising click identifiers, error reports, and a record of each tool a connected AI assistant calls. See “Analytics, cookies and metadata” below. Source: Collected automatically as you use hirly. |
| Résumés uploaded without an account | If you upload a résumé on hirly.me before signing in: the résumé text and file name, the matches or draft documents made from it, and keyed hashes of your IP address and of a session cookie, used to limit how often the free tools can be used. Source: You, before you have an account. |
| LinkedIn outreach | If you use LinkedIn outreach: which LinkedIn account you connected and its name, the people you asked hirly to reach (job titles, places, keywords), the message script you approved, the messages sent to hiring managers and their replies, and whether outreach was paused. Your LinkedIn password is typed on a secure sign-in page run by our outreach provider and never reaches hirly. Source: You, and your LinkedIn account once you connect it. |
| Details of other people | Names, job titles, work email addresses and LinkedIn URLs of hiring contacts at companies whose jobs you open. See “Data about other people (hiring contacts)” below. Source: A contact-data provider, not you. |
Why we use it
We use personal data for the purposes below. We do not sell your personal data, and we do not give your résumé, profile or answers to advertisers.
| Purpose | What we use, and how |
|---|---|
| Finding and scoring jobs for you | Your résumé and career profile are compared with public job postings to build your matches and explain each score. |
| Writing your application documents | Your résumé, profile and the job posting are sent to an AI model to write a tailored résumé and cover letter and to draft answers to ordinary screening questions. |
| Filling and submitting applications | Your profile, documents and answers are entered on the employer’s application form — in your own browser by the extension, or by hirly’s servers for a job you chose, if you allowed that. |
| Running your account and keeping it secure | Account details sign you in. IP addresses, hashes and tokens limit abuse of sign-in, the free tools and the AI-assistant connection. |
| Taking payment | Your email address, plan and payment details are used to charge you and manage your subscription. |
| Emailing you | Your email address is used for sign-in and account emails, for emails about your job search (new matches, reminders, an application waiting for your answer, how the applications hirly made for you went) and for offers. You can unsubscribe from the job-search and offer emails. |
| Keeping evidence | Consent records show that you allowed hirly to submit for you. Application records show what was sent, so you can check it and so the same job is not applied to twice. |
| Understanding and fixing the product | Usage data, session recordings and error reports show us which features are used and where pages break. |
| Measuring our advertising | Google Analytics and Google Ads tags on our sites tell us whether an ad led to a sign-up, a résumé upload or a purchase. For a sign-up or a purchase, the tag also sends Google a hashed copy of your email address. |
| Showing you who is hiring | On plans that include it, the company and title of a job you open are used to look up its likely hiring manager or recruiter. If you choose to have hirly message hiring managers automatically, the same lookup runs for each job you apply to, and hirly sends that person the note shown on the job, from your LinkedIn. |
Who receives it
Three categories of recipient receive personal data from hirly:
- Service providers
- Companies that run parts of hirly for us: hosting, database, AI models, application automation, email, payments, analytics and advertising measurement. Each is named in the table below with what it receives.
- Employers
- The employer you apply to, and the applicant tracking system it uses, receive the application: whatever is entered on their form and the résumé attached to it. What they do with it is up to them.
- Your AI assistant’s provider
- If you connect hirly to an AI assistant, what hirly returns to it is sent to that assistant’s provider at your request and handled under their terms. See “hirly in AI assistants” below.
The service providers we use
| Provider | What it does, and what it receives |
|---|---|
| Supabase | Database, file storage and sign-in Stores your account and everything in it, and handles sign-in, including the sign-in an AI assistant uses. Receives: All account data: profile, résumé, answers, documents, application records and consent records. |
| Railway | Hosting Runs the hirly website, the app and the background workers, and keeps their server logs. Receives: Every request to hirly and the data the servers process to answer it. Logs hold account identifiers and error details. |
| Cloudflare | Network Sits in front of hirly.me, app.hirly.me and mcp.hirly.me and routes traffic to hirly’s servers. Receives: Every request on its way to hirly, including your IP address and browser details. |
| OpenRouter | AI model gateway Carries hirly’s requests to the AI model that reads your résumé, writes tailored résumés and cover letters, and drafts answers. Receives: Your résumé text, name, email address, phone number, location and LinkedIn URL, the job posting, and the screening questions being drafted. Your stored self-identification answers are not sent. |
| OpenAI | AI model provider Provides the AI model our requests are currently routed to by OpenRouter. Receives: The same content OpenRouter receives, for the request it is answering. |
| trigger.dev | Application automation Runs the server-side process that submits an application for you, if you allowed that. Receives: Your account and job identifiers, and while a run is in progress your profile, tailored résumé and answers for that one job. |
| Browser Use | Application automation Provides the cloud browser and AI agent that fill in and submit the employer’s form for a job you chose. Receives: Your name, email address, phone number, location and profile links, your saved screening answers and the answers you gave for that application, your tailored résumé as a PDF, and the address of the application form. |
| Steel | Application automation A backup cloud browser for the same process, used only when Browser Use’s browser cannot be started. Receives: The address of the application form it opens and the contents of that page. |
| Resend | Email delivery Sends hirly’s emails: sign-in links and codes, account notices, and emails about your job search. Receives: Your email address and the content of each email sent to you. |
| Trustpilot | Review invitations After you buy a plan or pass, sends you one invitation to review hirly on Trustpilot. Writing a review is up to you, and Trustpilot handles reviews under its own terms. Receives: Your name and email address, and the date of the thank-you email we sent after your purchase. Nothing else about your account or job search. |
| Stripe | Payments Takes payment and manages subscriptions. Receives: Your email address, account identifier, plan, and the card and billing details you enter on its form. |
| PostHog | Product analytics Records how hirly.me and app.hirly.me are used: page views, clicks, session recordings, error reports and feature switches. Receives: Your account identifier and email address, usage events, recordings of your sessions (what the page showed; what you type into form fields is masked), your IP address and browser details, and the record of each AI-assistant tool call. |
Sign-in, analytics and advertising measurement Signs you in if you choose “Sign in with Google”, and measures visits and ad results through Google Analytics and Google Ads tags on hirly.me and app.hirly.me. Receives: Page views, cookie and advertising click identifiers, your IP address and browser details, the fact of a sign-up, résumé upload or purchase (with the amount paid), and for a sign-up or purchase a hashed copy of your email address. | |
| BetterContact | Contact data Finds the hiring contacts for a job you open. Receives: The company’s name, website domain or LinkedIn page, and the kinds of job title to look for. Nothing about you. |
| Our LinkedIn outreach provider | LinkedIn messaging Holds the connection to your LinkedIn account when you connect it, and sends, from your account and within LinkedIn’s daily limits, the connection requests and messages your outreach agents write and the messages to hiring managers that you send from a job, or that hirly sends for you after you apply. Receives: Your LinkedIn sign-in (entered on its secure page, never seen by hirly), your outreach settings and message script, the messages to hiring managers word for word, and the LinkedIn profiles of the people contacted and their replies. |
| Clearbit | Company data Looks up a company’s website domain before a contact search. Receives: The company’s name. Nothing about you. |
Neon hosts our database of public job postings, which holds no account data. When hirly collects postings from job boards and company career pages, it sends them nothing that identifies you.
Employers receive an application only when it is submitted: by you, after the extension has filled the form, or by hirly for a job you chose, if you allowed that.
How long we keep it
This is what the system does today. Where there is no time limit, the table says so instead of naming one.
| Data | How long it is kept |
|---|---|
| Your account, profile, résumé text, answers, matches, written documents, application records and consent records | Kept until you delete your account. Deleting your account deletes these database records straight away. Nothing is deleted for inactivity. |
| PDF files of your tailored résumés and cover letters, and application screenshots | A job’s files are replaced when its documents are written again; otherwise they are kept while your account exists. They are stored as files, separately from the database. Deleting your account also deletes these files. |
| A résumé uploaded on a job page before you sign in | Deleted once it is 24 hours old, at the next clean-up, unless you sign in and keep the result. If you do, the résumé copy held with that preview is cleared after 7 days; your profile keeps its own copy. |
| A résumé uploaded to the free matching tool before you sign in | Deleted once it is 7 days old, at the next clean-up, unless you sign in and keep the result, when it is kept until you delete your account. |
| Hashes of IP address and session used to limit the free tools | The usage counter is deleted after 2 days. A hash stored with an uploaded résumé is deleted with that upload. |
| The record that you allowed hirly to submit for you | Kept until you withdraw the permission, which deletes it, or delete your account. |
| A question an application is waiting on | hirly waits 72 hours for your answer and then stops the application. The question and any answer stay with the application record until you delete your account. |
| The browser extension’s sign-in token and cached profile | Held in your browser until you sign out of the extension or remove it. The token stops working after 90 days, or when you revoke it in settings. |
| An AI assistant’s connection to your account | Kept until you disconnect the assistant or delete your account. |
| Hiring contacts | Stored per company and looked up again when a stored result is more than 30 days old and someone opens a job at that company. There is no automatic deletion: a result is kept until it is replaced. |
| Copies held by our service providers | Analytics events and session recordings, advertising measurement data, payment records, email logs, review-invitation records, AI request logs, automation run logs and server logs are held in those providers’ systems until the retention period set in each provider’s service ends. hirly sets no separate period for them, and deleting your account does not remove them automatically — email us to ask for deletion. |
Your controls
What you can do yourself, in the app or your browser:
- See and change your profile
- Your résumé, profile, work-eligibility answers and optional self-identification can be viewed and changed in the app at any time. You can replace your résumé with a new one.
- Delete saved answers
- Settings lists the screening answers hirly remembers; each can be edited or deleted.
- Stop hirly applying for you
- Withdraw the permission in Settings. Future submissions stop immediately and the consent record is deleted. The extension never submits for you in any case.
- Disconnect an AI assistant
- Open Connected assistants in hirly and press Disconnect; its access ends straight away. The same page lets you keep it connected but stop it applying. Also remove hirly in the assistant itself.
- Sign out of or remove the browser extension
- Signing out or removing it clears what it stored in your browser. You can revoke its token in Settings, and withdraw its optional access to other employer sites in Chrome’s extension settings.
- Unsubscribe from email
- Every email about your job search or an offer has an unsubscribe link. Emails you need in order to sign in are still sent.
- Limit analytics and advertising cookies
- There is no analytics switch inside hirly today. Your browser’s cookie settings and content blockers work on our sites, and blocking analytics does not stop hirly working.
- Delete your account
- In your account settings. This deletes your profile, résumé, answers, documents, saved résumé versions and application history from our database. See “How long we keep it” for what is held elsewhere.
Connected assistants is at app.hirly.me/oauth/connections.
Some things cannot be done from the app yet: downloading a copy of your data, and deleting a single application record or saved résumé version. For those — and to ask what we hold about you, to have it corrected or deleted, or to have copies held by our service providers deleted — email [email protected].
Sensitive information
Application forms ask some questions whose answers are sensitive. hirly can hold two kinds:
- your answers about work authorisation, visa sponsorship and the countries you may work in; and
- optional self-identification: gender, race or ethnicity, veteran status, disability status and criminal record.
Self-identification is optional. hirly asks for it only on its eligibility screen, every question there starts at “decline to answer”, and you can change your answers at any time.
These answers are used for one thing: answering the same question on an employer’s application form. They are entered only when the form asks for them, and only on an application you started — one you are filling with the extension, or one you told hirly to submit. The employer then receives them as part of your application.
hirly never guesses these answers. A question you have not answered is left for you. If an employer’s form asks one while hirly is submitting an application, the application pauses and you are asked; a self-identification answer given that way is used for that application only and is not saved for reuse.
Who else handles them: they are stored in our database, and an answer you give for an application hirly is submitting is passed to the service that fills in that form (see “Who receives it”). Your stored self-identification answers are not sent to the AI model that drafts other answers, and when hirly’s own browser takes a screenshot of a filled form those fields are blacked out first. Session recordings capture what a page displays, so a recording of a visit to the eligibility screen can show the options selected there.
They are kept until you change them or delete your account. To withdraw a self-identification answer, set it back to “decline to answer”.
hirly’s own forms do not ask for government identity numbers, health records, or bank or card numbers. hirly never asks for the password to an employer’s site or for a verification code, and connected assistants are told not to send them.
Data about other people (hiring contacts)
For a job you open, on plans that include it, hirly can show the people most likely to be hiring for it: a hiring manager’s or recruiter’s name, job title, work email address, whether that address was verified, and LinkedIn URL.
This is information about other people, and it comes neither from them nor from you. hirly gets it from BetterContact, a contact-data provider, by sending the company’s name, website domain or LinkedIn page and the kinds of job title to look for. The company’s domain is looked up first with Clearbit, from the company’s name. Nothing about you is sent to either.
Results are stored per company, not per user, so the same result is shown to other hirly users who open a job at that company. hirly shows them in the app, with a draft note you can send yourself, and returns them to an AI assistant you have connected. hirly does not email or message these people.
If you are one of these people and have a question or a request about this information, email [email protected].
Analytics, cookies and metadata
Besides what you give us, hirly.me and app.hirly.me collect data about how they are used. This is all of it:
- Usage events. Page views, clicks and errors are sent to our analytics provider. Once you sign in they are tied to your account identifier and email address. A cookie shared by hirly.me and app.hirly.me links what you did before signing in to what you did after.
- Session replay. The same provider records your sessions on both sites: what each page showed and how you moved through it. What you type into form fields is masked. Text a page displays is not, so a session replay can include your profile and résumé as they appeared on screen.
- IP address and user agent.Your IP address and your browser’s user agent reach our servers, our network provider and our analytics providers with every request, and appear in server logs. Our sign-in provider keeps them with each sign-in session. hirly’s own tables also store them with the record of your consent to submit applications, and store a keyed hash of the IP address to limit use of the free tools.
- Google Analytics and Google Ads.Both sites load Google’s tag, which sets cookies and reports page views, the ad click that brought you, and whether you signed up, uploaded a résumé or paid. For a sign-up or a payment it also sends a hashed copy of your email address.
- How you arrived. The page that referred you, the first page you landed on, campaign tags in the link and advertising click identifiers are saved with your account when you sign up.
- Email events. Our email provider reports whether an email was delivered, bounced or marked as spam, and opens and link clicks when it tracks them.
- AI assistant tool calls.hirly records when you connect an assistant, and which one. For each call a connected assistant makes, it records which tool was called, whether it worked, how long it took, how many results it returned, your plan, the assistant’s client identifier and the start of its user agent — tied to your account identifier. It does not record what you asked the assistant or what the tool returned.
- hirly’s own cookies. These keep you signed in, remember a free-tool session for up to 7 days, and carry how you arrived until you sign up.
The browser extension does none of this: it contains no analytics and no tracking. Your choices are under “Your controls”.
What the browser extension does
The extension runs only on job boards and application forms: the supported applicant tracking systems listed in its manifest, LinkedIn job pages, and hirly’s own site. On those pages it reads the job posting and the form’s fields so it can fill them.
It may also ask, once and only when you press the button in its popup, for permission to fill forms on employer sites it does not already recognise. That grant exists because a job you open from LinkedIn can send you to any company’s own site. You can decline, and everything else keeps working; you can revoke it at any time from Chrome’s extension settings.
The extension contains no analytics, no tracking, and no third-party code. It sends data to hirly’s own servers and nowhere else. It does not read pages outside the sites above, and it never submits an application for you — you review every form and press submit yourself.
It stores a sign-in token and a cached copy of your profile in your browser so it can fill forms without a round trip. Signing out of the extension, or removing it, clears that.
What autonomous submission does
Separately from the extension, hirly can submit an application for you through a server-side process — not your browser. It only ever runs for one job at a time, and only for an account that has granted standing consent. Each application starts in one of three ways: you press Apply on that specific posting, you confirm that job to a connected assistant, or the job meets a standing rule you approved in hirly for that assistant (described under “hirly in AI assistants”), within the daily number and end date you approved. It is never a sweep of your feed beyond the rules you approved.
The form is filled in and submitted by a cloud browser run by one of the application-automation providers named under “Who receives it”. It is given your contact details, your tailored résumé and your answers for that one job, and it is told not to create an account or sign in on the employer’s site.
It uses only answers you have given — including the standard answers you saved (such as work authorisation and visa sponsorship for a country), which it matches to the employer’s wording of the same question; it never invents an answer to a legal or screening question. If the form asks something you have not answered, the application pauses and you are asked in the app, or through a connected assistant if you have one. A form that asks more questions on a later page pauses again, up to three times. hirly waits 72 hours for each round of questions and sends nothing if you do not answer.
Afterwards hirly keeps the confirmation the employer’s site showed, or the reason the application stopped, and shows it on the application’s page. When hirly’s own browser fills the form, it also takes a screenshot of the filled form immediately before submitting, with self-identification fields blacked out.
hirly in AI assistants
You can connect hirly to an AI assistant such as ChatGPT or Claude. You sign in with your hirly account and choose Allow. The assistant can then use the tools below and nothing else: it cannot delete anything, read the rest of your account or see your card details.
| Tool | What it reads and writes |
|---|---|
| get_matches | Reads: Your matched jobs that you have not acted on: title, company, location, match score, up to three reasons, posting URL, and whether a tailored résumé exists. Writes: Nothing. |
| get_job | Reads: One matched job’s posting, how your main résumé meets its requirements (matched and missing keywords, not the résumé itself), the résumé versions already tailored for it, and the hiring contacts already saved for its company and role, on plans that include them. Writes: Nothing. |
| find_hiring_contacts | Reads: The matched job you name (its company and title), and any hiring contacts already saved for that company and role. When none are saved, the company and role are sent to our contact-data provider to look them up. Writes: A daily count of contact look-ups for your account, and the contacts found, stored per company. |
| save_resume | Reads: Whether the job you name is one of your matches. Writes: The résumé text your assistant sends, saved as a new version. Only if you ask, it also replaces your main résumé, which re-reads your skills and rebuilds your matches. |
| record_application | Reads: The job and the résumé version you name. Writes: Marks that job as applied, with the résumé version used and a short note if you give one. |
| get_profile | Reads: Your plan, whether your profile is set up, a summary of your main résumé (headline, current title, years of experience, top skills) and how many matches are waiting. Writes: Nothing. |
| get_pending_questions | Reads: Applications that are waiting for your answer, the questions the employer’s form asked, and your own earlier answer to the same question where there is one. Writes: Nothing. |
| answer_questions | Reads: The application and questions you are answering. Writes: The answers you give in the chat. They are stored with the application, entered on that employer’s form, and remembered for later applications — except self-identification answers, consents and questions specific to one employer, which are never reused. An answer to a standard question (such as work authorization for the job’s country, or your notice period) is also saved as your standard answer to it. |
| submit_application | Reads: The matched job you confirmed. Under a standing rule you approved, the rule and that job’s title, company, location, remote setting, match score and any salary its description states, to check the job meets the rule. Writes: Starts one application for that job, which hirly then fills and submits as described under “What autonomous submission does”. Under a standing rule, it also records which rule allowed it, with the rule’s criteria and the job details it was checked against. |
| get_application_status | Reads: Where one application stands, when it was submitted, the confirmation or the reason it stopped, and any questions it is waiting on. Writes: Nothing. |
| get_saved_answers | Reads: Your standard answers (work authorization and visa sponsorship per country, salary expectation, notice period, start date, relocation, on-site or hybrid work, time-zone overlap) and the answers hirly remembered from earlier application forms. Writes: Nothing. |
| save_answers | Reads: Nothing beyond whether you allowed this assistant to apply. Writes: The standard answers you give in the chat, replacing your earlier answer to the same question. hirly enters them on your future applications without asking again; you can change or delete them under Settings → Answers. |
| propose_apply_rules | Reads: Whether you allowed that assistant to apply, and how many applications your plan sends in a day. Writes: A proposed standing rule — the criteria, daily number and length your assistant drafted from what you asked — waiting for your approval in hirly. It replaces that assistant’s earlier proposal still waiting. |
| get_apply_rules | Reads: The standing rules you approved for that assistant and its proposals still waiting, how many applications each started today, and how many your plan still allows today. Writes: Nothing. |
submit_application and answer_questions work only if you ticked the box that lets the assistant apply for you, on the same screen where you chose Allow. That is the autonomous submission described above, with the same rules, and you can turn it off at any time.
An assistant may also propose a standing rule: which of your matched jobs hirly may apply to without asking you each time, how many a day and for how long. Nothing is applied under a rule until you approve it on a hirly page you are signed in to, where we record when you approved it, your browser’s user agent and your IP address. Each application started under a rule is recorded with the rule and the job details it was checked against, and the next day we email you one list of them. You can revoke a rule at any time under Settings → Applying; stopping the assistant applying, or disconnecting it, revokes its rules too.
hirly does not receive your conversation with the assistant. It receives only what the assistant puts into a tool call — a job identifier, a résumé to save, an answer you gave — and stores only what the table lists under “Writes”.
What a tool returns is sent to that assistant’s provider — for example OpenAI or Anthropic — at your request, and is handled under their terms. That includes hiring contacts’ details. hirly also records that a tool was called, as described under “Analytics, cookies and metadata”.
Disconnect at any time in your assistant and in hirly under Connected assistants. Details: hirly in your AI assistant.
Changes
If what we collect or who processes it changes, this page changes first, and the date at the top changes with it.
Contact
hirly is operated by Insihts, Corp., which is the controller of the personal data described on this page.
Insihts, Corp.1111B S Governors Ave STE 21416
Dover, DE 19904
United States
Questions about your data, and requests to see, correct or delete it: [email protected].