Before publication
Monmap LLC must confirm its registered address, production hosting and transfer locations, infrastructure retention, and provider contracts. Qualified Mongolian counsel must review the final text.
1. Who we are and what this covers
Monmap LLC operates Ubhub Location Service, including its website, developer account, public map, API key console and geocoding, reverse geocoding and routing APIs. This policy covers personal information processed through those services. A customer that sends another person's location or address through an API is responsible for its own notice and lawful basis for that submission.
Data controller: Monmap LLC. Privacy contact: bilguuntugs@monmap.mn. Registered/contact street address has not yet been supplied and must be added before this draft is published as an effective policy.
2. Information we process
| Category | Actual data and purpose |
|---|---|
| Account and authentication | Name, email, account ID, password hash, email-verification status, session, verification-code and reset records; used for registration, sign-in, account security and support. |
| API keys and usage | Key name, non-secret prefix, protected key hash, scopes, status and last use; endpoint, method, status, response time, time, account/key IDs, quotas and daily counts; used to operate and bill the APIs. |
| Network and security | Trusted source IP address, bounded User-Agent, request ID, path, status and timing in API access logs. The public demo also stores a short-lived HMAC of the visitor IP for rate limits. Security events record account/key IDs and event details. |
| Geospatial requests | Search text, addresses, coordinates and route endpoints supplied to the map, playground or API; used to return results. The application-level Convex usage rows and structured API access logs do not contain query strings or request bodies. |
| Billing | Selected plan, payment intent ID, amount, status and timestamps; used for checkout and payment history. Card or bank credentials are handled by the payment provider, not stored in this application database. |
| Communications | Email-verification and password-reset destination addresses and messages; if an enterprise inquiry is submitted, name, email, company, estimated usage and message are emailed to Monmap LLC. |
Information is not made public by the account or billing features. API responses are sent to the requester holding the relevant credential. A customer may choose to display returned location data in its own application.
3. Purposes and grounds
We process account, session, API, security and billing information to provide the requested service, administer an account and payments, enforce limits and protect the platform. Signup separately records affirmative agreement to the Terms and consent to the service data processing described here. Where a different legal ground applies, or a legal record must be retained, withdrawing consent does not automatically erase that record. We currently have no marketing-email or optional product-analytics consent program in this codebase.
4. Location and geospatial data
Geocoding submits a search or address; reverse geocoding submits coordinates; routing submits origin and destination coordinates and a travel mode. The browser or customer sends these to the FastAPI gateway. The gateway forwards the data needed to answer the request to the configured ArcGIS service; deployments can instead be configured with Nominatim or OSRM. The supplied geocoding and routing datasets concern Mongolia, but the physical hosting location of every processing component has not yet been confirmed.
The API may hold geocoding results temporarily in bounded memory when caching is enabled. Application-level usage records contain endpoint and timing, not the search or route input. Upstream geospatial services, reverse proxies or infrastructure operators may have separate logs and retention. We cannot promise immediate deletion of those records without confirming their configuration and contracts. Browser map styles and tiles are served through our API gateway. The gateway requests basemap resources from the configured ArcGIS service without forwarding browser credentials or visitor IP headers. Our infrastructure receives the browser requests; the upstream receives tile coordinates and our server network address.
5. Providers and transfers
- Convex stores accounts, sessions, API key metadata, usage, security events and payment records. The repository's production profile self-hosts Convex on the application server; other deployment profiles may use Convex Cloud. The server's physical location needs confirmation.
- The configured ArcGIS service receives relevant searches and coordinates. Optional Nominatim/OSRM deployments receive equivalent location inputs instead. The configured ArcGIS basemap service receives resource requests from our gateway.
- Wire Payment processes the payment intent, account reference, plan and amount for paid checkout and may expose QPay/bank payment options.
- Resend receives email-verification and password-reset destination addresses and messages, and enterprise contact-form messages sent to Monmap LLC's contact mailbox.
- Hosting, reverse-proxy and backup operators may process account data and network logs according to the chosen deployment. Their identity, country, access and retention must be confirmed before production release.
Some of these recipients may be outside Mongolia. The production configuration and any cross-border transfer basis must be confirmed and disclosed before this draft becomes effective; we do not claim all account data remains in Mongolia. We do not sell account or location-request data.
6. Retention and deletion
| Record | Current application behavior |
|---|---|
| Raw API usage | Pruned after the configured USAGE_RETENTION_DAYS; default 30 days. |
| Security audit events | Pruned after AUDIT_RETENTION_DAYS; default 365 days. |
| Rate-limit and quota windows | Minute windows are pruned after five minutes; quota windows after roughly 400 days. |
| Playground tokens | Expire after 15 minutes and are pruned; revoking or rotating the key deletes them. |
| Account, daily usage totals, payment and policy records | No automatic erasure schedule currently exists. They remain until an operator reviews an applicable deletion request or a retention rule is implemented. |
| Access logs and backups | Retention depends on the deployment and has not yet been verified. Do not assume removal at the same time as live database records. |
In Account Settings, an account holder can request closure after confirming the password. The application then disables the account, revokes API keys and ends sessions. This is not immediate physical erasure: a manual review decides which records can be deleted or de-identified and which must be retained for payment, security, dispute or legal purposes. We will explain the outcome to the requester. The operator procedure is documented internally.
7. Your rights and controls
You can view and correct your profile name in Account Settings. There you can request access/copy, correction beyond the self-service field, withdrawal of consent or account deletion. You may also write to bilguuntugs@monmap.mn. We manually verify and review requests, including any applicable limits on erasure or cancellation. Withdrawing consent is a separate request from deleting an account; service functions that need the withdrawn processing may no longer be available.
Under applicable Mongolian law, data subjects may seek information about processing and recipients, request corrections and a copy, request cancellation or erasure where the law permits, and complain about a processing decision. You may contact the competent authority if you believe your rights were harmed.
8. Cookies and similar storage
The site uses httpOnly authentication cookies to maintain a signed-in session and a language-preference cookie. A migration routine removes old Convex authentication entries from local storage; current authentication credentials are held in memory and cookies. We did not find an optional advertising, analytics or tracking-pixel system in this application. A separate marketing-cookie banner is therefore not part of the current product.
9. Security and incidents
We use transport encryption in production, access controls, password hashing, protected API key hashes, rate limits, credential redaction and security logging. Access is limited to authorized personnel and service providers. No system is risk-free. If a processing violation harms data-subject rights or legitimate interests, our incident procedure requires containment, investigation and notification as applicable to affected people and authorities.
10. Changes and contact
Material updates will have a new version and will require an affirmative review and acceptance when appropriate; the application does not silently mark a new version accepted. For questions or requests, email bilguuntugs@monmap.mn.
Publication status
This version is a review draft. Its effective date, registered address, infrastructure locations, retention decisions and final legal basis for any foreign transfer remain to be confirmed before production publication.