This is a translation for your convenience. The German version is legally binding.
Für den Anwalt: Vorrang der deutschen Fassung und die englische Übersetzung prüfen.
This page sets out what data the TripHar app processes, what for, who sees it, how long we keep it and what rights you have. Last updated: ENTER DATE. For the website, the website privacy policy also applies.
Manuel Harrer, Lilienweg 1, 4064 Oftering, Austria.
Privacy questions and requests: privacy@triphar.com ·
Help with the app: support@triphar.com ·
Further details in the legal notice.
We have not appointed a data protection officer; we are not required to do so (to be checked).
“Contract” means: we need the data to provide the app to you in the way you use it (Art. 6(1)(b) GDPR). “Consent”: Art. 6(1)(a), for specially protected data Art. 9(2)(a) — can be withdrawn at any time. “Legitimate interest”: Art. 6(1)(f) — you can object (see Your rights). “Legal obligation”: Art. 6(1)(c).
| What for | What data | Legal basis |
|---|---|---|
| Account and sign-in | Identifier from Apple or Google, or email address and password (the password is stored only by Firebase Authentication, encrypted — we never see it), email address (with Apple possibly a relay address), name, user ID, @handle; which version of the Terms of Use applied when you signed up in the app, and when (proof that the contract was concluded) | Contract; proof of the version: legitimate interest |
| Confirmation by SMS | Phone number and time. The number is kept in your sign-in account with Firebase Authentication (Google); our database only holds a check value (hash), so that one number can’t be used for many accounts. Google sends the SMS with the code. | Contract; protection against multiple and fake accounts (legitimate interest) |
| Profile | Display name, handle, picture, cover image, bio, links, interests, the country you live in (optional, shown as a flag next to your name; where you live, not where you come from), points, level, streaks, badges, followers | Contract |
| Private details | Date of birth, gender and request filter, emergency contacts (third-party data), travel preferences, home location, language, currency, notification settings, push tokens | Contract; emergency contacts: legitimate interest in your safety |
| “Locals' favorites” for restaurants | your home location (only if you have entered it) and your star ratings for venues in that city. Only our server matches the two, once a night. Afterwards the venue shows only a yes or nothing — and a yes only once at least 5 different people from the city have rated it well. We don’t store who was counted, and nobody can see it. | legitimate interest (better restaurant tips from an anonymous result). Objection: clear your home location in your profile or email privacy@triphar.com |
| Trips, Trippys, Stories, posts, reviews, comments, likes, photo albums, wishlists | your content, photos, videos, places, travel dates, travel companions, visibility | Contract |
| Messages | Text, photos, voice messages, shared content, read receipts | Contract |
| Tables you add and places with the bell | Tables you add yourself (place, date, time, number of people, the venue’s time zone, optionally the trip) — for the reminder beforehand and the question “How was it?” afterwards; places you follow with the bell (nobody but you sees them, not even the owner) | Contract |
| Meetups and safety | Requests, meetups, meeting point, check-in at the meetup, cancellation of a meetup (who, when and your reason if you give one; only the other person sees it), review after the meetup, trust score (the average of the stars from these reviews, counting only the latest review from each person who has reviewed you). If your trust score is below 4.0 stars after at least 3 reviewed meetups, you can’t request new meetups or create or join open meetups until it reaches 4.0 again. Our system decides this automatically from the reviews of your meetups; you receive a statement of reasons and can object. Meetups already arranged and requests from others to you continue. AUTOMATED DECISION WITHOUT A TIME LIMIT — PERMISSIBLE? LAWYER (QUESTION 46) | Contract; safety of participants (legitimate interest) |
| Location features | see Location | Contract (you switch them on yourself) |
| tripHARRY | see AI features | Consent |
| Moderation, reporting, suspensions | Reports, reasons, suspensions, appeals, statements of reasons sent to you, automated pre-screening of public texts; for removed content, a copy kept as evidence (content, time, who posted it), accessible only to our admin team | legitimate interest; obligations under the Digital Services Act (DSA); preservation of evidence: legal obligation (e.g. Art. 6 of Regulation (EU) 2021/784 on terrorist content) and legitimate interest |
| Suggesting details for places and reporting places | what you suggest (e.g. opening hours, cuisine), your account, time, the moderation decision; reports about places (no longer exists, wrong details, duplicate); internally, who on the moderation team hid or unhid a place | legitimate interest (correct details for everyone) |
| Protection against fraud with cashback and commissions | Indications of suspicious bookings and multiple accounts | legitimate interest; legal obligation (accounting) |
| Cashback, Credits, payouts | Commissions, balance, IBAN or PayPal address (stored in full as a record, accessible only for accounting); if a payout to you as a guide or creator is on hold (proof of age required, under 18, age not confirmed): since when, why, amount and deadline, and whether we have asked you to enter your birthday (until the payout) LAWYER (Q1, QUESTION 65): CHECK NEW “AGE NOT CONFIRMED”; for the complete trip bonus, whether your trip is completed, public and confirmed on site, its photos and your check-ins at its places (the result is kept with the cashback record of the booking) | Contract; retention: legal obligation |
| Bookings via partners | Forwarding to the partner with a random identifier per click — the partner receives neither your user ID nor your trip or the place and cannot link your clicks to each other. Only we store which identifier belongs to your account, your trip and the place (90 days after the click) | Contract (so that your cashback can be assigned) |
| TripHar+ and purchases | Purchase receipts from Apple, subscription status, Credits | Contract; retention: legal obligation |
| Original Creator (by invitation only) and Verified Creator | the badge or the status and since when (public on your profile); Original Creators are also Verified Creators, so the status is public as well. Until when the status and creator perks run, whether before the App Store launch, whether we extended automatically or manually and how often, whether our team has asked you for information (until when), whether we are not extending and on which day your status ends or ended (only for you); for Original Creators also whether you already had Verified Creator status before, together with the earlier period (so that we can leave it with you when we withdraw the badge). If you received the badge before 22 October 2026, your free TripHar+ appears there instead of the creator perks until the changeover; publicly only that it is currently running (for the gold badge). For awarding the status, approving a creator application and every extension, our server checks whether your age of 18 or over is confirmed; our team only sees yes, or why not, never your date of birth. For the extension, our server counts how many of your trips from the 3 and the 6 months before expiry are complete (public, completed, confirmed on site, with a destination, a cover image and at least 3 photos, checked in at all linked places, with your own public Trippy and your own Story on the trip; the same conditions as for the complete trip bonus); to do this it reads your check-ins at the trip’s places, whether one of your Trippys is linked to it and whether one of your Stories is attached to it. LAWYER (83, 2026-10-22): NEW — STORY ON THE TRIP FOR THE CHECK If there are at least 3 in 3 months or 6 in 6 months, it extends automatically. In the app you see your trips from this period, each marked as complete or with what is still missing (only you). LAWYER (R1, 2026-10-22): NEW — CHECK-INS AND TRIPPY LINK FOR THE CHECK Otherwise our team sees an overview of your activity by area: complete and public trips, public Trippys, Stories, shared trip links and bookings made through them, your own events, places added and accepted suggestions, each for the period and the one before it, with the date of your last activity (numbers only; reviews don’t count). You see the same numbers in the app. Internally: who on the team awarded and decided, and the text of any request for information sent to you; your reply to it goes to creator@triphar.com (a forwarding address to our support inbox, same retention period as support emails). If your status ends, the entry stays for another 12 months with the end date, so that we can decide on an appeal, match a new application (simplified until then) and pay out what you have already earned; after that we delete it, and the “Original Creator” badge on your profile stays. Deleted when the badge is withdrawn (Original Creator) and when you delete your account LAWYER (NO. 76, 2026-10-22): 12 MONTHS AFTER THE STATUS ENDS | Contract |
| Guide bookings | Guest, date, number of people, price, payment status; after a cancellation, the refund (amount, deducted Stripe fee and who bears it, identifiers at Stripe, who cancelled and whether because of a deleted account; also “I can't make it” without a refund; without payment, who cancelled and whether because of a deleted account) and, if the guide calls off the tour, the guide’s reason, which the guest sees; for the guide, the payout of their share after the tour (amount, status, date, payout identifier at Stripe) | Contract |
| Business profiles | Company name, team, claimed places; contact and verification details (not public); messages to people who follow the place (text, who on the team sent it, how many people it reached, reports) | Contract |
| Views and clicks for businesses | how often a place page was opened and website, phone, route, “Reserve a table” or menu was tapped — stored only as a number per place and day, without storing who. To prevent double counting (each person counts once per place, button and day), a shortened marker derived from your user ID, place, button and day, which we delete after two days. A business’s team is not counted on its own places. Only the business (and moderation) sees the numbers, and only from 5 upwards: if a day or the total for the last 30 days is below that, it only says “fewer than 5”, so that nobody can draw conclusions about individual guests. So that this can’t be worked out backwards either, the total of views only counts days with 5 or more, and we show the tapped buttons only in steps of five. We show the current day only on the following day | legitimate interest (businesses see whether TripHar brings them guests — from anonymous numbers) |
| Photo book, postcards (currently not available) | Photos, texts, delivery address, address book with third parties’ addresses | Contract; recipients: legitimate interest |
| Payout when you delete your account | Account holder, IBAN, amount, reference (record, without a link to your deleted account); a check value of your pickup code (not the code itself); optionally a contact email and the app language — only to let you know if the transfer comes back | Contract, also after the contract has ended (Art. 6(1)(b) GDPR); record: legal obligation |
| Warning before inactive accounts are deleted | The email address of your sign-in, language, when you were last active, when we warned you and whether the email was sent (not the address) | Contract; legitimate interest (you shouldn’t lose your account without noticing) |
| Data export | all data relating to your account as a file | legal obligation (Art. 15, 20 GDPR) |
| Operation and security | IP address, user ID and object IDs in server logs, technical counters (e.g. daily limits), device integrity check (Apple App Attest) | legitimate interest |
We use no tracking, no advertising tools, no third-party crash reporting and no contact syncing. Only when you pay by card or Apple Pay in the app (guide tours) does Stripe’s payment module record how it is used and check for fraud (see Recipients). We count how often place pages are opened and buttons are tapped — without storing who; a shortened marker against double counting is deleted after two days. Businesses only see these numbers from 5 per day or per 30 days. Others can search for you only by name and handle, not by phone number or email.
TripHar uses your location only while you are using the app — and only if you allow it. In the background only for route recording, if you switch it on for a trip yourself (see below).
| Feature | Accuracy | Who sees it | How long |
|---|---|---|---|
| Map, places nearby | precise, on the device only | nobody | not stored |
| Check-in at a place | we check whether you are at the place; afterwards only the place is stored, not your device’s position | depending on your choice: nobody, only your followers (excluding people you have blocked) or confirmed travellers (phone number confirmed), in each case only people who are currently visible to others themselves (anyone who is only visible to followers sees it only if you follow each other) | visible for 3 hours; the “Was there” record 24 months (longer as long as you have reviewed the place or it counts for a group trip) |
| “Let people find me in my city” / city presence | rounded to approx. 5 km | confirmed travellers aged 18 or over who are currently visible to others themselves (anyone who is only visible to followers, only if you follow each other) | ends after 24 hours or after 15 days without using the app |
| Share live location | precise (approx. 10 m) | only the people or the chat you choose | 15 minutes to 8 hours; the position is deleted at the latest 15 minutes after the end, the whole session after 24 hours |
| tripHARRY tips nearby | rounded to approx. 100 m | our AI provider (with your yes) | see AI |
| Checking the start of a trip and the meeting point | precise, only for the check | nobody; only “confirmed yes/no” is stored | not stored |
| Where review photos were taken | from the photo data | nobody; serves as proof of the visit | only the result |
| Where trip photos were taken | from the photo data, read only on your device | anyone who can see the trip only sees which of the trip’s destinations a photo belongs to | only the destination, never the location itself; we store the photo without location data |
| Record route automatically (on a trip, optional) | precise, with time, also in the background; on your device only | only you; if you share the trip route, a simplified route without the start, the end and places where you stayed longer (approx. 500 m) | until you delete the track, the trip or your account, or sign out |
| Emergency call button at a meetup | only to find the country for the right number: first the country of the meeting point; if that is missing, its coordinates; otherwise the position your device already knows (only with your location permission, at most 6 hours old, no new location fix). Apple’s geocoder converts the coordinates into a country. | nobody; Apple receives the coordinates for the conversion | not stored; the app remembers the country until it is closed |
Route recording (optional, on your device only). If you switch on “Record route automatically” for a trip, TripHar continuously stores your precise location with time and accuracy during the trip period (from the start day to the end of the end day; without an end date until you complete the trip, at most 30 days), even while the app is in the background. iOS shows this with the blue location indicator. Recording is off by default, and you can pause or switch it off at any time. The data stays on your device only: it is not transferred to TripHar or to third parties and is not included in your iCloud backup. It is only used to show you your route on the trip route. Others do not see your route in the app. If you share the trip route yourself as an image, story or post, an image of the simplified route is uploaded and treated like your other posts; TripHar leaves out the start and the end as well as the surroundings of places where you stayed longer (such as your accommodation or home) within a radius of about 500 m. You can delete the track per trip; when you delete the trip, sign out or delete your account, TripHar removes all tracks from the device. Legal basis: your consent by switching it on (Art. 6(1)(a) GDPR), which you can withdraw at any time by switching it off; storage on your device at your express request (§ 165(3) of the Austrian Telecommunications Act 2021, TKG). PRÜFEN (Anwalt): Rechtsgrundlage.
Mutual: You only see other travellers nearby while you show yourself. If you are visible to everyone, you see everyone who is visible to everyone, plus the “followers only” check-ins of people you follow; if you are only visible to your followers, you only see people you follow who also follow you (however they are visible). Our server compiles this list: it matches who you follow and who follows you, and only passes on these people. The same applies to “… is nearby right now” notices. That way nobody watches without being seen.
tripHARRY is an AI from our provider Anthropic (USA). Before he does anything for you for the first time, the app asks whether you agree. With your yes, the following goes to Anthropic: what you write to tripHARRY and the photos you send, your travel preferences and your home location, your trips and saved places, in companion mode your approximate location (approx. 100 m), what tripHARRY remembers about you (only with memory switched on), and for captions the place and keywords of your Trippy. Under its contractual terms, Anthropic does not use this data to train its models.
To protect the community from harassment, spam and illegal content, an AI from Anthropic automatically checks texts that become public or visible to others: reviews, Trippy texts, comments, status posts, Story texts and submitted events. It also translates and summarises public reviews (“What travelers say”). We store a review’s translations with the review, so they aren’t created again for every reader, until the review is changed or deleted. The AI only flags; whether content is removed is decided by moderation (see Moderation). A flagged review does not, however, count towards the Foodie badge and a venue’s dish tips. Requests to businesses are only pre-screened automatically if you have consented to the AI; if the AI clearly considers a request to be spam or off-topic, we show you a warning with the reason. If you send it anyway, the request goes to the business, and our team sees a copy to check the AI (subject, text, the AI’s reason). We delete it 12 months after the review, after 90 days if it is not reviewed, and immediately if you delete your account (see section 9). The business learns nothing about the warning. Before your first public text, we point this out to you in the app. You can object to this processing (privacy@triphar.com).
Transfer to the USA: on the basis of the European Commission’s standard contractual clauses (Art. 46(2)(c) GDPR) in the data processing agreement with Anthropic. Anthropic is not certified under the EU-US Data Privacy Framework (list at dataprivacyframework.gov, accessed on 19 October 2026: no entry, neither active nor inactive). DPF FOR ANTHROPIC NOT CONFIRMED — CHECK THE LIST AGAIN BEFORE PUBLICATION According to Anthropic, it deletes requests and responses within 30 days; if content violates its usage policies, it keeps them for up to 2 years.
When you sign up, we ask for your date of birth. It remains private and can only be changed via support.
Minimum age for the app: 18. If you enter a date of birth when signing up that makes you younger, you won’t get an account: we don’t store the date and delete the sign-up immediately. There is no block on the device. If it turns out that the holder of an existing account is under 18, we don’t delete the account but put it on hold until their 18th birthday: in that case we store the date of birth and the day on which the block ends. Until then the app only shows a notice; meetup features, location and push notifications are off, and the account doesn’t appear on the leaderboard. The profile and anything already shared remain visible. You can delete the account yourself at any time. If the date of birth is wrong, we only lift the block with proof: a photo of an ID card, passport or driving licence on which only the name and date of birth are visible. We look at it, delete it immediately afterwards and only store that proof was checked — no image, no face comparison.
Doubts about age: If someone tells us that you are not yet 18, we ask you first. If we still have justified doubts after that, we block the features where you meet strangers (Meetups, open meetups, “Nearby now”, visible check-ins, city presence, “Open to dating”) until you prove your age. Until then the following also applies: you only receive messages and trip invitations from people you follow; there are no 18+ events and no payouts; new trips are followers only by default. For this we only store since when proof has been required (private, until the proof is provided or until you delete your account), and send you the reason. You won’t find out who reported you. The proof works as above: a photo showing only the name and date of birth, deleted immediately. Legal basis: our legitimate interest in protecting minors when meeting strangers (Art. 6(1)(f) GDPR). LAWYER: CHECK THE LEGAL BASIS OF THE BLOCK WITHOUT A REQUEST FROM THE PERSON AND THE ART. 14 INFORMATION TO THE REPORTED PERSON
We only pass on data where this is necessary for the respective feature. Processors act on our instructions on the basis of a contract under Art. 28 GDPR.
| Recipient | What for | Role | Location |
|---|---|---|---|
| Google Ireland Ltd. (Firebase) | Account, database, files, server functions, push notifications, SMS confirmation, logs | Processor | Database and functions in Frankfurt (europe-west3) CHECK STORAGE REGION; sign-in, push and logs partly worldwide/USA. Google LLC (USA) is certified under the EU-US Data Privacy Framework (adequacy decision of the European Commission of 10 July 2023, Art. 45 GDPR; list at dataprivacyframework.gov, accessed on 19 October 2026: active, also for non-HR data); standard contractual clauses apply in addition. |
| Google (Sign in with Google) | Sign-in | Independent controller | USA possible |
| Apple Distribution International Ltd. | Sign in with Apple, push (APNs), purchases, maps and place search (including the country for the emergency call button), speech recognition (if your device can’t do it itself), device integrity check | Mostly independent controller | USA possible |
| Anthropic, PBC | tripHARRY, AI check, translation | Processor | USA (see AI) |
| Stripe Payments Europe Ltd. | Payments for guide tours (and postcards/photo books, currently not available), payouts to guides and creators, ID check (not yet active); when you pay in the app, also usage and device data of the payment module (fraud prevention, improvement of the module) | Partly processor, partly independent controller ROLE REGARDING THE PAYMENT MODULE DATA: INDEPENDENT CONTROLLER? — CHECK | EU/USA |
| Booking partners (e.g. hotels, flights, activities, restaurants) | your booking if you continue via a TripHar button; from us only a random click identifier, no user ID | Independent controllers | depending on the partner |
| PayPal or your bank | Cashback payout | Independent controllers | EU |
| Hostinger International Ltd. | Website triphar.com, support inbox, sending of service emails (warning before inactive accounts are deleted, returned payouts) DECIDE ON THE MAIL SERVICE — IF IT IS ANOTHER PROVIDER (SEE docs/MAIL_VERSAND.md), A ROW OF ITS OWN | Processor (Art. 28 GDPR) | Larnaca, Cyprus (EU); onward transfers outside the EU under standard contractual clauses CHECK THE CONTRACTING PARTY IN THE HOSTINGER ACCOUNT (MANUEL) |
| Prodigi (UK), POKAmax | Photo book and postcard printing (currently not available) | Processor | UK (adequacy decision) / CHECK |
Without any link to you, our server also retrieves weather (Apple WeatherKit; until the switchover Open-Meteo), open place data (OpenStreetMap via a paid Overpass instance of Geofabrik GmbH, Karlsruhe; until then via the public instance overpass-api.de), flight prices (Travelpayouts) and events (Ticketmaster). Only the location is sent, rounded to about 1 km for the weather and to about 100 m for the place search, never your account. We cache the responses briefly so that the same questions don’t have to be asked again: weather for at most one hour, place search 24 hours, without any link to an account; the place search under a checksum (hash) of the query instead of the location. GEOFABRIK AND WEATHERKIT ONLY ACTIVE ONCE ORDERED OR SWITCHED ON — THEN DELETE “UNTIL THE SWITCHOVER” The app loads images of imported events directly from the organiser’s server or from Ticketmaster; that server sees your IP address.
You receive notifications about your trips, messages, meetups and your account if you allow push notifications; you choose which ones under Settings → “Push settings”. Tips & inspiration (promotional notifications, e.g. a food tip in the city of your trip) are only sent if you explicitly say yes; we store when you agreed. If you follow a place with the bell, you receive at most 4 messages from the owner per month; the bell on the place switches them off. About your content: People who follow you and have switched on the bell for you receive a notification about your new content that they are allowed to see — e.g. a review (“… ate at …”), a Trippy, a shared or completed trip, or that you are travelling. People who follow you may also see such content in the weekly summary “You missed this”. We never mention content to anyone who is not allowed to see it (e.g. private trips). Push notifications are delivered via Apple and Google; they may contain your name and a short preview. Emails are only sent to you about your account (currently: warning before inactive accounts are deleted; and to the optional contact email if a payout comes back after you have deleted your account) — without advertising, without tracking pixels, without remotely loaded images.
You can report profiles, content and messages. Our moderation team reviews reports; you receive feedback once a decision has been made. If content of yours is removed, your account is suspended or something is reversed, we tell you why, whether it happened automatically and how you can object; we keep these statements of reasons for 3 years (see section 9). What happens automatically (e.g. the 7-day suspension after two confirmed reports from real meetups, or the pause on Meetups after a low trust score, see section 2) and what is always decided by a person (e.g. every permanent suspension) is set out in the Terms of Use, section 13.2. We keep a copy of removed content as evidence, which only our admin team can see (period in section 9). If there is a threat to life or safety, we inform the authorities (Art. 18 DSA).
Protection against fake reviews (legitimate interest: genuine reviews for everyone, Art. 6(1)(f) GDPR). So that only reviews from confirmed accounts count towards the average, our server records for each review whether the person’s phone number is confirmed (this is shown on your public profile anyway) and when it created the review. For the daily limit (at most 10 new reviews per day), it counts which reviews you have written today; the counter is overwritten every day and is deleted together with your account. A job checks every hour whether a place is receiving a suspicious number of reviews within a short time from new accounts or without proof of a visit; for this it reads when the accounts were created. It only reports the place and figures to moderation, no persons, and decides nothing. Anyone permanently suspended is on a list that only our server reads — for as long as the suspension applies; their reviews then no longer count.
If what the app does with your data changes, we update this policy. If the change affects a consent (e.g. a new AI provider), we ask you again in the app.
docs/DATENSCHUTZ_AUDIT.md; addendum from the preliminary legal review of
18 October 2026, docs/rechtspruefung/). Before publication: decide on or fill in the parts marked
in red, conclude the data processing agreements and have the text checked by
someone qualified to do so (the initial consultation of the WKO, the Austrian Economic Chamber, is free of charge).