Privacy & legal
What we hold, what we won’t, and what you can demand.
This site collects delivery photos, order confirmations and email addresses from diners, and it publishes prices and performance figures about named businesses. Both of those carry obligations under Philippine law. Here is all of it in plain words, with retention periods, because a privacy policy without them is a decoration.
Contact [email protected]
01 — Who we are
Two people, and what this is not
What Kada is
A price comparison site for prepared meal plans in Metro Manila, run by a husband-and-wife team here. It reads providers’ public prices, divides them onto one per-day axis, and publishes what diners report back about delivery and food.
- Reachable at [email protected], usually the same day. That address is the data protection contact as well as everything else.
- The methodology is published in full, including a log of every correction we have had to make.
What it is not
- Not a merchant or a marketplace. No orders are taken here, no payments are processed, no cart exists. Every plan link goes to the provider’s own site, where their terms apply and ours stop.
- Not affiliated with any provider listed. No provider has approved, reviewed or paid for their listing, and none uses their logo here.
- Not earning a commission. Every discount code on the site carries the line “we earn nothing from this code” because that is currently true of all 0 of them. If one ever pays us, that line changes on that code before it goes live.
- Not funded. A domain and hosting, out of pocket. Two things are for sale and both are sold to providers rather than to you: a monthly report about the market a kitchen competes in, at ₱3,000 a month, and a labelled sponsored box above the results, at ₱3,000 a month on its own. Both rates are published on the provider page rather than negotiated, and nothing has been sold. Neither buys a change to anything published here, including where a plan sits in the ranking. When money does come in it will be registered and taxed like any other income.
02 — What we hold
Every category, why, and for how long
Under the Data Privacy Act of 2012 (RA 10173) we have to collect only what a stated purpose needs, and keep it only as long as that purpose lasts. The right-hand column is the part most policies leave out.
| What | Why we hold it | How long |
|---|---|---|
| Your email address | Only if you asked for city alerts, or asked us to reach a province we do not cover at all — and only ever to send you the one thing you asked for. There is no newsletter and no other mail. | Until you unsubscribe |
| One city name | So the alert knows where you are. That is the entire record: an address and a city, with no goals, no price range and no plan list — see health data. | With the email |
| A province you asked us to cover | The counterpart to the alert list, for somewhere we do not list at any grain: it is the only way to learn that a whole province is asking. A province and not a city, because the coarsest answer that works is the one to keep, and never free text. | With the email |
| Your report answers | On time, whether the food was good, what you flagged, portion, chilled, would-order-again. These become the published percentages, and the second year is what lets a kitchen’s figures be compared with the same month last year. A published figure only ever uses the last twelve months. | 24 months |
| Your reminder to report | One mail about one order, and the token that routes your answer back. It is the only record that holds your address beside a provider, and it is deleted the moment you submit. | 21 days |
| Your delivery photo or order confirmation | It is what makes a report verifiable, and it is the only reason a provider cannot pad its own figures. | 90 days |
| The free-text box | Read by one person to decide which fixed question to add next. Never published, never shown to a provider. There is no such box today and the period is stated in advance of one. | 12 months |
| Your click through to a provider | To tell a provider how many clicks opened their plans this month against the same month last year. This is a click record, not a profile: which plan, which day, and nothing about you — no name, no address, no identifier, so it cannot be joined to your reports or to your other clicks. Which goals were filtered is removed from it at 6 months — the rest of the row lives on without it, because no figure we publish needs a goal compared year on year. | 24 months |
| A discount code you revealed | That a code was uncovered, and which one. Not that it was used — a redemption happens on the provider’s checkout and we cannot see it, which is stated wherever the figure is printed. The same shape of record as a click, with no identifier on it either. | 24 months |
| A search that returned nothing | The filters that emptied a result list, with no plan and no provider attached. It is the only signal that says which kitchen to go and read next, and which cities are asking for something nobody sells. The goals come out of it on the same schedule as a click. | 24 months |
| Monthly click totals, already counted | The per-plan and per-city counts a provider’s monthly report is drawn from. There is nothing in one to age out: no identifier, no filters, no goal, and no time finer than a month. They are what the click rows above are compacted into, so deleting them would destroy the year-on-year figure the period above was written to preserve. | Kept indefinitely |
| Provider corrections and contacts | To verify a correction came from the business, and to publish the same-day fix. | Business record |
| The link to your monthly report | If you run a kitchen we list: the link in your monthly mail, which opens that month and nothing else. We store a hash of it rather than the link itself, so a copy of this database contains no working one, and it stops opening on the date below whether or not anyone asks. | 90 days |
| Which goals were filtered, by city | Aggregate demand at city grain, counted across the whole market so a provider can see what a city is asking for. Part of the paid report, and never crossed with a person, a plan or a provider. | Never stored against a person |
Nothing in this table is sold, and no diner’s contact details go to a provider — not for a fee, not as a favour. The aggregate is what providers get; the person is not part of the product. If any of that changes, this table changes first.
03 — Health data
Filtering for “PCOS-friendly” says something about you
Four of the eight goal filters — diabetic-friendly, PCOS-friendly, heart-friendly and keto — imply a medical condition. Under RA 10173 information about health is sensitive personal information, which carries a materially higher duty of care than an email address. A comparison site that quietly logged “this address searched for diabetic plans” would be building a health database by accident.
So we don’t keep it
- A goal filter is never written against an email, an account or a device identifier. It increments a city-level counter and is discarded.
- The one alert we offer — a new provider or a new promo code in your city — is keyed to a city and nothing else. Both events are rare, and that rarity means the email does not need targeting by goal — so no goal is ever stored against it. There was an earlier design that stored the matching plan IDs instead; keying on the city removed the inference altogether rather than disguising it.
- The aggregate given to providers is counts by city, with no minimum-cell trickery available to reverse it to a person.
What that costs you
Real things, and it is fairer to name them than to claim the choice was free:
- The site cannot personalise. It will never greet you with “new PCOS-friendly plans this week”, because it does not know that about you.
- Your alert can tell you a new provider or promo code has turned up in your city. It cannot tell you whether the plan suits you, because it does not know what you want — the email names what they sell and you judge it.
- Clearing your browser storage loses your theme choice and nothing else, because there is nothing else.
04 — Photos
The most sensitive thing you can send us
A delivery photo often has a doorway, a street number or a face in it. An order confirmation almost always has your full name and delivery address. We ask for one of the two because verification is the whole basis of the on-time and food figures — and that makes handling them carefully our problem, not yours.
- An order confirmation is never published in any form. It is read by one person, checked against what the report says, and the report is marked verified. The file is deleted at 90 days.
- A photo is published only after cropping — names, addresses, faces, door numbers and anything else identifying comes out first. Nothing has been published yet, which is why the provider pages show a labelled empty strip instead of a stock image of someone else’s food.
- You can withdraw a photo at any time, including after it is published, with one email and no reason required.
- No face recognition, no image analysis, no third-party processing. The files sit in storage we control and are looked at by a person.
If you would rather not send either, send the report anyway. It will be read and it will not be counted — and the provider page says how many reports that applies to.
05 — Your rights
What you can demand, and how
These are yours under RA 10173 whether a policy grants them or not. One email to [email protected] exercises any of them, and the commitment is a reply within five working days — the law allows longer.
To be told
What we hold about you and why. That is what the table in section 02 is for, and you can ask for your specific records rather than the categories.
To see it
A copy of everything tied to your email or your reports, in a format you can read, at no charge.
To correct it
Anything wrong gets fixed. If a corrected report changes a published percentage, the percentage moves with it.
To have it deleted
Your email, your reports, your photos. The aggregate figure already published cannot single you out and will not be recomputed backwards, which we would rather state than pretend otherwise.
To object
Withdraw from anything at any time. There is no account to close and no dark pattern to get through.
To take it elsewhere
Your data in a portable format, on request.
To complain over our heads
The National Privacy Commission takes complaints about any Philippine site including this one, and you do not need our permission or our cooperation to file one.
To be compensated
The Act provides for damages where a breach of it causes you harm. We would rather say so here than leave you to find out.
06 — No reviews
Why nothing you type about a kitchen gets published
Every report ends with an open box. We read all of them and publish none. There are two reasons and the legal one belongs here.
Cyber-libel is a real exposure
Online libel under the Cybercrime Prevention Act of 2012 (RA 10175) applies to statements about a named business, and it exposes both the person who wrote it and the site that published it. We are two people with no legal budget.
A delivery photo timestamped against a stated window is a fact and defensible. “This kitchen is filthy” may well be true and we are not equipped to prove it in front of anyone. So we do not host it — and we say that plainly rather than accepting reviews and moderating them away quietly.
What we publish instead
Fixed questions, one tap each, aggregated with the base printed: on time, whether the food was good, what diners flagged, portion, chilled, would-order-again. An aggregate of a fixed question is a statistic rather than an allegation.
That distinction is the entire design, and it took a correction to get right — the methodology used to say food quality was out of scope because opinion cannot be verified, which confused prose we cannot check with a question we can count. The reasoning in full.
07 — Providers
Names, prices, and what a takedown gets you
Why we can name you
- A provider’s name is used to identify the business being compared and nothing else. No logos, no brand assets, no suggestion of endorsement or partnership.
- A price on a public order page is a fact about a business, and every listing prints the quote it was derived from and the date it was read so the arithmetic can be checked.
- Corrections from the provider outrank everything else we hold and publish the same day. We would rather you corrected us than let us guess.
What we will and won’t remove
- Will: any wrong price, window, city, calorie figure or plan, same day.
- Will: publish your reply of up to 300 characters, unedited, under any figure you dispute, plus the rule and the base behind it.
- Will: delist you entirely on request. Listing is free and it is also optional.
- Won’t: delete a verified diner report because it is unflattering.
- Won’t: remove an accurate price, or a competitor’s listing, at anyone’s request.
- Won’t: change a ranking. It is arithmetic and it is not for sale.
Think we have infringed something? [email protected], with the specific page and what is wrong with it, and you will get a person rather than a form.
08 — Tracking & breach
What runs in your browser
Almost nothing, and it is checkable
- No Google Analytics, no Facebook pixel, no ad network, no session recorder. None. This is the claim easiest to verify and hardest to fake — open your browser’s network tab. You will see requests to this site and to nowhere else, and the only ones that are not the page itself are the four below, which happen when you do something rather than when you arrive.
- No third-party requests at all. The fonts are served from this site rather than fetched from Google, so nobody else learns that you visited.
- One item in local storage: kada-theme, holding “light” or “dark” if you chose one. No cookies are set on the public site.
- Four things this site records, all of them to itself. An outbound click — which plan, which day, and the filters that were active. A discount code being revealed. A search that came back empty, with the filters that emptied it. And the alert or area form, if you fill one in, which is the only one of the four that holds an address, because you typed it.
- None of the first three holds an identifier of any kind. No cookie, no device id, no hashed anything — so there is nothing on those rows that could be joined back to you, to each other, or to a report. It is what lets a provider be told how many clicks opened their plans without anyone being told who did the clicking, and it is the same reason we could not tell you what you personally did here even if you asked.
If something leaks
The realistic worst case here is the photo and order-confirmation store, which is why it holds 90 days rather than forever.
- We notify the National Privacy Commission and every affected person within 72 hours of establishing that a breach happened, as the Act requires.
- The notice says what was taken, when, and what we have done — not that “an incident may have occurred”.
- It gets published on this page as well as emailed, so it cannot be handled quietly.
Two people maintaining a site is a security limitation in itself, and stating it is more honest than a paragraph about industry-standard encryption.
09 — Page history
When these terms changed
Same rule as the methodology: a policy that can be edited silently is not one. Every change belongs here, dated, and a change that reduces your protection will be emailed to anyone on the alert list before it takes effect.
- 9 October 2026. Section 01 now says the site is run by a husband-and-wife team rather than one person, and sections 06 and 08 say the same. Nothing about what is recorded, how long it is kept or who it is shared with changed, so there was no change to notify.
Parts of what is described here have been recording since the site went live: clicks, code reveals, empty searches and the two forms. None of that has ever been sent anywhere.
The retention periods in section 02 are the ones the site launched with. If they turn out to be unworkably short in practice, they get longer here first, with a reason, before any data is kept longer.