Location and proximity queries
Prepare data models for nearby stores, deliveries and location-aware content. Manage sensitive location with consent, retention and access boundaries.
How to design the workflow
Background location consent differs from foreground consent. Avoid unnecessary continuous tracking. Use distinct rules for users’ own location and authorized operational records.
Cost and service boundaries
Map tiles, routing and geocoding provider fees are not included in backend plans. Managed maps and PostGIS allocation are not available; this page plans the data and API architecture.
Pre-launch checklist
Validate these steps in your app and with the providers you choose. Measure concurrent load alongside CPU, memory and storage before selecting a plan.
- Limit location retention.
- Validate coordinates and search radius.
- Budget map and geocoding fees separately.
Common questions
Is this service available today?
This page describes a service plan and architecture. Managed customer services are not enabled; publication does not activate resources or integrations.
Which plan should I consider?
Consider the resource scope of Pro. This is not a capacity guarantee; validate it against application load and external provider fees.