Privacy
What we store, and what we do not
SkillAppMD has no accounts, sets no cookies and runs no analytics. This page says what that means in practice, and how to have information about you corrected or removed.
No cookies
This site sets no cookies. There is no banner because there is nothing to consent to.
Your theme preference is kept in your browser’s local storage under the key skillappmd-theme. It never leaves your device and is never sent to us. Clearing site data removes it.
No accounts, no tracking
No sign in
There is no account system. The API is read only and has no write surface, so there is nothing to register for.
No analytics
No analytics script, no tag manager, no session recording, no fingerprinting, no advertising pixel.
No third-party embeds
Agent logos are served from this domain. No fonts, scripts or images are loaded from anyone else, so no third party observes your visit.
What the server sees
Requests to the API are rate limited per client identifier, which means request metadata is processed to enforce that limit. This is operational, used to keep the service available, and is not used to build a profile of you or joined to anything else.
Information about people in the index
This is the part that matters, because the index is built from public repositories and the people in it did not opt in.
Repository and owner handles are retained
A repository is identified as owner/repo, and the owner may be a person rather than an organisation. Attribution is mandatory on every record, so this is retained and served.
Individual author fields are minimised
Beyond what attribution requires, person-linked fields are not published.
Never collected
Email addresses, real names beyond a public handle, follower graphs and contribution histories are not collected at all.
A field without a stated purpose is not stored
Every person-linked field must record the provenance purpose that justifies it. Minimisation is enforced as a schema rule, not left to policy.
We also never publish the contents of a SKILL.md file. What is served is metadata, provenance and a licence position, with a link to the original repository.
Correction and removal
If you are named in the index and want that corrected or removed, you can ask, and we will act on it.
Authors did not opt in, so a correction and removal route is a requirement of the system rather than a courtesy. Every request is recorded with the request itself, who handled it, the outcome and the time.
One limit, stated plainly: removal deletes the indexed bytes, but the record that a removal happened is kept permanently. Otherwise the index could not show that something was once there and is no longer, which is itself provenance information.
Changes
If this page changes in a way that affects what is collected or published, the change will be reflected here. There is no mailing list to notify, because we do not hold your email address.