Privacy Policy — Pathemu

Last updated: 2026-11-14

You can read this text in Italian or English.

1. Who we are and scope

Pathemu (Android app and website, technical package ID com.drao.mapa) is a map of events and points of interest organised in groups. This policy explains what data we process, why, who we share it with and what rights you have.

The data controller (Art. 4(7) GDPR) is the operator of Pathemu, reachable at the contacts in this page and on the app’s store listing.

This notice is provided under Arts. 13 and 14 of Regulation (EU) 2016/679 (GDPR) and Italian Legislative Decree 196/2003 (Personal Data Protection Code), as amended by Legislative Decree 101/2018.

The app is not directed at children under 16. We do not knowingly collect data from children; if we find that an account belongs to someone under 16, we close it.

2. Data we process

Account: username, email address, password (stored in protected, non-plain form by the authentication provider), user ID. If you sign in with Google, we receive the identifiers Google needs for login (email and Google account ID).

Profile and groups: active group, roles (member, moderator, founder), memberships, join requests and join date.

Content you post: title, address, notes, link, category, expiry and coordinates of the event or point of interest; custom categories (filters) you create.

Device location: precise and approximate location only while you use the app and only if you grant permission, to centre the map and show distances. We do not track location in the background and do not keep a location history; if you create an event, the pin coordinates (which may match where you are) stay on that event.

Notifications: if you enable them, a device token (Firebase Cloud Messaging on the native app or a Web Push subscription in the browser) so we can send reminders 48 and 24 hours before events expire.

Activity: the date and time of your last app visit. It is used to manage groups automatically (see section 5).

Reports and blocks: if you report an event, we store the reason you write and a copy of the event (title, address, notes), so we can review it even if it is later edited or deleted. If you block a user, we store who you blocked so their events are hidden from you.

Deletions by moderators: when a moderator deletes someone else’s event, we keep a copy of the event and the names of its author and of whoever deleted it (moderation log), so we can reconstruct what happened in case of a dispute.

Group deletion requests: if the founder asks to delete a community, we store the request with the reason they wrote, so we can assess it.

Address and place search: while you type in the search or address fields, the text (after a short typing pause) and the centre of the map you are viewing are sent to the search service (Geoapify) to obtain suggestions.

Link previews: if an event contains a link, our server reads the linked public page to obtain a preview image and title. We do not store the image or the page content.

Technical data: UI language, usage and performance diagnostics via hosting services (pages viewed, load metrics), IP address and device information processed by providers as part of HTTPS traffic. To limit abuse (login attempts, password reset, link previews) we keep, for a short time, a counter associated with your IP address.

3. Purposes and legal bases (Art. 6 GDPR)

To provide your account, groups, the map and the features you request: performance of a contract (Art. 6(1)(b)).

To use your location and send notifications: consent (Art. 6(1)(a)), given through the system permission and withdrawable at any time from your device or app settings, without affecting processing already carried out.

Security, abuse and fraud prevention, rate limiting, moderation of reported content, automatic management of inactive groups and aggregate diagnostics: our legitimate interest (Art. 6(1)(f)) in keeping the service safe and working, balanced against your rights. You may object by writing to us (section 11).

To answer lawful requests from authorities and comply with legal obligations: legal obligation (Art. 6(1)(c)).

4. Sharing and providers

We do not sell your data, we do not show ads and we do not do commercial profiling. Data is shared only with the technical providers the service needs, within the limits below.

Supabase (database and authentication: accounts, profiles, groups, events, reports, notification tokens). It acts as a processor (Art. 28 GDPR) under a data processing addendum (DPA) incorporating the standard contractual clauses (Commission Implementing Decision (EU) 2021/914). Our project is hosted in: AWS eu-central-1 (Frankfurt, Germany / Francoforte, Germania — UE). Supabase states that the database, authentication and backups stay in the region chosen for the project. Details: https://supabase.com/legal/customer-resources/data-processing-addendum and https://supabase.com/legal/privacy-resources/data-residency-and-transfers-faq

Google (Google sign-in, if you use it; Firebase Cloud Messaging for Android push notifications). Google LLC participates in the EU-US Data Privacy Framework, which also covers Firebase Cloud Messaging; Google generally acts as a processor for end-user data we send it. Information: https://firebase.google.com/support/privacy and https://policies.google.com/privacy

Mapbox (map tiles and style). Your device contacts Mapbox directly to download the map: Mapbox receives your IP address and view data (the area shown) and acts as an independent controller. Mapbox states that it participates in the Data Privacy Framework and relies on standard contractual clauses where needed; data is served from infrastructure in the United States and cached elsewhere. Information: https://www.mapbox.com/legal/privacy

Geoapify (address and place search and suggestions, geocoding). The request starts directly from your device: Geoapify receives the text you type (including the address of an event you create), the centre of the map you are viewing and, as in any connection, your IP address and device information. According to its policy it keeps information only as long as needed to produce aggregated usage statistics and hosts its servers with Hetzner; it offers a data processing agreement under Art. 28 GDPR. Information: https://www.geoapify.com/privacy-policy and https://www.geoapify.com/data-processing-agreement/

Vercel (hosting of the site and APIs, which receive for example sign-in and password-reset requests, link previews and reminders; performance measurement and usage analytics). Vercel therefore sees the IP address and technical data of requests. According to Vercel’s documentation, its analytics does not use third-party cookies and provides aggregated data. Vercel runs globally distributed infrastructure, including in the United States, with the safeguards of its agreements (Art. 46 GDPR). Information: https://vercel.com/legal/privacy-policy and https://vercel.com/docs/analytics/privacy-policy

Linked sites in events (for example Instagram, TikTok, Facebook, YouTube or other sites): to show the preview your device downloads the image directly from the linked site’s servers, which receive your IP address and device information and act as independent controllers under their own policies. If you do not want this, do not open events that contain links to those sites.

Public authorities: only on lawful request and within legal limits.

5. Automated processing on groups

To keep groups tidy we automatically use your last-visit date and activity in the group: plain members of an open community who have been inactive for 180 days are removed from the group (not from the account); moderators inactive for 90 days go back to plain members; if the founder stays inactive for 180 days or leaves the group, the role passes to the longest-serving moderator or, if there are none, to a member chosen by tenure, recent activity and number of events posted. In time-limited communities all members leave on the date set by the owner.

In the app a band (Member, Active member, Moderator) based on your tenure and activity in the group is shown only to you; it is not visible to others.

These are not decisions producing legal effects or similarly significantly affecting you (Art. 22 GDPR): they only concern your membership of a group, which you can regain with a new invitation. If you think a removal is wrong, write to us and we will review it with human intervention.

6. Transfers outside the European Economic Area

Some providers (notably Google, Mapbox and Vercel) may process data in the United States or other non-EEA countries. Transfers rely on a European Commission adequacy decision, in particular the EU-US Data Privacy Framework decision (Commission Implementing Decision (EU) 2023/1795 of 10 July 2023) for participating providers, or on standard contractual clauses (Commission Implementing Decision (EU) 2021/914) and supplementary measures, under Chapter V GDPR (Arts. 44-49).

On request you can obtain information on the safeguards applied by writing to the contacts in this page.

7. Retention

Account, profile and memberships: while the account is active. A group membership ends if you leave, are removed or in the automatic cases of section 5.

Events: until you delete them, they expire (events with an expiry date are deleted automatically after it) or the group or the account of their author is deleted.

Notification tokens: until you turn notifications off, sign out or delete the account.

Anti-abuse counters associated with an IP address: for a very short time (windows of minutes or hours, with automatic clean-up of rows older than a day).

Reports and blocks: while needed to handle abuse or until the account of the event’s author or of the reporter is deleted. Moderation log: while the group exists or until the account of the event’s author is deleted. Group deletion requests: for the time needed to handle them and document the decision.

Providers’ technical logs and analytics: under their own policies, linked in section 4. Database backups may hold data for a limited time after deletion until overwritten.

We may keep some data longer only where the law requires it or to establish, exercise or defend legal claims.

8. Deleting your account

When you delete your account we delete your profile, memberships, notification tokens, the reports you sent, the events you created (including copies in any moderation log and reports) and your authentication user.

Events created by others that you only edited remain, but the reference to you is removed.

If you are the founder or a moderator of an open community, the role passes to another member; if you were the only member, the group and its events are deleted. Friends or catalogue groups you own remain without an owner. Custom filters you created stay in the group without your name.

9. Security

Traffic between the app, the site and providers uses HTTPS. Application data access is filtered by database rules (Row Level Security) based on the signed-in user and the groups they belong to; passwords are never stored in plain text; login attempts are rate-limited to counter abuse; administrative functions are restricted to a few authorised accounts.

No system is 100% secure. In case of a personal data breach likely to put your rights at risk, we notify the supervisory authority within the legal time limits (Art. 33 GDPR) and, where the risk is high, we also inform you (Art. 34 GDPR).

10. Cookies and local storage

We only store on your device what the service needs to work (Art. 122 of the Italian Privacy Code, implementing Art. 5(3) of Directive 2002/58/EC; the Italian Data Protection Authority’s cookie and tracking guidelines of 10 June 2021). In practice:

Sign-in session: cookies of the authentication service (Supabase) that keep you signed in and are renewed while you stay signed in.

Language: a cookie and a local-storage entry called NEXT_LOCALE that remember your chosen language (up to one year).

Notification reminder: a local-storage entry (push_prompt_dismissed_until) that remembers for 7 days that you closed the invitation to enable notifications.

Offline use (installable web version only, not the Android app): a service worker saves in the browser’s storage copies of pages, scripts, images and service responses, including those of events you viewed, to make the app faster and work without a connection. You can clear them from your browser settings.

Map (Mapbox): the map library stores an anonymous identifier in local storage (mapbox.eventData) and sends Mapbox technical statistics about map usage, also used to bill the service. We do not use it for other purposes. Mapbox’s rules: https://www.mapbox.com/legal/privacy

Analytics and performance (web version only): the Vercel tools described in section 4; according to Vercel’s documentation they do not use third-party cookies. They are not active in the Android app.

We do not use profiling or marketing cookies or advertising tools.

11. Your rights and how to exercise them

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20) and objection (Art. 21), and to withdraw consent at any time (Art. 7(3)), within the limits of the GDPR. We normally reply within one month (Art. 12(3)).

For questions, requests about your data or reports, email mapaapp11@gmail.com.

You can delete your account and associated data from Settings → Delete account in the app, or from this site’s Delete account page (/delete-account). This is permanent.

If you believe the processing breaches the law, you may lodge a complaint with the Italian Data Protection Authority (Garante per la protezione dei dati personali; Art. 77 GDPR; www.garanteprivacy.it) or with the supervisory authority of your country of residence, or go to court.

12. Android permissions

Internet: required for the app to work.

Location (precise and approximate): foreground only, to centre the map. We do not use background location.

Notifications: only if you enable them, for event reminders.

13. Changes

If we change this policy in a material way, we will update the date at the top of this page and, if the changes significantly affect you, notify you in the app too. The version in force is always the one published on this page.

Privacy Policy · Terms of Use · Delete account