🔒 Privacy
Atlasemoji is built to help people remember places and tell stories — not to sell your life. We collect the minimum data needed to run the app, keep it reliable, and give you control.
Who we are (Data Controller)
For data protection purposes, Atlasemoji is the data controller for personal data we process in the app.
Questions or requests can be sent through our in-app feedback channel: 💬 Feedback.
What we collect
1) Account data (if you sign in)
- Account identifier (e.g., user ID)
- Basic profile info from your sign-in provider (typically name and email)
- Authentication metadata needed to keep your account secure
2) Content you create
You control what you enter. Depending on features you use, content may include:
- Waypoints/posts (title, emoji/category, notes)
- Location data you choose to attach (map point/area)
- Time you choose to attach (date/time, including historical dates)
- Optional media you upload (images/video)
- Optional datasets you upload (e.g., KML reference layers)
Fixed geofence trial location data
When you start a Fixed Geofence Trial, Atlasemoji may collect the geofence center, radius, address or coordinates you entered, your contact details, consent status, masked session token metadata, and phone location pings from phones that accepted the session. These pings are used to show participating phones on the map and determine whether a phone is inside, outside, entering, or exiting the geofence boundary.
Participant links use masked session tokens. A manifest ID or participant ID alone is not enough to join or update a session. Location updates are accepted only from the creator phone or an invited participant phone that accepted location sharing for that test session.
Atlasemoji uses this phone-location data to operate the test, display the session map, produce geofence event records, and provide access to the user-created data. We do not use the Fixed Geofence Trial consent checkbox as permission to send unrelated marketing material.
3) Technical data (reliability + security)
- Device/app information (browser type, OS, app version)
- Log data (errors, crash reports, performance metrics)
- Security logs (abuse prevention, rate limiting, fraud/spam detection)
- Approximate network data (IP address) used for security and abuse prevention
Public vs private
- Private content is intended to be visible only to you (subject to standard hosting/storage processing).
- Public content can be viewed by others via the map and shared links. If you mark something public, you are choosing to publish it.
Once public, others may copy/share/screenshot it. If you’re unsure, keep it private.
Why we use data (purposes)
- Provide core features (maps, posts, routes, datasets, sharing)
- Authenticate you and keep your account secure
- Store and retrieve your content across devices
- Prevent abuse (spam, harassment, illegal content)
- Maintain and improve reliability (debugging, performance, incident response)
- Comply with legal obligations where applicable
- Operate consented geofence sessions, display participating phones, evaluate boundary crossings, and generate session event records.
Legal bases (GDPR)
- Contract: to provide the service you request (account, storage, core functions).
- Legitimate interests: to secure the service, prevent abuse, and keep it reliable (balanced against your rights).
- Consent: where required (for example, optional features or communications, if introduced later).
- Legal obligation: when we must comply with applicable laws.
What we don’t do
- No selling your personal data.
- No “follow you around the internet” ad profiles.
- No data brokerage.
- We do not treat Fixed Geofence Trial location consent as permission to send unrelated marketing emails.
Sharing & processors (third parties)
Atlasemoji relies on infrastructure providers to operate. For example:
- Google Firebase (hosting, authentication, storage, database, and related services). Google generally acts as a data processor for Firebase under its published privacy and data processing terms.
- Google Maps Platform (map display and place search).
These providers process limited data to deliver their services. We do not authorize them to use your content for unrelated advertising.
International transfers
Because we operate globally and use global infrastructure providers, your data may be processed outside your country, including outside the EEA. Where required, transfers are protected using lawful mechanisms such as Standard Contractual Clauses (SCCs) and other safeguards under GDPR Chapter V.
Data retention
- Account + private content: retained until you delete it or delete your account (subject to backups and legal obligations).
- Public content: retained until removed by you or moderated/removed under the Terms.
- Logs: retained for a limited period for security and reliability, then deleted or aggregated.
- Fixed geofence trial records: Saved manifests, geofence records, CRM/base-user records, consent logs, and event records may remain available so the creator can access the test data. Live phone-location updates stop when the session ends, permission is revoked, or sharing is paused/stopped.
Backups may persist briefly after deletion for disaster recovery, then expire.
Your rights
- Access your personal data
- Correct inaccurate data
- Delete data
- Object to or restrict certain processing
- Data portability (where applicable)
- Withdraw consent (where we rely on consent)
You can request help through 💬 Feedback. If you are in the EEA/UK, you also have the right to lodge a complaint with your local data protection authority.
Children
Atlasemoji is designed to be family-friendly, but we do not knowingly collect personal data from children without appropriate consent where required by local law. If you believe a child has provided personal data without consent, contact us via 💬 Feedback.
Security
We use reasonable technical and organizational measures to protect data (access controls, encryption in transit, and security monitoring). No method of storage is 100% secure.
For geofence trials, Atlasemoji masks participant sessions with tokenized links and limits location updates to phones that accepted location sharing. This is intended to reduce the risk of someone guessing IDs and joining or updating a session without authorization.
Changes
We may update this policy as features ship. We’ll update the date and, if changes are material, provide an in-app notice.
Last updated: 2026-02-19