Bespoke is a browser extension developed by Roberto Tome (contact@robtome.com). It helps job seekers generate tailored CVs and cover letters by combining their saved profile with job descriptions extracted from the current web page, track applications through an interview pipeline, and prepare for individual interview rounds. Document generation, match scoring, and interview prep use an AI model provider that you configure and authenticate yourself.
This Privacy Policy explains what data the extension collects, how it is used, and the choices you have. By installing and using Bespoke you agree to these practices.
Bespoke has no server of its own. Everything below is stored
locally on your device using the browser's
chrome.storage.local API:
We do not collect browser history, general browsing behaviour, cookies, or any data beyond what you explicitly enter into or generate within the extension.
Your data is used exclusively for the following purposes:
Bespoke does not sell, rent, or share your data with any advertising networks, analytics providers, or unrelated third parties.
The only external services that may receive your data are the ones you configure:
Bespoke supports Ollama, OpenAI, Anthropic, Google Gemini, OpenRouter, DeepSeek, Mistral, or any custom OpenAI-compatible endpoint. You choose which provider(s) to enable and supply their API key (or, for Ollama, an endpoint URL). Your profile, the extracted job description, and — for interview prep — your relevant application data are sent to whichever provider and model you route each task to (scoring, drafting, or interview prep can each use a different provider). We have no control over, and no visibility into, how a third-party provider handles data you send it; refer to that provider's own privacy policy.
If you enable company research, the company name and related context may be sent to Perplexity, Tavily, Brave Search, or Exa — whichever you have configured — or, when no research provider is configured, the extension may instead fetch the company's own public website directly. Only the provider(s) you enable and authorise with your own API key are used.
If you enable backup, the data listed in Section 5 is uploaded to the private
drive.appdata folder of your Google account. This folder is not visible
to other users, other apps, or to us; only Bespoke can access it, using the
authorisation you grant.
Bespoke requests the https://www.googleapis.com/auth/drive.appdata OAuth
scope. This scope grants access only to a hidden application data folder in your
Google Drive; it does not provide access to files you have created or any other
part of your Drive.
When enabled, the following locally-stored data is included in the backup: your profile, saved applications and interview data (rounds, prep, debriefs), AI and research provider configuration (including API keys), model routing preferences, prompt templates, and generation tuning settings.
You will be shown Google's standard consent screen before any Drive access is granted. Authorisation is entirely optional — the extension is fully functional without it.
To revoke access at any time, visit Google Account → Security → Third-party access and remove Bespoke.
When you use "Generate CV for this job" or open the match dialog on a job listing page, the extension's content script reads text from that page (job title, company name, job description) to use as context for document generation and scoring. The content script is present on pages you visit so it can respond when you trigger it, but it only reads page content at that point — it does not run continuously or report pages you browse.
This data is held only in memory for the duration of the request and is discarded immediately afterwards, other than the fields you choose to save with an application record (which are then stored locally as described in Section 2). It is never sent to any service other than the AI provider you configured for that task.
Your data remains in chrome.storage.local until you explicitly delete it.
You can remove locally stored data from the extension's Settings → Storage screen.
If you have enabled Google Drive backup, disabling the integration or revoking Google's permission will stop future backups. To delete existing backup data, use the restore/delete controls in the extension's Backup & Sync settings.
Uninstalling the extension removes all data stored in chrome.storage.local.
Your data, including any API keys you enter, is stored in the browser's local storage mechanism, which is sandboxed to the extension and not accessible by websites or other extensions. No additional encryption is applied beyond what the browser provides natively.
Communications with AI and research providers use HTTPS, except for a self-hosted Ollama endpoint, where the protocol follows the endpoint URL you provide — we strongly recommend using HTTPS for any remote Ollama server.
Communications between the extension and Google Drive use HTTPS enforced by Google's APIs.
We may update this Privacy Policy from time to time. Any changes will be reflected on this page with an updated "Last updated" date. We encourage you to review this page periodically. Continued use of the extension after changes constitutes acceptance of the revised policy.
If you have questions or concerns about this Privacy Policy or the data practices of Bespoke, please contact:
Roberto Tome
contact@robtome.com