VERSION 2026-09-07

Privacy Policy

This policy covers the seemykitchen.live website and the See My Kitchen Live mobile apps for Android and iOS. It is written to be checked against the product rather than to sound reassuring — where we say we do not collect something, it means the field does not exist.

1. The short version

• Video is never recorded. There is no archive, no replay, and no stored footage of any kitchen, at any point, ever.
• No audio is captured anywhere in the system. Not muted — never captured.
• Diners have no accounts. There is no sign-up, no sign-in, and no profile.
• We do not track you across the internet. No advertising identifiers, no third-party analytics, no tracking cookies, no data sold or shared with data brokers.
• Your location never leaves your device.

2. If you are a diner

2.1 We do not know who you are

Browsing kitchens requires no account, no email address and no phone number. We do not ask for your name, and there is nowhere to give it.

2.2 What we count

So a restaurant can see whether its listing is worth paying for, we record counts of seven kinds of event: a listing being opened, a kitchen being watched in the feed, an arrival from a printed QR code, and taps on the Swiggy, Zomato, directions and phone buttons.

Each record contains only the kind of event, which restaurant it concerned, and the time. That is the whole row.

Deliberately absent from it: your IP address, your device or advertising identifier, your user agent, any session or visitor ID, the page you came from, and any cookie. Nothing in this data can be linked back to you, or used to recognise you on a second visit. This is the only form of analytics consistent with what we promise restaurants, and it is a constraint written into the database itself.

2.3 Location, for “kitchens near you”

If you use the “near you” feature, your device asks your permission for your approximate location. The coordinates are used on your device only, to sort a list of kitchens we have already sent you by distance.

They are never transmitted to us, never written to any log, and never stored. We do not receive them, so we could not disclose them to anyone if we were asked to. You can decline the permission and the rest of the product works normally.

2.4 Asking us to add a restaurant

If you ask us to approach a restaurant, we store which restaurant you asked for and a random identifier generated by the app on your device. That identifier exists for one reason — so that one phone counts as one request rather than forty — and it is used for nothing else. It is not an advertising identifier, it is not derived from anything about your device, it does not survive reinstalling the app, and it is never attached to what you watch, tap or search. The event records described above still contain no identifier at all, so the two cannot be connected, by us or by anyone who asks us to.

The name you pick comes from a list of businesses supplied by Google. What you type into that search box is passed to Google to find matches and is then discarded — we do not store it, and nobody at this company can read it.

If you have notifications switched on, we also keep the address of your device against that request, so we can tell you what the restaurant said. That is the only thing it is used for.

2.5 Notifications

If you choose to turn on notifications, we store the address your device's push service gives us, along with the keys needed to encrypt a message to it. For diners this record has no user account attached to it — it is a device we can reach, and nothing else about you. Turning notifications off in your device settings ends it; we also delete these records automatically once the push service reports the device is no longer reachable.

2.6 Watching a stream

Video reaches you from our streaming server, which necessarily sees your IP address in order to send you the video at all — as any website does. It is used to deliver the stream and is not combined with anything else, not used to build a profile, and not retained as a record of what you watched.

3. If you appear in a kitchen stream

If you work in a kitchen that streams here, this section is about you, and it is the part of this policy we take most seriously.

Nothing you do is recorded. Video passes through memory on our server and is overwritten within seconds. There is no archive, no replay and no export. We cannot produce footage of you to your employer, to a customer, to an insurer, or to any authority, because it does not exist anywhere.

No audio is captured. Conversations in the kitchen are not transmitted and cannot be listened to.

Cameras must be positioned so faces are not readily identifiable — over a tandoor, tawa, handi or pass, rather than at head height across a room. The deliberately low picture quality supports this: at the resolution these cameras produce, faces, screens and documents are not reliably legible. We do not sharpen, upscale or enhance the picture, and we do not operate any face recognition, identification or tracking of any kind. We will not build one.

Under the Digital Personal Data Protection Act 2023, the restaurant that operates the camera is the Data Fiduciary for anything its camera shows; we transmit its stream on its instructions. Your employer is required by our terms to obtain your written consent before streaming and to display signage in the kitchen.

If you have not consented, or you withdraw consent, write to seemykitchenlive@gmail.com. You do not need to go through your employer, and you do not need to explain why. We will take the feed offline while it is investigated.

4. If you run a restaurant

To operate your listing we hold the email address you sign in with, your business name, address, area and contact details, your FSSAI licence number and expiry, the opening hours and listing content you enter, your camera configuration, and a billing record of what you have been invoiced.

We also hold operational technical data from the kitchen agent software — which version it is running, the machine name it reports, and when it was last heard from — so that a stream that stops can be diagnosed without anyone visiting your premises. Your recorder password is stored on your own machine and is not transmitted to us.

Much of your listing is public by design: that is what you are paying for. Your email address, billing records and diagnostic data are not.

5. Who else processes this data

We use a small number of infrastructure providers, each doing one job:

• Supabase — the database holding listings, accounts and the event counts described above.
• Vercel— serves the website and the apps' API.
• Hetzner — the streaming server. Video passes through its memory and is never written to its disks.
• Google and Apple push services — deliver notifications to devices that asked for them.
• Google Places — matches what you type when you ask us to approach a restaurant against a list of real businesses, so that everyone asking for the same place is counted together. Your search text reaches Google for that purpose only. We send no identifier of yours with it.

We do not sell personal data, do not share it with advertisers or data brokers, and run no advertising network code in the website or the apps.

6. How long we keep things

• Video — seconds. It is never written to storage.
• Event counts — retained as aggregate history for the owner dashboard. They contain nothing that identifies a person.
• Notification records — until you turn notifications off or the device stops being reachable.
• Restaurant requests — kept while we are still trying to bring that kitchen here, so we can tell you what they say. Reinstalling the app ends your side of it: the identifier is gone and the request can no longer be traced to your device.
• Restaurant accounts — for as long as the listing exists, and afterwards only as required for tax and accounting.

7. Your rights

Under the Digital Personal Data Protection Act 2023 you may ask what personal data of yours we hold, ask for it to be corrected, ask for it to be erased, and complain about how it has been handled. Write to seemykitchenlive@gmail.com.

For diners this will usually be a short answer, because there is normally nothing held that is linked to you.

8. Children

This service is not directed at children, has no social features, no messaging, no comments, no user profiles and no way for anyone to upload content or contact another user. We do not knowingly collect personal data from children. Our standards on child safety are set out at /child-safety.

9. Security

Stream playback is authorised by short-lived signed tokens, so stream addresses are neither public nor permanent. Publishing to a kitchen feed requires a per-camera key. Database access is restricted so that the public can read only published listings. The single most effective security measure in this product, though, is that the sensitive material is never stored in the first place.

10. Grievance Officer

As required by the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021 and the Digital Personal Data Protection Act 2023, complaints may be addressed to our Grievance Officer at seemykitchenlive@gmail.com. We acknowledge within 24 hours and aim to resolve within 15 days.

11. Changes

If this policy changes materially we will update the version at the top of this page. Continued use after that date is acceptance of the revised policy.

Restaurant operator? The Restaurant Publisher Terms set out your obligations. Using the site or apps as a diner is covered by the Terms of Use.