traipse
What Traipse sends, who receives it, and how to request deletion.
Effective 21 October 2026 · Traipse iOS TestFlight beta
Während der Testphase nur auf Englisch. Fragen auf Deutsch: hello@traipse.tech.
En anglais pendant la phase de test. Questions en français : hello@traipse.tech.
AI import sends tickets to our server and Anthropic to read them. We keep uploads and reviews to improve and train Traipse’s own model. With it off, you enter tickets by hand.
Error reporting, Google Maps, TestFlight and device backups also handle data. Traipse has no accounts or advertising, and we do not sell your data.
Traipse is run by Luca Liechti in Switzerland, the controller for the data we collect. Contact: hello@traipse.tech.
AI import is optional. Turning it on consents to collecting uploads and reviews for extraction and model training. It also enables address suggestions and usage counts.
Turn it off in Settings → AI import to use manual entry. This stops new AI imports, address suggestions, review reports and usage reports. Requests already underway may finish, and earlier uploads remain subject to retention.
Error reporting and server logs continue in either mode. Google Maps (see section 6), TestFlight and device backups operate separately from this switch.
| Data | When | Details |
|---|---|---|
| Documents and reviews | AI import | Uploaded files and filenames, extracted details, review corrections, review timing and edit information, and problem reports. |
| Device identifier | Requests to our server | A persistent random ID links uploads, errors and usage counts from your phone. Tickets can identify you through names and booking details. |
| Address searches | AI import and suggestions | Typed or extracted addresses, language and trip coordinates for map lookups. Address caches do not store your device ID. |
| Map pin checks | AI import | The address printed on a ticket, the address and coordinates a map service found for it, and the coordinates of the trip’s other pins, to check that a map pin is in the right place. For a pin we reject, we keep the reason, the check’s scores and the ticket’s address, never the map service’s answer. |
| Error reports | Failures, in either mode | Failure messages, app and iOS versions, phone model, language and AI setting; document source, type and size when relevant. |
| Usage counts | Daily, with AI import on | Trip and ticket counts, tickets per trip and category, and app version. |
| Server logs | Service activity, in either mode | Connection details such as IP address, request path and time, plus technical logs for diagnosing faults. This website also produces connection logs. |
Traipse does not request your phone’s location or contacts. Uploaded documents may contain personal details. If you email us, we receive your address and message.
Consented imports and reviews help us read tickets and improve and train our extraction model. Map pin checks keep a wrong place off your map. Usage counts help us understand how the app is used. Error reports and logs help diagnose faults and keep the service running in either mode.
We do not use your data for advertising or tracking across apps and websites.
Our server does not forward your device ID to Photon, Google, Nominatim or TypeSafe.
Traipse’s maps are Google Maps. The app loads the maps on your passes and in “Adjust pin” from Google, and the addresses you open go to the Google Maps app or website. Google receives the map area shown, which is where the place on your ticket is, your IP address, and data its map software reports: a device identifier, crash and performance data, and how the map is used. Traipse starts Google’s map software the first time it shows a map.
With AI import off, your phone sends the addresses you type to Google directly to place them on the map; our server is not involved.
Google uses this data under its own responsibility, not on our behalf. Traipse sends Google no personal names, booking details or our device ID.
Use of Google Maps features and content in Traipse is subject to the Google Maps End User Additional Terms of Service and the Google Privacy Policy.
The server’s cleanup does not delete trips stored on your phone.
Email hello@traipse.tech to request access, a copy, correction or deletion of your data, or to ask us to restrict or stop processing it. Include the Device ID from Settings → Privacy so we can find your records. Copy it before changing phones.
Deleting a trip in the app does not delete earlier server uploads. We delete your device’s server records on request. Shared files, caches and backups follow the retention rules above.
You may complain to the Swiss Federal Data Protection and Information Commissioner or the relevant authority where you live.
App-to-server traffic is encrypted. Server access is restricted, and backups are encrypted before leaving it.
The beta is for people aged 16 and over. Contact us if a child’s data needs removal.
TestFlight shares crash and usage information with us automatically, and shares feedback you submit. Email invitations can also make your name and email visible to us. We use this to manage the beta and improve Traipse.
Local app data may be included in your device backups, including iCloud Backup when enabled.
Updates appear here with a new date. The app records which consent text you answered.
hello@traipse.tech — English, Deutsch, français.