Privacy policy

Last updated: 1 November 2026

Meet In Town helps you and your friends find a fair place to meet. This policy describes what data the app processes and what happens to it. The short version: there are no user accounts, no profiles, no advertising and no tracking — our server only keeps anonymous daily totals that cannot be linked to anyone. A solo search stores nothing. A shared meet stores a rounded location and a display name for about a day — up to about two days if the group settles on a place and keeps chatting — and your exact location only if you explicitly choose to share it.

Who we are

Pintumo UG, Eisenacher Str. 116, 10777 Berlin, Germany. E-mail: info@pintumo.com. Details are in the imprint.

Location data when you search

When you search for meeting points, the addresses or coordinates you enter — optionally including your device location, if you grant the permission — are sent to our server to compute candidate places and travel times. Our server forwards the coordinates to Google (Places, Distance Matrix, Directions) to obtain venues and travel estimates; Google's own privacy policy applies to that processing. For these searches our server does not store your coordinates: they are processed for the duration of the request and discarded with it.

Shared meets

A shared meet works differently, because several people contribute to it over time and it therefore has to be stored. When you create or join a meet we store, in our database: a rounded version of your location, the display name you type in (if any), your chosen travel mode, your votes, and an unguessable token that identifies you within that meet. There are still no accounts — that token is the only identity, it exists only inside that one meet, and it is not linked to you, your device or any other meet.

Your location is rounded to a grid of roughly 500 metres before it is stored. We do not keep the exact position you contributed. Other participants are never shown your location, your travel mode or your travel times — each person sees only the candidate venues, their own travel times, and the other participants' display names.

Sharing your exact location in a meet

Inside a meet you may choose to share your exact location with the other participants. This is off by default and entirely optional; nothing in the app requires it. While it is on, your precise coordinates are stored and are shown on the map to everyone in that meet. When you switch it off, the stored coordinates are deleted, not merely hidden — after that we hold only the rounded location described above.

Joining a meet in your browser

If you open an invite link without the app, you can join the meet on our web page instead. The page sends our server the same things the app does: the display name you type (if any), where you are starting from — either the location your browser lets the page read once, if you allow it, or an address you type — your travel mode, and later your votes and the messages you write. All of it is stored, rounded and deleted exactly as described for shared meets above.

If you type an address, the page sends what you typed through our server to Google (Places) to find matching places and their coordinates; our server passes it on for that one request and neither stores nor logs it. So that matches near the meet come first, our server adds the meet's approximate area — the average of the participants' already rounded locations — to that request; it is never shown to you or anyone else. You pick one of the results, and only its coordinates are used to join.

Your browser keeps, in its local storage on your device: your participant key for that meet (the token that identifies you in it, so you can come back to the meet), the meet's expiry time, the last display name you used, and any participant whose messages you chose to hide. None of it is sent anywhere except the key, which goes to our server with each request for that meet. The page deletes the stored key and expiry once the meet has expired, the next time you open an invite page in that browser; you can also clear it at any time by clearing the site's data in your browser.

The page, its scripts, styles and fonts all come from our own server; it sets no cookies and uses no analytics, maps or font services. The only things it loads from a third party are photos of the suggested venues, which your browser fetches from Google's servers — so, as with any image, Google receives your IP address and browser details for that request.

Messages in a meet

A meet has a chat. What you type there is stored with the meet and shown to the other participants of that meet — nobody else — together with the display name you were using when you sent it. Messages are deleted with the meet, like everything else attached to it.

Reporting and hiding

If someone writes something objectionable, you can report that message from the app. A report stores, separately from the meet so that it survives the meet's deletion: the text of the reported message, the time of the report, an optional reason you may type, and the in-meet tokens of the message and of you as the reporter. We use it only to review the report and act on abuse. Reports are deleted automatically after 30 days. This is the one thing in this policy kept longer than a meet; it still involves no account, and those tokens stop referring to anything once the meet itself is deleted.

You can also hide all messages from a participant. Hiding happens entirely on your own device — the choice is never sent to us, the other person is not told, and you can undo it at any time.

Notifications

If you turn notifications on for a meet, your phone gives us a push token — an identifier that Apple or Google assigns to this app on your device — and we store it with your entry in that meet. We use it for four things only: to tell you when someone joins, when someone writes in the chat, when everyone has voted (if you started the meet), and when the place is decided. The token is not linked to you, not linked to any other meet, and is deleted with the meet — or earlier, if you turn notifications off for that meet or your phone reports it invalid. The notification itself carries the meet, the event, the display name of whoever acted, a short preview of the message or the name of the chosen place; the text you see is composed on your phone, in your language. Delivery goes through Apple's or Google's push service; on Android that is Firebase Cloud Messaging, which we use with analytics switched off. Notifications are optional: everything they announce is also shown in the app.

How long meets are kept

A meet nobody settles expires 24 hours after it is created. When the group does settle on a place, the meet gets one more day from that moment, so people can keep arranging the evening in the chat after the place is fixed; it then expires like any other.

Expired meets are deleted automatically, together with everything attached to them: participants, rounded locations, any shared exact locations, display names, push tokens, candidate lists, votes and messages. Deletion runs at least hourly, so nothing survives more than about two days — the single exception being a reported message, which is kept for up to 30 days as described above.

Your own phone keeps a copy of the places you saw and the messages in your meets. That copy never leaves the device, is not readable by us, and is deleted when you remove the meet from your Recent list or delete the app.

Anyone with the link

A meet is reached through an invite link containing an unguessable token. Anyone who has that link can join the meet and will then see the display names of the people in it, and the exact location of anyone who has switched sharing on. Share invite links only with people you intend to meet.

Who processes your data

Our servers and database run in Amsterdam, in the European Union, on infrastructure operated by Fly.io, Inc. (United States). Venue, address and travel-time lookups are performed by Google, in the United States. Push notifications, if you turn them on, are delivered by Apple (Apple Push Notification service) or Google (Firebase Cloud Messaging), also in the United States. Where data reaches a US company, the transfer relies on the European Commission's standard contractual clauses. Subscriptions are handled by Apple or Google as described below. We use no other processors, and no advertising, analytics or tracking services of any kind.

Anonymous daily counts

To know whether Meetin works for people, our server keeps a handful of daily totals: how many invite pages were opened, how many meets were created — and how many of those were created on a device that had joined someone else's meet before (the app sends this as a simple yes or no when you create a meet; it is not stored with the meet) — how many people joined from the app and from the web page, how many meets were decided, how many chat messages were sent, and how many address lookups the web page made.

Each of these is a single number per day and nothing else. A count carries no meet, no participant token, no device or advertising identifier, no IP address, no browser details and no location, so it cannot be linked to you, to your device or to any meet. Because the counts contain no personal data, they are kept indefinitely.

Data stored on your device

Your search history is stored locally on your device so you can repeat searches. On iOS it also syncs between your own devices through your personal iCloud account. It never reaches our server, and deleting the app deletes it.

For shared meets, your device also keeps the tokens that identify you in the meets you have joined, and a local list of those meets showing the participants' display names and the place that was chosen. This list contains no locations. It stays on the one device, is not synced, never reaches our server, and is removed when you delete the entry or the app.

Subscriptions

Premium subscriptions are processed entirely by Apple (App Store) or Google (Google Play). We receive no payment details and no identity from either; the app only learns whether an active subscription exists.

What we do not do

No accounts. No advertising. No analytics or tracking SDKs. No sale or sharing of personal data. The only servers your data reaches are ours and — for the searches and address lookups you actively make, and the venue photos the web page shows — Google's, as described above, plus Apple's or Google's push service if you turn notifications on.

Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction of processing, data portability and objection, and the right to lodge a complaint with a supervisory authority.

For searches, we hold nothing once the request completes, so these rights are satisfied by design. For a shared meet, the data described above exists until the meet is deleted; you can erase your own contribution at any time by switching off exact location sharing and leaving the meet, and everything is deleted automatically within about two days — or, for a reported message, within 30 days, which we keep on the legal basis of our legitimate interest in preventing abuse (Art. 6(1)(f) GDPR). Because meets are anonymous, we have no way to find your data from your name or e-mail address — if you want to exercise a right over a specific meet, send us its invite link at info@pintumo.com. The legal basis for processing in a meet is your consent (Art. 6(1)(a) GDPR), given by creating or joining it, and separately for exact location sharing by switching it on; you may withdraw either at any time.