Privacy policy

This policy describes the information Pakratt collects and how it is used.

Information collected

Pakratt collects analytics about how the app is used, such as the screens opened and the features used, along with a randomly generated identifier for your device, the type of device, and an approximate location derived from your IP address.

If you make an account, Pakratt keeps your email address, your name and your password. The password is kept only as a hash, so it cannot be read back. Signing in gives the device a session token, which lasts until you sign out.

If you sign in with Apple, Apple gives Pakratt an identifier for you, your name the first time, and an email address, which may be one of Apple’s relay addresses if you chose to hide yours. Pakratt keeps no password for that account.

While you are signed in, the server keeps the trips on your account: their names, the lists and things on them, what was packed and anything noted about them, and the names of the people you add to them. Each change is stored with a name for the device that made it, such as ios-3f9a12c0: the kind of device and some random characters.

If you buy a pass, the purchase is made through the App Store or Google Play, and RevenueCat, which handles purchases for Pakratt, receives an identifier for your account, the store’s receipt and your IP address. Pakratt’s server keeps which pass your account has and until when. Your card and billing details stay with Apple or Google; Pakratt never sees them.

Feedback you send, from the app or the support page, goes with the email address you give to Mountain Loop Labs’ feedback service, so a person can read it and write back.

When the app crashes or hits an error, a report is sent with what went wrong, the type of device and its system version, and the version of the app. It does not include your trips, your email address or your name.

How it is used

Your trips are kept on the server so the same trips are on each of your devices, and on the devices of the people you share a trip with. The people on a trip see that trip, and your name and email address. Nothing from your other trips is shared with them.

What Pakratt remembers from one trip to the next is worked out on your device, from the trips it has. Analytics are used to improve the app. None of this is sold or used for advertising.

While you are signed in, the names of your trips, their lists and things, and the people coming on them are sent to TypeSafe AI, through Pakratt’s server, to rank what the app offers you. Your notes are never sent, and the server does not keep what it passes on. TypeSafe says it does not train on what it is sent.

Signed out, the app works on its own: your trips stay on your device and are not sent to the server.

What is not collected

Pakratt has no ads. This page, pakratt.com, counts visits with Pakratt’s own analytics on its own server: the page viewed, where you came from, and whether you tapped the beta or web buttons, sent the Android address form, or played a demo, with a random id kept in your browser so visits and visitors can be told apart. Nothing is sold and nothing is shared; the app at app.pakratt.com has the analytics described above.

Mailing list

If you leave your email address on this website to hear when Pakratt is ready for Android, it is kept to send you one email when it is. To be removed from the list, write to support@pakratt.com.

Service providers

Pakratt runs its own analytics. Third-party service providers, such as its hosting provider, Railway, process this information on its behalf. Crash and error reports go to Sentry. RevenueCat handles purchases. Apple and Google have their own privacy policies governing the App Store and Google Play.

Your choices

In the app, open Settings and choose Delete account. This removes your account from the server, along with every trip nobody else is on. Your trips stay on your devices.

To request access to or deletion of your information, or with any questions about this policy, write to support@pakratt.com.

Pakratt is developed by Gregory Schier. This policy may be updated as the app changes. Last updated October 13, 2026.