Privacy & Data Practices
This page explains the data practices built into the current Atlas release.
Account information
Account authentication is provided through Clerk. The Atlas stores application profile and authorization records in its own Cloudflare D1 database so access decisions remain under Atlas control.
Profile information
If you create or complete an Atlas profile, information you provide such as display name, home city or state, experience level, interests, industry role, organization information, and onboarding status may be stored in D1 to provide the requested account experience.
Contributions and reports
Public media submissions and correction reports are disabled at the initial Release 2 production cutover. If those features are enabled later, information submitted for moderation may include contact details, contribution metadata, uploaded files, rights confirmations, and the content of a correction report. Submissions are reviewed before publication and do not automatically overwrite canonical Atlas records.
Infrastructure
The Atlas uses Cloudflare infrastructure for application hosting, database storage, media storage, and operational observability. Technical request information may be processed by those systems as part of delivering, securing, and operating the service.
Third-party destinations
The Atlas may link to winery, vineyard, booking, shop, source, or other third-party websites. Their privacy practices are governed by their own policies.
Questions about Atlas data practices can be directed through the project’s published contact channel. This notice may be updated as features, vendors, or data practices change.
Return to the Atlas