Geolocation capture

The geolocation field type uses the browser Geolocation API to capture GPS coordinates from the respondent’s device. Add it to an IntakeBot like any other field. The respondent chooses when to share their position.

How it works

The respondent taps Share Location. The browser asks for location permission. After they allow it, ioZen stores the coordinates and shows a static map preview. Tiles come from OpenStreetMap. There is no separate geocoding service and no API keys to manage, so you do not pay for map or geocoding usage on top of your ioZen plan.

Where coordinates appear

Captured coordinates show up everywhere you already work with field data:

• Submissions and records list the value with context for your team.
• Process Board cards surface the same field on cards as they move through stages.
• CSV export includes the coordinates for spreadsheets and downstream tools.

Each place that shows the field also includes an Open in Google Maps link so people can open the pin in a familiar map app.

Privacy and sensitive data

Geolocation fields plug into the same private and encrypted field options as other field types. Mark a field private if you want it excluded from AI features (the model never sees it). Mark it encrypted if you want Vault-backed storage for extra protection. Pick the level that matches your policy and compliance needs.

When to use it

Teams use geolocation when the answer has to be “where this happened” rather than a typed address. Inspection reports in construction, insurance, or real estate often need a verifiable pin on site. Security and safety workflows use it for incident location. Field service trades (HVAC, plumbing, electrical) confirm someone was at the job. Delivery and property teams use it for proof of visit or unit-level checks. Events use it for check-ins when you care about physical presence, not just a name on a list.

Plans

Geolocation capture is available on Free, Pro, and Business. No plan gate for this field type.

Technical notes

• Coordinates come from the device GPS path exposed by the browser. Accuracy depends on the device and whether the user is indoors or outdoors.
• Preview maps use static tiles. They do not add a heavy client bundle or shipping cost tied to a third-party maps SDK.
• AI-assisted form generation can propose a geolocation field when the prompt clearly fits location capture. You still control the final schema.
• For embedded IntakeBots, geolocation permission policy and iframe allow attributes are set so location works safely across origins where embedding is supported.

If you need developer-level embed or API details, see the developer documentation.