Sub-processors

Our own servers (Canada)

Luncheezy isn’t hosted by a cloud company. Meiko Technologies Ltd. runs the app, the database, the cache and this website on servers it operates itself, in Canada. They aren’t a sub-processor: no other company has access to them.

Purpose

Running the app and this website; storing the database, sign-in sessions, job queues and logs.

Information

Everything Luncheezy keeps, including children’s allergy and diet information.

Location

Canada.

Backblaze B2 (files and backups)

Purpose

Storing files and the backups of our database.

Information

Meal photos (with their location and camera data removed), the reports staff export (such as class lists, labels and dietary lists, deleted after 30 days), dispute evidence files, and backups of the database.

Location

Toronto, Canada (Backblaze’s Canada East region).

Stripe

Purpose

Card payments for lunches, payouts to schools, councils and caterers, refunds, disputes, identity checks on sellers, and schools’ Luncheezy subscriptions and invoices.

Information

For a family’s payment: the payer’s email address, what was bought (meal, lunch and date, never a child’s name), the amount, and the card details and name the payer types directly into Stripe’s form (we never see full card numbers). For a dispute: the payer’s name and email, the receipt, the times lunches were handed out and the cancellation policy; a child’s first name and last initial only if the school’s treasurer chooses to add them. For sellers: business, representative and bank details, which Stripe collects itself. For a school’s plan: the organization’s name, billing email, province and any purchase order number.

Location

The United States and other countries where Stripe operates.

MailerSend

Purpose

Sending email: sign-in codes, receipts, menus, reminders, notices and our team’s alerts.

Information

Each recipient’s email address and the content of each email, which can include a name, a child’s first name, meals, dates and amounts. Emails never contain allergy or diet information. When an address bounces or someone reports spam, we keep only a scrambled code of the address, never the address itself.

Location

The European Union.

Plivo

Purpose

Sending codes by text message, through its Verify service, to people who sign in with their mobile number or confirm a new one. Plivo creates the code, texts it and checks it when it’s typed in. We send no other texts.

Information

The mobile number, the language of the message, and the code Plivo creates.

Location

The United States.

Push services (Apple, Google, Mozilla, Microsoft)

Only for people who turn on push notifications. Each browser delivers notifications through its maker’s service: Safari and iPhone through Apple, Chrome and Android through Google, Firefox through Mozilla, Edge through Microsoft. We don’t choose which one; your browser does.

Purpose

Delivering the notifications you turned on (receipts, reminders, volunteer news and staff alerts) to your phone or computer.

Information

The address your browser gives us for your device, and each notification, encrypted so the service can’t read it (a short title and message with a first name, a lunch, a date or an amount). Notifications never contain allergy or diet information. The service also sees when each notification is sent.

Location

The United States and other countries where these companies operate.

What we don’t use

No advertising, analytics, tracking, session-recording or error-tracking services, on this website or in the app. Our logs stay on our own servers and never contain sign-in codes, PINs, tokens, email addresses or allergy information.

Caterers that sell at a school aren’t our sub-processors: the school chooses them, and what they see is described in our privacy policy and the caterer terms.

Changes to this list

We update this page before a new provider receives any personal information. Schools, councils and caterers are told by email at least 30 days ahead, as our data processing agreement describes, unless we must replace a provider urgently to keep the service running or secure; then we tell them as soon as we can.