Lentra — Privacy Policy

Effective date: May 8, 2026 Last updated: May 26, 2026

This policy explains what Lentra (“we,” “us”) collects, why, where it goes, and how to delete it. Lentra is the Chrome extension at getlentra.com, operated by Lentra LLC.

If you’d rather skim: we collect what’s needed to fill job applications and keep your profile synced across devices, we never sell or share your data with advertisers, we don’t use your data to train AI models, and you can delete everything from Settings → Account → Danger Zone in two clicks.

The summary above is for readability. The numbered sections below are the legally binding statement; if there’s any ambiguity, those sections control.

1. What Lentra is

Lentra is a browser extension that fills out online job applications using a profile you save once and an AI service for free-text questions (“Why are you interested in this role?”). You sign in with Google so your profile and resume sync across devices.

This policy covers data we collect through the extension, our backend, and the marketing site at getlentra.com.

2. Data we collect

We split data into three categories based on where it goes.

A. Stays on your device (never sent anywhere)

• Form values you’ve already typed yourself.
• Pages you visit that don’t trigger an autofill.
• The contents of any field that was filled by a local rule or directly from your profile (no AI involved).

B. Sent to our servers

When you sign in:

• Your Google email address and a unique account identifier to authenticate you and scope your data. We do not request or access your Google contacts, calendar, or any other Google data.
• Sign-in tokens so we can keep you signed in across sessions.

When you save profile data:

• Your profile — name, contact information, citizenship, work-authorization answers, optional equal-employment self-ID answers, professional links (LinkedIn, GitHub, portfolio, personal website), education, work experience, skills, projects, certifications, awards, custom Q&A, and your application defaults (compensation, notice period, etc.).
• Equal-employment self-ID answers (gender, race, veteran status, disability, sexual orientation) are voluntary. You can leave any of them blank, set them to “Decline to state,” or change them at any time. We use these values only to fill the corresponding fields on application forms when you trigger a fill — we do not use them for any internal decisioning, sharing, or analytics, and (per §2.C) they are never sent to any AI provider.
• Your resume file (PDF or DOCX) and the extracted text of it. The file is stored encrypted at rest, and the extracted text is used to inform AI answers about your background.

When you click Fill on a job application:

• An analytics row containing the page’s hostname, the detected applicant-tracking-system identifier, the count of fields filled and unfilled, and — when we can extract them — the role title, company name, and canonical URL of the posting. This powers the Recent Fills list and our rate limits.

We do not store the values you fill into form fields. We store counts, not contents.

When you use the extension (unless you opt out):

• Product-usage events — anonymous events such as which screens you open, which buttons you click, and errors that occur. Each event includes the extension version, the surface (popup, sidebar, settings), and a timestamp. These events do not contain field values, page content, browsing history, or any profile data. They are sent to PostHog (see §4) and used solely to understand how people use Lentra so we can fix bugs and improve the product. You can turn this off at any time in Settings → Preferences.

C. Sent to AI providers

When a field can’t be answered by a local rule or your profile, the extension sends one request per field to our backend, which forwards it to an AI service to draft an answer. Each request contains:

• The page URL (host + path).
• The field’s metadata — its label, placeholder, options, nearby text — so the model can write a sensible answer. We do not send the page’s full HTML.
• A redacted subset of your profile, intentionally chosen to give the model context for essay answers without leaking strict PII. High-level categories: your name, public profile links, education, work experience, skills, application defaults (compensation, work authorization, etc.), and any custom Q&A you’ve saved.
• The extracted text of your resume so the model can pull project specifics when answering essay questions.

We do not send to any AI provider:

• Your email address, phone number, full street address, or postal code.
• Your demographic self-ID answers (gender, race, veteran status, disability, sexual orientation).
• The raw resume file (only the extracted text).
• Anything from any other browser tab.

3. Why we collect it

• Sign-in identity — to authenticate you and scope your data.
• Profile + resume — so Lentra can fill applications without you re-entering the same information on every site.
• Per-fill analytics — to show you the Usage dashboard and enforce rate limits.
• Product-usage events — to understand how Lentra is used, diagnose bugs, and prioritize improvements.
• AI request payload — so the model can write coherent answers grounded in your actual background.

We do not use your data to train AI models. We do not sell it. We do not share it with advertisers.

4. Subprocessors

We use the following third parties to operate Lentra. Each receives only the data necessary for their role.

• Cloudflare, Inc. — runs our backend. Receives all extension requests for routing and processing. (Privacy)
• Supabase, Inc. — stores your profile, resume file, resume extracted text, and fills analytics. Encrypted in transit (TLS) and at rest. (Privacy)
• Google LLC — verifies your identity at sign-in via Google Sign-In. We use the OAuth scope openid email profile and request no additional Google data. (Policy)
• AI inference providers — receive the redacted prompt described in §2.C to draft answers to free-text questions. Lentra does not use your data to train AI models. Each AI provider has its own data-handling and retention terms, which we review when we select or change providers. We may change AI providers from time to time; the data categories sent (per §2.C) remain unchanged.
• PostHog, Inc. — receives anonymous product-usage events (screen views, button clicks, error reports, extension version). PostHog does not receive your profile, resume, field values, or browsing history. Data is hosted in the US. You can opt out at any time in Settings → Preferences. (Privacy)

We do not transfer data to any other third party for advertising or model training.

5. How long we keep it

• While your account is active — indefinitely. You can update or delete any field via Settings, or delete everything via Danger Zone.
• Once you delete your account — your profile, resume, fills history, and authentication record are removed from our live database within seconds. Provider-side backups containing your data are purged within 90 days. We do not retain any of your data — in any form, on any system — beyond 90 days after you delete your account, except where retention is required by law (for example, to respond to a subpoena that pre-dated your deletion).
• AI provider retention — varies by provider. AI providers may retain transient request logs per their own policies; we have no control over those logs.

6. Your rights

You can:

• See your data — Settings → any tab. Your profile and resume are visible there.
• Export your profile — Settings → Profile → Export. Returns a JSON file.
• Delete individual fields — clear the field in Settings; the change syncs.
• Delete your account and all data — Settings → Account → Danger Zone → Delete account. Two-step confirmation; once you confirm, server-side rows and locally-stored data are wiped immediately.

EU / UK (GDPR)

If you’re in the EU or UK, you have rights to access your data, correct inaccuracies, request erasure, restrict or object to processing, and request your data in a portable format. The Delete-account flow above satisfies the core erasure right; for any other request, email us (see §12). You also have the right to lodge a complaint with your country’s data-protection authority.

United States

Residents of California, Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, and Virginia have additional rights under their state privacy laws, including the right to access, correct, delete, or obtain a portable copy of personal data we hold about them, and the right to opt out of any sale or sharing of their personal data. We do not sell or share your data with third parties for advertising, so the opt-out right is automatically satisfied for all users.

How to exercise these rights

For account deletion, use the in-extension Danger Zone — that’s the fastest path. For any other request (access, correction, portability, complaint), email support@getlentra.com from the Google address on your Lentra account. We’ll verify your identity by sending a confirmation email to that address, and we’ll respond within 30 days.

If we decline a request, our reply will explain why and how to appeal — typically by replying to the same email thread with additional information. We’ll review the appeal within 60 days. If we still decline, you can escalate to your state attorney general (US) or data-protection authority (EU/UK).

7. Cookies and tracking

The extension does not set cookies. The marketing site at getlentra.com does not use advertising cookies.

The extension sends anonymous product-usage events to PostHog, a third-party analytics service, so we can understand how Lentra is used and fix bugs. These events contain only interaction data (screen views, button clicks, error counts, extension version). They never contain your profile data, field values, or browsing history. You can turn this off at any time in Settings → Preferences → “Usage analytics.” When you opt out, no further events are sent.

8. Security

• Sign-in tokens are stored in chrome.storage.local, accessible only to the Lentra extension on your device.
• Your resume and profile are encrypted in transit (TLS 1.2+) and at rest (AES-256).
• We do not log or store the values of form fields you fill.
• The extension’s permissions are limited to those required for autofill and listed at install time.

If you discover a security issue, please email us (§12) before disclosing publicly. We aim to respond within 72 hours.

9. Children

Lentra is not directed to children under 13 (under 16 in the EU/UK). We do not knowingly collect data from minors below that age. If you believe a minor has signed up, contact us and we’ll delete the account.

10. International transfers

If you sign up from outside the United States, your data is transferred to and processed in the US. We rely on standard contractual clauses with our processors where applicable.

11. Changes to this policy

If we make a material change (new data category, new subprocessor, change to retention), we’ll update the “Last updated” date at the top of this document and post a notice at getlentra.com/privacy. Continued use after a material change means you accept the updated policy. You can always delete your account if you don’t.

12. Contact

Questions, deletion requests, or concerns:

support@getlentra.com

We aim to respond within 5 business days.

Lentra LLC Wyoming, USA