Encrypted trip content
Shared content can include location, route information, progress, ETA, remaining time and distance, stops, speed and other live trip state.
Shared live-trip content is encrypted on the Android phone before it is sent. The people you choose receive a private tracking link, and their browser uses the secret key in that link to decrypt the shared trip.
The actual shared-trip content is encrypted on Android before transmission. Iiro currently uses AES-256-GCM, an authenticated encryption mode that protects confidentiality and detects tampering.
Shared content can include location, route information, progress, ETA, remaining time and distance, stops, speed and other live trip state.
Limited technical metadata remains outside the encrypted payload so the system can synchronize updates and know whether the trip is active. It is not intended to contain the actual route, coordinates, ETA, speed or stop content.
# part of the linkConceptually, an Iiro link looks like viewer.html?id=trip-id#k=secret-key. The exact link is generated by Iiro.
A browser keeps the URL fragment, the part beginning with #, on the browser side instead of sending it in the normal HTTP request. The current viewer reads the key locally and uses it to decrypt the shared trip.
Iiro creates the shared trip and encrypts its actual content on the Android device.
Encrypted trip data is carried and stored temporarily so the viewer can receive updates.
You send the complete link to the people you choose. The link contains the decryption key.
The viewer receives encrypted data and decrypts it locally using the key from the link.
Anyone who receives the complete tracking link can use the key inside it to open the shared trip. That is intentional: the link is how you give someone access.
Shared live trips are temporary and are not stored under a permanent Iiro user account. Relay cleanup removes old shared-trip information after the applicable technical retention period.
Iiro does not provide a permanent account history or recovery archive for old live trips.
Iiro can use location for GPS starting points, route progress, live sharing and the current trip state shown to selected viewers.
Iiro does not use location data for advertising and does not sell personal data.
Place searches and route requests may send the information needed for that request to relevant map, geocoding or routing services. Depending on the feature, this can include search text, selected places, coordinates or route-request information.
Iiro uses technologies and services that can include Firebase / Google Cloud, Firestore, Firebase Hosting, Google Play Services Location, OpenStreetMap, MapLibre, routing services and Iiro relay servers. Their own privacy terms may apply to their processing.
Settings, language choices, an optional nickname, saved places and saved routes are mainly stored on the device. Favorites and saved routes may also be included in Android system backup if device backup is enabled.
This is separate from the temporary shared live-trip system.
The person using Iiro starts the shared trip and chooses to share its link. Iiro is not designed as hidden tracking, child surveillance, workforce monitoring, fleet surveillance or an emergency locator.
Use Iiro to plan your route and timing, then give the people waiting for you one simple way to follow the trip.
No account required.