Privacy Policy

Last updated: November 2026

1. Privacy at a glance

MyTripWallet manages the documents of a trip. Two different kinds of data arise in the process, and the roles differ between them:

• Your account data and trip content: everything that arises because you use MyTripWallet. For this we are the controller within the meaning of the GDPR.
• Third-party data you enter: fellow travellers, clients of a travel agency or people shown on uploaded documents. For this you are the controller; we process it solely on your behalf.

Without an account the data never leaves the device. We use no analytics or tracking services, no social media plugins and no newsletter systems; there is no profiling and no automated decision-making. In the Basic tier the app shows advertising (see below). Data is not sold to third parties.

2. Controller

The controller is the natural or legal person who alone or jointly with others determines the purposes and means of the processing of personal data.

Legal bases

We process personal data on the basis of Art. 6(1)(b) GDPR (performance of the user contract, see Terms), Art. 6(1)(f) GDPR (legitimate interest in secure, trouble-free operation), Art. 6(1)(c) GDPR (statutory retention obligations for payments) and, where consent has been given, Art. 6(1)(a) GDPR. Consent given can be withdrawn at any time with effect for the future.

SSL/TLS encryption

This site and all interfaces of the service are delivered exclusively over an encrypted connection (recognisable by https:// in the address bar). Data transmitted cannot therefore be read by third parties.

3. Hosting

MyTripWallet runs on a server in a data centre within the European Union. All application data (accounts, trips, uploaded documents and receipts, and the shares between accounts) is held on that server. No content delivery network is used; fonts, icons and scripts are also delivered from our own server and not loaded from external hosts.

4. Website access data

When a page is requested, your browser transmits technically necessary information that the server records in log files:

• the address requested, date and time of the request
• the amount of data transferred and the HTTP status code
• browser type and version, operating system
• the referring page, where transmitted
• IP address

The legal basis is Art. 6(1)(f) GDPR; the legitimate interest lies in secure operation and the defence against attacks. This data is not merged with other data sources. Logs are deleted after 30 days at the latest, unless they are needed to investigate a specific case of abuse.

To fend off automated attacks we store the IP address of suspicious requests in a block list for a limited time.

Contacting us

If you write to us by e-mail, we process your details in order to handle the enquiry and in case of follow-up questions. The legal basis is Art. 6(1)(b) or (f) GDPR. Messages remain with us until the purpose ceases to apply and no statutory retention periods stand in the way.

5. Account and sign-in

An account is needed only for syncing, sharing and backup. In doing so we process:

• e-mail address and, if provided, name
• the password, solely as a non-reversible hash, never in plain text
• a session identifier by which the app recognises you on each request
• the tier booked and the confirmation status of the account
• timestamps of creation and last change
• time-limited identifiers for the confirmation e-mail and for resetting the password

The legal basis is Art. 6(1)(b) GDPR. The account is valid for MyTripWallet only. Other applications of the provider maintain separate accounts with their own records, even for the same e-mail address; no comparison takes place between them.

6. Trips, documents and shared trips

When syncing with the server (from the Premium tier upwards) the following is held there:

• trips with name, period, destination and notes
• entries per trip: tickets, bookings, receipts, links and tasks with their details
• uploaded files and images (ticket PDFs or photographed receipts, for instance)
• for shared trips, which account sees which trip in which role
• in client management, the client records you create

The legal basis is Art. 6(1)(b) GDPR. For personal data of third parties that you enter, you are the controller; we process it on your documented instructions (Art. 28 GDPR) and provide a data processing agreement on request. Each account's files reside in a directory of its own; permission is checked on every request.

If you share a trip, the invited accounts see its content. A share can be revoked at any time; copies already saved by other accounts (an exported PDF, for instance) cannot be recalled.

7. E-mail

The service sends e-mail only in response to an event: confirmation of registration, password reset, a notice after a password change, invitation to a shared trip and notices about the account. Dispatch is handled by the provider's mail server. There is no advertising or newsletter mailing.

8. Purchases via the App Store

Purchases and subscriptions are processed via the Apple App Store. You enter your payment details with Apple; they do not reach our server. We only receive confirmation from Apple as to which tier is unlocked for your device or App Store account, and store this status against your account.

The legal basis is Art. 6(1)(b) GDPR (performance of contract) as well as Art. 6(1)(c) GDPR for commercial and tax retention. Apple's privacy notices additionally apply.

9. Storage on the device

The app stores data in the device's local storage. Without an account it stays there exclusively:

• trips, entries and attachments (IndexedDB)
• the session (account identifier, session identifier, display name) and the PIN lock
• the chosen language, the light/dark setting and the view last opened

Receipt recognition (OCR) and the generation of the itinerary PDF run entirely on the device; no images or texts are transferred to us or to third parties in the process. The legal basis is Art. 6(1)(b) GDPR. Signing out and clearing the app data removes these entries.

From the Enterprise tier, you can store your own branding for the PDF itinerary: logo, travel agency name and accent color. If you are signed in, the app stores these details on the server together with the profile backup described below.

If you are signed in, the app keeps a profile backup on the server in every tier, so that your profile is the same on all your devices. It contains your profile picture, the hash of your PIN code (if set up) and the unlocked tier. The app checks the PIN code itself only on the device; it is not transmitted.

10. Advertising in the app

If the app shows advertising in the Basic tier, it is delivered as a banner at the bottom of the iOS app via Google AdMob (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Google processes device data such as the device's advertising identifier, IP address and coarse location data to select advertisements and enable billing and abuse detection.

If the app offers ad videos in return for a reward (rewarded ads), you only ever start such a video yourself; these videos are also delivered by Google AdMob.

The legal basis is Art. 6(1)(f) GDPR (financing the Basic tier); where personalised advertising or access to the advertising identifier requires consent, it is obtained through the operating system's prompt and can be withdrawn there at any time (Settings > Privacy & Security > Tracking). The advertising identifier can also be reset or disabled in system settings.

From the Premium tier onward there is no advertising banner. A connection to AdMob is then only made if you start an ad video yourself.

11. Retention and deletion

• Account data: until you delete the account.
• Trips, entries and files on the server: until you delete them or your account. We do not delete them on our own initiative.
• Data held only on the device: until you delete it or remove the app; it is not restored afterwards if no sync was running.
• Purchase records: for the statutory retention periods, as a rule six to ten years.
• Access logs: after 30 days at the latest.
• Payment records: for the statutory retention periods, as a rule six to ten years.

You delete your account yourself in the app. The account is then deactivated and the associated data on the server is removed. This cannot be reversed. Accounts with other applications of the provider are unaffected and have to be deleted there separately.

12. Your rights

You have the right at any time to free information about your stored personal data, its origin and recipients and the purpose of the processing (Art. 15 GDPR), to rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on a legitimate interest (Art. 21). Consent given can be withdrawn at any time with effect for the future.

Please contact [email protected]. If another account has shared a trip with you, please address questions about the content entered there to that account first; it is the controller for that data.

Without prejudice to other remedies, you have the right to lodge a complaint with a data protection supervisory authority, in particular in the member state of your residence, your place of work or the place of the alleged infringement.

13. Changes to this policy

We adapt this policy when the service or the legal situation changes. The version published here at the time applies. In the case of substantial changes we additionally inform account holders in the application or by e-mail.