Dishory is your digital journal for dishes and restaurant visits. Here you can learn which data is processed when you use the Android app, web app, and our homepage.
Dishory is intended for people aged 16 or older. In the Android app, we ask you to confirm your age before sign-in; we do not collect your date of birth for this purpose.
Last updated:
1. Controller and contact
The person responsible for processing personal data when operating Dishory is:
Marc Ueberschaer
Traminerweg 7
68309 Mannheim
Germany
When you sign in, an account identifier and email address are processed in particular. Dishory supports Google sign-in and, for accounts already enabled for it, sign-in with email and password through Firebase Authentication. Google sign-in may also provide your name and profile photo. We also process your Dishory username, profile details such as city and display name, and your visibility settings. This data enables sign-in, account management, and display of your profile. Passwords are not stored in journal entries or Dishory profiles.
Dishes, visits, and photos
We store the dishes, ratings, prices, visit times, restaurant associations, public and private notes, and uploaded photos that you enter. This enables your journal, synchronization across devices, and the sharing features you use.
Social features
Follow relationships, follow requests, invitations to shared visits, shared entries, and saved-item entries are processed so that you can find other profiles, discover content, and share visits with friends.
Food preferences
You may voluntarily provide dietary choices, dietary rules, allergies, avoided ingredients, and taste preferences. Allergies may be health data; dietary rules may reveal religious beliefs. You can set their visibility in your profile settings.
Location and search
When searching for nearby restaurants and using the map, an approved device location, search text, and map areas may be processed. Saved visits may include the address and coordinates of the associated restaurant.
Technical data and notifications
Accessing the service generates technical data such as IP address, browser or device information, and request times. If push notifications are enabled in the Android app or a supported web browser, a delivery token and its association with your account are also processed.
In the Android app, providing allergies and dietary rules is voluntary. Before saving these details, we ask for your explicit consent. They are private at first; sharing them with followers or other Dishory users is a separate choice. You can withdraw consent and delete the sensitive details in food preferences without removing ordinary preferences. The consent version and timestamp are stored. Temporary migration archives of details provided before the change are accessible only to the account owner; they expire 30 days after migration and are then deleted asynchronously by Firestore.
3. Visibility and sharing
Dishory distinguishes private content, content for followers, and community posts. What other users can see depends on the feature and your settings. Profiles are public under the current default setting; you can change your profile’s visibility.
Journal entries as community dishes
Dishory makes a separate community version of eligible restaurant-visit journal entries available if the entry has been shared with the community. These community dishes help other Dishory users discover dishes and restaurants. Restaurant entries with photos are generally created as community posts; home-cooked dishes are not added to this community collection.
The community version includes, in particular, the dish, rating, price if provided, restaurant and its location, visit day, public note, and processed photos. The author’s name is not displayed on the community card. Private notes and the profile photo are not included in this version.
‘Without a displayed author name’ does not currently mean complete anonymization: community posts remain technically linked to a user identifier and the original entry. Free text and image content can also reveal people or places. Do not share confidential information about yourself or others in public fields.
Shared visits
For shared visits, selected entries and photos may be passed on to invited users. Other users may save shared content outside Dishory. Control over those copies is limited.
4. Location, photos, and permissions
If you use a location feature, Dishory may process your current location after your device or browser grants permission. Location features are intended for use while the app is open. You can revoke location access in your device or browser settings.
When importing selected photos, capture time and existing GPS metadata may be read to suggest an association with a visit. The Android app may need access to location metadata of selected media for this purpose.
For community photos, the server creates new image files without copying the original EXIF metadata. The visible image content and associated restaurant details remain unaffected.
You can turn off notifications in your device or browser settings. Without location or notification permission, the features that depend on them are limited.
5. Service providers and data transfers
Google and Firebase
Dishory’s Firestore database is set up in europe-west3. Firebase Authentication processes sign-in data in US data centers. Storage for uploaded images is in us-central1; server-side functions run in us-central1, us-east1, and europe-west3. Processing therefore also takes place in the United States. A separate backup store is located in the EU.
Dishory uses Firebase Authentication for sign-in, Cloud Firestore for stored app data, Cloud Storage for images, Cloud Functions for server-side processing, and Firebase Hosting for the websites. Firebase Cloud Messaging is used for push notifications in the Android app and supported web browsers. If you voluntarily enable it in the app settings, we also use Google Analytics for Firebase to understand pseudonymous usage events such as feature areas viewed and dish entries created. Dish names, notes, and precise restaurant locations are not sent as Analytics event data. The choice is stored on the relevant device and can be changed there at any time. Google also processes technical data to provide and secure these services.
Google sign-in and restaurant search through Google Places also use Google services. Search terms and, for nearby searches, location coordinates may be sent to Google. A Google Maps link you open takes you to a separate Google service.
Our support mailbox is operated by IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany. For our 2026 contract, the data processing agreement is part of the IONOS general terms and conditions.
OpenStreetMap
The map loads map tiles from tile.openstreetmap.org. Place search uses nominatim.openstreetmap.org. Your IP address and technical request data, as well as requested map areas or entered search text, are sent to OpenStreetMap services.
Google services may process data outside the European Economic Area; image storage and some server-side functions are explicitly configured in US regions. For transfers to appropriately certified US companies, Google describes the EU–US Data Privacy Framework. For other restricted transfers, the applicable Firebase terms or the Google Cloud Addendum provide for appropriate transfer solutions, including EU standard contractual clauses. The linked terms and clauses are available there; you can also request a copy of the applicable safeguards from our privacy contact.
6. Homepage and local storage
When you visit the homepage, Firebase Hosting processes technical connection data, including your IP address, to deliver and secure the website.
The homepage uses locally served styling, icons, and a map illustration, as well as system fonts. Merely visiting these pages does not load additional presentation resources from third-party servers.
The web app uses local browser storage and IndexedDB to retain sign-in status, settings, drafts, and cached content. ‘Clear all local data’ in the app clears local app data but does not delete your account or server-stored content.
The app stores information on your device for sign-in, language settings, drafts you create, and offline access you choose. Where this is strictly necessary for the feature you expressly request, access does not require separate consent under Section 25(2)(2) TDDDG. Usage analytics is enabled only after your separate consent.
7. Legal bases
For sign-in, account management, your journal, and the social features you use, we process the data needed for those features under Article 6(1)(b) GDPR. This also covers the restaurant and map search you request and notifications you enable. For map tiles, Google Places, and Google sign-in, the providers named above receive the data needed for the respective request.
Voluntarily providing allergies and dietary rules is based on your consent under Article 6(1)(a) GDPR. Where this reveals health data or religious beliefs, we also rely on your explicit consent under Article 9(2)(a) GDPR. Voluntary usage analytics is likewise based on Article 6(1)(a) GDPR and, where information is stored on or read from your device, Section 25(1) TDDDG. Usage analytics remains disabled without this consent.
Technically necessary delivery and security of the app and websites, prevention of misuse, operational logs, and backups are based on Article 6(1)(f) GDPR. Our interest is reliable operation protected against misuse.
The required sign-in details are necessary for an account. You may omit optional profile details. You may withdraw consent for the future at any time; this does not affect the lawfulness of processing before withdrawal.
8. Retention and account deletion
We store account data, entries, and images while your account exists and the relevant feature is used. You can delete individual content earlier. Following a verified account deletion request, we process the deletion without undue delay. Data exceptionally needed to meet a legal obligation or establish, exercise, or defend legal claims is retained only for that purpose and the necessary period.
For the global Cloud Logging buckets we checked, standard logs are retained for 30 days and the mandatory audit bucket for 400 days. Firebase describes further service-specific deletion periods in its privacy information; after Firebase Authentication account deletion is initiated, data may remain in live and backup systems for up to 180 days.
Our cloud backups become eligible for automatic deletion at 30 days of age. Execution is asynchronous; deleted objects then remain recoverable in the backup bucket for seven more days. Deleted objects in image storage also have a seven-day recovery period. Manual local exports are created only for backup or maintenance and are deleted when no longer needed for that purpose. After a restore, we recheck deletion requests before returning data to normal operation.
Delete your account and associated data
You can request deletion of your Dishory account and associated data by emailing support@dishory.de . The account deletion page describes the information required and how your request is verified. This option is available even without the app installed.
After verifying that the request belongs to your account, we process it manually. Deletion covers your sign-in account, profile, own entries and images, personal community derivatives, follow relationships, invitations, and delivery tokens. We retain community posts only if they have first been genuinely anonymized and checked; otherwise we delete them. Entries already copied by other users into their own journals may remain as their own entries where links to your account and personal content about you have been removed. We cannot directly delete copies other users have saved outside Dishory. Signing out or clearing local data does not replace account deletion.
Contact form and support requests
When you use our contact form , we process your email address, the category of your request, subject, message, and, if provided, your name to handle and answer your request. The data is transmitted through a Firebase Cloud Function in europe-west3 and over an encrypted SMTP connection to our IONOS support mailbox. The message content is not additionally stored in Firestore.
To prevent misuse, we use short-lived sending counters and an identifier derived from your IP address using a secret key. The raw IP address is not stored in these counters. The counters have a one-hour expiry time; Firestore deletes them asynchronously. Technical logs of the services involved are separate from these counters.
For requests concerning a contract or steps taken before entering one, processing is based on Article 6(1)(b) GDPR; for other requests and misuse prevention, it is based on Article 6(1)(f) GDPR. Our legitimate interest is answering requests and operating the contact form securely. Information remains in the support mailbox for as long as needed to handle the request or to meet statutory retention obligations.
9. Your rights
Subject to the legal requirements, you have the right to access, rectification, erasure, restriction of processing, and data portability. Where processing is based on legitimate interests, you may object for reasons relating to your particular situation. You may withdraw consent for the future.
For privacy requests, use the privacy contact above. You can also lodge a complaint with a data protection supervisory authority, in particular in the member state of your habitual residence, workplace, or the place of the alleged infringement.
10. Changes to this policy
This policy is updated when features, data processing, or legal requirements change. The version date helps you identify changes.