Privacy

Privacy policy for Loopboy.

This policy describes what Loopboy collects, how it is used, and how data moves between the Chrome extension, the Loopboy web app, and the configured backend.

Last updated: April 3, 2026

What Loopboy collects

The product collects only the information needed to support account access, profile storage, and job application autofill.

Account and authentication data

Name, email address, and account identifiers.
Password credentials if you create a password-based account.
GitHub account information if you sign in with GitHub.

Profile and application data

Profile details you save in Profile Studio, including education, experience, reusable answers, and long-form context.
Visible form fields, job descriptions, page title, page URL, and other visible job-page content needed to generate fill plans.
Extension settings stored locally in Chrome, such as backend URL, extension token, toolbar preferences, and last-run status.

How the data is used

Loopboy uses collected data only to provide the autofill workflow and support related account features.

To authenticate users and secure access to saved profiles.
To store and return profile data that powers form autofill and generated answers.
To inspect the current job application page, match visible fields, and return a fill plan for that page.
To generate responses for open-ended application questions using the saved profile and the visible job posting context.
To preserve extension preferences locally on the user’s browser.

How data is shared

Loopboy does not sell personal data. Data is shared only when required to deliver the product’s single purpose.

The extension sends relevant page and form context to the backend URL configured by the user in order to request a fill plan.
The backend may send prompt data to Google Gemini to generate answers for unresolved or narrative application fields.
Profile and account data may be stored with infrastructure providers used to operate the service, such as hosting and database providers.
Data may also be disclosed if required by law, to investigate abuse, or to protect the service and its users.

Loopboy is intended for job-application assistance only. It is not designed to use collected data for advertising, data brokerage, or unrelated profiling.

Retention and user choices

Users control most of their product data directly through the app or browser.

Saved profile data remains in the account until the user updates it or requests deletion.
Extension settings stored in Chrome can be cleared by removing the extension or clearing extension storage in the browser.
If you want account or profile data removed from the backend, contact support using the methods listed on the support page.

Security

Loopboy is designed to keep secrets server-side and to transmit user data securely in production.

Extension tokens are stored locally in the user’s browser and are used to authenticate extension requests.
Gemini API access is performed from the backend, not directly from the extension.
Production deployments should use HTTPS and secure storage for credentials, database access, and API secrets.

Chrome Web Store limited-use disclosure

This section is intended to support Chrome Web Store review and user understanding.

Loopboy accesses visible job application fields, job posting content, page title, page URL, and related profile data only to provide its user-facing autofill features. Loopboy does not sell that data and does not use it for advertising or any unrelated purpose. Data is transferred only as necessary to operate the autofill workflow, including backend processing and AI-assisted answer generation.