Privacy Policy

To provide deterministic form autofill, resume management, and application workflows, we collect only the data you explicitly provide:

• Account & Profile Data: Your name, contact email, phone number, location, work history, education credentials, skills, projects, current CTC and expected salary (each with its currency), and notice period.
• Job Preferences: The work setup, locations, relocation, roles, seniority and employment types you are looking for, where you are authorized to work, whether you need visa sponsorship, and the languages and certifications you list.
• Saved Jobs: The job board listings you bookmark, and when you saved them.
• Resume & Career Assets: PDF resumes uploaded to your account for ATS file-upload matching and automatic profile parsing, and the text of each one (with email addresses, phone numbers and links removed) for the extension's ATS Match tab. Our server reads that text from the PDF when you upload it, or for an older resume the first time the tab uses it, and keeps it with the resume until you delete it. Uploading a resume on lazee.dev also fills the profile fields that are still empty (name, contact details, links, job type, and skills, experience, education or projects when you have none) by reading the PDF on our server, without AI. It never changes a field you already filled in, and what it fills shows on your public profile like anything you type yourself.
• Saved Questions & Answers: Custom prompt templates and recurring answers you save to your personal Q&A library.
• Authentication & Session Tokens: Cryptographically signed session tokens used solely to synchronize your profile securely between the web platform and your browser extension. Signing out on lazee.dev also signs the extension out.
• Account Activity: Your plan, AI credit balance and usage, Pro Passes, referral records (who invited whom), and when your browser extension first connected, which is what completes a referral.
• Feedback: Messages you send through the feedback form, with the name and email you choose to include.

The extension works with the job description of the role you are applying to. Reading it and scoring your fit happen in your browser:

• Automatic Detection: When you open lazee.dev on a job page, the extension reads the job description from that page, or from the job board's public data for that posting, inside your browser.
• Fetch from a Job Link: When you paste a job link, your browser downloads that page straight from the job site, without your cookies or login, and reads it locally. The link and the page are not sent to lazee.dev.
• Offline ATS Match: The match score compares the job description with the copy of your profile already in the extension, including your job preferences (for example, a job that won't sponsor a visa when you need one), and the text of the resume picked in the tab (your primary resume by default), which the extension gets from lazee.dev once and keeps on your device. It is calculated in your browser and nothing is sent anywhere.
• Free ATS Checker on the Website: On lazee.dev/ats-resume-checker, the resume PDF or text you add and the job description you paste (or that the extension reads from a job link, in your own browser, when you are signed in with it) are read and scored inside your browser tab, with no account. Nothing is sent to our servers or to an AI model, and closing or reloading the tab discards it. Only if you press “Fix it in the resume builder” are the resume as read and the job kept in your browser's storage (for at most 10 minutes) so the resume builder can open them; it then removes them, and they become that browser's unsaved resume draft until you save or discard it.
• Free Resume Screener on the Website: On lazee.dev/resume-screener, the resume PDFs (or resume text) you add, which may be other people's resumes, and the job description you paste (or that the extension reads from a job link, in your own browser, when you are signed in with it) are read and scored inside your browser tab, with no account. The names, email addresses, titles and skills shown in the ranked list are read from those files on your device. Nothing is sent to our servers or to an AI model, nothing is saved in your browser's storage, and closing or reloading the tab discards it all. The CSV export is built in your browser and saved only where you save it. Signed-out and free-plan visitors see Google ads on this page (see Cookies & Analytics): the ad code runs in the same tab, but we never pass it the resumes, the job description or the results. If you add other people's resumes, you are responsible for having their permission or another lawful basis to process them.
• Showreel Videos on the Website: On lazee.dev/showreel, when you are signed in, the page loads your profile (name, role, location, skills, links, photo, projects with their screenshots, and experience) into your browser to fill in the video form, the same way your profile page does. The preview plays inside your browser tab, and the downloadable project (a zip) is built there too: your browser fetches your profile photo and project screenshots from our storage to put them in it. What you type in the form, and the template you picked last, are kept in your browser's local storage as a draft for each template, and never change your profile. A photo, screenshot or screen recording you pick from your device is kept in your browser's storage (IndexedDB) on that device, so it is still there after a reload, until you remove it, pick something else for that spot or reset the template; it is never uploaded. Clearing your browser's site data removes all of it. Nothing about your video is sent to our servers or to an AI model, and the page loads its player, fonts and music from lazee.dev only. Anyone you share the finished video with sees what you put in it.
• Tailored Resume: The one-page “lazee.dev tailored resume” under the score is written in your browser from the copy of your profile in the extension (name, contact details, skills, experience, projects, education, certifications, languages) and the job description. Nothing is sent anywhere, no credits are used and the PDF is not stored: it is built again each time you open the job or attach it. Skills from the job description that you tap on the card to put in that resume are kept in the extension on your device, per job; they are never sent on their own or added to your profile (they only travel inside the draft if you choose the AI polish). Only the optional AI polish and “Save to profile” described in “How We Use Data” below send anything.
• Salary Check: When a job description states its pay, the ATS Match tab compares it with your expected salary (or your current CTC when that's empty), in your browser. For a job paid in another currency, the extension asks lazee.dev for the day's exchange rates, at most once a day, and keeps them on your device; that request carries no profile or job data. The comparison never changes the match score.
• Sent Only When You Choose: A job description leaves your browser only when you turn on “Use job description” for AI answers (off by default) or run the AI rescore of your match. See “How We Use Data” below.
• Tracking Parameter Stripping: Tracking query parameters (such as UTM parameters, Google Click IDs, and referral tags) are stripped before associating the posting with the canonical job URL.
• Local Cache Retention: Job descriptions are cached strictly within your browser's local extension storage (retaining up to 100 recent postings) so you do not have to re-paste them across multi-page forms.
• Zero Commercial Harvesting: Job descriptions you analyze are never shared with recruiters, employers, or third-party datasets.

The chat agent on lazee.dev/agent runs in your browser tab and does its work through the lazee.dev extension. Without the extension (on a phone, for example) it can still chat and search jobs, on lazee.dev AI or on your own key if you saved it to your account or typed it for that tab; reading job links, the fit score and AI check, tailored resumes and calls still need the extension. It thinks with your own AI key or with lazee.dev AI, whichever you pick:

• Your AI Provider: On your own key, your messages, the conversation so far and the results of the agent's tools go to the AI provider and model you picked in the agent, sent by the extension with your own key, or, without the extension, straight from the page with the key it holds in memory. Our servers only supply the agent's instructions, which carry your first name, your plan, how many Pro Passes you have, and the job preferences on your profile so it can search “for your profile”: preferred roles and levels, workplace, regions and typed locations, employment types, relocation, work authorization and sponsorship, your city and country, your total years of experience and up to 12 of your skills. The model you pick and the Thinking switch are remembered in this browser only, separately for each lazee.dev account.
• lazee.dev AI in the Agent: When you pick lazee.dev AI, the same things (your messages, the last 60 messages of the chat, fewer when a long chat would pass its size limit, the agent's instructions above and the results of its tools) go to our servers instead, which pass them to a free model served through OpenRouter (the one you picked, or our default) and stream its answer back. Our servers don't keep that request after answering it; the chat is kept only as a saved chat (below). Each message you send takes credits from your balance, and we keep the new balance, not the message. For each reply we also keep a short record (when it started and how many steps it took), used to cap a reply's steps and the messages you can send a minute; records older than 20 minutes are cleared when you send your next message.
• Attached Resumes, the AI Check & Installing the Extension: A resume you attach in the agent is uploaded to your lazee.dev account like one from your profile page: it takes a resume slot, counts toward the monthly upload limit, and replaces another resume only after you pick which one. Its extracted text is used as evidence in the offline fit score and stays in that tab. The fit score itself is computed on your device; only the agent's reply about it goes to the AI model you picked, like any message. The AI check of your profile or a resume (Pro, or a Pro Pass on Free) is offered only when you ask for it and runs only when you tap its button: it sends that text and the job description to the AI provider and model you picked in the agent, through the extension; on lazee.dev AI it goes through our servers to OpenRouter, like the extension's AI rescore. Its result is saved with the chat. When you install the extension from the agent's install card, “I installed it” keeps the message to send again in this browser tab (session storage) through the reload; it isn't sent anywhere until it goes as your next message, and it's cleared once read. When you finish the agent's setup chat, your account stores the time you did, so your other browsers and devices skip it.
• Saved Chats: Each chat is saved to your lazee.dev account after every reply, so it shows on your other devices: your messages, the agent's replies and reasoning, its tool calls and their results (job search results, the job descriptions it read, fit scores) and the transcript of any call. What the extension returns to a card is saved with it, so a reopened chat reads the same: AI check results, and for a tailored resume the job description it was built from, its details (file name, page count, which of the job's skills it shows), the job skills you added to it with its keyword chips, its offline ATS score and AI check result and, for the AI version, its rewritten text. Skills added on a resume card stay with that chat and are never written to your profile. Audio, files and resume PDFs are never saved. A chat is deleted 30 days after its last message, and you can delete one sooner from the chat list. Your account keeps your 25 latest chats on Free and 200 on Pro: starting a new chat past that deletes the oldest one.
• Job Search & Job Links: Job searches go to the lazee.dev Jobs API through RapidAPI with your RapidAPI key, sent by the extension or, without it, straight from the page (see “Job Board & Jobs API” below). On lazee.dev AI they run on our servers against the same job board, with the filters the agent picked, and aren't kept apart from the saved chat. Job links are read by the extension in your browser, the same way as the job description panel.
• Fit Score & Tailored Resume: The fit score is the extension's offline ATS match and sends nothing. For a tailored resume, the agent hands the job description to the extension, which builds the PDF on your device from your lazee.dev profile. The AI-tailored version runs only when you ask for it (the card's “Make the AI version”, asking the agent for the AI version, or “Rewrite with AI” after you change the skills on an AI version) and sends the same draft as the AI polish (described under “How We Use Data”), with the job description, to the provider and model you picked in the agent, or on lazee.dev AI through our servers to OpenRouter. The PDF stays in that browser tab and is never saved, unless you click “Save to profile” on the card (Pro): then that PDF, offline or AI version, is uploaded to your lazee.dev account and stored like any other resume you upload (see “Cloud Resume Delivery” below), and the chat keeps the id of that saved resume so the card knows it is already on your profile. When you reopen the chat, the extension builds it again on your device from what the chat saved (see “Saved Chats”) and your current profile, with no new AI call; without the extension the card shows its saved details and asks you to install it. Once a tailored resume is built, the extension scores its text offline on your device against the job (nothing is sent). “Check with AI” on the card (Pro, or a Pro Pass on Free) runs only when you tap it, every time, and sends that resume's text, with its emails, phone numbers and links removed, and the job description to the AI provider and model you picked in the agent, through the extension, or on lazee.dev AI through our servers to OpenRouter, like the extension's AI rescore. Its result is saved with the chat.
• Cold Emails & Your Gmail (Pro): When you ask the agent for a cold email, it needs the recipient's email address (and their name, if you give it) and the job, from its link or the description you paste. To write it, your profile (name, what you're looking for, location, skills, experience, projects, education and your LinkedIn, GitHub and portfolio links), the job description, the recipient and your wishes go to the AI: on lazee.dev AI through our servers to OpenRouter; on your own key our server only assembles the prompt and your browser sends it to your provider. Each email is stored on your lazee.dev account: the recipient's address and name, the job's link, title, company and description, the subject and text, and once sent, when, from which address and the resume's file name. The chat also keeps the email and which resume you picked. To send, you connect a Gmail or Google Workspace address with a Google app password: our server checks it with Gmail, then stores the address and the app password encrypted (AES-256-GCM, with a key kept outside the database), and uses them only to send an email after you confirm it on its card. The email goes from our server through Google's Gmail SMTP server to the recipient, with the resume you picked attached: an uploaded resume is read from our storage, a resume builder resume is built as a PDF on our servers. Google keeps a copy in your Gmail's Sent folder, and replies go to your Gmail; we never read your inbox. Drafts you don't send are deleted 30 days after their last change, and past 200 unsent emails the oldest are deleted. To enforce the limits below, your account also keeps the times of the emails the agent wrote or changed in the last 24 hours and of your Gmail connect attempts in the last hour (times only). Sent emails stay on your Sent emails page (Profile) until you remove them there or delete your account; removing one doesn't unsend it. “Disconnect” on that page deletes the address and app password from lazee.dev at once; you can also delete the app password in your Google account.
• Calls: When you call the agent, the extension uses your OpenAI, Google Gemini or xAI Grok key to get a short-lived call token from that provider, and your microphone audio then streams straight from your browser to it; the agent's voice comes back the same way. The provider transcribes both sides, and the transcript is saved with the chat like typed messages. Call audio never reaches our servers and isn't kept by lazee.dev.
• Agent Keys: The keys you paste on the agent page (your AI model, your RapidAPI key and a key for calls) are stored encrypted in the extension, like your other AI provider keys, and go only to the service they belong to. With the extension, the page only ever sees their last few characters, and only while the account that saved them is signed in. If you save keys to your account (see “Bring Your Own Key” above), or add one on a browser without the extension, they are stored encrypted on your account, or kept for that tab only if you untick “Save to my lazee.dev account”.

• Making the PDF: The resume builder on lazee.dev/resume-builder makes the PDF and its preview in your browser tab. Editing, the preview and Download don't send your resume anywhere; the extension isn't needed for them.
• Your Own Fonts: A font file you upload in the Design tab is read and kept only in this browser (IndexedDB) and is never sent to our servers. The PDFs you download in that browser include the parts of the font they use. The resume keeps only the font's name and which styles you uploaded, and those are saved with it when you press Save, so another browser can tell you the font is missing there. Fonts that no resume has used in this browser for 60 days are removed automatically, and clearing this site's data removes them too.
• Signed Out: Without an account, the resume you build is kept only in this browser (local storage) so it's there when you come back. It isn't sent to our servers. When you sign in or sign up, that draft opens in your account as unsaved changes and moves out of the signed-out spot; it reaches our servers only when you press Save.
• Unsaved Changes: Signed in, editing doesn't send your resume to our servers. Until you press Save (or Ctrl+S), your unsaved changes to the open resume are kept as one draft per account in this browser's local storage, with your account's ID in its name, so they come back if you reload or return later. Saving or Discard removes that copy from the browser. Signing out doesn't remove it, so on a shared computer save or discard your changes before you leave.
• Saved Resumes: Signed in, a resume is saved to your lazee.dev account when you press Save: its name, headline, contact line, sections and text, design settings (template, font, size, margins, spacing, paper size, color, and the name of a font you uploaded, never its file) and, once you match it to a job, that job's title, company and keywords. Your first draft is filled in on our servers from your lazee.dev profile (your name, contact details and links, skills, experience, projects, education, certifications and languages); editing a resume never changes your profile. Saved resumes aren't on your public profile and aren't used to fill job applications. On every plan the extension lists their names and edit dates when you switch its resume picker to Resume builder, and matching one in its ATS tab sends the extension its text. When you attach one, our servers build its PDF from the saved resume and send it to the extension, which puts it in that page's upload field. On the free plan, a Pro Pass spent on one is recorded with the resume's ID, when it was unlocked and until when, and whether the attach worked or the pass was refunded, so it stays unlocked for 30 days and refunds can be limited; these records are deleted with your account. Nothing is sent until you switch to the builder list. The extension keeps the list it was sent (names, edit dates and unlock dates, never the resumes themselves) in its own storage on your computer, so it shows at once next time, and deletes it when you sign out or switch accounts. Free accounts keep up to 100, Pro up to 1,000. You can delete them one by one or several at once in My resumes, and deleting your account deletes them all.
• Job Match: The job description you paste (or the job page the extension reads from a link, in your own browser) and your resume's text, headline, job titles and the years its dated jobs add up to go from the page to the extension on your device, which scores the match offline; none of it is sent to our servers for it. “Saved jobs” lists the jobs you bookmarked on the job board (title, company, location and link, from your account); the job you pick is read from its link by the extension, the same way. The job description and the last AI check stay in that browser tab (session storage) until the tab is closed. Tailoring changes only what you confirm in the dialog. The AI check (Pro, or a Pro Pass on Free) runs only when you tap its button and works like the extension's AI ATS rescore (below): the job description, the parts of your profile that bear on fit and this resume's text (with email addresses, phone numbers and links removed on our server) go to the AI you picked, through the extension. On lazee.dev AI they go through our servers to OpenRouter; with your own AI provider, our server only assembles the prompt and the extension sends it to your provider. Its result isn't saved to your account.
• AI Section Editor (Pro): When you ask the AI to edit a section, that section's text, your instruction, a summary of your lazee.dev profile (name, skills, jobs and their descriptions, projects, education and certifications) and, if “Use the job” is on, the job description are sent to the AI. On lazee.dev AI they go through our servers to a free model served through OpenRouter, which answers with the new section; we don't keep the request, only your new credit balance. On your own AI key the same content goes from the page through the extension, with your key, to the provider you picked. Nothing changes in your resume until you accept the result. The AI you picked is remembered in this browser.
• Importing a Resume: When you import a resume (Import, or dropping a PDF on the page), the PDF or the text you paste is read in your browser tab: the file isn't uploaded or stored, and the result replaces the open resume only when you press Load. Signed in, the “Uploaded” tab can also open a resume you already uploaded to your profile: its PDF comes from our storage to your tab and is read there the same way, with nothing new stored. It reaches our servers only if you then press Save, like any edit. “Fix with AI” (Pro) is the one exception: it sends the text read from your resume (up to 20,000 characters, including your contact details) and the import's first result to the AI. On lazee.dev AI they go through our servers to a free model served through OpenRouter, which answers with the corrected resume; we don't keep the request, only your new credit balance. On your own AI key the same content goes from the page through the extension, with your key, to the provider you picked.
• LaTeX Mode (Pro): The builder's LaTeX tab turns your resume into LaTeX code and compiles it into a PDF in your browser tab, with a TeX engine (pdfTeX) that runs on your device: your code and resume aren't sent anywhere to be compiled. The first time, your browser downloads the engine's files (about 17 MB, up to about 23 MB with every font) from our Cloudflare R2 storage and keeps them in its cache storage for next time; no other site is contacted. When you press Save, the compiled PDF is stored with your uploaded resumes (like a PDF you upload on your profile, so the extension and cold emails can attach it), together with its LaTeX code and the resume data it's in sync with. Deleting it in My resumes or on your profile deletes all three. Until you save, the code is kept only in your browser, in the same unsaved draft as the rest of the resume. An AI edit in the LaTeX tab (Pro) sends your instruction and the code it should change to the AI: the part you selected with up to 3,000 characters of the code around it, or, with nothing selected, the whole code (which includes your name and contact details); a “Fix with AI” also sends TeX's error message. On lazee.dev AI they go through our servers to a free model served through OpenRouter, which answers with the changed code; we don't keep the request, only your new credit balance. On your own AI key the same content goes from the page through the extension, with your key, to the provider you picked. The answer is test-compiled in your browser and goes into your code only when you accept it.

We use your stored profile information strictly to fulfill your requested actions:

• Form Autofill Automation: Mapping your career data (contact details, CTC, experience, education, links, job preferences) to detected input fields. Short questions such as “Do you require visa sponsorship?” are answered from your job preferences inside the extension, without any AI call.
• lazee.dev AI Answers: When you use credit-based lazee.dev AI, your request, the profile details it needs (including your job preferences, so screening questions about work authorization, visa sponsorship or relocation are answered correctly, and your current CTC and expected salary for pay questions) and, if you turned it on, the job description are sent to our servers and from there to an AI model served through OpenRouter. lazee.dev AI runs on openly available models, including free ones whose providers may log prompts or use them to improve their models under their own policies. We do not use your data to train any model. If you would rather no AI provider sees your data, use BYOK with a provider you trust, or a local model.
• AI ATS Rescore: Sends the job description with the parts of your profile that bear on fit: skills, job titles and dates, experience and project descriptions, degrees, certifications, languages, and job preferences (including where you can work without a visa and whether you need sponsorship). When a resume is picked in the ATS Match tab, the text read from that PDF is sent too, with email addresses, phone numbers and links removed first in the extension and again on our server; the PDF itself is not sent. With your own AI provider, our server only assembles this prompt and the extension sends it to your provider. Never your email, phone number, address or links.
• AI Polish of the Tailored Resume: When you tick “Also polish my tailored resume with AI” on an AI rescore, the draft of that resume goes with the rescore request: its headline, summary, skills line, each experience's company, role and bullets, each project's name, stack and bullets, and each education entry's school, degree and note. Your name, email, phone number and links are never part of it. With lazee.dev AI it is sent to our servers and from there to a model served through OpenRouter, like the rescore; with your own AI provider or a local model, the extension sends it to your provider. The rewritten text is kept in the extension on your device with the rescore result for that job, so reopening the job doesn't send or spend anything again; the PDF itself is never stored by the extension. If you then click “Save to profile” (Pro), the polished PDF is uploaded to your lazee.dev account and stored like any other resume you upload (see “Cloud Resume Delivery” below).
• Job Board Filters: “Use my preferences” on the job board turns your saved job preferences into filters. Your bookmarks and preferences are used only to show you your own results.
• Running the Service: Counting credits, granting referral rewards, preventing fraud and abuse, and keeping the platform secure. When you sign up, we compare your email address with existing accounts' so free credits go to one account per inbox. With an email link, we also check the address's domain against a public list of temporary-email services and look up its mail servers (a DNS lookup).
• No Data Selling: Your personal information is never sold, rented, or licensed to third-party advertisers, recruiters, or data brokers under any circumstances.

lazee.dev offers an optional public developer portfolio feature (lazee.dev/u/[username]):

• Opt-in Public Showcase: Claiming a username publishes a profile page anyone with the link can see. It shows what you have filled in of: your name, photo, target role, location, contact email, notice period, social links, skills, work experience, public education entries, projects, intro video, primary resume download, and gender, veteran and disability status. Your current CTC is shown only if you tick “Show on my public profile” under it in Professional Details (off by default). Leave a field empty to keep it off the page.
• Markdown Copy for AI Tools: The same profile is also available as plain text at lazee.dev/u/[username].md, for AI assistants that read Markdown. It shows exactly what the page shows, is never cached, so changes and removals apply right away, and individual profiles are not listed in our AI index files (llms.txt, llms-full.txt).
• Job Preferences: Your work setup, locations, relocation, roles, seniority, employment types, work authorization, visa sponsorship need, languages and certifications are shown too, unless you untick “Show on public profile” in the Job Preferences section. Autofill uses them either way.
• Never Public: Your phone number, expected CTC, custom AI notes, cover letter, saved answers, saved jobs and AI provider keys are never shown on public pages.
• Cloud Resume Delivery: Resume PDFs are hosted in secure Cloudflare R2 object storage. Authenticated download links and public portfolio downloads are generated using secure, time-limited presigned URLs.
• Resume Upload Limit: Each resume upload, a new resume or a replacement, counts toward a limit of 10 uploads per monthly credit period on Free and 100 on Pro, whether you upload on the profile page, from the extension or in the lazee.dev Agent. Deleting a resume doesn't count and doesn't give an upload back. To count them we keep the time of each upload in this period on your account; the count starts again when your monthly credits reset.
• Resume Copy in the Extension: The first time you attach a resume with the extension, it keeps a copy of that PDF in its own storage on your device, so it isn't downloaded again. The first time the ATS Match tab scores with a resume, it keeps that resume's text there too. The copy is never sent anywhere. Both are deleted when you log out or sign in with another account, and when the extension next syncs your profile after you delete that resume.

Advertising cookies come only from Google's ads on the pages listed below; nothing else on the site tracks you across sites. What we use:

• Sign-in Session: An essential cookie that keeps you signed in on lazee.dev and lets the extension pick up your session.
• Referral Code: When you open a referral link, the code is remembered in a cookie for up to 30 days so the invite is credited when you sign up.
• Preferences: Your light or dark theme is stored in your browser, along with a simple yes/no flag for whether you were signed in last time, so the header loads in the right shape. The flag holds no account details and is cleared when you sign out.
• Analytics & Security: Vercel Web Analytics counts page views in aggregate without cookies, and records a few actions the same way (for example a sign-up and whether it used Google or email, a click on an extension store link, starting checkout, or using an AI feature). Each one carries only coarse labels such as the plan, the feature or the email provider type (Gmail, iCloud, Outlook, Yahoo, Proton or other): never your name, email address, account ID or what you wrote. Cloudflare, which protects the site, processes IP addresses and may set short-lived security cookies to stop bots and abuse, and its Web Analytics counts page views and page load times in aggregate, also without cookies.
• Advertising: The job board list, blog posts, the About page, the feature pages (AI cover letter generator, AI job application answers, recruiter message generator, ATS resume checker, resume screener) and the description below the resume builder show ads from Google AdSense to visitors who are signed out or on the free plan, including Google's full-screen ads between pages and a banner at the bottom of the screen where Google places them. Pro members never see them, and no other page shows ads; the home page, your profile and the agent never load Google's ad code. On the resume builder, the ATS resume checker and the resume screener the ad code runs in the same page as the resumes you are working on: we never pass it a resume, and our ads sit in the description below the tool, never inside it. Google loads the ads straight into your browser and may use cookies or similar identifiers, your IP address and the page you are on to show, limit and measure them, and to personalize them where you allow it. In the EEA, UK and Switzerland, Google's consent message asks for your choice first. We send Google nothing from your account: no name, email, profile or resume. See how Google uses information from sites that use its services; you can turn off personalized ads in Google's Ad Settings.

• Public Job Listings: The job board at lazee.dev/careers lists job postings that companies publish on their own career pages. They describe roles and contain no candidate data, and browsing the board needs no account.
• Saved Jobs: Bookmarking a job needs an account. Your saved jobs are visible only to you, and a saved job is deleted automatically when the company takes the posting down.
• ATS Match from the Board: The “ATS match” button passes the posting's link to the lazee.dev extension in your own browser, which reads the job and scores it as described in “Job Descriptions, Job Links & ATS Match” above. Nothing extra is sent to our servers.
• Jobs API Customers: The same listings are sold as an API through RapidAPI, which handles API subscribers' accounts, keys and billing. We receive their requests through RapidAPI and keep only technical logs needed for security and abuse prevention.

We apply comprehensive technical safeguards across our platform and extension:

We partner with reputable infrastructure providers to deliver our services:

• Authentication: Google sign-in and NextAuth.js; sign-in link emails are sent through Google (Gmail).
• Cold Email Sending:the agent's cold emails go out through Google's Gmail SMTP server from the Gmail address you connect, under Google's terms and policies for your account.
• Hosting & Network: Vercel (web hosting and cookieless analytics) and Cloudflare (DNS, content delivery and security filtering).
• Advertising:Google AdSense serves the ads on the job board, blog, About, feature pages and the resume builder's description for signed-out and free-plan visitors, and shows its consent message in the EEA, UK and Switzerland (see Cookies & Analytics).
• Database & Storage: Supabase (managed PostgreSQL) and Cloudflare R2 (resumes, profile photos and project images).
• Feedback: Notion stores messages sent through the feedback form.
• Jobs API:RapidAPI manages API subscribers' accounts, keys and billing.
• Exchange Rates:Our server fetches the day's currency rates (European Central Bank reference rates, via Frankfurter) once a day for the ATS match's salary check, the job board's salary filter and pay shown in your currency. No user data is sent with that request. To show a job's pay in your currency, the job board and the agent use the currency of your expected salary (or current CTC) from your profile; the conversion happens on our server or in your browser and is never shown to anyone else.
• Billing & Payments:Dodo Payments processes subscription checkouts as Merchant of Record. lazee.dev does not store your credit card or banking details. From Dodo's subscription updates we keep your subscription's ID, plan (monthly or yearly), next renewal date (or the day Pro ends after you cancel) and whether it is set to cancel; your profile page shows the date. We use your account's email address to send subscription emails: a welcome email when Pro starts, a reminder 7 days before each renewal, and emails when it renews, is cancelled or resumed, ends, is paused, or a payment fails. These are part of the service, so they have no opt-out; we record which ones were sent so none goes twice. To check the renewal date before a reminder, our server reads the subscription from Dodo Payments.
• AI Model Providers:lazee.dev AI requests go through OpenRouter to the provider of the model in use, under OpenRouter's and that provider's policies. When using BYOK, your requests are governed directly by your agreement with your chosen AI provider.

You retain complete ownership of your personal information:

• Edit or Remove: Update your profile data and job preferences, delete resumes, or modify saved questions and saved jobs anytime on your profile page. Saved jobs that expire are removed from your list automatically. You can hide your job preferences from your public profile at any time.
• Purge BYOK Keys:Remove any configured AI provider key directly in your extension or web AI settings to instantly delete it from local device storage, and from your account and your other browsers if you save keys to your account. Turning off “Save my AI keys to my account” deletes every key saved to your account.
• Account Deletion: Request permanent deletion of your account, resumes, and associated records by contacting privacy support.
• Retention: We keep your data while your account exists. After a deletion request we remove your profile, resumes, saved answers and saved jobs, except records the law requires us or Dodo Payments to keep, such as payment history. Data in your browser (BYOK keys, cached job descriptions) is removed when you clear it or uninstall the extension. BYOK keys saved to your account are kept until you delete them, turn saving off or delete your account.