Privacy

Veeee uses cameras in two very different ways, and this page keeps them apart. Visitor localization is a visitor’s phone finding where they stand. Mapping capture is an organization photographing its own building. The rules below describe what the product does today.

Visitors

No account, no app, no GPS

A visitor opens a web page. Veeee does not ask them to sign in, install anything or share their location. The visitor page never uses GPS or the browser’s geolocation. The only data a visitor keeps on their phone are two preferences (the light or dark theme and whether voice is on), a random token that lets an organization count returning visitors without knowing who they are, and, for the length of the tab, the reference of a help request they opened.

Camera views

• The camera opens only after the visitor taps Start navigation, and only after the browser’s own permission prompt. Audio is never requested.
• Veeee does not record video. It captures small still frames, downscaled in the browser to at most 768 px on the long edge, two at a time about once a second while navigation is active.
• The frames are sent to Veeee over the same secure connection as the page, compared with the map’s reference images to find the visitor’s position, and then discarded by the browser. They are not kept on the phone and are not saved by Veeee as part of the visit, as the page states beneath the Start button: camera views find your location and are not saved.
• The camera stops when the visitor pauses, arrives, stops navigation, leaves the page or switches apps.

Motion sensors

Footsteps and heading come from the phone’s motion and orientation sensors (on iPhone, after a permission prompt). This data is used on the phone to time the instructions and is never sent to Veeee. Declining the permission does not block navigation.

What is sent to Veeee

• The text of each destination request, so it can be matched to a place.
• The start location, the destination and the planned route, kept in a navigation session for the duration of the walk.
• The camera frames described above, for localization only.
• The standard details any web server receives: the connection’s network address and the browser type.
• If the visitor chooses to: a rating with optional problem tags and comment after arriving, and a help request with whatever location and contact details they agreed to share. See Feedback, help requests and Insights.

Diagnostics for a walk exist only when a link is opened with ?diagnostics=1. They are kept in the browser’s memory, hold timings, scores and location names, and are scrubbed of links, tokens, email addresses and image data before they can be copied or downloaded.

Organizations

Mapping capture

Reference photos and videos are different from visitor camera views: they are stored. They are uploaded to Veeee’s storage, processed into the visual index that recognises visitors, and kept with the indoor map for as long as the organization keeps them. Optional text detection reads printed signs in them. Organizations are responsible for what their reference media shows; capture permanent features and avoid people.

The web mapper records up to 45 seconds of video per location during a walk, or a burst of still frames on browsers that cannot record. Veeee Mapper, in development, will capture frames and motion on the device and does not upload anything yet; see Veeee Mapper.

Account and organization data

• Account details (name, email, role), organization details (name, address, website) and the indoor maps themselves are stored by Veeee for the organization.
• Settings › Security lists every signed-in device, with the option to sign out any of them. Two-factor authentication secrets and recovery codes are created when the owner turns it on.
• Transactional email (sign-in security alerts, payment receipts, support confirmations) is sent to account addresses; some categories can be turned off in Settings › Notifications and some are always sent.
• Subscriptions and payments are handled on the payment provider’s hosted pages; card details are entered there, not in Veeee.
• Visitor sessions are not linked to any visitor identity, and the workspace shows no per-visitor history. Insights counts visits with a keyed hash of the browser token above, keeps them for a period the organization sets, and the owner can erase them at once.

What this page is

This page documents how the product behaves. It is not the privacy policy. For the privacy policy and data-processing terms that apply to your organization, contact Veeee.