Privacy Policy
What information Project Atlas handles, why, and the choices you have. We collect as little as possible and never sell it.
Last updated: 6 October 2026
Overview
Project Atlas PH (“Project Atlas”, “we”, “us”) is a location-intelligence platform for Philippine retail, FMCG, and pharma teams. This policy explains what information we handle when you visit our public pages or use the authenticated application, how we use it, and the choices available to you.
Project Atlas is a business tool for authorized users. It is not directed at consumers or children, and it does not build profiles of individual members of the public.
Information we collect
We keep data collection to the minimum needed to run the service:
- Account information — the username and securely hashed password used to sign in, and the role assigned to your account.
- Usage data — for admin analytics we record page views within the authenticated app (which page, when). We do not sell or share this.
- Technical data — standard server logs (IP address, request path, timestamp) used for security, rate-limiting, and debugging.
- Content you create — saved views, bookmarks, and report selections you assemble inside the app.
- Your profile — the job title, product categories, retail chains, and coverage areas you choose to set, used to tailor what the tools show you first.
- Ask Atlas chats and memories — the questions you ask Bob, its answers and a trimmed copy of the lookups behind them, kept for 180 days after a chat's last question; and the names of any groups you sort your chats into and the notes you choose to save for Bob, kept until you delete them. Both are encrypted, visible only to you, and never shown to administrators. Phone numbers, email addresses and TINs are removed before a chat is stored.
The map & market data
The store, point-of-interest, demographic, and demand data shown in Project Atlas is derived from public and open sources — including the Philippine Statistics Authority (PSA), Demographic and Health Survey (DHS), Bureau of Internal Revenue (BIR) zonal values, the Department of Tourism, OpenStreetMap, and published research. It describes places and markets, not private individuals.
This dataset is our compiled work product. It is provided for use inside the product by authorized accounts and may not be extracted, scraped, or redistributed — see our Usage Policy.
How we use information
- To authenticate you and provide the application and its features.
- To secure the service — detecting abuse, enforcing rate limits, and investigating incidents.
- To understand and improve which parts of the product are used (aggregate, admin-only).
- To respond to your requests and support enquiries.
Data retention
Account and content data is retained for as long as your account is active. Security and server logs are retained only as long as needed for the purposes above and are then rotated out. You can request deletion of your account data at any time.
Saved Ask Atlas chats are deleted automatically 180 days after their last question, and private chats aren't saved; the notes you save for Bob and your chat groups stay until you delete them, and deactivating an account deletes all of it. When you send a chat along with your feedback on an answer, that copy is kept separately for the Atlas team to review; deleting your chats doesn't remove it. From your profile page you can delete any chat or note, or everything, and download a copy. Deleted data can remain in encrypted database backups until those backups expire.
Recordings of spoken questions aren't kept: each goes to the speech-to-text provider and is dropped once its words come back. We keep a usage record of each one — when, how long, and what it cost — never the recording or the words.
Your choices & rights
You may request access to, correction of, or deletion of your account information, and you may ask questions about how your data is handled. To exercise any of these, contact us using the details below and we will respond within a reasonable period.
Security
Access requires authentication, traffic is served over HTTPS, and passwords are stored only as salted hashes. We apply per-IP and per-account rate limits to protect the service. See our Trust & Security page for more detail.
Changes to this policy
We may update this policy as the product evolves. Material changes will be reflected here with a new “last updated” date.
This document is provided for transparency and general information. For a specific request or question, please get in touch through your Project Atlas account representative.