Privacy

• No cookies.
• No analytics, tracking pixels or ad scripts.
• No third-party scripts or fonts: every script, stylesheet, font and image comes from this site.
• The pages don’t contact other sites while you read them. Data such as release notes and code stats is copied into the site when it’s built, not fetched from GitHub while you browse.
• Nothing is stored in your browser beyond its normal cache.
• No forms, no accounts and no sign-in.

Server logs. Railway hosts this site. Cloudflare handles the domain’s DNS only, so your visit doesn’t pass through Cloudflare. Railway’s own HTTP logs record each request: your IP address, your browser’s user agent, the page and domain requested, the time, the response status, its size and timing, and which Railway edge region served it. Railway’s documentation says logs stay available for 3 to 90 days, depending on the account’s plan; how long Railway itself stores them is covered by Railway’s privacy policy. The site’s own server writes one line per request, such as GET /helm/ 200: the method, the page and the status, which Railway stores with the time. It doesn’t log your IP address, your user agent or anything after a ? in the address. Atlas Studio doesn’t use any of these logs to track you.

Download buttons, source links and issue links go to GitHub, and the Discord link goes to Discord. A few pages also link to things they mention, such as Anthropic’s Claude Code docs, and the Mantle page credits each wallpaper photo with a link to Unsplash. Once you follow a link off this site, you’re on someone else’s, and their privacy policy applies.

This page is about the website. Helm, Quartz and Mantle run on your PC and have no Atlas Studio account or sign-in. What each one does with your data is described in its own repository; the points below are the ones that matter most. They aren’t a complete audit of every network request: the code is public, and it’s the full answer.

Helm

• Keeps its settings and sessions in %APPDATA%\Helm on your PC. Your conversations stay where Claude Code keeps them.
• Never signs you in and never sees your Claude login. An Anthropic API key, if you add one, is stored encrypted with your Windows account.
• On first run, downloads Anthropic’s Claude Agent SDK from the npm registry.
• Settings → Helm → Updates checks GitHub for a newer release.

MoreHelm README, “Where data lives”

Quartz

• Its in-app updater follows Quartz’s GitHub releases.
• Features that use other services, such as Brave Search or a Claude answer, use keys you add yourself.

MoreQuartz READMEQuartz has no separate privacy document yet.

Mantle

• Uses the camera for one opt-in feature, “Blur the screen when I look away”. A face detector runs on your PC, and no frame is saved or sent.
• Google Calendar in the clock is optional and read-only, through a Google Cloud OAuth client you set up yourself.
• Its in-app updater follows Mantle’s GitHub releases.

MoreMantle README, “Privacy: the camera”

Ask on GitHub issues, in the Discord, or by email. GitHub issues are public, so don’t post anything private there; email is the private way to reach us. Mail to hello@atlasstudio.software arrives through Cloudflare Email Routing, which hands it to a small Cloudflare Worker. The Worker sends a backup copy to the studio’s Gmail inbox and delivers the message to the studio’s own mail server, hosted on Railway, where it’s stored. If that server can’t be reached, the Worker keeps the message in Cloudflare’s storage and retries, then deletes it there once it’s delivered. Replies are sent through Resend, with its open and click tracking turned off.