Privacy Policy

#The short version

We wrote this policy to be read, not just agreed to. Here is what matters most. The full policy below explains each point, and the full policy controls.

1. We use your information to run your job search, and nothing else. Your résumé, answers and applications are used to find jobs, tailor documents, fill and send the applications you authorize, sort the replies, and prepare you for interviews.
2. We do not sell your personal information, and we do not share it for targeted advertising. We run no advertising pixels.
3. We do not train AI models on your content. Not our own models, and not our AI providers' models. Our AI providers are contractually barred from training on what we send them.
4. Sensitive answers are yours to give, and only used with your consent. Work authorization, visa sponsorship, desired salary and voluntary equal employment opportunity answers (gender, race or ethnicity, veteran status, disability status) are used only to fill application forms you authorize, only if you have switched that category on, and never for scoring, ads or anything else.
5. Employers get what you send them. When you apply, the Employer and its hiring system receive your application. After that, their privacy policy governs it.
6. You stay in control. You can see, download, correct and delete your information, withdraw consents, switch off Autopilot and delete your account from your settings. We honor these rights for everyone, wherever you live.
7. We never ask for your passwords to other sites. oyapilot does not store your LinkedIn, Indeed, email or employer-portal passwords or cookies.
8. You must be 16 or older to use oyapilot, and under 18 only with a parent or guardian's permission.

Questions: privacy@oyapilot.ai.

#1. Who we are and what this policy covers

#1.1 Who we are

oyapilot is made by Oyatco LLC, a limited liability company organized under the laws of [STATE OF FORMATION] and based in the State of Texas, United States ("Oyatco", "oyapilot", "we", "us" or "our").

For the personal information described in this policy, Oyatco LLC is the "business" under US state privacy laws and the "controller" under the EU and UK General Data Protection Regulations, except where Section 1.4 says otherwise.

#1.2 What this policy covers

This policy explains how we collect, use, share, keep and protect personal information when you:

• visit oyapilot.ai or any of its subdomains;
• create or use an oyapilot account;
• use the oyapilot web application, including job search, the job board, Kit Studio, tailoring, agents, the tracker, the application mailbox, interview preparation and settings;
• use the Application Engine, Hybrid mode or Autopilot to fill or send applications;
• install or use the oyapilot browser extension;
• connect an AI client to the oyapilot MCP server;
• use a free tool, such as the ghost-job checker, the résumé score, the keyword checker, a calculator or a letter writer, with or without an account;
• receive emails from us or send email to an oyapilot reply address;
• contact our support team or send us feedback; or
• otherwise interact with us.

We call all of these the "Services".

#1.3 What this policy does not cover

This policy does not cover:

• Employers and hiring systems. When you apply to a job, the Employer and its applicant tracking system (for example Greenhouse, Lever, Ashby, Workable or Recruitee) receive your application and handle it under their own privacy policies. We do not control what they do with it.
• Third-party websites and services that we link to or that you choose to use, including AI clients you connect through the MCP server, your email provider, your browser and Google when you sign in with Google.
• Stripe's own processing of your payment details as an independent controller for certain purposes, such as fraud prevention and compliance, which is governed by Stripe's privacy policy.

#1.4 When we act for someone else

We do not currently process personal information on behalf of employers or other business customers. If we offer services to businesses in future, a separate agreement and notice will apply.

#1.5 How this policy relates to our Terms

This policy is part of, and should be read with, the oyapilot Terms and Conditions. Terms that are defined in the Terms (such as "Application Engine", "Autopilot", "Hybrid mode", "Kit" and "Needs You") have the same meaning here.

#2. Words we use in this policy

"Personal information" or "personal data" means information that identifies, relates to, describes or can reasonably be linked to you, directly or indirectly.

"Sensitive personal information" means the categories described in Section 4, including work authorization and immigration status, voluntary equal employment opportunity (EEO) self-identification, account sign-in credentials, and the contents of the email messages we receive on your behalf.

"Process" means anything done with personal information, such as collecting, storing, using, sharing or deleting it.

"Service provider" or "processor" means a company that processes personal information for us, under our instructions and a written contract.

"Employer" means a company, organization, government body or recruiter that posts a job, receives an application, or writes to you about a job.

"Hiring system" means an applicant tracking system or careers website used by an Employer.

"De-identified" means information that cannot reasonably be used to identify you, which we have committed not to re-identify.

#3. The information we collect

We collect information in four ways: you give it to us, it is created when you use the Services, we receive it from others, and we generate it from other information. We collect only what we need to run the Services you use.

#3.1 Information you give us

Account information. Your email address, your password (we store only a secure hash of it, managed by our authentication provider), your display name, and your invitation code while signup requires one.

Waitlist. If you join the waitlist while oyapilot is not yet open to new accounts, your email address and, if you give them, the role you want, the plan or referral code in the link you followed, the page you joined from and the language of that page. Joining the waitlist does not create an account.

Profile and job search goals. The roles, seniority, locations, work arrangements (remote, hybrid or on-site), industries, salary floor, search status and timeline you tell us about, including answers you give in the pre-signup "start" wizard.

Application Profile. The information you provide so that forms can be filled for you, including:

• identity: legal name, preferred name, pronouns, and a profile photo if you choose to upload one;
• contact details: email address, phone number and postal address;
• links: LinkedIn, GitHub, portfolio or personal website;
• work history, education, skills, certifications and languages;
• job preferences, notice period, relocation willingness and start date;
• common answers, such as whether you are over 18 and whether you are willing to relocate;
• professional references, which include other people's names and contact details (see Section 24); and
• Sensitive Answers, if you choose to provide them: work authorization, visa sponsorship needs, visa or immigration status, desired salary, and voluntary EEO self-identification (gender, race or ethnicity, veteran status and disability status). Section 4 explains how we handle these.

Résumés, cover letters and documents. Résumés and documents you upload (PDF or Word files) and the text extracted from them, the base résumé and cover letters you build in Kit Studio, your cover letter voice and tone preferences, every version of your Kits, and the documents we tailor for each job.

Instructions to the AI. What you type to the Kit Studio builder and to the agent chat when you create or talk to an agent, and the settings you choose for agents (targets, exclusions, quality bar, ghost-risk tolerance, daily limits, schedule and mode).

Application content. Answers to screening questions, answers you save to your answer library, reasons you give for rejecting a job, notes, and the decisions you make in your queue.

Interview preparation. The job and Kit you prepare with, your written practice answers, and, in voice mock interviews, what you say (see Section 6.6 for how voice is handled).

Interview and offer details. Interview dates, times, locations or meeting links, notes, and offers or outcomes you log in the tracker.

Messages you send. Replies you send to Employers from an oyapilot reply address, and the forwarding address you verify.

Support and feedback. Messages, ratings, screenshots and attachments you send us through the feedback form, by email or otherwise, and the details of any request you make to us.

Payment and billing. When you buy a paid plan, you give your card or other payment details directly to our payment processor, Stripe. We do not receive or store your full card number. We receive from Stripe your billing email, the last four digits and brand of your card, its expiry month and year, your billing country and postal code where needed for tax, and the status of your payments.

Student status. If you apply for student pricing, the student email address or other information you use to verify eligibility.

Referrals and promotions. Your referral code, the promotion codes you redeem, and, if you invite someone, the fact that they signed up through your link.

#3.2 Information created when you use the Services

Usage and activity. The pages and features you use, jobs you view, save, import or dismiss, searches you run, the scores you see, actions you take in your queue, applications you approve, agents you create and run, and the times you do these things.

Agent and application records. A log of what each agent did and when, the jobs it screened and why it kept or skipped them, and, for every application sent by the Application Engine, the posting address, the employer's domain, the mode used, the fields submitted, a snapshot of the materials used, the outcome, the results of our fraud and safety checks, and screenshots of the filled form or the confirmation page (see Section 7).

Usage counters. How many tailored applications, quick applies, fit analyses, builder edits, ghost checks, voice minutes and MCP calls you have used, so that plan limits can be applied.

Device and technical information. Your IP address, browser type and version, operating system, device type, screen size, language, time zone, referring page, and the page addresses you visit (including query strings), collected through server logs, our analytics tools and cookies (see Section 14).

Approximate location. Our hosting provider tells us the approximate city, region and country associated with your IP address. We use it to suggest a location for your job search and for security. We do not collect precise location from your device.

Security information. Sign-in times, failed sign-in attempts, token usage, and information needed to detect abuse, fraud and attacks.

Extension information. If you use the browser extension, the information described in Section 8.

Credentials we issue. When you create an extension key or an MCP access token, we store a one-way hash of it, its last four characters, its creation and expiry dates and how often it is used. We never store the token itself after showing it to you once.

#3.3 Information we receive from others

Sign-in providers. If you sign in with Google, Google shares your name, email address, whether your email is verified, and your profile picture if you have one, according to the permissions you approve. We do not receive your Google password, and we do not receive access to your Gmail, Calendar, Drive or contacts.

Employers and hiring systems. Messages Employers and their hiring systems send to your oyapilot reply addresses (for example acknowledgments, interview invitations, rejections, offers and requests for information), including their attachments. When the Application Engine submits an application, the hiring system's confirmation page or message.

Stripe. Payment status, subscription status, invoices, refunds and disputes.

Job and company data sources. Public job postings from employers' hiring systems, public government job sources, licensed job data partners, and public company datasets. These sources describe jobs and companies. They occasionally include the names or contact details of recruiters or hiring managers mentioned in a posting (see Section 25).

People who refer you. If someone referred you, we know that you signed up through their link.

#3.4 Information we generate

We generate information from the information above, including:

• ghost-risk scores and fit scores for jobs, fit analyses, matched and missing requirements, and screening reasons;
• embeddings, which are numeric representations of the meaning of text, created from your résumé sections and your job preferences so that jobs can be matched to you;
• résumé scores, Kit scores and practice scores;
• the category and extracted details of messages in your application mailbox;
• salary estimates and negotiation ranges for jobs; and
• aggregated and de-identified statistics about how the Services are used.

These are generated to serve you. They are not used to make decisions about you that have legal or similarly significant effects, and they are not sold or shared with anyone for their own purposes (see Section 6.7).

#3.5 Information we do not collect

We do not ask for or collect:

• your passwords or cookies for LinkedIn, Indeed, your email account, employer portals or any other third-party website;
• Social Security numbers, national identification numbers, passport numbers, driver's license numbers, or bank account details (and the Application Engine refuses to fill fields that ask for them);
• precise geolocation from your device;
• biometric identifiers (we do not create voiceprints or face templates); or
• your contacts or address book.

Please do not upload documents that contain these kinds of information. If a document you upload contains them (for example, a résumé that lists your date of birth or a photo ID), you can delete it at any time.

#3.6 Communications with us

When you email us, send feedback or ask for help, we keep the message, our reply and any attachments, so that we can help you and keep a record of what was agreed. Feedback sent from inside oyapilot includes technical details that help us reproduce a problem: the page address, your browser and its version, screen and window size, language and, if you add them, screenshots. Please remove personal information you do not want us to see from screenshots before sending them.

#3.7 Surveys and research

We may invite you to answer a survey or take part in a research interview about oyapilot. Taking part is always optional and does not affect your account. If you take part, we use your answers only to improve oyapilot. We will tell you in advance if a session is recorded, and we record only with your consent. If we offer a thank-you (for example, a free month), it does not depend on what you say.

#3.8 Social media

We have accounts on social media, such as X (@oyapilot). If you interact with us there, the platform's own privacy policy applies to what you post and what the platform collects. We may see and respond to your public posts and messages you send us. We do not import your social media data into your oyapilot account.

#4. Sensitive personal information

Some information you may give us is especially sensitive, and the law gives it extra protection. This Section explains exactly what we collect in these categories, why, and the limits we place on ourselves.

#4.1 Which information we treat as sensitive

#4.2 You choose whether to give it

Every Sensitive Answer is optional. EEO questions on application forms are voluntary, and you can always leave them blank in oyapilot or choose "I do not wish to answer". If you do not provide a Sensitive Answer, oyapilot leaves that question on each application for you to answer yourself or sends the application to your Needs You queue.

#4.3 We ask for your consent

We collect and store Sensitive Answers only with your express, opt-in consent, which you give separately for each category (work authorization, compensation, and EEO self-identification) in your Application Profile, after we explain what the category is used for. Using a Sensitive Answer on an application requires that the category's consent is switched on. You can withdraw consent at any time, for one category or all of them, from your Application Profile. When you withdraw consent, oyapilot stops using those answers on applications immediately and deletes the stored answers within 7 days, unless you tell us to keep them for later use.

#4.4 How we use it, and nothing more

We use Sensitive Answers only to:

(a) fill the matching questions on application forms you authorize us to fill or send, under the consent you gave for that category; (b) show them back to you so you can review and edit them; (c) decide whether a job is compatible with your stated sponsorship needs when you have asked us to filter jobs that way; and (d) keep the Services secure and comply with the law.

We do not use Sensitive Answers to:

• calculate ghost-risk scores, fit scores or any other score;
• decide which jobs to show you, other than the sponsorship filter you ask for;
• infer characteristics about you;
• create a profile of you for any purpose other than filling your applications;
• advertise to you or anyone else; or
• train any AI model.

We do not sell or share Sensitive Answers, and we disclose them only to the Employers you apply to (in the form fields that ask for them), to the service providers that store and process them for us, and as required by law. Because we use sensitive personal information only for these permitted purposes, we do not offer a separate "Limit the Use of My Sensitive Personal Information" link, but you can still stop all use at any time by withdrawing consent.

#4.5 How we protect it

Sensitive Answers are stored in a separate database table from the rest of your profile, protected by row-level security so that only you (and the specific services that fill your applications) can read them. They are not included in the information available to AI clients through the MCP server. They are sent to our AI providers only when an AI step genuinely needs them to fill a specific form field, and the Application Engine's AI field-matching step receives descriptions of the values available, not the values themselves.

#4.6 Sensitive information in the extension

If you choose to let the browser extension fill Sensitive Answers, a copy of the categories you have consented to is kept in your browser's extension storage on your device so that the extension can fill forms, and it is removed when you sign out of the extension or remove it. See Section 8.

#4.7 What Employers do with it

When a Sensitive Answer is sent to an Employer, the Employer controls it. US employers typically collect EEO information for government reporting and are generally required to keep it separate from hiring decisions, but we cannot control or verify how any Employer uses it. If you are unsure, leave the question for the Employer's own form and read the Employer's notice.

#4.8 Health data laws

Some US states, including Washington, Nevada and Connecticut, have laws that protect consumer health data. Because a disability self-identification answer may count as health data under those laws, we follow the additional rules in Appendix 5 for it.

#5. How we use your information, and our legal bases

We use personal information only for the purposes below. If we want to use it for a new purpose that is not compatible with these, we will tell you first and, where the law requires, ask for your consent.

For people in the European Economic Area, the United Kingdom and Switzerland, each purpose lists our legal basis under the GDPR. For others, the legal basis column explains why we need the information.

#5.1 Our legitimate interests

Where we rely on legitimate interests, those interests are: running a secure, reliable and affordable service; understanding how the Services are used so we can improve them; preventing fraud and abuse; protecting Employers and hiring systems from harmful use of the Services; telling existing users about relevant features; and establishing, exercising and defending legal claims. We have balanced these interests against your rights and expectations, and we do not rely on legitimate interests where your interests override ours. You can ask us for more detail about the balancing test.

#5.2 What we never do

We do not use your personal information to:

• sell it, rent it or trade it;
• show you targeted advertising on other websites, or let advertisers track you on ours;
• make decisions about your eligibility for credit, insurance, housing or employment;
• train AI models (see Section 6.4); or
• build profiles of you for anyone else.

#5.3 Collecting only what we need

We design oyapilot to collect the minimum personal information needed for each feature, to use it only for the purpose we collected it for, and to delete it when it is no longer needed. For example, the free résumé score does not store your résumé, agent chats are not stored as transcripts, voice audio is not stored, and Sensitive Answers are optional and used only on the forms that ask for them.

#5.4 Emails we send

We send transactional emails (such as sign-in links, receipts and status updates) and optional emails (such as job digests), through our email providers. Our emails do not contain advertising for other companies.

If you join the waitlist, we use your email address only to tell you when oyapilot opens to new accounts. We do not add it to a newsletter or share it with anyone else.

[We do not use hidden pixels to track whether you open our emails, and we do not track clicks on links in our emails.]

#5.5 Your job search stays private

Many people look for work while employed. We never tell your current employer, or any employer, that you use oyapilot, what you search for, which jobs you view or save, or where else you have applied. An Employer learns about you only from the Application you choose to send it, and, if you use an oyapilot reply address, that its messages to you reach you through oyapilot. oyapilot does not publish user profiles or make users searchable by employers or recruiters.

#6. How AI is used on your information

AI is central to oyapilot. This Section explains which AI providers we use, what we send them, what they may do with it, and what we promise.

#6.1 Our AI providers

We may change or add AI providers. We will update Appendix 2 before a new provider receives personal information.

#6.2 What our AI providers may and may not do

We use our AI providers under their commercial or business terms, not their consumer terms. As of the date of this policy:

• They may not use your information to train their models. Anthropic's commercial terms prohibit it from training models on customer content sent through its API. OpenAI's business terms state that API data is not used for training by default.
• They keep it only briefly. Under their standard terms, Anthropic and OpenAI may keep API inputs and outputs for up to 30 days, mainly to detect and prevent abuse, after which they delete them, unless the law requires longer retention or content is flagged for a policy violation.
• They act as our service providers, processing information only to provide their services to us, under data processing terms.

[Engineering and Counsel: (1) sign or confirm the Anthropic and OpenAI data processing addenda; (2) consider requesting zero data retention from both, which would let this section say "do not keep it at all"; (3) re-check both providers' terms on the effective date, because they change.]

#6.3 What we send, and what we hold back

We send AI providers only what a task needs. For example:

• scoring a job's ghost risk sends the job posting, not your résumé;
• tailoring a résumé sends your résumé and the job description;
• sorting an Employer's email sends that email;
• matching form fields sends the field labels and descriptions of the values available, not your actual values.

We do not send your password, payment details, extension keys or MCP tokens to any AI provider.

#6.4 We do not train AI models on your content

We do not use your résumés, cover letters, Kits, Application Profile, Sensitive Answers, application answers, agent chats, application mailbox messages, interview practice answers, voice or extension data to train, fine-tune or improve any AI model, whether ours or anyone else's.

We do use aggregated, de-identified information (for example, how often a type of form field appears on Greenhouse forms, how often tailoring removes an unsupported claim, or how accurate our ghost-risk bands turned out to be against later outcomes) to improve our own rules, prompts and non-generative scoring methods. This information does not identify you.

#6.5 Chats that are not stored

The agent chat you use to create an agent, and the chat you have with an existing agent, are not stored as transcripts by us. The result (for example, the agent's settings, or a change you apply) is saved. The Kit Studio builder chat is not stored as a transcript, but the document versions it produces are saved in your Kit history. The text of these chats is sent to Anthropic to generate replies and is subject to Section 6.2.

#6.6 Voice mock interviews

When you start a voice mock interview (available on the Pro plan):

• your browser asks for microphone permission, and you can refuse or withdraw it at any time;
• your voice is streamed directly from your browser to OpenAI's real-time voice service to run the conversation, and transcribed by OpenAI;
• the AI interviewer is given your résumé, the role, the company and your prep kit so that it can ask relevant questions;
• we do not store audio recordings of your voice; we store the transcript of your answers, the feedback and the scores in your account;
• we do not use your voice to identify you, and we do not create voiceprints or any other biometric identifier; and
• OpenAI processes the audio under the terms in Section 6.2.

Do not include other people in a voice session, and do not say anything you do not want transcribed.

#6.7 Automated decisions

oyapilot uses automated processing to score jobs, choose which jobs an agent keeps, and, if you switch on Autopilot, decide which of the jobs matching your rules to apply to within your limits. These are recommendations and actions for you, under rules you set. They are not decisions about you that produce legal effects or similarly significant effects on you, and oyapilot does not decide whether anyone is hired. You can always review scores and reasons, change your rules, approve applications one by one in Hybrid mode, or switch Autopilot off. If you would like a person to review how an automated step affected you, write to privacy@oyapilot.ai.

#6.8 You are told when you are talking to AI

The Kit Studio builder, agent chats, reply drafts and voice mock interviewer are AI systems, and we label them as such. Documents oyapilot writes for you are AI-assisted. You decide whether and how to use them.

#6.9 Untrusted content and hidden instructions

Some of the text our AI reads is written by third parties, such as job postings, web pages you ask us to check, and emails from Employers. That text can contain hidden instructions intended to manipulate AI (often called prompt injection), for example to make it reveal information. We protect your information by:

• treating third-party text as information to analyze, never as instructions to follow;
• giving AI steps that read third-party text access only to the data the task needs, and only for your own account;
• never allowing an AI step to send an application, an email or your data to anyone on its own; sending always goes through the approval rules and Autopilot rules you set; and
• keeping Sensitive Answers out of AI prompts entirely.

If you see AI output that looks like it followed instructions from a job posting or an email, please tell security@oyapilot.ai.

#6.10 People do not read your AI conversations

We do not have people review your documents, chats or AI outputs to evaluate or improve our AI. People at oyapilot see your content only in the limited situations described in Section 16.2.

#7. Applying for you: the Application Engine, Autopilot and evidence

#7.1 What is sent to an Employer

When you approve an application in Hybrid mode, or when Autopilot sends one, the Application Engine opens the Employer's application form in a browser we operate on our cloud infrastructure and fills it with information from your account. Depending on what the form asks, this can include:

• your name, preferred name and pronouns;
• the oyapilot reply address for that application (in place of your personal email, where the form accepts it), your phone number and your address;
• your LinkedIn, GitHub and portfolio links;
• your work history, education and skills;
• your résumé as a PDF (tailored for that job, or your chosen Kit), and your cover letter;
• your saved answers and drafted answers to screening questions;
• your notice period, start date and relocation willingness; and
• your Sensitive Answers, only for the categories you have consented to.

The Employer and its hiring system receive this information and process it under their own privacy policies.

#7.2 Where the Application Engine runs

The Application Engine runs on cloud servers operated by our hosting provider (Railway) and is coordinated by our workflow provider (Inngest). To create your résumé PDF, it creates a temporary file on the server, which is deleted after the application attempt.

#7.3 Fraud and safety checks

Before sending an application, we check the posting and form for signs of fraud or risk (for example, whether the domain is real, whether the form requires a login, whether the posting's ghost risk exceeds your tolerance, and whether the form asks for identity numbers or financial details). We store the result of these checks with the application record.

#7.4 Screenshots and evidence

The Application Engine takes screenshots of the filled form and of the confirmation page, so that you can see exactly what was sent and so that an application is marked "Applied" only when the Employer confirms it. Screenshots show the information entered in the form, which can include your personal information and Sensitive Answers. They are stored in a private storage area that only you can view (and our systems, to show them to you), and they are kept as described in Appendix 4.

#7.5 Needs You

When the Application Engine stops (for example, at a CAPTCHA, a login wall or a question it cannot answer), it saves what it filled, the reason it stopped and the questions it could not answer, and places the application in your Needs You queue.

#7.6 Records of what was sent

For every application sent by the Application Engine, we keep a record of the posting address, the Employer's domain, the time, the mode, the outcome, the fields submitted and a snapshot of the materials used. We keep these records so that you can see what was sent in your name, so that we can apply per-employer limits, to support the Interview Guarantee, and to handle any dispute.

#7.7 Consent for Autopilot

Autopilot is off by default. When you switch it on, we record the time and the version of the consent screen you accepted.

#8. The browser extension

#8.1 What the extension does

The oyapilot extension shows oyapilot scores on supported job pages, fills application forms in your own browser session from your Application Profile, and lets you save a job or send an application to your Needs You queue.

#8.2 Permissions it asks for

• Storage: to keep your extension sign-in, your profile for filling forms, your settings and a daily fill counter on your device.
• Alarms: to refresh its sign-in on a schedule.
• Active tab and scripting: to fill the form on the page you are viewing, only when you click the extension.
• Host access limited to oyapilot.ai and the job sites it supports (Greenhouse, Lever, Ashby, SmartRecruiters and USAJOBS).

#8.3 What it reads on web pages

On supported job and application pages, and on a page where you click the extension, it reads:

• the page's address and title;
• the application form's fields and their labels, so it can decide what to fill; and
• job identifiers in the page address, so it can look up oyapilot scores.

It does not read or collect your browsing history, the content of pages that are not job or application pages, your passwords, your cookies for other websites, or the contents of your email.

#8.4 What it stores on your device

In your browser's extension storage: a sign-in token for your oyapilot account and its expiry, your Application Profile (for filling forms), your fill settings, a count of fills today, and, only if you choose to let it fill Sensitive Answers, the categories of Sensitive Answers you have consented to. These are removed when you sign out of the extension or remove it.

#8.5 What it sends to us

• requests to sign in and refresh its token;
• a request for your Application Profile;
• the job page address or identifier, to fetch scores and form-filling plans;
• reports that a form field could not be filled (which field type, the technical selector and the error, without the value you entered), to help us fix form support; and
• when you send an application to Needs You, the reason, the page address and the page title.

All communication uses encrypted connections (HTTPS).

#8.6 Limited Use

oyapilot's use of information received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use extension data only to provide and improve the extension's features that you use. We do not use it for advertising, we do not sell it, we do not transfer it except as needed to provide those features, comply with the law, or as part of a merger or acquisition, we do not use it to determine creditworthiness or for lending, we do not use it to train AI models, and people at oyapilot do not read it except with your permission, for security, to comply with the law, or when it has been aggregated and de-identified.

#8.7 Your control

You can see the extension's permissions in your browser, sign out of it, turn off Sensitive Answer filling in its settings, and remove it at any time.

#9. The application mailbox

#9.1 How it works

When oyapilot sends an application, it can give the Employer a unique reply address for that application (at apply.oyapilot.ai). Email sent to that address is received by our email provider (Postmark), delivered to oyapilot, and shown in your Mail tab.

#9.2 What we do with those messages

We store each message (sender, recipient, subject, text, formatting and attachments), use AI to classify it (for example, as an interview request, offer, rejection, recruiter message, acknowledgment or action needed), extract details such as interview dates, update the status of the matching application and your calendar, and, if you ask, draft a reply. If you verify a forwarding address, we forward messages to it.

#9.3 Replies you send

Replies you send from your Mail tab are sent through Postmark from the reply address for that application, and stored in the conversation.

#9.4 Other people's information in messages

Employer messages contain the names, email addresses, job titles and words of the recruiters and hiring staff who wrote them. We process that information only to deliver the message to you and to run your mailbox (see Section 24).

#9.5 Keeping it private

Only you can see your mailbox. The MCP server can share thread summaries (sender, subject, date and category) with an AI client you connect, but not message bodies. We do not use mailbox content for any purpose other than running your mailbox, supporting your tracker and calendar, checking Interview Guarantee eligibility if you claim it, keeping the Services secure, and complying with the law.

#10. The MCP server and connected AI clients

#10.1 What it shares

If you create an MCP access token and connect an AI client (such as a desktop AI assistant or code editor), that client can use the token to ask oyapilot for: job searches and job details, ghost checks, your applications and their statuses, your saved jobs, your queue, summaries of your mail threads (without message bodies), and a summary of your profile that excludes Sensitive Answers and contact details beyond what the summary needs.

#10.2 Your direction, their policies

When your AI client retrieves information through the MCP server, you are directing us to disclose that information to the client you chose. From then on, the client and its provider handle it under their own terms and privacy policies. We do not control what they do with it, including whether they keep it or use it to train models. Choose AI clients you trust, and check their data settings.

#10.3 Tokens and logs

We store a one-way hash of each token, its last four characters, its expiry date and call counts, and we log each tool call (which tool, when, and whether it succeeded) for security, limits and product analytics. You can revoke a token at any time.

#11. Free tools, anonymous use and public reports

#11.1 Using free tools without an account

You can use many free tools without an account. When you do:

• Résumé score: the résumé you upload is converted to text and sent to Anthropic to generate the score and critique. We do not store the résumé or the result after showing it to you, other than as part of our AI provider's temporary retention (Section 6.2).
• Ghost-job checker: the posting text or link you provide is analyzed. If you provide a link, our servers or our job page reader fetch the public page. The resulting report may be saved as a public report (Section 11.3).
• Calculators and letter writers: the numbers and text you enter are processed in your browser or on our servers only to produce the result, and are not stored.

#11.2 Anonymous usage limits

To keep free tools available and prevent abuse, we limit how many times each visitor can use them each day. To do that, we store a one-way hash of your IP address with a count and date, and we set a cookie (Appendix 3). We keep these hashes for 30 days.

#11.3 Public ghost reports

When the ghost-job checker produces a report, it may be saved with its own link so that it can be shared. Anyone with the link can view the report, and report pages may be indexed by search engines. A report contains the job title, company and our verdict and reasons. It does not contain your name, email or account details. If you paste text that contains personal information into the ghost checker, that text may be analyzed, so please remove personal information first. If you want a report removed, write to privacy@oyapilot.ai with the link.

#11.4 Pre-signup start wizard

If you answer the questions in our "start" wizard before creating an account (such as target roles, locations, salary floor and search status), your answers are kept only in your browser's local storage until you create an account and choose to import them. We do not receive them until you import them. You can clear them by clearing your browser's site data.

#12. How we share information

We share personal information only in the situations below. Appendix 2 lists our service providers by name.

#12.1 With Employers and hiring systems, at your direction

When you apply to a job through oyapilot, whether you approve it in Hybrid mode, Autopilot sends it, or you use the extension, we send your application to the Employer and its hiring system (Section 7.1). This is a disclosure you direct. It is not a sale.

#12.2 With our service providers

We use companies that help us run the Services, such as hosting, database and storage, authentication, AI, email delivery, payments, product analytics and workflow scheduling. They process personal information only on our instructions, under written contracts that require them to protect it, keep it confidential, use it only to provide their services to us, and delete or return it when their work ends. Appendix 2 lists them, what they do and what they receive.

#12.3 With your chosen AI clients and other destinations

When you connect an AI client through the MCP server, set up email forwarding, share a ghost report link, or export your documents, we send information where you tell us to.

#12.4 With Stripe for payments

Stripe processes your payments as our service provider and, for some purposes such as fraud prevention and meeting its legal obligations, as an independent controller under its own privacy policy.

#12.5 With Google when you sign in with Google

When you use Google sign-in, Google knows that you signed in to oyapilot. We do not share your oyapilot content with Google.

#12.6 For legal reasons

We may disclose information if we believe in good faith that it is reasonably necessary to:

• comply with a law, regulation, court order, subpoena or other legal process;
• respond to a lawful request from a government authority, after checking that the request is valid;
• enforce our Terms or investigate possible breaches;
• detect, prevent or address fraud, security or technical problems; or
• protect the rights, property or safety of oyapilot, our users, Employers or the public.

Where the law allows and it is safe to do so, we will tell you before disclosing your information in response to a government or legal request, so that you can object. We will push back on requests that are overly broad or lack a proper legal basis.

#12.7 In a business transfer

If Oyatco LLC is involved in a merger, acquisition, financing, reorganization, bankruptcy or sale of all or part of its assets, personal information may be transferred as part of that transaction. We will require the recipient to honor this policy, and we will notify you before your information becomes subject to a materially different privacy policy.

#12.8 With your consent

We may share information for other purposes if you ask us to or give us your consent.

#12.9 Aggregated and de-identified information

We may share aggregated or de-identified information that does not identify you, for example in our public ghost-job report or job market statistics. We will not try to re-identify it, and we require anyone who receives it not to try either.

#12.10 What we never share

We never share your personal information with data brokers, advertising networks or other companies for their own marketing, and we never give Employers access to your account, your other applications, your scores or your search activity.

#12.11 Requests about you from employers and others

If an Employer, recruiter, current employer or anyone else asks us whether you use oyapilot, what you applied to, or anything else about you, we will not tell them, unless you ask us to or the law requires it. The only information an Employer receives from us is the Application you send to it and your replies.

#12.12 How we handle government and law enforcement requests

We disclose personal information to government or law enforcement authorities only when we are legally required to, and we follow these principles:

• we require a valid legal process, such as a subpoena, court order or search warrant, appropriate to the information requested, except in a genuine emergency involving a risk of death or serious physical injury;
• we check each request for legal validity and scope, and we challenge or narrow requests that are unlawful, overbroad or unclear;
• we disclose only the information the process specifically requires;
• we notify you before disclosing your information, unless the law prohibits it, or notice would create a risk of harm or an emergency exists; if we are prohibited from notifying you, we will notify you once that prohibition ends; and
• we do not build backdoors into oyapilot or give any government direct access to our systems.

#13. No sale, no sharing for advertising, and Global Privacy Control

#13.1 We do not sell or share

We do not sell personal information, and we do not share personal information for cross-context behavioral advertising (targeted advertising), as those terms are defined in the California Consumer Privacy Act and similar laws. We have not done so in the past 12 months. We do not sell or share anyone's personal information, including that of users under 18. We do not use advertising pixels or advertising cookies on our website or in our product.

#13.2 If that ever changes

If we ever start using advertising tools that would count as selling or sharing, we will update this policy first, provide a clear "Do Not Sell or Share My Personal Information" link, and honor opt-outs, including through Global Privacy Control.

#13.3 Global Privacy Control

We honor the Global Privacy Control (GPC) signal. If your browser sends GPC, we treat it as a request to opt out of any sale or sharing of your personal information and of targeted advertising, for your browser and, if you are signed in, for your account. Because we do not sell or share, GPC does not change how the Services work for you today, and we display a message confirming that your opt-out has been received.

#14. Cookies, local storage and analytics

#14.1 What these are

Our Cookie Policy (oyapilot.ai/cookies) gives full detail on every cookie and storage item, and is part of this policy.

Cookies are small files a website stores in your browser. Local storage and session storage are similar browser features that keep information on your device. We call them all "cookies and similar technologies" here. Appendix 3 lists every one we use.

#14.2 The kinds we use

• Strictly necessary: keep you signed in, protect your session, enforce the invitation gate and free usage limits, and remember the discount or referral link you arrived with. The Services cannot work without them.
• Preferences: remember your theme, navigation layout, sidebar state and recent searches.
• Analytics: help us understand how the Services are used so we can fix problems and improve them (PostHog and Vercel Web Analytics).

We do not use advertising cookies.

#14.3 Product analytics

We use PostHog to understand how people use oyapilot. PostHog records the pages you visit (including the page address), when you leave a page, clicks and form interactions that it captures automatically, and specific events we send, such as signing up, running a score, saving a job, starting a tailoring, sending an application, starting checkout, starting cancellation, connecting an MCP client, and the cost of AI calls. When you are signed in, these events are linked to your account ID and email address. PostHog stores this information for us on servers in the United States.

We configure PostHog not to capture what you type into form fields, and we do not use PostHog session recordings.

We also use Vercel Web Analytics, which counts page views and measures performance without using cookies.

#14.4 Third-party requests from your browser

Some pages load small resources directly from third parties, which means those third parties receive your IP address and the request:

• company logos and icons from DuckDuckGo's and Google's public favicon services, which receive the company's domain; and
• city suggestions from Open-Meteo's geocoding service, which receives the letters you type into a location field.

#14.5 Your choices

You can block or delete cookies in your browser settings. If you block strictly necessary cookies, you will not be able to sign in. [If you are in the EEA or UK, we will ask for your consent before setting analytics cookies, and you can change your choice at any time from the "Cookie settings" link in the footer.]

#15. How long we keep information

We keep personal information only as long as we need it for the purposes in this policy, and then we delete it or de-identify it. Appendix 4 gives specific periods for each kind of information. The main rules are:

• While your account is open, we keep your account information, Application Profile, Kits, applications, mailbox, tracker and interview preparation so that the Services work, unless you delete individual items sooner.
• When you delete your account, we delete or de-identify your personal information within 30 days, and it is removed from our backups within a further 60 days (90 days in total), except for the limited records listed in Section 15.1.
• Inactive free accounts: if a Free plan account has not been used for 24 months, we will email you, and if you do not sign in within 30 days, we will delete it.
• Waitlist entries are kept until we have emailed you that oyapilot is open, and deleted [90 days] after that email. Write to privacy@oyapilot.ai and we will remove your entry sooner.
• Anonymous free tool inputs are not stored, except public ghost reports and the anonymous usage counters described in Section 11.

#15.1 What we keep after deletion

After you delete your account we may keep, for the periods in Appendix 4:

• billing and tax records, which the law requires us to keep (usually 7 years);
• records of consents you gave for automatic renewal and Autopilot, as some laws require;
• a minimal record of applications sent by the Application Engine (date, Employer domain, outcome, without documents or answers), to respond to disputes, complaints from Employers or hiring systems, and legal claims;
• information needed to prevent fraud and abuse, such as a record that an account was closed for breaching our Terms, and a hash of your email address so we can honor the one-per-person limits on free usage, the Interview Guarantee and promotions;
• information we must keep because of a legal obligation, a legal hold or an ongoing dispute; and
• aggregated or de-identified information, which does not identify you.

#15.2 What we cannot delete

We cannot delete applications already received by Employers, messages already delivered to your forwarding address, information your AI client already retrieved through the MCP server, or information held by Stripe as an independent controller. You can contact those parties directly.

[Engineering, critical before publishing: as of 26 September 2026 deleteAccountAction (apps/web/src/app/(workspace)/settings/actions.ts) deletes the auth user and relies on database cascades, but it does NOT (1) delete Storage objects in kit-sources, apply-evidence, profile-photos, mailbox-attachments and feedback-attachments; (2) cancel the Stripe subscription or delete the Stripe customer; (3) delete the PostHog person; (4) delete feedback rows (user_id is set to NULL, content kept). All four must be fixed, and a scheduled backup-expiry process documented, before this Section can be published. Also reconcile the help page that says "There is no retention period."]

#15.3 Deleting individual items

When you delete an individual item (for example, a Kit, an application, a mail message or a Sensitive Answer), it is removed from your account at once and deleted from our active systems within 30 days, and from backups on the schedule in this Section. Deleting an application also deletes its screenshots. Items you delete cannot be restored.

#15.4 De-identified information

When we de-identify information, we take reasonable measures to make sure it cannot be linked to you or your device, we publicly commit (in this policy) to keep it in de-identified form and not to try to re-identify it, and we require anyone we share it with to make the same commitment.

#16. How we protect information

We use administrative, technical and physical safeguards designed to protect personal information, including:

• Encryption in transit using TLS (HTTPS) for all connections to our website, API, extension and service providers.
• Encryption at rest of our database and file storage, provided by our database and storage provider.
• Row-level security in our database, which enforces at the database level that each user can read only their own records, even if an application bug occurred.
• Separation of sensitive data: Sensitive Answers are stored separately from the rest of your profile.
• Private file storage for résumé uploads, application screenshots, mailbox attachments and feedback attachments, available only through short-lived signed links.
• Hashed credentials: passwords, extension keys and MCP tokens are stored only as one-way hashes.
• No third-party passwords: we never store passwords or cookies for other websites.
• Least-privilege access: only the systems and people who need access to personal information to run the Services have it, and privileged service keys are kept in secured environment configuration.
• Monitoring of our systems for errors, abuse and unusual activity.
• Vendor review: we choose service providers that maintain recognized security programs and sign data processing terms.

Profile photos. If you upload a profile photo to your Application Profile, it is stored at an unguessable web address so that it can be attached to forms that ask for one. Anyone who has that exact address can view the photo. Do not upload a photo if you are not comfortable with this. You can delete it at any time.

No system is perfectly secure. We cannot guarantee that information will never be accessed, disclosed or destroyed by a breach of our safeguards. You help protect your account by using a strong, unique password, keeping your email account secure, and revoking tokens you no longer use.

Our Security and Vulnerability Disclosure Policy (oyapilot.ai/security) describes our safeguards in more detail and explains how to report a vulnerability.

#16.1 If there is a breach

If a security incident affects your personal information, we will notify you and the relevant authorities as and when the law requires, and we will tell you what happened, what information was involved, what we are doing, and what you can do.

#16.2 Who at oyapilot can see your information

oyapilot is run by a small team. Access to user data is limited to people who need it to run the Services, and each of them is bound by confidentiality obligations. People at oyapilot do not browse user accounts. They look at specific personal information only when:

• you ask for help and the request needs it;
• they need to investigate and fix a specific problem, such as a failed application or a broken form, using the least data possible;
• they need to investigate fraud, abuse, a security incident or a breach of our Terms, or a complaint about an account;
• you make a privacy request, a refund request or an Interview Guarantee claim; or
• the law requires it.

#16.3 Keeping your account safe

Security is shared. You help protect your information by using a strong, unique password, securing the email account connected to oyapilot, signing out on shared devices, and revoking MCP tokens you no longer use. Our Security and Vulnerability Disclosure Policy has more tips, and explains how to recognize real messages from us.

#17. Your choices and controls

You can do the following yourself, at any time, from your settings, without writing to us:

Unsubscribing from emails. Every job digest and product email includes an unsubscribe link. Service messages (such as sign-in links, receipts, security alerts and renewal reminders) cannot be switched off while you have an account.

#18. Your privacy rights

We give every user the rights in this Section, wherever you live, subject only to the limits the law allows (for example, where a request would reveal another person's information, or where we must keep information to comply with the law).

#18.1 Your rights

• Know and access: ask what personal information we hold about you, how we got it, why we use it, who we share it with, and get a copy.
• Portability: get a copy of information you gave us in a structured, commonly used, machine-readable format, and have us send it to another company where technically feasible.
• Correct: ask us to fix inaccurate information. You can correct most information yourself in your settings.
• Delete: ask us to delete your personal information, subject to Section 15.1.
• Withdraw consent: withdraw any consent you gave, including for Sensitive Answers and Autopilot, at any time. Withdrawal does not affect processing that already happened.
• Object and restrict: object to processing based on our legitimate interests (for example, product analytics), or ask us to restrict processing while a question is resolved.
• Opt out: of any sale, sharing or targeted advertising (we do none), of profiling that produces legal or similarly significant effects (we do none), and of marketing emails.
• Human review: ask for a person to review an automated step that affected you (Section 6.7).
• Non-discrimination: we will not deny you service, charge you a different price, or give you a lower quality of service because you exercised your privacy rights.

#18.2 How to make a request

• Use the controls in your settings (Section 17), or
• email privacy@oyapilot.ai from the email address on your account.

oyapilot operates only online and has a direct relationship with each user, so email and the in-app controls are our request methods.

#18.3 Verification

To protect your information, we verify requests. If you are signed in, or you write from the email address on your account, that is usually enough. For requests for specific pieces of information or for deletion, we may ask you to confirm a code sent to your account email. We will not ask for more information than we need, and we use the information you give for verification only for that purpose.

#18.4 Authorized agents

You may use an authorized agent to make a request for you. We will ask the agent for proof that you authorized them (such as a signed permission or a power of attorney), and we may ask you to verify your identity directly, unless the agent has a valid power of attorney under the law.

#18.5 Timing

We respond within 45 days (or one month in the EEA, UK and Switzerland). If we need more time, we will tell you why, and we may extend the period by up to 45 more days (or two more months) where the law allows. We do not charge for requests unless they are clearly unfounded or excessive.

#18.6 Appeals

If we decline your request, in whole or in part, we will explain why. You can appeal by replying to our decision or emailing privacy@oyapilot.ai with the subject "Privacy request appeal" within 60 days. A person not involved in the original decision will review the appeal, and we will respond within 45 days (or 60 days where the law allows) with a written explanation. If you are not satisfied, you can contact your state attorney general or your data protection authority (Sections 19 and 20).

#18.7 Requests we may decline or limit

We may decline or limit a request, and will explain why, if:

• we cannot verify your identity after reasonable effort;
• fulfilling it would reveal another person's personal information or confidential information about them, such as another person's message to you, unless that person agrees;
• we must keep the information to comply with a legal obligation, to complete a transaction you asked for, to detect security incidents or fraud, or to establish, exercise or defend legal claims;
• it is manifestly unfounded, excessive or repetitive; or
• the law otherwise allows us to decline.

When we decline to delete some information, we delete the rest and tell you what we kept and why.

#18.8 Deceased users

If an oyapilot user has died, a family member or legal representative may ask us to close the account and delete its data by writing to privacy@oyapilot.ai with reasonable proof of death and of their relationship or authority. We will not give anyone access to the contents of another person's account unless the law requires it.

#18.9 Records of your requests

We keep a record of privacy requests and how we responded for at least 24 months, as some laws require. These records contain only what is needed to show that we handled the request.

#19. Additional information for US state residents

#19.1 Which laws

Residents of California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia and other states with comprehensive privacy laws have specific rights under those laws. Section 18 gives those rights to everyone. Appendix 6 summarizes them by state.

#19.2 California notice at collection

If you are a California resident, this Section and Appendix 1 are our notice at collection and privacy policy under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, "CCPA").

In the past 12 months, we have collected the categories of personal information listed in Appendix 1, from the sources in Section 3, for the business and commercial purposes in Section 5, and disclosed them for business purposes to the categories of recipients in Appendix 1. We have not sold or shared personal information (Section 13). We keep each category for the periods in Appendix 4.

Sensitive personal information. We collect the sensitive personal information described in Section 4 and use it only for the purposes permitted by the CCPA regulations (to provide the Services you request, to ensure security and integrity, and similar permitted purposes). We do not use it to infer characteristics about you.

Shine the Light. California Civil Code Section 1798.83 lets California residents ask for information about disclosure of personal information to third parties for their direct marketing. We do not disclose personal information to third parties for their direct marketing.

#19.3 Consumer health data

Residents of Washington, Nevada and Connecticut should also read Appendix 5.

#19.4 Maryland

We collect sensitive data (Section 4) only where it is strictly necessary to provide the specific service you request, which is filling in the application forms that ask for it, and we never sell sensitive data.

#19.5 Colorado, Connecticut, Virginia and others: profiling

We do not engage in profiling in furtherance of decisions that produce legal or similarly significant effects about you. Our job scoring ranks jobs for you under your rules, and you can switch off or override it.

#19.6 Data protection assessments

Where the law requires, we carry out and document data protection assessments for processing of sensitive data and other higher-risk processing, and we make them available to regulators on request.

#19.7 Texas

If you live in Texas, you have the rights described in the Texas Data Privacy and Security Act, which Section 18 covers. We process sensitive data only with your consent (Section 4). We do not sell personal data, sensitive personal data or biometric data. If we decline your request, you may appeal (Section 18.6), and if your appeal is denied, you may contact the Texas Attorney General at texasattorneygeneral.gov/consumer-protection.

#19.8 Nevada

Nevada residents may ask us not to sell covered information. We do not sell covered information, but you may still submit a request to privacy@oyapilot.ai, and we will record it.

#19.9 Where to complain

If you are not satisfied with our response to an appeal, you may contact the attorney general of your state. For example: California residents may contact the California Privacy Protection Agency (cppa.ca.gov) or the California Attorney General; Colorado, Connecticut, Virginia, Oregon and other residents may contact their state attorney general.

#20. Additional information for people in the EEA, UK and Switzerland

#20.1 Who is responsible

Oyatco LLC is the controller of your personal information. Our contact details are in Section 29.

EU representative: [NAME AND ADDRESS, if appointed under Article 27 GDPR] UK representative: [NAME AND ADDRESS, if appointed under Article 27 UK GDPR]

#20.2 Legal bases

Section 5 lists the legal basis for each purpose. Where we rely on consent (for example for Sensitive Answers, which are special category data under Article 9, and analytics cookies where required), we ask for it separately and you can withdraw it at any time. Where we process special category data (such as racial or ethnic origin, and health data in a disability answer), we rely on your explicit consent under Article 9(2)(a).

#20.3 Contractual necessity

Much of the information we process is needed to provide the Services under our contract with you. If you do not provide it, we may not be able to provide some or all of the Services. For example, without a résumé we cannot tailor documents, and without contact details we cannot fill applications.

#20.4 Your additional rights

In addition to the rights in Section 18, you have the right to lodge a complaint with your local data protection authority. In the UK, that is the Information Commissioner's Office (ico.org.uk). In Switzerland, it is the Federal Data Protection and Information Commissioner. In the EU, you can find your authority at edpb.europa.eu. We would appreciate the chance to address your concern first.

#20.5 Automated decision-making

We do not make decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you, within the meaning of Article 22 GDPR.

#20.6 Transfers

See Section 22.

#21. Additional information for other countries

#21.1 Canada

We handle personal information of people in Canada in line with the Personal Information Protection and Electronic Documents Act and applicable provincial laws. Your information is stored and processed in the United States and may be accessible to courts and authorities there. You may contact our privacy officer at privacy@oyapilot.ai. You may complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information.

#21.2 Australia

We handle personal information of people in Australia in line with the Australian Privacy Principles. You may complain to us, and if you are not satisfied, to the Office of the Australian Information Commissioner.

#21.3 Brazil

If you are in Brazil, you have the rights listed in Article 18 of the Lei Geral de Proteção de Dados (LGPD), which Section 18 covers. You may contact our privacy contact at privacy@oyapilot.ai.

#21.4 Everywhere else

We will honor any additional rights the law of your country gives you. Contact privacy@oyapilot.ai.

#22. International data transfers

oyapilot is operated from the United States, and our service providers process personal information mainly in the United States. [Our database is hosted in [SUPABASE REGION, for example "the United States (us-east-1)"].] If you use the Services from outside the United States, your information will be transferred to, stored in and processed in the United States, where data protection laws may differ from those in your country.

Where the law requires a transfer mechanism (for example, for transfers from the EEA, UK or Switzerland), we rely on:

• the European Commission's Standard Contractual Clauses, with the UK International Data Transfer Addendum and Swiss amendments, in our contracts with service providers;
• the EU-US Data Privacy Framework, its UK Extension and the Swiss-US framework, for service providers certified under them; and
• where applicable, the necessity of the transfer to perform our contract with you.

You can ask for more information about these safeguards, and a copy of the relevant clauses, at privacy@oyapilot.ai.

#23. Children and teenagers

The Services are not directed to children under 16, and people under 16 may not use them. We do not knowingly collect personal information from anyone under 16. If you believe a person under 16 has given us personal information, contact privacy@oyapilot.ai, and we will delete it and close the account.

Users aged 16 and 17 may use oyapilot with a parent or guardian's permission, as our Terms explain. For these users:

• we never sell or share their personal information, and never use it for targeted advertising (we do none for anyone);
• we apply the same protections we give every user, including the limits on Sensitive Answers in Section 4; and
• a parent or guardian may exercise the user's privacy rights on their behalf by writing to privacy@oyapilot.ai, after we verify the relationship.

#24. People who are not oyapilot users

We sometimes process personal information about people who do not use oyapilot. This Section explains how, and what they can do.

#24.1 Professional references

If a user adds you as a professional reference, we store your name, contact details, relationship and any notes the user provides, so that the user can include them in applications. We require users to have your permission before adding you. We do not contact you ourselves.

#24.2 Recruiters and hiring staff who email a reply address

If you write to an oyapilot reply address about an application, we receive your message (including your name, email address, signature and any attachments), store it for the user, and use AI to sort it and draft a reply for the user to review. We do not add you to any mailing list or use your message for any other purpose. Replies come from the user, who decides what to send.

#24.3 People named in job postings

Public job postings sometimes include the name or contact details of a recruiter or hiring manager. We store postings as published by the Employer, in our job index and posting history, so that users can see and apply to them and so that we can estimate ghost risk. We do not build profiles of the people named in postings.

#24.4 Your rights

If you are one of these people, you can ask us about the information we hold about you, and ask us to correct or delete it, by writing to privacy@oyapilot.ai. Where information is part of a user's own records (for example, a message you sent them), we may need to balance your request against that user's rights.

#24.5 Employers and hiring systems

When the Application Engine submits an application, the Employer's hiring system may show a confirmation page or send a confirmation message that includes information about the Employer and the application process. We keep that confirmation in your account, as evidence that the application was received.

#25. Public job and company data

#25.1 What we collect

oyapilot builds its job index from public job postings published by employers through their hiring systems and careers websites, from public government job sources, and from licensed job data partners. It builds its company database from public company information and licensed datasets, such as company names, websites, industries and sizes. We record each observation of each posting over time (our posting history), which is how we estimate ghost risk.

#25.2 How we use it

We use it to show jobs to users, match jobs to users, estimate ghost risk and salary, and publish public pages and aggregate statistics about hiring activity and ghost jobs.

#25.3 Employers' requests

If you represent an Employer and have a question about how our data describes your postings or your company, or would like a correction, contact legal@oyapilot.ai.

#26. Notice of financial incentive

We offer certain incentives that California law may treat as financial incentives connected to personal information:

• First-month discount. New accounts that start a paid plan within 7 days of signing up get a discount on the first month.
• Referral program. When someone you invite signs up through your link and pays for a plan, you and they may each get a free month of service (up to the limit in our Terms).
• Student pricing. Verified students get a discount.

Personal information involved: your account information and, for referrals, the fact that a new user signed up through your link; for student pricing, your student email or other verification information.

How to opt in and out: you opt in by creating an account, using your referral link or verifying student status. You can stop taking part at any time by not using your referral link, by asking us to remove you from the referral program, or by deleting your account. Rewards already earned may be lost if you withdraw.

Why the value is reasonably related to your data: we estimate the value of these incentives based on the expected cost of acquiring a new paying customer through other channels and the expected revenue from a paid subscription. We do not sell or share the personal information involved, and the value of the incentive is not based on the value of your data to any third party.

#27. Do Not Track

Some browsers send "Do Not Track" signals. There is no industry standard for responding to them, so the Services do not change behavior in response to Do Not Track. We do honor Global Privacy Control (Section 13.3), and we do not track you across other websites.

#28. Changes to this policy

We may update this policy as the Services, the law or our practices change. The "Last updated" date at the top shows when it last changed. If we make a material change, we will tell you at least 30 days before it takes effect by email and by a notice in the Services, unless a change is needed sooner for legal or security reasons. We will not use personal information we have already collected in a materially different way without your consent where the law requires it. We keep previous versions of this policy and will provide them on request.

#29. How to contact us

Oyatco LLC is an online business based in Texas. We do not have a public office, and every privacy question or request can be handled by email.

#Appendix 1. Categories of personal information (California format)

This table uses the categories in the California Consumer Privacy Act. It covers the 12 months before the "Last updated" date. "Sold or shared" is "No" for every category.

#Appendix 2. Our service providers and where your data goes

We list every company that receives personal information from oyapilot to provide the Services. We will update this list before a new provider receives personal information.

Employers and hiring systems (for example Greenhouse, Lever, Ashby, Workable, Recruitee, SmartRecruiters, Workday) receive your applications at your direction (Section 12.1). They are not our service providers, and they process your information as independent controllers under their own policies.

Job data sources we read from, such as public hiring system job boards, USAJOBS and France Travail, receive no personal information about you.

#Appendix 3. Cookies and browser storage

#A3.1 Cookies

#A3.2 Local storage and session storage

#A3.3 Extension storage

See Section 8.4.

#Appendix 4. Retention schedule

"Account life" means for as long as your account exists, unless you delete the item sooner. After account deletion, the 30-day deletion and 90-day backup rules in Section 15 apply unless a longer period is stated here.

#Appendix 5. Consumer Health Data Privacy Policy (Washington, Nevada, Connecticut)

This Appendix summarizes our Consumer Health Data Privacy Policy, which is published as its own page (oyapilot.ai/consumer-health-data) and linked from our homepage, as Washington law requires. The standalone page controls if the two differ. It is our Consumer Health Data Privacy Policy for the purposes of the Washington My Health My Data Act, Nevada Senate Bill 370, and the consumer health data provisions of the Connecticut Data Privacy Act. It applies to consumer health data we collect about consumers in those states, and we apply it to all users.

[Founder decision, 27 September 2026: oyapilot stores disability status, with separate consent, so that Autopilot can answer the voluntary self-identification question. This Appendix must therefore be published and linked from the homepage footer.]

#A5.1 Consumer health data we collect

The only consumer health data we may collect is your answer to a voluntary disability self-identification question (for example, "Yes, I have a disability", "No, I do not have a disability", or "I do not wish to answer"), if you choose to save one in your Application Profile. We do not collect diagnoses, treatment, medications, health conditions or any other health information. Please do not include health information in your résumé, answers or messages to us unless you want it used in your applications.

#A5.2 Why we collect it and how we use it

We collect it only to fill the voluntary disability self-identification question on application forms you authorize us to fill or send, and to show it to you so you can review and change it.

#A5.3 Where it comes from

Only from you.

#A5.4 Consent

We collect disability status only with your separate, specific consent, given in your Application Profile after we show you what it is used for. We share it with an Employer only as part of an application you authorize, which is a sharing you request, and only while your consent is active. You can withdraw consent at any time in your Application Profile, and we will stop using the answer and delete it.

#A5.5 Who we share it with

• Employers and their hiring systems, in the disability self-identification field of applications you authorize; and
• our service providers that store and process it for us (our database and hosting providers, the Application Engine's hosting provider, and, if you use it, the extension on your own device).

We do not sell consumer health data, and we do not share it with anyone else.

#A5.6 Your rights

You have the right to:

• confirm whether we collect, share or sell your consumer health data, and access it;
• get a list of all third parties and affiliates with whom we have shared it, with their contact information;
• withdraw consent; and
• have it deleted, including from our service providers' systems.

To exercise these rights, use the controls in your Application Profile or email privacy@oyapilot.ai. We will respond within 45 days, and you may appeal a refusal as described in Section 18.6. If your appeal is denied, you may contact the Washington State Attorney General at atg.wa.gov/file-complaint, the Nevada Attorney General, or the Connecticut Attorney General.

#A5.7 Geofencing

We do not use geofences around health care facilities or for any other purpose.

#Appendix 6. State privacy rights summary

Section 18 gives these rights to every user. This table shows which rights each state's law provides, for reference.

We provide the most protective version of each right to all users. If your state gives you a right not listed here, contact privacy@oyapilot.ai and we will honor it.

#Appendix 7. Browser extension data disclosure

The oyapilot extension shows the following disclosure, and asks you to agree, before it collects or sends any data. The Chrome Web Store requires this disclosure to appear inside the extension, not only in this policy.

Before you start

oyapilot fills job applications in your browser using the profile you saved in oyapilot.

To do that, the extension reads the page address, the page title and the application form's fields and labels on supported job sites (Greenhouse, Lever, Ashby, SmartRecruiters and USAJOBS) and on any page where you click the extension. It sends the page address to oyapilot to fetch scores and form instructions, and it tells oyapilot when a form field could not be filled (never the value).

It keeps your oyapilot sign-in and your profile on this device so it can fill forms. If you turn on "Fill sensitive answers", it also keeps the work authorization, salary and self-identification answers you consented to in oyapilot.

It never reads your browsing history, other websites, your passwords or your email. It never submits a form for you. We never sell this data, use it for ads, or use it to train AI.

[Agree and continue] [Not now]

Read the full Privacy Policy: oyapilot.ai/privacy

End of the oyapilot Privacy Policy.