Privacy for the Zackisch platform
Information for merchants, guests, staff, support users and partners. Updated 5 November 2026. Unknown provider and process details are marked as editable fields.
Controllers and scope
For Zackisch’s own contract administration, account security and communications, the controller is Selim Eser, trading as Zackisch, Musterstraße 1, 12345 Musterstadt, Germany. Contact: [email protected]. [Add a data protection officer if appointed.] These notices cover merchant accounts, guest orders, staff access, support and the partner programme. Separate website notices cover the marketing website.
Restaurant and Zackisch
The restaurant determines its sales, order fulfilment, staffing and tax records. Its identity appears during ordering. Where Zackisch processes its data solely on instruction, Zackisch acts as a processor under a separate agreement. Zackisch’s independent purposes are distinct. [Confirm the final allocation of roles, including any joint controllership, against the actual agreements.]
Merchant account and setup
Data includes name, email, sign-in and verification data, permissions, region, business and contact details, menu content and uploaded venue images. Contract and setup steps may be recorded with timestamps. This supports the account and agreed software service, generally under Article 6(1)(b) GDPR; for employees or representatives of legal entities, point (f) supports administering the business relationship. Required fields are necessary for setup.
Guest orders and confirmations
Guest ordering does not require a Zackisch account. Data includes venue, table or pickup, items and options, quantities, amounts, tips, timestamps, order number and order, payment, refund and POS-recording status. The restaurant and authorised staff need this information to fulfil the order. An email address for a confirmation is optional and is not marketing consent. Order fulfilment generally falls under Article 6(1)(b) GDPR; legally required records are handled separately under point (c).
Payment processing with Stripe
Payments are processed through Stripe in the connected merchant account. Zackisch receives necessary payment references, amounts, status and billing information. Full card numbers and card security codes must not be entered into Zackisch forms, tickets or logs. Stripe processes data for payment services and its own legal obligations under its privacy notices. [Complete the applicable Stripe entity, account configuration, legal bases and international processing from the actual agreements.]
Staff, sessions and security
Session and permission data is processed for paired staff devices and signed-in users. POS acknowledgements and privileged changes may record the actor and time. Purposes include attributing authorised actions, preventing abuse and troubleshooting. Zackisch relies on Article 6(1)(f) GDPR for its own security purposes; the restaurant determines the legal basis for its employee data. [Add the security-log retention period and any further employee notices.]
Support and internal handling
Tickets contain contact and, where relevant, business details, category, subject, messages, handling status and uploaded attachments. Customer replies and internal handling notes are distinct message types. Authorised support staff use necessary information to assist and follow up under Article 6(1)(b) or (f) GDPR, depending on the enquiry. Submit only necessary information, never card secrets or unsolicited identity-document copies. Retention after closure: [add period and exceptions].
Newsletter and partners
Newsletter data includes email, language, region, signup source and confirmation and unsubscribe times. Optional subscription is separate from contract and order messages. Newsletter delivery is based on consent, withdrawable through the unsubscribe process at any time. [Add proof and suppression-list periods.] The partner programme processes contact, contract, attribution and commission data for contract performance and required accounting under Article 6(1)(b) or (c) GDPR.
Browser storage
The merchant app uses the zakkig_session sign-in cookie with a configured maximum age of 30 days. Selected language is stored in NEXT_LOCALE and language-storage; region in zackisch_region and zackisch-region-storage. The two preference cookies have a configured maximum age of one year; local-storage values remain until cleared or overwritten. Staff and support areas use separate sessions. The guest cart is held in the current app state. [Complete the inventory of other session and Stripe storage with actual lifetimes.] Strictly necessary access falls under section 25(2) TDDDG; optional access needs separate assessment and, where required, prior consent.
Providers and transfers
Technical services include Cloudflare for web delivery, Convex for backend and storage, Stripe for payments and [SMTP/email contracting party]. [For each, add contracting entity, location, processing locations, actual tasks, subprocessors and applicable transfer safeguards.] EU hosting alone does not exclude third-country access. A processing agreement does not replace a required transfer basis. Information about the actual safeguards is available through the privacy contact.
Erasure and retention
There is no single retention period for all data. Account and profile data: [period after termination]. Operational order data and optional confirmation email: [separate periods]. Tickets and attachments: [period after closure]. Session and verification data: [expiry and cleanup periods]. Contract evidence: [period]. Statutory records follow their category: invoices generally eight years under section 14b UStG, other tax records ten, eight or six years under section 147 AO, with statutory starting points and possible extensions. This does not justify retaining all profile data indiscriminately. [Complete backup rotation, reapplication of erasure after recovery and documented legal holds.]
Rights and complaints
Subject to legal requirements, you have rights to access, rectification, erasure, restriction and portability. Consent may be withdrawn prospectively; legitimate-interest processing may be opposed for reasons relating to your situation, and direct marketing at any time. Contact the privacy contact or the restaurant for its processing. You may complain to a supervisory authority. [Add the competent authority based on the actual business location.]
Data sources and decisions
Data comes from your entries, access set up by the venue, ordering and necessary payment-status messages from Stripe. Relevant services cannot be supplied without necessary account or order data. Optional email confirmation or newsletter subscription is not required for a guest order. [Add any actual automated decisions with significant effects, particularly by payment providers, and their notices; do not make an unverified blanket claim that none exist.]