Privacy, made explicit.

Scope

This policy describes how Kepler Hiring Exporter handles information when a user installs and operates the Chrome extension. The extension is intended for recruiters and hiring teams who are authorized to access the applicant information they capture.

The policy covers the extension and this static policy website. It does not replace the privacy policies of LinkedIn, Chrome, Firebase, or any other service a user may access separately.

Data handled

When the user explicitly starts a capture run, the extension may read and store information that is already visible in the authorized applicants page, including:

• Candidate names, headlines, locations, application status, and visible scores.
• Contact details shown by the recruiter interface, such as email addresses and phone numbers.
• Visible qualifications, screening questions and answers, and resume or profile links.
• Optional screenshots and scroll evidence when the user enables evidence capture.
• Run identifiers, checkpoints, progress counters, and diagnostic events needed for restart recovery.

The extension does not ask for or store passwords, authentication cookies, private messages, hidden fields, or data from unrelated websites.

How data is used

Captured information is used only to provide the extension’s single purpose: organizing visible applicant information for local hiring review and exporting it to an Excel workbook with audit evidence.

Optional Chrome built-in AI notes are disabled by default. If enabled, they are generated from redacted visible detail text and are stored separately from the deterministic capture. AI notes do not make hiring decisions and are not the source of truth.

The extension does not use applicant information for advertising, profiling unrelated to the hiring workflow, credit decisions, or sale of data.

Sharing and transfers

Kepler Hiring Exporter does not transmit captured applicant data to the publisher, an analytics provider, an advertising network, or another third party. It does not sell or rent applicant data.

The user may choose to share the exported workbook or screenshots with members of their hiring team. That sharing is initiated and controlled by the user outside the extension.

The policy website is a static page. Standard hosting infrastructure may process ordinary technical request data needed to deliver the page, but the extension does not send applicant records to this website.

Storage and retention

Extension records are stored locally in the browser’s IndexedDB and Chrome local storage. Excel files and optional evidence screenshots are saved to the user’s local Downloads folder.

The publisher does not control the user’s local retention period. Users should delete exports, screenshots, and extension data when the hiring process or their organization’s retention policy requires it.

Uninstalling the extension may remove its local storage, but downloaded exports and screenshots must be deleted separately.

Security

The extension uses the narrowest workflow intended for its feature: a user-initiated capture on the authorized applicants page, local persistence, and local export. It does not use stealth tooling, CAPTCHA bypasses, credential collection, or remote executable code.

Users remain responsible for securing their browser profile, device, Downloads folder, exported files, and access to the recruiter account.

Your choices

• Do not start a capture run if you do not want the visible data stored locally.
• Pause or stop a run at any time from the extension side panel.
• Disable optional screenshots and optional AI notes in the extension settings.
• Delete local records, downloaded workbooks, and screenshots from the browser and device.