Legal
Presr privacy policy
Effective October 3, 2026
Presr is a Chrome extension that reads a LinkedIn profile, and a résumé builder at getpresr.com/app that turns it, or a résumé you already have, into a résumé. Warner Labs LLC makes both. This policy says what Presr stores, what it sends anywhere, and how to delete it. Questions go to help@getpresr.com.
The short version.
- What Presr reads from LinkedIn, and everything you type into it, stays in your browser: in the extension if you have it, and in your browser’s storage for getpresr.com if you don’t.
- Text leaves your browser only when you use an AI feature, and only the text that feature needs. It goes to our server and on to Google’s Gemini, which writes the answer. We don’t keep the text. Google keeps it for up to 55 days, only to check for abuse, and doesn’t use it to train its models.
- Presr has no ads, no tracking and no analytics service, and we don’t sell your data.
What Presr keeps in your browser
With the extension installed, Presr stores these in Chrome’s storage for the extension, on your computer, and the builder on getpresr.com reads and saves them there directly, inside your browser. Without the extension, the builder keeps the same things in your browser’s own storage for getpresr.com (IndexedDB), on your computer. Either way, we can’t see any of it. Without the extension, clearing your browser’s data for getpresr.com deletes them, so the builder lets you download a backup.
| What | How long |
|---|---|
| Profiles you scan: each section Presr read, and the person’s name, headline, location and a link to their photo. Contact details come only from your own profile. | Until you close the browser. A finished scan is also kept for 24 hours, so restarting Chrome doesn’t lose it. |
| Résumés you haven’t saved | Deleted once you’ve closed the résumé’s tab and it has gone 7 days without an edit |
| Saved résumés and their folders | Until you delete them |
| Saved job postings, and — on Plus and Pro — what AI read out of each | Until you delete them |
| The last 20 profiles you scanned: each one’s LinkedIn handle and name, how many sections were read, whether it was your own, and when | Until newer scans push it out, or you remove Presr |
| Your Google sign-in, which contains your Google account ID and email address | Until it’s replaced, our server rejects it, or you remove Presr |
| On getpresr.com only: which Presr extension to talk to (its public ID), in the site’s local storage, and a random number for each builder tab, in that tab’s session storage | The extension’s ID until you clear the site’s data; the tab number until you close the tab |
A résumé or job posting you delete waits 30 days in Recently deleted, where you can restore it, and is then deleted for good.
The ATS check, which says whether applicant tracking systems can read your résumé, runs on your computer. Checking your résumé against a job posting uses AI, on Plus and Pro; what it sends is below.
Presr reads your clipboard only when you click “Paste from clipboard”, and writes to it only when you click a copy button. Résumés you export go wherever you save them.
What leaves your browser
Text you send to an AI feature
Presr sends text only when you use an AI feature, and only what that feature needs:
- Skill suggestions: the name of the list, the skills already in it and elsewhere on the résumé, your headline, and up to 5 job titles and 4 employers.
- Rewriting part of a résumé: the text being rewritten, its section, your headline, job titles and employers. If you’ve picked a job posting to tailor it to, also the posting’s title, company and up to 12 of its requirements.
- Enhancing your LinkedIn profile: the résumé text, the matching text on your profile, its section, your headline and your job titles.
- Reading a job posting (Plus and Pro): the posting’s title, company and text, once, when you attach it to a résumé or save it in the side panel.
- Checking your résumé against a job (Plus and Pro): what AI read out of the posting, and your résumé’s text as it reads on the page, with email addresses, phone numbers, web links and your name taken out. Only when you press “Check match”.
- Tailoring your résumé to a job: your bullets, a section at a time, with your headline, job titles and employers, and the posting’s title, company, requirements and what the check found missing, and the rest of your résumé’s skills, bullets, schools and certifications, so a rewrite can use something you wrote elsewhere. If your résumé lists coursework, also your schools’ degrees and fields of study and the courses you list.
- Importing a résumé you already have: the whole text of the PDF or Word file you chose. This is the one feature that sends a complete résumé, including your name and contact details, because reading it into sections is what it does. The file itself never leaves your computer — Presr reads the text out of it in your browser and sends only that — and it only happens when you pick a file.
Apart from importing a file, Presr never sends your email address, phone number, LinkedIn address or photo as part of a request. Your name is sent only if it’s in text you choose to rewrite or enhance. Checking your résumé against a job sends the rest of the résumé’s text, which can include a city.
The text goes to our server, which runs on Cloudflare. The server checks that you’re signed in, counts the request, sends the text to Google’s Gemini API and returns the answer. It doesn’t keep the text or the answer.
Google’s Gemini API writes the answer. Google doesn’t use it to improve its products. It keeps requests for 55 days, only to detect abuse and to meet legal requirements. The request comes from our server, so Gemini doesn’t see your IP address or your Google account.
Signing in with Google
The first time you use an AI feature, Google asks you to sign in to Presr. Google then gives Presr a sign-in token holding your Google account ID and email address. Presr keeps it in your browser and sends it with each AI request. With the extension, the sign-in runs in the extension, and the website uses that same sign-in, so signing in or out on either does both. Without it, the website opens Google’s sign-in in a pop-up window, and keeps the token in your browser’s storage for getpresr.com. Our server keeps your account ID and email address in a list of accounts, with the dates you first and last used it and your plan, so we can find your account when you write to us and change your plan if needed.
Request counts
To limit how much each account can use, our server counts requests per Google account ID: per day, kept for 48 hours, and per minute, kept for 2 minutes.
Counting how many people get how far
Presr counts how many people get how far: how many times it was installed, how many of those installs ever finished a scan, exported a résumé, signed in or upgraded, and — as running daily totals — how many scans, exports and builders were opened, and how many scans failed and on which section.
What gets sent is the name of the thing that happened and nothing else — not your account, not a sign-in token, not an ID of any kind, not whose profile you scanned or what you exported. The one extra detail is which résumé section a failed scan gave up on, from a fixed list of section names, so we can tell when LinkedIn has changed and broken it.
Our server keeps totals per day and cannot tell one install from another, or a new visitor from a returning one. If you pay for Presr, we also count how many subscriptions were used in a given month — a single number, not a list, and never for free users. There is no analytics service involved and nothing that follows you.
Error logs
When a request fails, our server writes a line saying what went wrong, such as an expired sign-in or an error from Gemini. These lines never contain your text, your account ID or your email address. Cloudflare keeps them for up to 7 days. We don’t keep a record of each request.
Cloudflare
Every request to our server passes through Cloudflare, which sees your IP address in order to deliver it. We don’t store your IP address.
Presr reads the LinkedIn pages you open, and sends LinkedIn nothing. When you sync a section, Presr opens that section’s full list in your tab, as an ordinary page load under your own LinkedIn account. Profile photos and company logos load from LinkedIn’s servers, so LinkedIn sees those requests.
Other people’s profiles
Presr can read anyone’s public profile, not only yours. It keeps it the same way it keeps yours, only in your browser: the scan until you close the browser (24 hours if the scan finished), and one line in your list of the last 20 profiles.
Presr does not read another person’s contact details — not their email address, not their phone number, and not the address on their contact card. It does not open that card at all, and the panel tells you so while it scans. The one thing it does keep is the public address of the profile page itself, which is the page you are already looking at.
Their information leaves your browser only if you use an AI feature on text taken from their profile.
What we don’t do
- Presr has no ads, crash reports or tracking, and uses no analytics service. The extension loads no code from the internet, and the builder’s code comes only from getpresr.com. The only thing it counts is described above, and it cannot be tied to you.
- We don’t sell your data. We share it only with the companies below, and only to run Presr’s features.
- We don’t use your data for anything except Presr’s features, and never to judge creditworthiness or for lending.
- Presr sets no cookies, in the extension or on getpresr.com. It doesn’t track you, so there’s nothing for a browser’s “Do Not Track” signal to turn off.
Paying for Presr
Presr has three plans: a free one, and two paid ones you sign in with Google to buy. If you upgrade, Presr opens a checkout run by Polar, in a new tab — we never see or store your card details, only Polar does. Polar is the merchant of record, which means Polar is the seller for that purchase.
We don’t send Polar your email address. All we send is which plan you’re buying and an id for your account. Polar asks you for an email itself, at its own checkout; whatever you give it there is Polar’s record, not ours.
Once you subscribe, Polar tells our server which plan you’re on, so it knows what to allow. Our server keeps your plan, a Polar account id and a subscription id, with your subscription’s status — never a card number — in the same account record as your email address, until you ask us to delete it (see below).
To manage or cancel a subscription, open “Manage billing” on Presr’s account page, getpresr.com/app/account (the plan badge in the side panel opens it too). “Manage billing” is run by Polar.
Companies that handle data for us
- Cloudflare, Inc. runs our server and this website, and stores the request counts and your plan.
- Google LLC runs the Gemini API and Google sign-in.
- Polar Software Inc. runs checkout and billing for the paid plans, and is the merchant of record — the seller — for them.
Deleting your data
- Everything: remove Presr from Chrome. That deletes everything Presr stored in your browser. If you’ve used the builder without the extension, also clear your browser’s data for getpresr.com.
- One résumé or job posting: delete it from its ⋯ menu in the side panel, or a résumé from Your résumés at getpresr.com/app. It waits in Recently deleted for 30 days. Delete it there, or empty Recently deleted, to delete it at once.
- Your Google sign-in: open Presr’s account page, getpresr.com/app/account (or the plan badge, top right of the side panel), and choose “Sign out”. This removes the sign-in from your browser; it doesn’t cancel a subscription — do that from “Manage billing” first if you want both.
- Your account and plan record: email help@getpresr.com to have your account ID, email address and plan deleted from our server. Cancel any subscription first.
- Request counts delete themselves within 48 hours.
We hold no other data about you. If you have a question about your data, email help@getpresr.com.
Children
Presr is for people 18 and older. Don’t use it if you’re under 18. We don’t knowingly collect information from anyone under 18.
Where Presr is offered
Presr is offered in the United States and most other countries. It isn’t offered in the European Union, Iceland, Liechtenstein, Norway, the United Kingdom or Switzerland: the Chrome Web Store doesn’t list it there, and this policy is written for the places where it is.
Google API data
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
This website
getpresr.com sets no cookies and runs no analytics. Its pages load nothing from other companies’ servers, except that a résumé built from LinkedIn shows the profile photo and company logos from LinkedIn’s servers in the builder. Cloudflare, which hosts the site, sees your IP address in order to deliver the page.
The résumé builder and the account page at getpresr.com/app keep your résumés where “What Presr keeps in your browser” says: in the extension, or in your browser’s storage for this site. Nothing you build there is sent to our server, except the text you send to an AI feature.
Changes
If this policy changes, we’ll post the new version here and change the date at the top.
Contact
Warner Labs LLC
8735 Dunwoody Place, Ste R
Atlanta, GA 30350, USA
help@getpresr.com
LinkedIn is a trademark of LinkedIn Corporation. Presr is not affiliated with, endorsed by or sponsored by LinkedIn.