Rivkin CateringRivkin Cateringעברית

Privacy Policy

Last updated:

This policy explains what personal information is collected and processed by the Rivkin Catering order and event management system and its related sites and services, and why. These are the business-client portal, the catering-trays site, the events portal, the coupons site, the pickup station and our messaging channels. The policy also explains who the information is shared with and how you can exercise your rights under the Israeli Protection of Privacy Law, 5741-1981, as amended, including Amendment 13.

1. Who we are and how to contact us

Rivkin Events Ltd., trading as "Rivkin Catering" ("we", "us", "the company").

We are the controller of the database. For any privacy matter, or to request access, correction or deletion, contact us using the contact details at the bottom of this page.

2. What we collect, by source

Staff members (users of the system):

  • Name and username.
  • Password (stored as a hash) or PIN code.
  • E-mail, mobile number, role and permissions, and their start page.
  • Last sign-in time, and an activity log: who changed what and when, with the IP address and browser details.
  • Optional Google Sign-In (see section 4).

Customers and orders. These come from our online store, event and catering orders, the private-events portal, the catering-trays site, and phone orders typed in by staff:

  • Name, phone, e-mail and delivery address.
  • Event or pickup date and details, order contents, and notes the customer wrote.
  • Amounts and payment status. We do not receive or store payment-card details.
  • Trays site: phone verification by a one-time code (the code itself is not stored), the IP address the order was sent from, and optional questionnaire answers (number of guests, budget, type of event).
  • Customer records: name, phone, e-mail, address, internal staff notes, total purchases, and consent to e-mail and WhatsApp marketing.
  • Hall family bookings: the family name and notes.

Business (B2B) clients, including "Shifra & Puah":

  • Business and contact name, phone, e-mail, delivery phone numbers, and portal sign-in details.
  • For Shifra & Puah orders: the names of the people who receive the portions (for example new mothers), sometimes with a phone number and notes per portion. The business client gives us this information so we can prepare and deliver each portion.

Coupons and gift cards:

  • Recipient name, contact details (phone, e-mail), an identifier used to verify redemption (phone or ID number), a greeting, and a redemption log (when, where and by which staff member).

Pickup and delivery station:

  • Order and handover status, and the names of the staff who picked, packed and handed over the order.

Messages and communication:

  • WhatsApp, through Meta's WhatsApp Business Cloud API (see section 5).
  • SMS: phone number and message text (for example an order confirmation or a verification code).
  • E-mail: recipient address and message content. For marketing e-mails we also record when the e-mail was delivered and opened.
  • Telegram: internal messages to staff groups. Business clients who chose to connect their Telegram account: chat id, name and the time of consent.
  • A send log: the recipient number or address and the content of outgoing messages.

3. How we use the information

We use the information only to operate the service:

  • To take, prepare, price, deliver and coordinate orders and pickups.
  • To send confirmations, updates, PDF documents and verification codes.
  • To manage coupons and their redemption.
  • To send internal staff notifications and to print labels and work plans.
  • To identify staff and business clients, keep the system secure, and audit changes.
  • To meet legal obligations, such as accounting records.

Marketing messages (e-mail or WhatsApp) are sent only to people who have not asked to be removed, and anyone can opt out at any time (see sections 5 and 9). We do not sell personal information and do not use it for third-party advertising.

4. Google user data (Sign in with Google)

Sign in with Google is optional and offered to staff members only. We request only the basic scopes openid, email and profile, which give us the name, e-mail address and profile picture.

We use only the verified e-mail address, and only to identify the staff member and match them to an existing staff account with the same address. We do not store the profile picture, the Google account name or the Google account ID. We do not access any other data in the Google account, such as e-mail, contacts or files.

Rivkin's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

  • We do not sell this information.
  • We do not use it for advertising.
  • We do not transfer it to anyone, except as needed to provide the service (the sign-in itself).
  • We do not use it to train artificial-intelligence or machine-learning models.

You can revoke our access at any time in your Google Account settings (myaccount.google.com/permissions). Signing in with a username and password keeps working.

5. WhatsApp and Meta

We send and receive WhatsApp messages through Meta Platforms' WhatsApp Business Cloud API.

  • What we send: the phone number and the message text, such as order confirmations and updates, a tracking link, reminders, verification codes and, where applicable, marketing.
  • What we receive and store: messages the customer sends us (text only; we do not store media files), the WhatsApp profile display name, and delivery status (sent, delivered, read, failed).
  • Replies: an incoming message may get an automatic reply, either a predefined answer or an AI reply when enabled (see section 6). The customer can ask for a human agent at any point.

Opt-in: service messages go only to the number the customer gave us in their order or inquiry, and only about that order.

Opt-out: you can ask at any time to stop receiving WhatsApp or SMS messages from us, by replying in WhatsApp or by contacting us (section 1). Our staff handle the request and mark the number as not wishing to receive marketing. There is currently no automatic stop keyword.

Meta also processes messages under its own policies; see the WhatsApp and Meta privacy policies. For internal staff notifications only (new-order alerts, order documents), we also use other WhatsApp gateways: Green API, and an internal gateway we operate. These messages go to staff groups and numbers, and may also reach a customer where an automation is configured to do so.

6. Third parties and processors

We use the following providers. Each one receives only the information its role needs:

  • Meta Platforms (WhatsApp Business Cloud API): WhatsApp messages to and from customers.
  • Green API and an internal WhatsApp gateway: internal staff notifications and order documents.
  • SMS providers (019 SMS or Twilio, depending on configuration): SMS messages and verification codes.
  • Resend: e-mail delivery (confirmations, order summaries, password resets, newsletters) and delivery and open tracking.
  • Telegram: messages to staff groups and to business clients who connected their account.
  • Google: Sign in with Google for staff (section 4).
  • Anthropic and Google (Gemini): automatic AI replies to incoming WhatsApp messages, when enabled. They receive the message text and, in some cases, the sender's name and their orders. Administrators who approve it can also connect Claude (Anthropic) to look up order data.
  • WooCommerce / WordPress (our online store): store orders (name, phone, e-mail) come into the system, and coupon data is synchronised to the store.
  • Our point-of-sale (POS) system: coupon redemption.
  • n8n and webhooks: automations we operate for order updates and printing.
  • Printing and PDF services we operate (labels and order documents).
  • Hosting: a cloud server (VPS) we manage, with a PostgreSQL database and HTTPS. Brand files (logo and images) load from our own file server (f.hbh.co.il).

We do not sell personal information. We do not share it with anyone other than these providers, and only to provide the service, unless the law requires it.

7. How long we keep information

  • Orders, invoices and documents needed for accounting: as long as needed for the service, and at least as long as the law requires (usually 7 years).
  • Customer records: while there is a business relationship, or until a deletion request (subject to records the law requires us to keep).
  • Message logs and WhatsApp conversations: up to 12 months.
  • Staff activity log: up to 24 months.
  • Staff accounts: while active. An account is deleted when the person leaves or asks for it.
  • One-time verification codes are valid for 10 minutes and are not stored. Password-reset links are valid for 30 minutes.
  • Google data: nothing is stored beyond the e-mail address already registered on the staff account.

At the end of the period, information is deleted or anonymised.

8. Security

  • Connections to the system are encrypted with HTTPS.
  • Staff passwords are stored as hashes (scrypt), and sessions are cryptographically signed.
  • Access is limited by role and permissions, with sign-in attempt limits and an activity log.
  • Incoming webhooks (Meta, WooCommerce, Telegram, Resend and others) are signature-checked, and some sensitive keys are encrypted in the database.

No security is perfect. If a serious security incident happens, we will act as the law requires, including reporting to the Israeli Privacy Protection Authority where needed.

9. Cookies and browser storage

We use only cookies that the system needs to work. There are no advertising cookies and no third-party analytics or tracking.

  • rivkin_session: identifies a signed-in user (staff or business client). httpOnly, valid for up to 12 hours.
  • rivkin_google_flow: protects the Google sign-in flow. Deleted when the flow ends, and valid for 10 minutes at most.
  • rivkin_labels and rivkin_labels_dev: sign-in to the staff labels site, and identification of the device used.
  • wa_approver and wa_approver_otp: identify the device of a staff member who approves orders from a WhatsApp link.

On the catering-trays site, your browser keeps your cart and the contact details you typed (localStorage), so you don't have to type them again. You can delete them by clearing the site's data in your browser.

E-mail marketing: use the unsubscribe link at the bottom of every marketing e-mail.

10. Your rights

Under the Protection of Privacy Law you may access the information about you, ask us to correct it if it is wrong or out of date, and ask us to delete information that is no longer needed. You may also opt out of marketing at any time.

How to make a request: contact us using the contact details at the bottom of this page. We verify the requester's identity first, for example by the phone number on the order, and we reply within 30 days at the latest.

Detailed deletion instructions are on the "Data deletion" page (/data-deletion).

11. Children

The service is intended for businesses and adults and is not directed at minors under 18. We do not knowingly collect information about minors. If we learn that such information was provided, we will delete it.

12. Changes to this policy

We may update this policy. The date of the last update appears at the top of this page. We will announce material changes in the system or through our usual contact channels.