Privacy & data
sticky doesn't have user accounts, doesn't track individuals, and only operates on public GitHub repos. The data model is intentionally small.
What gets stored
Every successful generation creates one row in the wikis table on Neon Postgres. The row holds:
- slug — the URL path (
commander-js,u-abc123def, etc.). - repoOwner and repoName — the parsed identifier.
- repoUrl — the canonical GitHub URL.
- repoDefaultBranch and repoCommitSha — what the snapshot was taken against, so a future regenerate feature can tell when a wiki is stale.
- summary — the first non-heading line of the wiki, extracted on finish. Used in the Library listing.
- content — the full Markdown of the generated wiki.
- listed — whether the wiki appears in the public Library.
- generationModel — the model identifier used (currently
anthropic/claude-sonnet-4-6). - createdAt — the timestamp of insertion.
No IP address, user agent, session ID, or identifier of the submitter is stored.
Listed vs unlisted
The checkbox "Add to public Library" on the submission form controls this single flag. The choice affects three things:
| Listed | Unlisted | |
|---|---|---|
| Appears in /library | Yes | No |
| Slug shape | Human-readable (commander-js) | Random (u-abc123def) |
| Deduped against existing wikis | Yes — second submitter shares the existing one | No — every submission gets its own copy |
Either way, the wiki URL is shareable — there's no access control. Treat an unlisted slug as "unguessable but not secret" (the random suffix is 10 base32 characters, so guessing is impractical, but anyone with the link can read it).
What sticky talks to
- GitHub's public REST API, via Octokit, to read repo metadata and file contents. No authenticated requests are made by default — this is the same access an anonymous browser would have. Private repos return 404.
- Vercel AI Gateway, which proxies to Anthropic for the actual model call. The function authenticates with Vercel's OIDC token; no provider API key is held by the app. The Gateway is configured for zero data retention on the provider side.
- Neon Postgres, for storing wikis.
Cookies and tracking
sticky doesn't set any cookies of its own and runs no client-side analytics. Vercel's platform-level metrics (response times, error rates) are still in play — those are bucketed and anonymous.
Takedowns
If you maintain a public repo and want its wiki removed from the Library, open an issue on the sticky.codes repository with the wiki URL. Same for delisting (keep the wiki at its URL but remove it from /library) — the listedflag is a single boolean and is easy to toggle. There's no automated takedown form yet because there hasn't been enough volume to need one.
Next: FAQ — the questions most people ask after using sticky for the first time.