Open Source Privacy Policy

Three different things share the name ProposalLift, and this policy applies to them differently. Reading it is much easier once they are apart:

The operator of each instance chooses and controls the infrastructure that runs it. So if you connect the extension to an instance operated by somebody else, that operator, not ProposalLift, is responsible for the data you put into it, and this policy does not describe their practices. Installing the extension by itself creates no relationship with ProposalLift and sends ProposalLift nothing.

Every feature follows the same path, and each hop is something you initiated:

The boundary that matters for the extension is between steps 2 and 3. The extension itself sends network requests only to the ProposalLift server address you configured. That instance may then communicate with the third-party services described in section 8 in order to do what you asked.

Everything below is stored in the database of the instance you signed up on, owned by your account, and readable only by you. It exists because you entered it or asked the app to create it.

Upwork job listings are not stored. The job feed is fetched live from Upwork each time you open it and is never written to the database, in keeping with Upwork's terms on caching their data. Whether you have applied to a job comes from Upwork's own records.

• No analytics or telemetry. There is no Google Analytics, no Sentry, no session recording, no heatmaps, and no product analytics anywhere in this codebase.
• No advertising or tracking. No advertising identifiers, no cross-site tracking, no fingerprinting, and no third-party marketing pixels.
• No payment data. This build has no billing, no plans, and no payment processing, so there is nothing to collect.
• No browsing history. The extension reads only the Upwork apply page you are working on, when you act.

On sharing, the precise position is this: personal information is never sold or rented, and it is never shared with third parties for their own independent advertising or commercial purposes. It is transmitted to service providers only where doing so is necessary to deliver a feature you asked for (sending a prompt to your AI provider, fetching jobs from Upwork, delivering a verification email), as described in section 8.

Your information is used only to run the features you asked for:

• To authenticate you and keep you signed in.
• To fetch job listings from Upwork on your behalf, using the credentials you connected.
• To assemble a proposal (the job, your chosen persona, the portfolio projects most similar to that job, a hook, and any template or knowledge-base notes) and send it to the AI model you selected.
• To notify your configured webhook when a saved filter matches a new job, if you set that up.
• To send transactional email: address verification, password reset, and job alerts. No marketing email is sent.
• To keep the service secure and to enforce rate limits.

You are not profiled, no automated decision with legal effect is made about you, and your content is not used to train any AI model belonging to ProposalLift.

This build has no shared AI key. Generation, job qualification, rewriting, and portfolio embedding all run on the OpenAI or Anthropic key you save in Settings, and nothing works until you provide one.

The path is always the same:

The content sent for generation (the job text, your persona, the matched portfolio projects, your hook, template, and knowledge-base notes) is transmitted by the instance directly to that provider under your own account, and their privacy policy and data-retention terms govern what happens to it. Review OpenAI's policy or Anthropic's policy for whichever you use.

Your key is encrypted at rest, is never sent to the browser, and is never given to the Chrome extension. When the extension asks what it may offer you, the instance answers with the list of models you have configured and a yes-or-no on whether a key exists, never the key itself.

Because this build is self-hosted, the providers behind an instance are chosen by whoever operates it, and an independently run instance may use entirely different ones. The list below is the default set the open-source build is wired for. Each is used for one job and nothing else.

The web app sets cookies that are strictly necessary for authentication: they keep you signed in and protect against cross-site request forgery. There are no advertising, analytics, or third-party tracking cookies, which is why you are not asked for consent to any.

The app also uses your browser's sessionStorage to cache AI qualification verdicts for the current tab, so that re-opening a feed does not repeat work you have already paid your AI provider for. It is cleared when you close the tab. The extension's own local storage is described in section 3.

• Every row in the database is owned by exactly one user and isolated by Postgres row-level security, so one account cannot read another's data even if application code is at fault.
• Upwork credentials and AI API keys are encrypted at rest, each under a separate, independently rotatable key.
• The extension refuses to store a server address that is not https, other than localhost, so tokens do not travel unencrypted.
• Extension sign-in uses a one-time code that expires after 120 seconds, requires an explicit click on a consent screen, and is bound by exact match to the extension that requested it.
• A session is tied to the server that issued it and is discarded rather than reused if the extension is pointed somewhere else.

No system is perfectly secure, and absolute security cannot be guaranteed. If you believe you have found a vulnerability, please report it to admin@proposallift.com rather than disclosing it publicly.

Your content is kept until you delete it or close your account. Deleting a persona, portfolio project, proposal, template, hook, or filter removes it immediately.

You can disconnect Upwork or remove your AI key at any time in Settings, which erases those credentials. Removing the extension from Chrome erases everything it held locally.

You can delete your account yourself, in Settings, with no request and no approval. It asks you to type your own email address to confirm, then removes the account immediately: there is no grace period, no waiting list, and nothing is archived.

Everything belonging to the account goes in the same operation, including records you never created by hand: your profile and settings, saved filters, personas, portfolio projects and their embeddings, proposals, templates, hooks, webhook configurations, their delivery logs, and your Upwork API usage counters. Deletion is irreversible.

Depending on where you live, in particular under the GDPR in the UK and EEA, and the CCPA/CPRA in California, you may have the right to access the personal information held about you, correct it, delete it, obtain a portable copy, object to or restrict certain processing, and withdraw consent where processing rests on it.

Most of these you can exercise yourself, without asking anyone: nearly everything held about you is visible and editable in the app, and erasure is a button in Settings rather than a request (see section 11). For anything else, email admin@proposallift.com and ProposalLift will respond within 30 days. You will not be treated differently for exercising a right. If you are in the UK or EEA and are unsatisfied with the response, you may complain to your local supervisory authority.

Where the GDPR applies, the lawful bases are performance of a contract with you (running the service you signed up for), legitimate interests (keeping the service secure and working), and consent where you have given it.

ProposalLift is a tool for professional freelancers and is not directed at children. Personal information is not knowingly collected from anyone under 16. If you believe a child has provided information, email admin@proposallift.com and it will be deleted.

The providers in section 8 may process data in countries other than your own, including the United States. Where personal information is transferred out of the UK or EEA, it is protected by the transfer mechanisms those providers maintain, such as the European Commission's standard contractual clauses.

This policy may be updated as the software changes. The date at the top always reflects the current version, and because ProposalLift is open source, the full history of this page is public in the project's repository. If a change materially affects how your data is handled, you will be told by email or in the app before it takes effect.

Questions about this policy, or about the data held on an instance operated by ProposalLift, go to:

If you use an instance operated by someone else, contact that operator instead. ProposalLift has no access to their data.