Skillo - Privacy Policy

Last updated 1 August 2026

Skillo has no servers. It collects nothing, transmits nothing to its developer, and contains no analytics or tracking of any kind. Everything it stores stays in your own browser, and the only place your data is ever sent is the AI provider you choose and configure yourself.

What Skillo stores, and where

Data	Where it is kept	Leaves your machine?
API keys for OpenRouter, OpenAI or Anthropic	`chrome.storage.local` — this device only	Only to the provider that key belongs to, when you generate. Never synced.
Your preferences: which provider and model, how much to change, page limit, fill toggle, panel layout	`chrome.storage.sync`	Yes — through Chrome's own sync to your Google account, so your settings follow you between machines. No keys or documents are included.
The job posting you paste or open	`chrome.storage.session` while you work, and in local history afterwards	Sent to your chosen AI provider when you analyse or generate.
Your resume (LaTeX)	Read from your open Overleaf tab, or pasted or uploaded by you. Kept in local history.	Sent to your chosen AI provider when you generate.
History of your last 20 runs, including the original and revised resume	`chrome.storage.local` — this device only	No. Never synced, never uploaded. You can clear it at any time from the History screen.

Who your data is sent to

Only the parties you choose to involve:

Your AI provider. When you press Analyse or Generate, the job text and your resume are sent to whichever provider you configured — OpenRouter, OpenAI or Anthropic — under your own API key and their privacy policy. Skillo has no account with them and never sees the traffic.
Claude Code, if you choose it. With the optional local bridge, prompts go to the Claude Code already installed on your computer instead of a third party.
LinkedIn. Skillo fetches the job posting you asked for, one at a time, the same way opening the page yourself would. It does not crawl, and does not collect postings in bulk.
Overleaf. Skillo reads the document open in your Overleaf tab, and writes the revision back only when you press Apply.
Google. Only the preferences listed above, via Chrome's built-in sync. This is the same mechanism Chrome uses for your bookmarks.

What Skillo never does

No analytics, telemetry, crash reporting or usage tracking.
No advertising, and no selling or sharing of data with anyone.
No Skillo-operated server. There is nowhere for your data to be sent to us.
No syncing of API keys or resume content.
No reading of pages other than LinkedIn job postings and Overleaf projects.

Permissions, and why each exists

Permission	Why
`storage`	Keep your settings, keys and history
`sidePanel`	The Skillo interface itself
`tabs`	Find your open Overleaf and LinkedIn tabs
`scripting`	Read an Overleaf tab that was open before Skillo was installed
`offscreen`	Parse fetched job pages (Chrome's background worker cannot)
`nativeMessaging` (optional)	Requested only if you choose the local Claude Code bridge
`*.linkedin.com`	Read the job posting you asked for
`www.overleaf.com`	Read and write your resume document
`openrouter.ai`, `api.openai.com`, `api.anthropic.com`	Send requests to the provider you configured

Retention and deletion

Nothing expires on a schedule because nothing leaves your machine. History keeps the last 20 runs and drops the oldest beyond that; Clear history removes it immediately. Removing the extension deletes everything it stored locally. To remove synced preferences, clear them in Skillo's settings or reset Chrome sync from your Google account. Data already sent to an AI provider is governed by that provider's own retention policy.

Children

Skillo is a tool for job seekers and is not directed at children under 13.

Changes

If this policy changes, the date at the top changes with it, and the history of every revision is public in the repository.

Contact

Questions or concerns: open an issue at github.com/mehrshaad/Skillo/issues.