1. What this covers
This policy explains what Second Reader collects, what we do with it, who else touches it, and how you get it back or get it deleted. It covers the Second Reader website, web app, mobile app, and browser extension.
Second Reader is operated by Losee Productions, LLC, a California limited liability company. Contact: info@secondreader.co
The short version: we hold your job-search material so we can build documents for you. We do not sell it, we do not advertise against it, we do not train AI models on it, and we delete it when you ask.
2. What we collect
Account. Your name, email address, and a password hashed by our authentication provider. We never see your password.
Résumé. The PDF you upload and the text extracted from it. Stored in private cloud storage that is not publicly reachable.
Profile. Your full name, headline, phone number, street address, city, state, ZIP, country, LinkedIn URL, pronouns, work authorization and screening answers, years of experience, salary expectations, personal angles, and conditional experience blocks you write.
Voluntary self-identification. Gender, race, ethnicity, veteran status, and disability status. See section 3.
Job and package data. Postings you paste or open, the documents generated for you, integrity-check results, ATS scores, saved jobs, and the applications you log.
Billing. Your plan, credit balance, and Stripe customer and subscription identifiers. We never receive or store your card number — Stripe handles that.
Extension pairing. A device token that links a browser to your account, plus the posting URL and the job title and company the extension detected on the page. See section 9.
Form-field maps. When the extension meets an application form we have not seen before, we store the shape of that form: the field labels, types, and options, and the site's host name. See section 9.
Server logs. Standard request logs from our hosting: IP address, timestamp, path, user agent, error traces.
We do not collect your browsing history, your contacts, your location beyond what you type into your profile, or biometric data.
3. Voluntary self-identification and other sensitive fields
Gender, race, ethnicity, veteran status, and disability status are optional. Every field includes a decline-to-answer option, and leaving them blank costs you nothing.
They are sensitive personal information, so we treat them narrowly:
- You consent by entering them. Typing or selecting a value is the consent; we ask for nothing else and infer nothing you did not enter.
- They are used for one thing: filling the voluntary EEO questions on an application form you chose to fill, on your click.
- They are never sent to the AI model. They are not part of the material we send Anthropic to write your résumé, cover letter, or any other document. They are never used to score you, never used for advertising or profiling, and never sold or shared for anyone else's purposes.
- You can change or delete them at any time on your profile page, or ask us to delete them.
Pronouns. Pronouns are optional and we handle them the same narrow way. They are never sent to the AI model that writes your documents. They are filled into an application form only when that form asks for pronouns and only on your click, and they are left out of every form that does not ask.
Once you submit an application, the employer holds everything you sent it, including any self-identification or pronoun answers. From that point the employer is an independent recipient acting on its own account, under its own policy. We have no control over it and cannot retrieve or correct what you sent.
4. How we use your information
We use it to run your account, generate your documents, fill forms you ask us to fill, track applications you log, take payment, send account and invitation email, keep the Service secure, debug failures, build the shared form-field maps described in section 9, and meet legal obligations. That is the whole list.
We do not use it for advertising, for building a profile of you, or for training AI models — ours or anyone else's.
5. AI generation
To generate a package we send Anthropic (Claude):
- your résumé: the extracted text, or the résumé PDF itself when the text extraction falls short, because a scanned or image-heavy PDF cannot be read any other way;
- the parts of your profile the writer needs: your name, and the personal angles and conditional experience blocks you wrote. Your contact details reach Anthropic only where they appear in the résumé itself;
- the job description, title, company, and location.
When you give us a link to a posting instead of pasting the text, we fetch that page and send the text of the fetched page to Anthropic so the posting can be located inside it. That page text is whatever the page contains, including any navigation and boilerplate around the posting.
We do not retrieve pages from LinkedIn, Indeed, Glassdoor, or ZipRecruiter. Give us a link to one of those and our servers make no request to it at all. Postings on those sites are read by the browser extension, inside your own browser, on a page you opened yourself; the text it read is what reaches us. Without the extension, paste the posting text instead.
For the extension's field mapper we send Anthropic the labels, types, and options of the fields on the page, never the values you or the extension entered.
We do not send your self-identification data, your pronouns, your billing details, or your password to Anthropic.
Anthropic processes this to return the generated document and, under our commercial API terms, does not use it to train models. It does retain inputs and outputs for a limited period under those terms, for abuse monitoring and legal compliance. See Anthropic's commercial terms.
6. Who processes your data
We use a small set of service providers. They process data on our instructions only:
| Provider | What it does | Data it sees |
|---|---|---|
| Supabase | Database, authentication, file storage, transactional email | Account, profile, résumé, packages, applications; auth and invitation email |
| Vercel | Website and app hosting | Requests and server logs |
| Anthropic | AI document generation, posting extraction, field mapping | Résumé text or PDF, profile fields listed in section 5, job description, fetched page text, field labels |
| Stripe | Payments and billing portal | Name, email, payment details you give Stripe directly |
| Jina AI | Renders a posting page when you paste a link, so we can read it — never for LinkedIn, Indeed, Glassdoor, or ZipRecruiter | The posting URL you pasted |
| Adzuna | Job search | Your keyword, location, and country |
| Remotive | Job search (remote roles) | Your keyword |
| Jobicy | Job search (remote roles) | Your keyword |
| USAJOBS | Job search (US federal roles) | Your keyword and location |
This list changes as the Service changes. The "Last updated" date at the top of this page is how we give you notice of a change to it, so check the date if the list matters to you.
We share data outside this list only when you tell us to, when a law or valid legal process requires it, to protect someone's safety or our legal rights, or to a buyer as part of a sale of the business — in which case this policy continues to apply until we give you notice of a change.
An employer you apply to is not on this list and is not our processor. When you submit an application, that employer receives your material as an independent recipient and handles it under its own policy.
7. What we do not do
- We do not sell or share your personal information, in the ordinary sense or as "sell" and "share" are defined by California law.
- No advertising or ad tracking. No ad networks, no pixels, no third-party trackers.
- No analytics products. We run no analytics or session-recording service. What we know about usage comes from ordinary server logs.
8. Cookies
We set session cookies for authentication only — they keep you signed in and protect the sign-in flow. There are no advertising, analytics, or third-party tracking cookies, so there is nothing to opt out of and no consent banner. Clearing them signs you out.
9. The browser extension
The extension is deliberately narrow. This is what leaves the page, and only at these moments:
- On a job page: the posting URL, plus the job title and company the extension read from the page, sent to Second Reader to check whether you already have a package for it. Nothing is generated or filled by this check.
- When you click Build package or Log applied: the posting URL and the title, company, location, and description text the extension read from the page, so the package can be generated or the application recorded against that posting. On LinkedIn, Indeed, Glassdoor, and ZipRecruiter this is the only way a posting reaches us — our servers never retrieve pages from those sites — so the text the extension read in your browser is what the package is built from.
- When you click Prefill: the labels, types, and options of the form's fields, sent to our field mapper so it can decide which profile answer belongs in which field. Values are never sent — not the ones you typed, and not the ones the extension filled.
- Never: passwords, Social Security numbers, government IDs, and card or bank numbers. Those fields are detected, skipped, and counted for the review panel. Detection is careful but not perfect, which is why the review panel tells you how many fields it left alone.
What it looks at, and what it sends. The detection script runs on every page you open, in every frame, because employers host application forms on any domain and often inside an iframe. It inspects each page entirely inside your browser to decide whether it is a job page. Nothing about a page is transmitted unless it detects a posting and one of the moments above applies. It does not collect your browsing history, does not fill anything on page load, does not overwrite an answer you already typed, and never submits an application.
Documents. Your résumé and cover letter are attached only after you confirm, by host name, on a site we do not already recognize as an application form. On LinkedIn and Indeed you confirm every time, the extension fills only inside an application dialog you opened yourself, and it never advances a step.
Pairing and device tokens. A device token links the browser to your account. It is minted on our own connect page and held by the extension's background worker. Plainly: the token does not expire on its own, and there is no screen yet that lists your connected devices or revokes one. A token is revoked when you reconnect or disconnect from that browser. If you lose a device, email us and we will revoke its token for you.
Field maps. The shape of an application form we have not seen before, meaning the field labels, types, options, and the site's host, is stored as a reusable map so the next person meeting that form does not need another model call. These maps are kept indefinitely and are shared across all users. They contain no answers, no values, and nothing that identifies you: a map records that a field labeled "Preferred first name" means the first-name key, not what your first name is.
Permissions. `storage` (the token and the per-tab posting cache), `tabs` (which tab the popup is acting on), `webNavigation` (finding the frame that holds a form embedded in an iframe — this carries Chrome's "read your browsing history" warning, and we do not read your history), and `downloads` (saving your own package files on your click).
Google APIs. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
10. The mobile app
The in-app apply view follows the same rules as the extension: it fills on your tap, never submits, and skips credential and payment fields. Subscriptions are sold on our website, not in the app.
11. Coach and client data
If a coach or agency uses Second Reader with you as their client, the coach decides what to upload and why — under privacy law the coach is the controller of that material and Second Reader is their processor. The coach is responsible for having your permission and a lawful basis to upload your résumé and details.
Coaches can keep private notes. A coach may write working notes about a client inside Second Reader. Those notes are the coach's record and a client cannot see them in the product. If you are a client and want to know what your coach holds about you, ask your coach, or email us and we will handle it as a data request and route it to the coach as the controller.
Coaches confirm they have your permission. A coach cannot add you as a client without ticking a box that says they have your permission to upload your résumé and generate documents for you. We record when they ticked it.
A coach can delete you. Archiving takes you off the roster; deleting removes your client record, the résumé the coach uploaded, and your contact details for good. Packages already generated stay on the practice's own books with your client record removed from them.
We are the controller for the account we hold in your own name. If you accept a coach's invitation and link your account, that linking is your consent; packages generated for you stay visible to both of you. Archiving you removes you from the coach's roster but does not delete packages. You can delete your own account yourself at any time (section 13), and we will tell the coach.
12. Where your data is held
Our database, storage, and hosting are in the United States. If you use Second Reader from outside the US, your information is transferred to and processed in the US, which may have different privacy protections than your country. Where a transfer mechanism is legally required, we rely on our providers' standard contractual clauses.
13. How long we keep it, and deletion
| What | How long |
|---|---|
| Profile, résumé, packages, logged applications | The life of your account, then removed when you ask us to delete |
| Extension and mobile device tokens | Until revoked; a token has no expiry of its own |
| Form-field maps | Indefinitely. They hold no personal data, so deleting your account does not remove them |
| Server logs | About 30 days, then discarded |
| Stripe billing and tax records | As long as tax and accounting law requires, after your account is closed |
| Coach client rows and coach notes | Until the coach deletes the client, or the organization closes its account |
| Data held by Anthropic | Anthropic's own limited retention period under its commercial terms, which we do not control |
Backups age out on their normal cycle after a deletion.
Deleting your account. Open your profile page in the web app, or the profile tab in the mobile app, and use Delete account. You type DELETE to confirm. We remove your profile, uploaded résumés, generated packages, saved jobs, logged applications, and any extension or mobile device tokens, then close the login. An active subscription is cancelled at the end of the period you have already paid for. We keep the minimum billing and tax records the law requires. If you would rather we did it, email info@secondreader.co from your account address and we will.
Getting a copy. Use Export my data on the same page. You get a JSON file with your profile, your résumé text, every document we generated, your saved jobs, your logged applications, and — if you are a coach — your client roster. It carries no device tokens and no payment details. Email info@secondreader.co if you would rather we sent it.
Self-service is immediate. An emailed request we answer within 30 days.
14. Security
- Everything travels over HTTPS; data is encrypted in transit and encrypted at rest by our providers.
- Row-level security policies in the database mean a signed-in user's queries can only reach their own rows, and a coach's only their organization's.
- Résumés live in a private storage bucket with no public URL. Server-side keys with elevated access are held only on the server and never sent to a browser, the extension, or the app.
- The extension's device token is scoped to one browser and revoked when you reconnect or disconnect.
No system is perfectly secure, and we cannot guarantee absolute security.
15. If there is a breach
If personal information is exposed in a way that creates a real risk to you, we will notify affected users by email without undue delay, and regulators where the law requires it, describing what happened, what was involved, and what to do about it.
Where the GDPR or UK GDPR applies, we notify the relevant supervisory authority within 72 hours of becoming aware of the breach, and affected people without undue delay where the risk to them is high. Where we act as a coach's processor, we notify the coach as controller without undue delay so the coach can meet its own deadlines.
16. Your California privacy rights
California residents have rights under the CCPA/CPRA.
Categories we collect: identifiers (name, email, IP); customer records (contact details, résumé); protected classification characteristics (the optional self-identification in section 3); commercial information (plan, purchases); internet activity limited to our own service (server logs); professional or employment information (your work history and job search); inferences we generate as job-fit output for you. Sources: you, and Stripe for billing status. Purposes: section 4. Disclosures for a business purpose: the processors in section 6.
We do not sell or share personal information, and we have not in the past 12 months. We do not use or disclose sensitive personal information for any purpose beyond what section 3 describes, so no "Limit the Use of My Sensitive Personal Information" link is required.
Your rights: know what we collect, access a copy, correct it, delete it, and not be discriminated against for exercising any of these. Access and deletion are self-service in the app (section 13) and take effect immediately. You can also exercise them by emailing info@secondreader.co from your account address; we verify by matching that address and may ask one confirming question. An authorized agent may act for you with written permission. We respond within 45 days and will tell you if we need 45 more.
17. Other US state privacy rights
If you live in Virginia, Colorado, Connecticut, Texas, Oregon, or another state with a comprehensive privacy law, you have broadly the same rights: access, correction, deletion, a portable copy, and an appeal if we refuse. Email info@secondreader.co and we will answer within the deadline your state sets, and tell you how to appeal if we say no.
Three things worth saying plainly for those states:
- Sensitive data is collected only with your opt-in consent. The self-identification fields in section 3 are blank until you fill them in on the profile form, and filling them in is the consent.
- We do not sell personal data, do not share it for targeted advertising, and do not profile you in a way that produces legal or similarly significant effects. There is nothing here to opt out of.
- We honor the Global Privacy Control signal where it is technically possible for us to act on it. Because we run no advertising and no sale or share, a GPC signal has nothing to switch off on our site.
18. Rights outside the US
If you are in the UK, EEA, or a place with comparable law, you may request access, correction, deletion, restriction, portability, and objection to processing, and you may withdraw consent for the self-identification data at any time. Our legal bases are: performing our contract with you (running the Service), your consent (self-identification data), and our legitimate interests (security, fraud prevention, debugging). Email info@secondreader.co. You may also complain to your local data protection authority.
19. Children
The Service is for people 18 and over. We do not knowingly collect information from anyone under 18, and we do not knowingly sell or share the data of anyone under 16. If we learn that we hold information from someone under 18, we delete the account and its data. If you believe a minor has given us information, email info@secondreader.co and we will delete it.
20. Changes to this policy
We will post any update here with a new "Last updated" date, and email you before a material change takes effect.
21. Contact
info@secondreader.co — privacy questions and data requests. Deletion and export are self-service in the app; email us if you would rather we handled either one.