Privacy Policy: Megálló Widget
Effective date: 2026-11-03
Last updated: 2026-11-03
Version: ca2a8223
This policy explains personal data processing in the Megálló Widget (FutárWidget) application for iOS and Android. The
app displays public transport departures, maps, favorite stops, home-screen widgets and journey planning aids. Transport
data source: BKK Zrt., CC BY 4.0, subject to the applicable data set terms. This is not an official BKK application.
1. Controller and contact
Controller: Botond Somogyi (individual developer)
Contact email: devsolvs@gmail.com
Privacy requests: devsolvs@gmail.com
You may send questions and privacy rights requests to this email address. No data protection officer is named unless the
law requires one. To verify before launch: postal contact information and whether a DPO is required.
2. Information processed
| Data | Storage / recipient | Purpose | Retention |
|---|---|---|---|
| Favorite stops, widget configuration and appearance settings | On-device | Favorites, widgets, personalization | Until deletion or app removal, subject to device backups |
| Saved places, routes, routines and local notification history | On-device | Planning and local reminders | Until deletion or app removal; history holds up to 10 entries |
| Last known location (rounded to approximately 10 m) | On-device shared app/widget storage | Nearby widget | Replaced with a new measurement; no longer used after 60 minutes |
| Current or map-selected coordinates | BKK FUTÁR / BKK geocoder when requested, over HTTPS | Nearby stops, search, routes | No app location history; provider logging retention must be verified |
| Address search text and journey endpoints | BKK geocoder / routing, over HTTPS | Search and planning | No separate server-side storage by us; provider retention to verify |
| Visible map area and technical connection data (including IP address) | VersaTiles | Map tiles, fonts and icons | Provider retention to verify |
| Optional crash diagnostics | Google Firebase Crashlytics | Diagnose crashes and unexpected errors | 90 days |
| Optional product analytics | PostHog EU Cloud | Understand app use and reliability | 1 year |
Favorites and settings are not uploaded to an operator-controlled backend because the current app has no such backend.
However, individual API requests are sent to the third-party services described below. **Location information does not
always remain only on the device.**
3. Location
Location is requested when needed for nearby departures or when you manually refresh a nearby widget. On iOS the widget
may request separate location access; otherwise it may use a sufficiently recent location stored by the main app. Shared
app and widget storage does not itself enable iCloud sync. There is no continuous background tracking or
location-history profiling.
Coordinates are included in relevant HTTPS requests to BKK FUTÁR. A manually selected map position is used for the
request and is not retained as a location history. You can revoke location permission in your device settings; favorites
and map browsing remain available without it.
4. Third parties and data sharing
- BKK FUTÁR: stop and departure queries, optionally including location coordinates and technical connection
information.
- BKK geocoder / routing: address queries, selected coordinates and journey endpoints. Saved favorites and routines
are not uploaded as collections.
- VersaTiles: map tiles, fonts and icons. The requested tiles can reveal the approximate displayed area and requests
may expose your IP address.
- Google Firebase Crashlytics: only after separate opt-in for crash diagnostics. Technical data may include device
and OS details, app version, crash stack, error categories, installation or diagnostic identifiers and, for native
crashes, exception messages.
- PostHog EU Cloud: only after separate analytics opt-in. May process pseudonymous randomly generated identifiers,
session identifiers, device and app context and the specific events listed below. The intended EU ingestion endpoint
is eu.i.posthog.com.
We do not display ads, use advertising identifiers or engage in cross-app advertising tracking as defined by Apple.
Provider roles, subprocessors, server logs and actual retention periods **must be verified against production contracts
and settings before launch**.
5. Optional diagnostics and analytics
Send crash reports (Firebase Crashlytics) and Anonymous usage statistics (PostHog, in practice pseudonymous) are
separate controls. Both are off by default and can be enabled or withdrawn independently during onboarding or under
Settings → Privacy. The legal basis for each is consent, GDPR Article 6 (1)(a).
PostHog events are limited to screen_view, widget_opened, aggregated refresh_success and refresh_failed, and
battery_saver_activated. The planned SDK setup disables autocapture, session replay, person profiles, IP-based
geolocation and advertising tracking. Automatically added technical attributes may include device model, OS/app version,
language, timezone, session ID and network characteristics.
Our manually sent telemetry events are designed to exclude GPS coordinates, stop IDs, favorites, saved routes, API keys,
tokens, full URLs, request headers or bodies. Because crash SDKs also capture native errors, not every exception message
can be guaranteed to be excluded. The iOS widget extension does not independently initialize these SDKs.
Withdrawing consent stops planned future collection and clears unsent on-device telemetry as implemented. **Previously
transmitted data is not necessarily erased automatically from the providers' systems.** You can request further deletion
as described in section 9.
6. Legal bases
- Local favorites, widget configuration and requested core features: GDPR Article 6 (1)(b), insofar as processing is
necessary to provide a service under an applicable contractual relationship. Legal suitability must be verified before
launch.
- User-requested location and routing queries: the applicable basis for provision of the requested service, as
above, separately from OS location permission; final legal assessment required.
- Crashlytics and PostHog: separate consent for each, GDPR Article 6 (1)(a).
- Responding to privacy requests: compliance with applicable legal obligations, GDPR Article 6 (1)(c) where
relevant.
Operating system location permission does not by itself constitute GDPR consent for all related processing.
7. International transfers and security
Connections to the providers use HTTPS. PostHog EU Cloud is intended for EU-region processing, which alone does not rule
out all international access. Where Google's services involve transfers outside the EEA, the applicable adequacy
decision, relevant framework and/or Standard Contractual Clauses and service agreements need to be checked.
On-device data is protected by OS storage and permission controls. The present functionality does not have an app
account system or an operator-hosted profile database.
8. Retention and erasure
You can delete favorites and saved items within the app. Uninstalling the app generally removes its local data, although
operating-system backups can follow different rules. You may withdraw telemetry consent under Settings → Privacy.
Provider-side erasure of previously transmitted data is subject to available identifiers, provider policies and legal
retention obligations. Send requests to devsolvs@gmail.com.
Firebase, PostHog, BKK and VersaTiles retention details must be cross-checked with production settings and agreements.
9. Your rights
Subject to the GDPR's conditions, you may request access, rectification, erasure, restriction and, where applicable,
portability and objection. Consent can be withdrawn at any time without affecting earlier lawful processing. We normally
respond within one month, subject to extensions permitted by law.
You may lodge a complaint with the **Hungarian National Authority for Data Protection and Freedom of Information (
NAIH)** at https://www.naih.hu/ , or another competent supervisory authority, and may seek judicial remedies.
10. Automated decisions and children
We do not use solely automated decisions producing legal or similarly significant effects under GDPR Article 22, or
profiling for that purpose. The app is not specifically directed to children. To verify: final age rating and any
child-specific functionality.
11. Notifications and future features
Remote push notifications are planned but are not represented here as currently active data processing. Before
launch of push functionality, we will update this notice with details of device tokens, recipients, retention and legal
bases. Device-local notifications may rely on OS permissions.
12. Changes
Updates to this notice will be published here. Where required, material telemetry changes will lead to renewed consent.
Production behavior and actual provider terms must be checked against this policy before publication.