Propel

Privacy Policy

Last updated: October 10, 2026

Propel Job Agent (“Propel”) fills out job applications through the Propel Chrome extension, your Propel account, and this website. This policy explains what data they handle, where it goes, and the choices you have. Sections marked “Legacy” describe the earlier Mac app and Propel Bridge.

Propel Chrome extension

The standalone extension reads form labels, choices, surrounding page text, and current field values on pages you choose to work on. It uses information you provide, saved answers, and documents to complete the task. Your Propel sign-in session, local task records, and an upload queue are stored in Chrome. Saved information, documents, and task history are also synchronized to your account on Propel’s Supabase service. Offline changes wait on your device until synchronization succeeds.

Relevant page content, document text, saved-answer values, and supporting information may be sent through Propel’s authenticated model service to OpenAI or Jev for retrieval, drafting, and browser planning. When visual understanding is needed, a screenshot of the visible task tab may be sent to OpenAI. Screenshots may include personal information and values visible on the page. The document you select may also be attached to the employer’s form. Employer browser-session cookies and credentials remain in the browser; credential headers and secret fields are excluded from task transcripts.

Auto-submit is on by default. Turn it off in Settings to review each application and submit it yourself. Service providers may retain data under their own policies. Questions about your data: zachcilwa@gmail.com.

Extension permissions

The extension uses storage for your sign-in session and local task records; tabs and webNavigation to identify and follow the application tab and page changes; sidePanel to show application controls; tabGroups to organize job tabs; and offscreen to keep its local agent running. It uses scripting and HTTPS site access to read and fill the application pages you choose, including supported embedded forms on employer domains. The debugger permission lets Propel send trusted clicks and keystrokes, capture the visible application tab when visual planning is needed, and keep a job tab responsive while it works. Access to Propel's Supabase service supports sign-in, saved answers, plan checks, and requested AI planning. The extension does not need a desktop app or native messaging.

The short version

  • Your profile, original saved answers, document files and extracted text, task history, and readable model inputs and outputs are stored in your Propel account on Supabase, with local copies in Chrome.
  • To complete a task, Propel sends relevant page content and supporting saved information or document text to its AI providers. Visual requests may also include a screenshot.
  • Employer browser-session cookies and credentials stay in the browser.
  • We don’t sell your data, show you ads, or use your data to train AI models.
  • Propel never asks for your LinkedIn or Indeed password.

Legacy Mac app and Propel Bridge

If you use the earlier Mac app and Propel Bridge, this section describes that legacy setup. The standalone Chrome extension stores account data as described above and below.

The legacy Propel app keeps its files in a private folder on your Mac. That includes:

  • the résumé files you add;
  • your application history, including the answers Propel filled in and up to eight screenshots of each application;
  • logs of each run, and your settings;
  • your Propel sign-in session.

Job-site logins. Some employer sites need an account before you can apply. If you turn on automatic sign-in or account creation (both are off by default), Propel creates a login using your email and a generated password. These logins are encrypted with a key protected by your Mac’s Keychain and are never uploaded.

The legacy Propel Bridge. Propel Bridge connects Chrome to the Propel app on your computer and makes no network requests of its own. It can see the titles and addresses of your open tabs, and it reads and controls the tabs Propel works in. It stores only its connection state in Chrome.

What is stored in your Propel account

When you sign in, Propel stores the following on our servers, which run on Supabase:

  • Account: your email address, plus your name and photo if you sign in with Google.
  • Profile: contact details (name, email, phone, address), work authorization, sponsorship, availability, salary expectations, links, and the roles and locations you want.
  • Documents: original files you add, including résumés, are stored in private Supabase Storage. Extracted text, source locations, file versions, and document references are stored with your account records.
  • Saved information: your original answers, separately derived facts, corrections, conflicts, source references, reuse preferences, and a search index used to find relevant information. If you provide health, disability, accommodation, demographic, or other sensitive answers for an application, those answers may be included in this account data.
  • Tasks and application history: job/page details, status and outcome, pending questions, your task-specific answers and drafts, decisions, browser action receipts, and verification results.
  • Model transcripts: readable inputs sent to models and their returned outputs, kept with the task history. These can include page text, saved-answer values, and document excerpts. Credential fields, raw screenshot image bytes, and embedding vectors are omitted from the readable transcript.
  • Run diagnostics: signed-in runs upload operational records automatically when the service is available. They include account/run/task/event identifiers, site information, extension version, timings, outcome and reason codes, and step summaries and references. Summaries can include labels, file names, answer text, and excerpts of page or document content. Credential values are protected. These operational records are separate from the durable task history and model transcripts.
  • Plan and usage: your plan and how many applications you’ve used.
  • Bug reports you choose to send.

What is sent to AI models

Propel uses OpenAI and Jev through its authenticated Supabase model service to retrieve supporting information, draft answers under your writing settings, and plan browser actions. Requests can include:

  • relevant page text, form labels, choices and current values;
  • relevant profile facts, saved answers, task-specific answers, and document text or excerpts;
  • screenshots when visual planning is needed;
  • text used to create a search index for your saved information.

OpenAI Responses requests set response storage to false. That setting does not prevent all provider retention. OpenAI’s handling of API data is described in its data-controls documentation. Propel retains readable model inputs and returned outputs as account-owned task history on Supabase. Providers handle requests under their own applicable policies.

We don’t use your data to train AI models.

Legacy Mac app: Gmail (optional)

In the legacy Mac app, you can connect Gmail so Propel can match employer replies to your applications and read verification codes sent while you apply. Propel asks for read-only access. It reads the sender, subject and a short preview of hiring-related emails from the last 30 days onward, and it opens a message only to read a verification code. Its access tokens are stored encrypted. Stored email details are deleted after 180 days, and disconnecting Gmail revokes Propel’s access and deletes them.

Payments

Payments are handled by Stripe on its checkout page. Propel stores account email and Stripe customer, subscription, checkout and payment-reference records, plus plan status, purchase amounts and currency, and application credits to manage access and usage. The Chrome extension does not receive your full payment-card number.

This website

If you sign in on propeljobagent.com, a cookie keeps you signed in. We use Vercel Web Analytics to count page views; it doesn’t use cookies. The site is hosted by Vercel, which keeps standard server logs.

Campaign links such as /tiktok help us count visits associated with a shared link. We keep the fixed campaign label in the URL and this tab’s session storage for up to 30 minutes across navigation. This label is not a personal identifier and does not prove that a visitor came from TikTok.

If you join the extension waitlist, we store the email address you enter in Propel’s Supabase database, along with a fixed campaign source when your first signup comes through a tagged link. We also store a keyed digest of your network address and a daily request count to limit abusive signups. Joining does not create an account, grant access, or subscribe you to marketing emails. We do not send an email when you join.

Who we share data with

We don’t sell your data or share it for advertising. We use these service providers to run Propel:

  • Supabase for your account, sign-in and stored data;
  • OpenAI for the AI models, as described above;
  • Jev (Typesafe AI) for selected saved-information retrieval and browser-planning requests;
  • Stripe for payments;
  • Google if you sign in with Google or connect Gmail in the legacy Mac app;
  • Vercel to host this website and count page views;
  • The employer or application site receives the form values and documents that Propel fills or attaches on your behalf.
  • GitHub, where the legacy Mac app checks for updates (GitHub sees your IP address and app version).

How long we keep data

Durable saved information, documents, task history, model transcripts, and committed record revisions are not subject to the operational diagnostic retention limit. They remain in your account unless removed through the available deletion controls or account deletion. Operational run diagnostics have a 30-day retention policy. Local copies remain until removed from the browser or legacy app. Legacy Gmail email details are deleted after 180 days. We keep payment records as long as we need them for accounting and tax purposes.

Stopping reuse does not delete saved information or the original file. “Delete file” removes the original file from this device and queues its cloud deletion; it is shown as deleted from your account after synchronization is acknowledged. Historical task records, excerpts, and previous record revisions may still contain information drawn from that file. Removing the extension does not delete your cloud account data.

Your choices

  • Inspect and correct saved information, change where it may be reused, or stop using it under Saved information.
  • Stop using a document while retaining its original, or select Delete file to remove the stored original. Offline deletions wait to synchronize.
  • Pause or stop tasks and turn auto-submit off in Settings.
  • Remove the standalone Propel extension from chrome://extensions to stop its browser access.
  • For the legacy Mac app, leave automatic sign-in and account creation off, disconnect Gmail, or remove Propel Bridge and uninstall the Mac app.
  • Delete your Propel account from your account page. Local files remain until you remove them from your device.
  • To get a copy of the data in your Propel account, email us from your account’s address.

Security

Data travels over encrypted connections. Supabase account records and private document storage use owner-scoped access controls. Browser-session credentials stay in the browser; credential headers and secret fields are excluded from task transcripts. The legacy Mac app’s saved job-site logins and Gmail tokens use the protections described in its sections. No system is perfectly secure, so please tell us if you find a problem.

Changes and contact

If this policy changes, we’ll update this page and the date at the top. Questions or requests: zachcilwa@gmail.com.

← Back to Propel