Privacy Policy
Last updated November 18, 2026
This page explains what data Claude Code Templates collects through the website at aitmpl.com and the
claude-code-templates command-line tool, why, and how to opt out. The project does not sell personal data
and does not use it for advertising profiles.
Browsing the website
You can browse the catalog without an account. Every page, including the catalog and blog articles under /blog, uses Google
Analytics to count visits and see which pages people find useful, which sets Google cookies in your browser. The site
loads no advertising trackers. Like any web server, our hosting provider (Cloudflare) processes your IP address and request details to
deliver pages and protect the site from abuse. Your theme and layout preferences, the components you add to your stack,
and a cached copy of the repository's GitHub star count are kept in your browser's local storage and never sent to us.
A stack link (/s/…) carries the list of components and the day it was made inside the link itself.
Making one stores nothing on our servers, and anyone who has the link can see that list. If you click "Save as collection"
while signed out, that link waits in your browser's session storage until you sign in, then becomes a collection in your
account; it is removed when it is used or the tab closes, and ignored after 30 minutes.
Google Analytics also receives a few named events, so we can see which features people use: viewing a component, copying its install command, adding it to your stack, copying the install command of your stack, of a stack link or of a collection, creating a stack link, sending a stack link to your computer from a phone, adding a shared stack to your own, clicking Save, opening and completing the sign-in, following a link to the component's source on GitHub, following a link to another component it suggests, and searching. They carry only the type and path of the components involved, the part of the site where it happened (for a sign-in, the feature that asked for it), a number of components, whether you were signed in, and for a search the number of results. They never carry what you type, a collection's name or your account details. When you open the sign-in, the feature that asked for it is kept in your browser's session storage so the completed sign-in can be counted; it is removed when the sign-in completes or the tab closes, and ignored after 30 minutes.
CLI usage statistics
When you install a component, the CLI sends a usage event so the site can show download counts and trending components. The event contains the component type, name and category, the CLI version, your Node.js version, operating system and architecture, whether the installation succeeded, how long it took, and a random identifier that groups the components installed in one run. When you install into a directory other than the current one, the event includes that directory relative to where you ran the command. When an installation fails, it includes the error message, which can contain local file paths. The contents of your files are never sent.
Since version 1.32.0, the event also says whether the CLI is running inside an AI coding agent such as Claude Code, Cursor or Codex, and which one; how Claude Code was started (for example from a terminal, an editor or the SDK) when it is that agent; and whether the output goes to an interactive terminal. The CLI does not send the account email or the account and session identifiers that Claude Code makes available to it. Our server records the request's IP address, the country our hosting provider derives from it, and the user agent with download events.
Commands that are not installations (the catalog browser, analytics, chats, the health check, workflows and options that were removed) send the command name, the CLI and Node.js versions, the operating system and architecture, and a random identifier created for each event. A workflow run also sends how many components of each type it contains, and a removed option sends its name.
To install components, the CLI downloads files from GitHub (raw.githubusercontent.com and
api.github.com) and from www.aitmpl.com, so those services receive your IP address, as with any download.
Plugins are installed by Claude Code itself from the aitmpl marketplace at www.aitmpl.com/marketplace.json.
To turn the usage events off, set CCT_NO_TRACKING=true (or CCT_NO_ANALYTICS=true) in your environment.
Nothing is sent when CI=true. Crash reporting is a separate, off-by-default feature that only runs if you
set CCT_ERROR_REPORTING=true.
MCP server
The aitmpl MCP server at mcp.aitmpl.com lets Claude and other AI tools search the catalog, read a component and
get the command that installs it. It has no accounts and needs no sign-in. The words you search for and the components you
look up are used only to answer that request: the server does not store or log them, and it never receives your
conversation, your files or any account details from the AI tool. Cloudflare, which runs the server, processes the request's
IP address and metadata to deliver it and protect it from abuse. The server installs nothing; a component is installed only
when you or your agent runs the returned command, and then the CLI usage statistics described above apply.
Accounts and collections
Signing in is optional for browsing the catalog and handled by Clerk. You need an account to save collections and to open job listings, certifications and courses. If you sign in, we store your account identifier and the component collections you create, including whether you made a collection public. Your name and email are held by Clerk, which also keeps a record of your sign-in sessions (device type, browser and approximate location). When you click Save, a job or a course before signing in, that one action (the component, or the link to open) is kept in your browser's session storage so it can be completed after you sign in. It is never sent to us. It is deleted when it runs, when you close the tab, or on the first page you open after 30 minutes; after 30 minutes it is never run.
Sending components to a GitHub repository
The "Send to repo" feature asks you to authorize our GitHub OAuth app. The resulting access token is kept in your browser's session storage, used only to create the commit or pull request you asked for, and is not stored on our servers.
From July to September 2026 we sent emails about new and trending components to people with an aitmpl.com account. The addresses came from the sign-in accounts held by Clerk; there was no separate sign-up form. Sending has been paused since September 20, 2026.
We still keep each of those addresses, with its account identifier and unsubscribe status, in our database and with our email provider, Resend. We also keep the delivery events Resend reported for each recipient: opened, clicked (with the link), bounced or marked as spam. Every email included an unsubscribe link. To have your address and these records deleted, email daniel@aitmpl.com.
Sponsored placements
If you buy a sponsored placement, payment is handled by Stripe on admin.aitmpl.com. We keep a record of the placement and the Stripe payment reference; we never see or store your card details.
To tell sponsors and partners what a placement delivers, the site counts how often a sponsored or featured placement is seen (at least half of it on screen for one second) and clicked. Your browser sends the placement, the part of the site and the kind of event to aitmpl.com; we add one to a daily counter by country (from Cloudflare) and keep nothing else: no IP address, no browser details, no cookie and no identifier, so these counts cannot be tied to a person. Sponsors receive only the totals.
Error monitoring
Server errors on the website are reported to Sentry so we can fix them. Reports contain the error and the API route where it happened, not account data.
Service providers
- Cloudflare: hosting, content delivery and the MCP server.
- Supabase and Neon: databases for usage statistics, collections, email records and placements.
- Clerk: sign-in.
- GitHub: OAuth for "Send to repo", the public source repository, and the files the CLI downloads.
- Resend: email delivery (paused since September 2026).
- Stripe: payments for sponsored placements.
- Sentry: error monitoring.
- Google: Google Fonts on every page, Google Analytics on every page.
Your choices
You can delete your account and collections, ask what data we hold about you, or ask us to delete it, by emailing daniel@aitmpl.com. We will answer within 30 days.
Changes
We will update this page when what we collect changes, and the date above shows the latest version. The page's history is public in the GitHub repository.