1. Who is responsible
Eaziflow | TakeOut (“Eaziflow”, “we”, “us”) provides the ordering platform at eaziflowtakeout.co.za. Privacy requests can be sent using the contact details below.
- Platform name
- Eaziflow | TakeOut
- Trading name
- Eaziflow Studio
- Legal operator
- EAZIFLOW STUDIO (PTY) LTD
- Company registration
- 2026/622535/07
- Place of registration
- South Africa
- Company representative
- Mr.J. Van der Westhuizen
- Legal status
- Private company registered in South Africa
- Business / legal-service address
- 92 Smith Street, Darling, Western Cape, 7345, South Africa
- Telephone
- +27 65 980 4982
- General communication
- eaziflowtakeout@gmail.com
- Legal and privacy notices
- eaziflowjohynen@gmail.com
This notice applies to restaurant owners and team members who use the dashboard, customers who place or track an order, and website visitors. For an order, the restaurant receives and uses the information as the food supplier. Eaziflow processes it to operate and secure the platform. Depending on the activity, Eaziflow and the restaurant may each be a responsible party under POPIA.
2. Information we collect
Customer order information can include name, mobile number, optional email address, delivery address and suburb, order notes, selected items, fulfilment and payment methods, order value, status history, private tracking and digital-slip references.
An optional customer account stores an authentication profile, saved contact and delivery details, and links to order history. Restaurant-account information can include a person’s name, email address, authentication profile, restaurant membership and role, account status, storefront content, subscription records, activity logs and uploaded images.
Technical information can include timestamps, IP address and device or browser information in request, authentication and security logs. The customer cart and checkout draft are also stored locally in the customer’s browser.
Restaurant subscription payments and refunds
When an owner chooses online platform subscription payments, Paystack receives the billing email, selected plan, amount, currency, payment reference and details the owner enters into Paystack’s secure checkout. EaziFlow receives payment status, transaction and customer references, recurring agreement identifiers and billing dates. Payment-provider records may include limited payment-method details, such as card type or last four digits. EaziFlow does not store full card numbers or card security codes.
We keep payment, cancellation and refund-request records to operate subscriptions, reconcile payments, assess refund requests, answer billing enquiries and meet financial recordkeeping requirements. A refund request can include the restaurant name, payment reference, reason, supporting correspondence, decision and any refund reference. Do not submit full card details, card security codes, passwords or verification codes. Required financial and dispute records may remain after an account is closed. Paystack handles payment information under its own privacy and security notices. Food-order payments and refunds are handled separately by the restaurant.
3. Where information comes from
We collect information directly from customers, restaurant owners and team members when they use the service. If a person chooses Google sign-in, Google may provide the name, email address, profile image and account identifier needed for that sign-in method. Restaurants also create order-status updates and account or menu records about their own operations.
Business-interest questionnaire
If you complete our business-interest form, we collect the business and contact details, ordering practices, estimated monthly order range, challenges, desired features, interest, timing and any optional budget or message you provide. We record the submission time, form and consent-notice versions, source label, your preferred contact method and your contact and marketing choices. An administrator can add private follow-up notes, a follow-up date and a progress status.
The form does not create an account or publish your business in the restaurant directory. Full responses are private to authorised platform administrators and our hosting and database providers; minimal private administrator alerts are described below. We use them to understand business needs and manage enquiries. We contact you about an enquiry only if you request contact, using your chosen method. Occasional product or plan updates require the separate optional marketing choice, which is unchecked by default. You can decline marketing without affecting the enquiry, and withdraw either permission by contacting us.
Answers are kept only while reasonably needed to review and follow up on the enquiry. An administrator can permanently delete a response and its private notes from the active database. A minimal audit record retains the response identifier and deletion event, not its business name, contact details or answers. Previously downloaded exports and residual backup copies are managed separately; deletion from the active database does not erase those copies immediately. You can request access, correction or deletion using the privacy contact details below. The form keeps unfinished answers in the open page only, not in persistent browser storage.
Enquiry replies and support history
When you request email follow-up, an authorised administrator can reply to your saved enquiry through Resend. We keep the recipient, subject, message, timestamps and sending status with the private enquiry to manage follow-up and avoid duplicate sends. Deleting the enquiry also removes this reply history from the active database, but cannot recall emails already sent; provider records, recipient copies, exports and backups are managed separately.
Restaurant owners and staff can view their own submitted support requests, references and current request status in the dashboard while they retain access to that restaurant. Private administrator notes are not shown in this history. Support responses arrive by email.
4. Required and optional information
A customer’s name and mobile number are required to place an order. A delivery address and suburb are required for delivery. Email and order notes are optional. Without the required details, the restaurant cannot accept or fulfil the order.
An owner’s name, email address and authentication details are required to create and protect an account. Restaurant setup also requires the operational information displayed to customers. Other profile, branding and menu fields are optional unless the interface marks them as required.
5. Why and on what basis we use it
We use information to send an order to the selected restaurant, provide tracking, authenticate users, administer restaurant accounts, operate subscriptions, deliver support, prevent fraud and abuse, secure and troubleshoot the service, enforce our terms, keep business records and comply with law.
Depending on the activity, processing is necessary to perform or prepare a contract, comply with a legal obligation, pursue legitimate interests in operating and securing the service, or act on consent where consent is required. We do not use solely automated decisions that produce legal or similarly significant effects.
Food-order payments are made directly to the restaurant using its configured cash, EFT or collection card-machine options. Owner platform subscription payments through Paystack are described above.
6. Who receives information
Order details are shared with the selected restaurant and its authorised team. We use Supabase for database, account authentication and image storage; Netlify for application hosting; Cloudflare for domain DNS; Google for optional customer and owner sign-in and administrator sign-in; and Resend for account and support emails. These providers process information needed to provide and secure their services.
A WhatsApp share button opens a pre-filled message in WhatsApp; no message is sent until the user chooses to send it. We may disclose information when required by law, to investigate misuse or protect rights and safety, or as part of a properly managed business transfer. We do not sell personal information and do not share it for third-party behavioural advertising.
When private administrator alerts are enabled, Telegram receives a short event notification that may contain a business name, record reference and submission timestamp, with a link to the protected administrator dashboard. Full support messages, full questionnaire responses, customer contact details and authentication credentials are not included in these alerts. They are sent only to the administrator’s explicitly connected private Telegram chat, not to a public group or channel. Delivery records contain references and delivery status and are targeted for removal after 30 days. Deleting a source enquiry removes its notification records from our active database, but does not recall a message already sent to Telegram. Copies held in Telegram or backups must be managed separately.
Optional email updates
Newsletter and product-information emails require an explicit, separate opt-in. Creating an account or restaurant does not subscribe you. Owners can subscribe or unsubscribe in dashboard settings. An administrator may add a subscriber only with evidence of permission, or import questionnaire responses that expressly selected optional updates and email contact. Previous unsubscribe choices are preserved during imports.
We store the subscriber’s email, optional name, audience group, consent source, evidence and timestamps, subscription status and a private unsubscribe reference. Resend processes individually addressed emails; recipients do not see other recipients’ addresses. Private administrators can view campaign content, recipient snapshots and sending attempts. Provider acceptance is not proof of inbox delivery or that a person read an email. We do not add newsletter tracking pixels.
Each newsletter includes an unsubscribe link. Opening the link displays a confirmation page; confirming stops future newsletters. Email providers may also offer a one-click unsubscribe action. Essential authentication, order and requested support emails are unaffected. We retain a minimal suppression record to honour opt-outs, and campaign records only as reasonably needed for administration and resolving sending issues. Deleting an original enquiry does not automatically remove a separately consented subscription; request removal using our privacy contact details. Emails already accepted cannot be recalled, and provider, recipient and backup copies are managed separately.
7. International processing
Some service providers may process or store information outside South Africa. We select providers and use contractual, organisational and technical safeguards intended to provide protection consistent with POPIA’s cross-border requirements.
8. Retention and deletion
We keep information only while reasonably needed for the purposes described here, to resolve disputes, protect the service and meet legal, tax, accounting or recordkeeping duties. Account and restaurant records support the service while the account is active. Order, payment, cancellation, refund and audit records may need to be kept after closure for those lawful purposes. We review records that are no longer needed and remove or de-identify them where appropriate; account closure does not mean immediate deletion of every related record.
Deletion from the active database does not immediately erase provider records, previously exported copies or residual backups. Those copies are managed under their separate retention arrangements. Uploaded storefront media can be replaced or removed through the available dashboard controls. Device-local cart and checkout information remains in the browser until it is cleared or replaced and is not the authoritative order record.
9. Security and incidents
We use access controls, tenant checks, private tracking references, server-side order-total validation, rate limits and managed cloud infrastructure to protect information. No system can guarantee absolute security. We will investigate suspected compromises and notify the Information Regulator and affected people when POPIA requires it.
Report a suspected privacy or security incident promptly to eaziflowtakeout@gmail.com.
10. Your choices and rights
Subject to applicable law, a person may ask whether personal information is held, request access or correction, object to certain processing, withdraw consent where processing relies on consent, ask for deletion where appropriate, or complain about how information is handled. Customer-account holders can update saved details or remove their customer profile from My Account. Removing a customer-only profile also removes its login; legally required restaurant order records may remain but are detached from the account.
Start a privacy request by emailing eaziflowjohynen@gmail.com. We may need to verify your identity before providing or changing private information. Customers can also contact the restaurant about a particular order. You may submit a POPIA complaint through the Information Regulator of South Africa.
11. Browser storage and cookies
The customer storefront uses browser storage to remember an in-progress cart and checkout draft on that device. Restaurant and administrator sign-in uses strictly necessary authentication cookies or equivalent session technology. The current platform does not use advertising or cross-site tracking cookies.
12. Children
The service is not directed to children and Eaziflow does not knowingly seek to collect children’s personal information. A person placing an order must be legally able to do so or act with a parent or guardian’s involvement. Contact us if you believe a child supplied information without appropriate involvement.
13. Changes and legal framework
We may update this notice as the service, providers or legal requirements change. The updated date at the top shows when this version took effect. Material changes will be communicated through the website, dashboard, account email or another reasonable channel.
This notice is designed around South Africa’s Protection of Personal Information Act 4 of 2013. It does not claim certification or replace advice from a qualified South African privacy professional.