Privacy policy
Last updated October 25, 2026
Adorably is a mod for Claude Code that shows developers perks matched to what they are building. It is operated by Amla Labs (“we”). This policy covers the Adorably mod, the api at api.adorably.io, and this website. Questions go to privacy@adorably.io.
The short version
Matching happens on your machine against a catalog the mod downloads. We learn which offers were shown to you and which you claimed. We never receive your code, your files, your prompts, your project’s tags or your dependency list. We don’t know your name or email, and there is no sign-in.
What the mod sends
Nothing is sent until you choose “Turn on” in the mod’s first-run screen. That screen is the only consent step. If you decline, the mod makes no network calls for events or claims.
Once you turn it on, about every ten minutes the mod sends a small batch of events to api.adorably.io. Each batch contains:
- A random install id. The mod creates it once and keeps it in its local store. It is not derived from your account, machine or name.
- Offer ids and what happened to them: shown, dismissed, muted, opened or claimed, and where (a card, the /perks pane or the status line). The mod also reports offer ids that matched but were not shown, with no tags attached, and once per session the number of offers that matched.
- The surface (for example terminal or desktop) and the mod version.
- A timestamp for each event, from your computer’s clock.
Country is derived on our side from the network request (Cloudflare’s country header), not sent by the mod. Your IP address is not stored with these events.
When you claim a perk, the claim link logs a hashed IP address and your user agent. We keep these for at most 30 days to count claims once per person and to stop abuse, then delete them. The claim record itself (install id, offer id, country, surface and time) is kept like other events until you ask us to delete it.
The mod also downloads the perk catalog and a small settings file from api.adorably.io. Those requests carry no install id.
What is sent, and what never is
| Sent | Never sent |
|---|---|
Random install id (from $.store) | Code, file contents, file paths, repo names or remotes |
| Offer ids shown, dismissed, claimed | Project tags or the dependency list |
| Surface (terminal/desktop), mod version | Prompts, transcript, model output |
| At claim time: a hashed IP and user agent, logged by the claim link and kept 30 days | Email (the mod never calls $.session.identity() and never reads the login file) |
| Country (derived server-side) | Env var values, .env files |
What stays on your machine
To match perks, the mod reads dependency manifests (such as package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml and Gemfile) and install commands it sees, and turns package names into tags. Those tags, the reasons for each match, how often you have seen cards, and the codes you have claimed stay in the mod’s local store. /perks why shows your tags and lets you remove any of them.
No AI model in this beta
This beta matches on dependency names only. It does not run Claude Haiku or any other model on your project. A later version may offer optional local tagging with Haiku on your own Claude plan. If it does, it will be a separate, clearly worded choice, its output will stay on your machine, and we will update this policy before it ships.
Turning it off
/perks offstops all cards and the mod’s event reporting immediately. Quiet hours take effect immediately too.- Setting
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1turns off all of the mod’s network calls. The mod respects it. - Uninstalling the plugin stops everything.
Deleting your data
/perks forget clears what Adorably keeps on your machine. To delete the events we hold for your install id, email privacy@adorably.io. Because there are no accounts, please include your install id if you can; without it we cannot tell which events are yours. The hashed IP on a claim is deleted after 30 days regardless; the rest of the claim record is deleted when you ask.
How we use what we receive
We use events to count which perks are shown and claimed, to keep the catalog relevant, to enforce limits on claims, to prevent abuse, and to report totals to the companies that offer perks. Those reports are aggregates; they never include install ids. We do not sell personal data and we do not use it for advertising elsewhere.
Perks and other websites
Perks are offered by third-party companies. When you open or claim one, you go to their site, where their own terms and privacy policy apply. Claim links add ref=adorably to the address so the company knows where you came from.
Service providers
Adorably runs on Cloudflare, which processes requests on our behalf to host and protect the api and this website.
This website
adorably.io sets no cookies, runs no analytics, and loads no third-party scripts or fonts.
Children
Adorably is a developer tool and is not directed at children under 16.
Changes
If we change what the mod sends, we will update this page and the date above before the change ships, and the in-session table under /perks privacy will match it.
Contact
Amla Labs, privacy@adorably.io.