Updated 9 November 2026
Privacy and data flows
Atlas Review is an open source desktop application by Loomtide. This page describes its desktop data flows and the analytics on these website pages. Local review does not require an Atlas-hosted service.
Your local profile
Project state, review history, findings, settings, and local logs are stored in your application profile. Provider credentials use the app's local credential storage or your provider CLI's existing authentication. Protect the profile and its backups; they can contain private repository information and authentication material.
Your AI provider
Reviews, walkthroughs, and chat send selected code and context to your configured AI provider. That context can include file contents beyond the diff, repository conventions, review findings, and conversation history. Provider CLIs can read repository files needed for the task. This is not a guarantee that only changed lines leave your machine.
Your provider account, configuration, retention policies, charges, and usage limits apply. Choose a provider and settings appropriate for confidential code. Running the desktop app locally does not by itself keep an external AI provider's processing within your network.
GitHub and updates
GitHub features contact GitHub to authorize your account and retrieve repository metadata, pull request changes, and conversations. Review comments and decisions you explicitly publish are sent to GitHub. Official desktop builds also contact GitHub for update checks and downloads. These requests are subject to GitHub's service and privacy terms.
Optional hosted sync
Fresh installations do not have a default hosted sync server. If a compatible sync service is configured, the app can send review state, findings, project and repository metadata, and data included in sync events to that service. Its operator controls access and retention.
Existing saved sync connections, including legacy hosted connections, are preserved when upgrading. They can continue reporting after an upgrade. To disable sync, remove its configured server URL from saved profile settings and any profile environment configuration. See the configuration and privacy guide for the supported settings and profile locations.
Website analytics
These website pages use Vercel Web Analytics for page views and interaction events, such as opening download options, selecting a download, and playing a demo. Configured events include the page or button location, detected operating system, and release or installer version. The website does not ask for your repository content or provider credentials.
Vercel's analytics can include page URLs, referrers, approximate location, and browser or device information. Vercel describes its Web Analytics as operating without third-party analytics cookies. Read Vercel's analytics privacy documentation and the Loomtide website privacy policy for more information. Website analytics is separate from optional desktop hosted sync.
Your choices and questions
You choose which repositories to review, which provider to configure, which GitHub actions to publish, and whether to configure hosted sync. Deleting a local profile does not delete data already sent to an AI provider, GitHub, or a sync service; contact the relevant operator about that data.
For questions about Loomtide's services or this website, email contact@loomtide.ai. The public source and configuration guide describe the implementation and available settings.