Data Processing Agreement

Version 2026-11. Between the Customer who accepts in the app ("Controller") and Edwinmar Colina, trading as Loopwise ("Processor"). It is accepted electronically when the restaurant signs up; the date, the person and the version are recorded.

This agreement meets Article 28 of Regulation (EU) 2016/679 (GDPR) and also serves as a processing agreement under other laws that apply to the Customer (for example, Brazil's LGPD, Mexico's LFPDPPP, Colombia's Law 1581, Argentina's Law 25.326, Peru's Law 29733, Panama's Law 81, UK GDPR).

0. In short

1. Subject and duration

The Processor processes personal data on behalf of the Controller only to provide Yield, for as long as the service lasts and, afterwards, only to return or delete it under section 10.

2. Data and data subjects

Data subjectsDataPurpose
Managers with an account (owner, chef, bar manager)Email, display name, roleAccess and notices
Staff without an accountFirst name, encrypted PIN, clock-in and clock-out times (if the restaurant uses time records), authorship of records (temperatures, batches, checklists)Time records and food safety self-checks
SuppliersData shown on invoices and receiptsPurchase control

No special categories of data and no biometric data are processed.

3. Instructions

The Processor processes the data only on the Controller's documented instructions, which are these terms and the Controller's use of the app, and never for its own purposes. If an instruction seems unlawful, it will say so.

4. Confidentiality

People who access the data on behalf of the Processor are bound by confidentiality.

5. Security

6. Sub-processors

The Controller authorises these sub-processors:

ProviderPurposeWhere
Supabase Inc.Database, access and filesEuropean Union
Cloudflare Inc.App hostingGlobal network
Anthropic PBCReading invoices and receipts with AIUSA (standard contractual clauses / valid transfer mechanism)
Resend Inc.Sending the app's emails (sign-in code, reports)USA (standard contractual clauses)
GitHub Inc.Database backups in a private repository (35 days)USA (standard contractual clauses)

The Processor will give 30 days' notice in the app before adding or changing a sub-processor; the Controller may object and cancel at no cost.

7. International transfers

The data is hosted in the EU. When a sub-processor processes it elsewhere, a valid mechanism is used (adequacy decision or standard contractual clauses). For Customers outside the EU, hosting in the EU is treated as a transfer to a country with adequate protection under their law or is covered by the clauses of this agreement.

8. Data subjects' rights

The app lets the Controller export all of a person's data, correct it and remove their access. The Processor will help the Controller answer any requests it receives.

9. Personal data breaches

The Processor will notify the Controller without undue delay and at most within 48 hours of becoming aware of a breach affecting its data, with the information available so the Controller can notify the authority in time (72 hours in the EU).

10. End of the agreement

When the service ends, the Controller has 30 days to export the data. After that, the Processor deletes all of it. The Controller can also order immediate deletion in the app (Settings → Delete the restaurant). Keeping the records required by law (for example, time records) is the Controller's obligation, and it must download them first. Backups (kept in a private repository) are deleted within 35 days at most.

11. Audits

The Processor will make available to the Controller the information needed to demonstrate compliance and will allow reasonable audits with prior notice.

12. Liability and governing law

The limitation of liability and the governing law of the Terms of use apply, without prejudice to mandatory data protection rules.

Version 2026-11 · fingerprint sha256 fc4434e4360ea7d30bae761e013980e8e912caa93e44aaaa28fadec010d09707