Privacy Policy — How It Went

Last updated: August 11, 2026

How It Went turns a multi-day trip into a short film, and is published by CodeUX.design e.U. (Austria). This policy covers the iOS, Android and macOS apps and this website at howitwent.app.

The short version

The app works on your tracks, your photographs and your video. All of it is the kind of thing a privacy policy usually exists to explain the sharing of. None of it is shared. The app makes no network requests at all: your files are read on your device, the film is rendered on your device, and nothing about either is sent to us or to anyone else.

What you give it, and where that goes

You pick three kinds of file, through your device's own file picker:

The app keeps its own copy of these inside its private storage, so that a tour is still there when you reopen it. Those copies stay on the device. Your originals are left where they are.

Everything the app works out from them — which day was which, where a photograph belongs on the track, what the film cuts to and when — is worked out on the device and written to a project file beside the copies.

Nothing leaves the device

There is no analytics, no crash reporting, no advertising, no account and no sign-in. The app makes no network requests, so there is no moment at which your tracks, your photographs, your video or your finished film could be transmitted anywhere. We cannot see any of it.

This is enforced by the builds themselves rather than resting on our care with the code: the released Android app ships without the INTERNET permission, and the released macOS app is sandboxed without the outgoing-network entitlement. Neither build is able to open a connection even if some future mistake asked it to.

There is no personal data here for us to sell or share, and we do not do either.

The app never asks where you are

It requests no location permission on any platform, and it does not use your device's location services. Every position it draws comes out of the files you chose to hand it — which is to say, out of a trip you already recorded, on purpose, on something else.

It cannot read your photo library

Photographs and clips arrive through the system file picker, which gives an app access to exactly the files you select and nothing else. The app never requests permission to browse your photo library, and cannot.

The one Photos permission it does ask for is permission to add — and only when you save a finished film to your camera roll. That is a deliberately narrower request than the read access it would need to look around, and the app is built so that it cannot be widened by accident.

Removing it

Deleting a tour in the app deletes the project file and the copies of the activity files, photographs and clips it was holding. Deleting the app removes everything it ever stored. Neither touches your originals, and neither touches a film you already saved to your camera roll — those are yours, in your own storage, and the app does not reach back into them.

The website keeps standard server logs

Visiting this site writes an ordinary web server access log entry: IP address, browser user agent, the file requested and the time. This is used only to operate and secure the site, is not combined with anything else, is never used to profile visitors, and is kept for a short period before being discarded. The legal basis is our legitimate interest in running a working, secure website (GDPR Article 6(1)(f)).

These pages load no third-party fonts, scripts, trackers or advertising.

Your rights

Under the GDPR you may request access to, correction of, or erasure of your personal data, and may object to or request restriction of its processing. In practice this can only concern the server logs described above, as the app holds nothing about you anywhere we can reach. You also have the right to lodge a complaint with a supervisory authority — in Austria, the Datenschutzbehörde.

Children

The app is not directed at children, and we do not knowingly collect personal data from anyone, of any age.

Changes to this policy

A future version may fetch map and elevation tiles for the area a trip covers, so that a film can be drawn over a real map without one being shipped in advance. That would mean telling a map server roughly where you rode or hiked — the first thing this app has ever had reason to send anywhere. It has not shipped, and if it does, this page will say so before that version is released, and the date above will change.

The same holds for anything else: if a future version collects or transmits something, we will update this page first.

Contact

Questions about this policy or your data: hello.howitwent@codeux.design