Nosh Privacy Policy
Last updated: 28 October 2026
Nosh Labs ("Nosh", "we", "us") operates Nosh, a conversational assistant on
WhatsApp and in your web browser that helps you search for restaurants, build a cart, and place
food orders on Swiggy, and order groceries from Swiggy Instamart where that
is available to you. This policy explains what data we handle when you
use Nosh and how we handle it.
1. Data we collect
- WhatsApp data. Your WhatsApp phone number, the text of
messages you send to Nosh, and which button or list option you tap in
Nosh's replies, received via the WhatsApp Business Platform.
- Nosh in your browser. If you use Nosh in your web
browser at nosh.arysha.app/chat instead of WhatsApp, no phone number is
collected. You can start chatting straight away as a guest; when you ask
for something that needs Swiggy, such as finding food near you, Nosh asks
you to sign in with your Swiggy account. Nosh creates an account identified
only by a random code when you first open the chat, and records when it was created and whether we have removed its
access (anyone can use Nosh in the browser; we remove an account's access
only if it is misused). Nosh receives the text of the messages you send and which
button you tap, as it does on WhatsApp. Your sign-in is a random code: your
browser keeps it in a single cookie
that the page's own scripts cannot read and that is used for nothing but
keeping you signed in. Nosh's server stores only an irreversible hash of
it. So that signing in again from another browser or device brings back
the same Nosh account, Nosh keeps a scrambled form of the user number
Swiggy gives your Swiggy login (made with a secret key, so it can't be
turned back into the number) alongside the accounts it belongs to.
- Voice notes. If you send Nosh a voice note, the recording
is converted to text so Nosh can act on it. Nosh does not store the
recording; the text is then handled exactly like a message you typed. When
you send a voice note, Nosh may also reply with one; that reply is delivered
through WhatsApp like any other message.
- Swiggy account data. Once you connect your Swiggy account
(via Swiggy's own sign-in), Nosh can read information needed to act on your
requests: saved addresses, restaurant and menu search results, your cart,
the coupons and payment methods Swiggy offers for it, your recent orders
(used to recommend dishes and to reorder), and order status. For grocery
orders this also covers Swiggy Instamart: product search results, your
Instamart cart and its bill, the items you often buy there, and your
recent Instamart orders, and where an order in progress has reached. If you
ask Nosh to add a new delivery address, the address, name and phone number
you give are shown back to you and, only after you confirm, sent to Swiggy
to be saved in your Swiggy account; Nosh keeps them for a few minutes while
it waits for your answer and not after. This data
comes from Swiggy and is subject to Swiggy's own privacy policy in addition
to this one. Nosh never sees your Swiggy password or OTP: you sign in on
Swiggy's own page.
- Public beta. Nosh is in public beta: anyone can
message it, and no sign-up or access request is needed. Before the public
beta, Nosh was invite-only, and people who asked to join gave us an
email address and a WhatsApp number through our request form (hosted on
Google Forms) or by email. We used them only to decide on the request, to
give that WhatsApp number access, and to tell the person the outcome.
- The Nosh website. The home page and Nosh in your
browser (the chat at nosh.arysha.app/chat) run one script for this: Google's
tag for Google Ads, so we can tell whether our ads lead people to use Nosh.
It lets Google set its own advertising cookies. On the home page it tells
Google when a "Message Nosh on WhatsApp" button is tapped; in the chat, when
the chat is opened and when something is added to your cart. The website's
other pages run no analytics, advertising or tracking scripts.
It is never told what you write, what you order, prices, your Swiggy
account or anything else about you. Apart from those, the only cookie is
the sign-in cookie of Nosh in your browser described above. Nosh in your
browser also remembers, in your browser's own storage, a counter of which
of Nosh's replies it has already shown you, so it doesn't show one twice. Like any
website, the servers that deliver it see the technical details of each
request (such as IP address and browser type) in order to respond to
it.
- Support tickets. If you open a ticket on the website's
Support page, we collect the email address and WhatsApp number you give
(no number is asked for when you are signed in to Nosh in your browser,
and the ticket is linked to that Nosh account instead), and whatever you
write in the ticket. Please don't put passwords, OTPs or
payment details in a ticket. To limit misuse, the Support page counts
requests from each IP address for up to an hour; that count is held only in
the server's working memory and is not stored. Starting a sign-in with
Swiggy is counted the same way, for the same reason.
2. How we use data
- To understand what you're asking for and carry out the requests you
make in the conversation - searching restaurants, updating your cart,
applying coupons, and placing orders you explicitly confirm.
- Message text, and the Swiggy data needed to answer it, is sent to
third-party AI services we use to interpret your requests, translate
between languages, and write replies (see "Third parties" below).
- Troubleshooting. We keep a short-lived, encrypted log
of your messages to Nosh and Nosh's replies, so that if you report
something went wrong, we can look at what actually happened in that
conversation and fix it. A voice note is logged only as the text it was
converted to, never as audio. This log is only ever reviewed to investigate
a specific reported problem, not browsed or monitored routinely. If you
open a support ticket and confirm your number, or open it while signed in
to Nosh in your browser, the support assistant reads it to answer that
ticket (see "Support" below).
- Support. A support ticket is read and answered first
by an AI assistant. It is given what you wrote in the ticket, and it cannot
see your Swiggy account or your orders. It can read your recent WhatsApp
conversation with Nosh (the troubleshooting log described above) only
after you confirm the number on the ticket is yours, by sending the short
code shown on your ticket page to Nosh on WhatsApp from that number.
Typing a number is never enough, so nobody else can have your conversation
read by entering your number. If you open the ticket while signed in to
Nosh in your browser, the assistant can read your recent conversation with
Nosh there, including from other browsers or devices you signed in to with
the same Swiggy login, from the start, because being signed in to your
account is the proof; nobody else can open a ticket that reads it. Otherwise, until you
send the code, the assistant sees only the ticket. If it cannot solve the problem, if the ticket is about a
payment, your data or security, or if you ask, the ticket is passed to a
person at Nosh, who reads it and replies on your ticket page and may email
you. To investigate, that person may look up the troubleshooting log for
the WhatsApp number you gave, or for the Nosh account the ticket is linked
to. We use your email address, number and account only to handle your
ticket.
- Preventing misuse. A number that sends Nosh a burst
of messages in a few seconds, or too many in a minute, is automatically
paused for an hour, and a
number that keeps doing so may be blocked. A blocked number is kept only
as an irreversible hash, so the list holds no phone numbers, until it is
unblocked.
- Orders need your confirmation. Nosh places an order
only after showing you the items and the final total and receiving your
explicit confirmation. A voice note cannot confirm an order.
- We do not use your WhatsApp messages or your Swiggy account data to
train AI models, for advertising, or for any purpose other than carrying
out your request in the conversation or troubleshooting it, as described
above.
3. Third parties we share data with
- Meta / WhatsApp - to send and receive your messages, under
the WhatsApp Business Platform.
- Swiggy - to search restaurants and Instamart products,
manage your cart, and place orders you request. Swiggy is the data fiduciary for your Swiggy account
data; Nosh only accesses what's needed to act on your request, and Swiggy's
own terms prohibit us from using that data for training, profiling, or any
purpose beyond fulfilling it. If you pay by UPI, you pay on Swiggy's own
payment page: Nosh sends you the link to it, and never asks for, sees or
stores your UPI ID or any payment details.
- Google Cloud (Gemini on Vertex AI) - the AI model that
interprets your request, decides what to look up on Swiggy, and writes
Nosh's replies. It also converts voice notes you send into text, for which
it receives the recording, and turns Nosh's reply into speech when Nosh
answers a voice note with one. To do that it receives the text of your messages and the
Swiggy data needed for the current request, such as restaurant, menu and
grocery product results, your cart, and the labels of your saved addresses. It also
receives the text of a support ticket you open, so the support assistant
can answer it, and, once you have confirmed your number as described
above, the text of your recent WhatsApp conversation with Nosh; your email
address and WhatsApp number are not sent with it. Under Google
Cloud's terms, Google does not use this data to train its models.
- Google Ads - on our home page, Google's tag tells
Google Ads when a WhatsApp button is tapped; if you use Nosh in your
browser, it tells Google Ads that the chat was opened and when something is
added to your cart, with Google's own cookies and the technical details of your
browser (such as IP address), so we can measure our ads. Nothing you write
or order is sent to it. Google's own privacy policy applies to that data.
- Render - the hosting provider that runs Nosh's servers
and the database holding the encrypted troubleshooting log described
below, your encrypted support tickets, your encrypted Swiggy connection token,
and browser accounts with the hashes of their sign-ins. It stores and processes data only on our
behalf.
We do not sell your data, and we do not share it with any other third
party.
Where data is processed. Nosh's servers are hosted in
Singapore, and the AI processing described above is carried out on Google
Cloud infrastructure that may be located outside India. By using Nosh you
understand that your messages, and the Swiggy data needed to answer them,
may be processed outside India by the providers listed above, for the
purposes described in this policy only.
4. Data retention
- Data obtained from Swiggy (addresses, cart contents, order details) is
used only for the current request and is not stored by Nosh beyond what's
needed to complete an in-progress conversation or order.
- We keep a Swiggy connection token so you don't have to reconnect your
account every time you message us. You can disconnect your Swiggy account
at any time through Swiggy; doing so removes Nosh's access to your Swiggy
data.
- While a conversation is in progress, Nosh keeps its recent messages,
your chosen address and your cart reference in the server's working
memory so it can follow what you say next. This is not written to
permanent storage and is cleared when an order is placed or the server
restarts.
- To keep each order short on WhatsApp, Nosh counts how many messages it
has sent your number for the order in progress (a number, kept only in the
server's working memory and reset when an order is placed or after 6 hours
of quiet). After about 20, or whenever you send "web", Nosh sends a link to
carry on in the web chat. The link works once, for 15 minutes, and signs
that browser in to your Nosh web account (made for you if you don't have
one, and linked to your Swiggy login) without signing in again. Your
conversation in progress, chosen address, cart reference and language move
to the web chat with you, and that account uses the Swiggy connection token
your WhatsApp chat already has, rather than a copy of it. Signing out of or
deleting the web chat account removes only its use of that token; your
WhatsApp chat stays connected. Anyone you forward an unused link to could
open your web chat with it, so please don't share it. A browser already signed in to another Nosh account asks before switching, and the web chat shows which WhatsApp number (partly hidden) the chat came from.
- The invite-only period has ended with the move to public beta. The access
requests collected for it (email address and WhatsApp number) and the list
of WhatsApp numbers that were invited, which was only ever kept in an
irreversibly hashed form, are being deleted as it ends. If you asked for
access and want yours deleted sooner, write to us and we will do it.
- A guest account (one that has never signed in with Swiggy) is
deleted 7 days after it was created, with its sign-in. A web chat account
that has signed in with Swiggy is kept until you delete it. A sign-in ends
when you sign out (on one device or all of them), after 30 days without
use, or 90 days after it began. You can delete your
account at any time from the Account menu in the web chat:
that immediately deletes the account, its sign-ins, its Swiggy connection
token, its link to your Swiggy login and its conversation in progress. Its troubleshooting log is then
deleted 14 days after its last message, like any other. If we removed an
account's access because it was misused, a scrambled (keyed-hash) form of
its Swiggy user number is kept after the account is deleted, so that
signing in again doesn't bring access back. It holds nothing else, and is
deleted if we give access back.
- Your WhatsApp number, kept in encrypted form with the troubleshooting
log so the administrator can find your conversation, is deleted together
with that log.
- The troubleshooting log described above is kept for 14 days after your
most recent message to Nosh, then automatically and permanently deleted.
An active conversation's log is retained on a rolling basis (14 days from
your last message, not your first) for as long as you keep messaging us.
- A support ticket (your email address, WhatsApp number and the
conversation in it) is kept encrypted for 30 days after it was last
updated, then automatically and permanently deleted. To have a ticket
deleted sooner, write to us.
5. Your rights
For requests about your Swiggy account data (access, correction,
deletion), please contact Swiggy directly through the Swiggy app, since
Swiggy is the data fiduciary for that data. For anything related to your
conversation with Nosh, or general questions about this policy, contact us
using the details below. You can delete a browser account yourself,
as described above.
6. Security
Data in transit between Nosh, WhatsApp, Swiggy, and our AI processors is
encrypted. Access to stored connection tokens and the troubleshooting log
described above is limited to what Nosh's service needs to operate, and
both are encrypted at rest. Your phone number is never stored as plain
text: your Swiggy connection is filed under an
irreversibly hashed form of it, and the troubleshooting log keeps it in
encrypted form, as described below.
Nosh's administrator can read troubleshooting logs, to investigate a
problem, through a private page that requires a password and a one-time code
from an authenticator app. So that the administrator can find a
conversation, the troubleshooting log keeps your WhatsApp number and the
time of your last message alongside it, encrypted in the same way as the
log, and that page lists the numbers that have messaged Nosh in the last 14
days. Your number is deleted from this record at the same time as your log.
The same private page is where the administrator reads and answers support
tickets. The page is not indexed by search engines and is never cached.
A support ticket can be opened only through its private link, which
contains a long random code. Anyone who has that link can read the ticket, so
keep it to yourself. When a ticket is passed to a person, our team is
notified with the ticket's reference only: nothing you wrote, and neither
your email address nor your number, is included in that notification.
7. Children's privacy
Nosh is not directed at, and we do not knowingly collect data from,
children under 18.
8. Changes to this policy
We may update this policy from time to time. Material changes will be
reflected by updating the "Last updated" date above.
9. Contact us
For privacy questions, requests, or grievances related to Nosh, contact
us at noshdev@arysha.app.