Privacy policy

Contact, subscription and support data are used to operate EdaraLab. For customer and employee data entered by an account owner, the business determines collection purposes and access while the platform processes it to provide the agreed service. The responsible legal entity and contact details must be completed before adoption.

Information may include names, phone numbers, email, business and branch details, employees and permissions, sales, purchases, suppliers, customers, balances, recipes, stock, images, attachments, support tickets and payment proofs. Passwords are stored as hashes. Operational logs may include IP addresses, event times, session and device information.

Data supports account setup, service delivery, access protection, operations, subscription reconciliation, responses, support and applicable obligations. Depending on the case and law, grounds may include contract performance, legal obligations, permitted legitimate interests or consent where required. Consent to a demo response is not blanket consent to unrelated marketing.

Published menus and QR links are accessible to their visitors; do not publish confidential information. Employees access what their permissions allow. Authorized support staff may access what is necessary for a legitimate support task under access controls. Demo requests and business account data are not displayed publicly.

Hosting, storage, backups, communications and integrations may involve approved providers. Activated AI imports or translations send the selected files or fields to the configured provider for that task. Loading Google Fonts connects to Google servers. Processing may occur outside your country depending on deployment and provider. Entities, countries and applicable safeguards must be disclosed before commercial adoption; this draft makes no claim of specific local hosting.

Session, protection and language cookies support the site. Offline workflows use local storage for required data and synchronization. The current introductory page has no advertising or marketing-analytics tools. Adding optional tools requires updated disclosure and consent where required.

Barcode scanning starts at the user’s request with browser permission. The scanner does not upload a camera video stream; required frames are processed on the device. Uploading a product image or attachment is separate: the image is prepared and may be reduced before upload to the server. Revoke camera access in browser settings.

Data is retained as necessary for service delivery, legal and accounting duties and disputes. Log and backup retention depends on data type and deployment; no unapproved automatic deletion deadline is promised. Request export or deletion through support. Identity, authority and required records are reviewed, and scope and timing are explained. Restricted backup copies may remain until their retention cycle ends.

Depending on applicable law, you may request information, access, correction, deletion, restriction, objection and withdrawal of consent where it is the basis, without invalidating prior lawful processing. For data held by a restaurant or shop, contact that business first. Permissions, additional verification and logs help protect access but do not guarantee absolute security. Report incidents to support.

The service is for business administration and is not directed at children. Do not enter unnecessary information about minors. Processing changes lead to policy updates and appropriate notice of material changes. Rights to complain to a competent authority are preserved where provided by law. Use the contact options below for privacy requests.