F Favon
Anmelden

Privacy policy

Information about how Favon processes personal data.

Last updated: 2026-10-21

1. Controller

Sascha Schwarz Giesebrechstr. 59 45144 Essen Deutschland Email: schwarz.sascha@gmx.de

2. General principles

Favon processes personal data to provide accounts and requested functions (GDPR Art. 6(1)(b)), to operate and secure the service, prevent abuse and handle legitimate requests (Art. 6(1)(f)), and to meet legal obligations (Art. 6(1)(c)). Where consent is required for a specific operation, it is obtained separately.

Favon follows the principle “Places, not people”. Public user profiles, visitor lists, movement profiles and public attribution of contributions to individual people are not intended features. Nevertheless, use of this service, favourites and location-related entries can reveal sensitive information about personal interests or sex life; they therefore require particular protection.

3. Website access and technical logs

When Favon is accessed, technically necessary connection data may be processed, including IP address, access time, requested address, browser or device information and technical error data. These data are used for delivery, system security, troubleshooting and abuse prevention.

Where implemented, application security events use a hash derived from the source IP rather than storing the raw IP address. Technically necessary server and hosting logs may exist independently of these application events.

4. Community accounts and Telegram sign-in

Community users sign in through Telegram using OpenID Connect (OIDC). For account mapping, Favon stores only the stable numeric Telegram ID together with the necessary internal account, role, status and timestamp information.

Favon does not store the Telegram display name, username, profile photo or phone number as part of community sign-in. When Telegram sign-in is opened, your browser is redirected to Telegram, which processes technically necessary connection and authentication data under its own responsibility.

Administrators and the system owner may additionally use a classic email/password login. Passwords are stored only as hashes.

5. Contributions and interactions

If you submit a place, use favourites, submit reports or request support, Favon processes the necessary records with an internal account reference. Moderation decisions and notifications may also be linked to your account.

Favon does not publicly show who submitted or favourited a place. It offers no public user profiles, free-text reviews or user/place photo uploads.

6. Location functions

If you explicitly use a location feature, your browser requests permission. The current “Near me” function transmits coordinates to Favon as URL parameters to order places by distance. These coordinates may also appear in browser history, referrer information or server access logs. Favon does not intend to store a permanent location history linked to the account.

The “Add place at my location” function currently passes coordinates in the URL to prefill the submission form. The final place coordinates you submit are stored as place data.

7. OpenStreetMap maps

Favon uses OpenStreetMap-based maps. If map tiles are loaded directly from servers of the OpenStreetMap Foundation or another map provider, your browser connects directly to that provider and technically necessary connection data such as your IP address are transmitted.

8. Place and address search

Where Favon uses an external geocoding service such as Photon for place or address search, search terms or coordinates and technically necessary connection data are transmitted to that service. Such requests are made only in connection with the relevant search function.

9. Cookies, sessions and internal statistics

Favon uses technically necessary session and security cookies for sign-in, session handling and protection against abusive requests. Your selected language may also be stored.

Favon currently uses no advertising, marketing or external analytics trackers. No general consent or cookie banner is therefore planned for the browser storage currently required for technical operation.

For internal usage statistics, page views and selected feature events may be stored without user ID, raw IP address, session ID, persistent visitor identifier or fingerprint.

10. Support and reports

Support requests and reports contain the information you submit and the context needed to process them. For signed-in users, a request may be linked internally to the account.

Support and report data are retained only as long as needed for handling, traceability, abuse prevention or legal obligations and claims.

11. Retention and account deletion

Favon generally retains personal data only for as long as needed for the relevant purpose. Security events are cleaned up according to the configured technical retention period; completed self-service data exports are made available for a limited period and then deleted.

On final account deletion, personal account data are removed or irreversibly anonymised under the implemented deletion process. Factual place data may remain without public attribution to a person.

12. Your rights

Subject to the GDPR, you may have rights including access, rectification, erasure, restriction of processing, data portability and, where the requirements are met, objection.

You can exercise these rights by contacting the controller. Where processing is based on consent, you may withdraw that consent for the future.

Privacy requests can be sent to schwarz.sascha@gmx.de.

13. Right to complain

You may complain to the North Rhine-Westphalia Data Protection and Freedom of Information Commissioner (LDI NRW) or another competent supervisory authority.

14. Recipients and provision of data

Hosting and technical service providers may process connection and operational data where required. External providers of Telegram sign-in, map tiles and geocoding receive the technically necessary requests; see the respective sections above.

A Telegram identifier is necessary for community sign-in; currently an account cannot be used without it. Optional location access and voluntary submissions are not required merely to sign in.

15. Changes to this policy

Favon will update this policy when functions, service providers or legal requirements change. The current version is published on this page.