How does Mizi use your data?

This notice describes Mizi guest accounts, the mobile app, digital menus, orders, reservations and support. Each restaurant receives information relevant to providing its own order or reservation service.

Registered address: Abasoft GmbH, Rudolfplatz 3, 50674 Köln, Germany. The product display name is Mizi. Support mailbox activation is still pending.

With your consent, the digital-menu contact form sends your name, phone, venue name and type, menu language and page path to the Mizi sales inbox to handle your request. Some demonstration forms only prepare information locally and transmit nothing; each form’s result distinguishes these states.

Depending on your chosen sign-in method, we process your phone number or email, display name, account identifier and information needed to verify access. Passwords are stored as hashes.

Apple or Google sign-in provides a verified provider identifier and the information you choose to share in that flow. The token needed to revoke Apple access is stored encrypted. Device and session information supports secure access and abuse prevention.

Orders, items, prices, payment status and wallet records support fulfilment and dispute handling. Delivery also requires your address and chosen delivery point.

Saved addresses, favorites, reviews, support messages and notes you submit are associated with your account. Published review text is visible to other people.

Payment card entry takes place with the payment provider; Mizi processes transaction references and status. Do not include passwords, verification codes or card details in support messages.

Nearby restaurant searches send coordinates rounded to three decimal places to the search service. Your selected delivery point can be more precise and linked to an order.

Nearby menu reminders require your choice and the relevant permission, and can use background location while the app is closed. Stored-region checks run on your phone. Declining permission does not block menu browsing.

Maps, address search and routing use map services; map providers also receive network requests, including IP addresses and requested map-tile areas.

The camera reads menu and table QR codes. Scan images are not stored as camera images to build a user profile.

Installation identifiers and push tokens support relevant notifications. You can disable notifications in device settings.

Secure sessions, language, preferences and menu caches are stored locally. The website stores language in a cookie and theme in browser storage. Sign-out and account deletion clear personal local data; public menu caches are not account data.

Restaurants and authorized staff receive information relevant to their services. Authorized support staff handle support requests.

Hosting, backups, Apple and Google sign-in, notifications, email, SMS, maps and payment providers participate depending on the features used. The final processor list and processing locations will be completed before public release.

The current app does not implement cross-app advertising tracking or advertising pixels. Infrastructure and SDK providers may process technical data needed to provide their services.

After account deletion, profile and contact details, addresses and personal preferences are erased or anonymized, and previous sessions are invalidated. Necessary financial and security records are retained separately.

Restricted, encrypted backups may contain older data until their retention period ends. A separate erasure ledger reconciles completed deletions before a recovered service is reopened; immediate erasure from every historical copy is not claimed.

The exact retention periods and grounds for financial, audit and contact-request records still need to be specified in the final notice.

Deletion requires signing into the same account, recent authentication when needed, and explicit confirmation. Active orders or reservations, wallet balances, pending payments or sole restaurant ownership must first be resolved.

Sign-in grants and sessions are invalidated. Apple revocation is queued and retried during provider outages. An offline restaurant device receives erasure when it reconnects and synchronizes.

You can correct editable account details, change location and notification permissions in device settings or delete your account. Use in-app support for access, correction or other data questions.

[email protected] is the planned support address; delivery is not confirmed until mailbox activation is verified. The response process will be completed before public release.