Privacy policy
2026-10-26
Data we use
Atlas stores your email, a protected password hash, language settings, sign-in sessions, and the trips, notes, photos and people tags you add. Google sign-in provides an account identifier and verified email. Atlas never receives your Google password.
Why we use it
To sign you in, restore access, save travel memories, collaborate and publish selected stories. Hashed email and network identifiers and attempt timestamps are stored to help prevent abuse.
Photos and location
Original photos may contain EXIF, coordinates and capture dates. Atlas uses these to suggest places and dates; you confirm imports. Public stories contain selected material only; photo EXIF and precise GPS coordinates are not published.
Who can see your content
Private trips are available to their owner and accepted participants. Anyone with a shared link can access the selected material. Public stories are visible to everyone and may be indexed by search engines. Copies, downloads and social network caches may remain after you revoke a link.
Storage and providers
Atlas uses a separate Google Cloud project and private photo storage. Cloudflare serves the domain and forwards requests. Resend may deliver account emails and receives the recipient address, message and one-time link. Choosing Google sign-in involves Google services.
Cookies and retention
Session cookies support sign-in. Your language and map style are stored on your device. Reset and verification links expire after 30 minutes. Travel content remains until deleted; backups may temporarily retain earlier versions.
Your choices and contact
You can edit and delete your content, revoke shared links and export data in settings. For account deletion, personal-data requests or backup-retention questions, contact the service owner at shelovanov@gmail.com. Never send passwords or recovery codes.