recEAT/ri-SEET/

PRIVACY NOTICE

Your privacy at recEAT

Last updated: September 2, 2026

Who is responsible for your information?

recEAT is operated by recEAT. The operator acts as the personal information controller for information collected through recEAT.

Privacy questions and requests: receatph@gmail.com.

What information recEAT processes

Depending on how you use the service, recEAT may process:

  • your account email and authentication information handled through Supabase Auth;
  • restaurant names, meal dates, item names, quantities, prices, service charges and payment amounts;
  • names or nicknames of people added to a meal;
  • optional receipt images;
  • optional payment details such as payment provider, account name, account number and QR image;
  • payment status, timestamps and optional payment-proof screenshots; and
  • technical information ordinarily processed by hosting, authentication and security providers when you use the site.

recEAT does not ask for card numbers, online-banking passwords, government IDs, or other information that is not needed to split a meal.

Why recEAT uses this information

  • to create, calculate, save and display meal splits;
  • to let an organizer share a completed recEAT with the group;
  • to show payment instructions chosen by the organizer;
  • to let participants mark payments as sent and let the organizer confirm them;
  • to maintain accounts, password recovery and account deletion; and
  • to secure, troubleshoot and operate the service.

recEAT aims to process only information reasonably needed for these purposes.

Shared recEAT links

A completed meal can have a public share link. Anyone who receives an enabled share link can view the names or nicknames, itemized shares, payment status, settlement information and any payment details the organizer chose to publish for that meal.

Do not put sensitive information into a person name, restaurant field or item description. Organizers can disable public sharing from the meal page.

Receipt and payment-proof images

Receipt images are stored privately and are not included on the public share page. The meal owner may access a receipt through a short-lived signed link.

Payment-proof screenshots are optional, stored in a private bucket, and can be opened only by the signed-in meal owner through a short-lived signed link. Participants should crop screenshots so they do not include unrelated balances, transactions or personal information.

Service providers and data location

recEAT currently relies on Supabase for authentication, database and file storage, and Vercel for web hosting and deployment. These providers may process information in locations outside the Philippines as part of providing their services.

How long information is kept

Saved meal data is kept while the account and meal remain active. Users can delete individual meals and can permanently delete their account. Account deletion is designed to remove saved meals, people, payment details, receipts, QR files and payment proofs associated with the account, subject to any temporary copies that may remain in provider backups or logs for their normal retention periods.

Your privacy rights

Under applicable Philippine data privacy law, data subjects may have rights including being informed, accessing and correcting personal data, objecting to certain processing, requesting erasure or blocking where applicable, data portability, filing a complaint, and seeking damages where provided by law.

If information about you was added to recEAT by a meal organizer, you may also contact that organizer so they can edit or delete the relevant meal.

Security and incidents

recEAT uses access controls, private storage for receipt and payment-proof images, row-level database policies and server-side administrative routes for selected sensitive operations. No online service can promise absolute security.

If recEAT becomes aware of a personal data breach, the operator will assess and handle it under applicable law, including notification duties when the legal requirements for notification are met.

Changes to this notice

This notice may be updated as recEAT changes. The date at the top will be updated when material changes are made.

Terms of UseBack to recEAT
recEAT

Split restaurant bills by what everyone actually ate.

USE CASESSplit a bill by itemShared dishesOne person paidBarkada / KKB splittingNo-download splitting
COMPARErecEAT vs Splitwise
GUIDESService chargeSplit with friendsAll guides →
PRODUCTHow it worksPricingrecEAT PlusSplit a bill →
LEGALPrivacyTermsFeedback
© 2026 recEATMade for the “magkano ako?” part after dinner.