Current as of 28 October 2026
Please note. This policy describes exactly what our software does today, and nothing it does not do. We update it whenever the product changes, and the date above changes with it.
You probably do not know what Leashloop is, so here is the short version.
Your dog trainer uses Leashloop to keep their client records, schedule sessions, write session summaries and keep track of payments. Our software sends you WhatsApp messages about these on their behalf. The messages come from our number rather than theirs, and their name is in each message so you know who it is about.
You do not have an account with us. You never signed up, and there is nothing to install or log in to. Your trainer entered your name and your phone number.
To reach your trainer, use the "Message trainer" button in the message. It opens a chat with your trainer's own WhatsApp number. We are not in that conversation.
If you reply to our number instead, no person reads it. You will get an automatic reply pointing you to the button. Your message is recorded by our system, but nobody monitors that inbox and your trainer does not see it.
What we send, and when. We message you when your trainer books, changes or cancels a session, on the evening before a session, when your trainer sends you a session summary, asks for a payment or records one, and when a prepaid pack has two sessions left. Section 5 lists what each message carries. We do not set alarms or notifications on your phone, and we cannot promise a message will arrive at any particular time.
To stop receiving these, see section 12.
If your trainer added your email address before October 2026, you may also receive a calendar invitation by email when a session is booked, changed or cancelled. That lands in your own calendar, and your own phone decides whether and when to remind you. If you reply to that email, your reply goes to your trainer. We are phasing these emails out.
Leashloop is operated by Anish Kamlakar Hirlekar, a sole proprietor trading as Leashloop, based in Mumbai, Maharashtra, India.
If you are a trainer using Leashloop, we decide how your own personal data is handled. Under India's Digital Personal Data Protection Act, 2023, we are the Data Fiduciary for it.
If you are a client of a trainer, your trainer entered your details and decides what to record about you and why. We store it and show it back to them. Your trainer is the Data Fiduciary and we act as their Data Processor.
One thing worth being plain about. When we message you about a session, the message comes from our own WhatsApp number and under our own name, and we wrote the wording. Your trainer chose to book the session and chose to enter your details; we decide how the message reads and when it goes out.
So if you want your details corrected or removed, please ask your trainer first. You can also contact us directly, and we will help, but the records belong to your trainer and we will normally check with them before changing anything.
Signing in with Google is the only way into Leashloop. We ask Google only for basic sign-in details. We cannot see your Google calendar, your email, your contacts or your files.
We never handle money: a payment goes from your own UPI app straight to your trainer, and your trainer marks it paid. We hold no card or bank account details and no identity document numbers for anyone.
We store this so your trainer can run their business, and we show it back to them.
What we send to clients. If the client's record has a phone number, we send that client WhatsApp messages from our own business number. Each carries the client's first name and:
Most messages have a button that opens a chat with the trainer's own WhatsApp number. A payment request's button opens a page showing the trainer's name, the amount, the UPI ID and QR code, and a link that opens your own UPI app. A receipt's button opens the receipt. We do not record that you opened any of them.
Messages are sent through Meta's WhatsApp Business Platform, so Meta handles each message in order to deliver it. Each message follows a fixed wording that Meta has approved in advance. Trainers cannot change the wording.
Change and cancellation messages are held for a few minutes before sending, so that several edits in a row arrive as one message rather than several. The message about tomorrow's session goes the evening before.
Where a trainer added a client's email address before October 2026, we also send a calendar invitation by email. That invitation carries the trainer's name and is set so that any reply reaches the trainer's own email address rather than us.
We also publish a session summary page when your trainer sends you a summary. After a session, your trainer writes what happened and what to practise, then sends it. That creates a web page at an address made of random characters, and we send you the link on WhatsApp. There is no account and no sign-in. We ask search engines not to index it, but it is not password protected: anyone who has the address can read it.
The link shows a preview without being opened. Wherever the link is posted in WhatsApp, everyone in that chat, and in any chat it is forwarded to, sees a preview showing the dogs' names, the session date and your trainer's business name, or their own name if they have not set one.
What that page carries: the name of each dog the summary is about, and its photograph if your trainer added one; your trainer's business name, the line under it and their logo; the session number, the date and time of the session; the text your trainer wrote; and links to that dog's other shared summaries.
What it does not carry: your name, your phone number, your email address or your address. Nothing from your dog's health records, vaccination dates or medication notes. Nothing about any other client of your trainer, and nothing about a dog that was not in that session.
A shared link has no expiry and cannot be withdrawn. Once a summary is shared it stays readable, and it travels wherever the link is forwarded. If you would rather a summary were not shared this way, tell your trainer.
A receipt page works the same way: a random address, no sign-in, not indexed by search engines, readable by anyone who has the link. It carries your trainer's business name, the line under it and their logo, the amount, the date it was paid, the dogs' names and the session date. It does not carry your name, your number or anything else about you. If your trainer marks the payment unpaid again, the page stops working.
Voice summaries. A trainer can talk through a session, or choose an audio file, instead of typing a summary. We send the audio to Sarvam AI, which turns it into text, with the names of the dogs in that session so it spells them correctly. We then send that text to Anthropic, with the dogs' names and the client's name, and Anthropic's model turns it into a draft summary. Anthropic never receives the audio, and the client never hears it. If a trainer types notes and asks for a draft instead, only those notes and the same names go to Anthropic, and nothing goes to Sarvam. The draft is not sent to anyone: the trainer reads it, can change any of it, and decides whether to send it.
We do not sell personal data, share it with other trainers, use it for advertising, or use it to train any artificial intelligence system. We do not use a client's number to send anything other than messages about their own sessions.
Two cookies, both ours, both strictly necessary.
| Cookie | Purpose | Lifetime |
|---|---|---|
| Session cookie | Keeps a trainer signed in. Contains only an account identifier | 365 days |
| Sign-in cookie | Protects the Google sign-in process against a known attack | 10 minutes |
No analytics, no advertising cookies, no tracking pixels, no tag managers. Because we set nothing non-essential, we do not show a cookie banner. Our typefaces are served from our own domain, so simply loading a page sends nothing to any third party.
| Who | What they receive |
|---|---|
| Vercel | Hosts the application. Receives technical request logs, which include IP addresses. Our servers run in Mumbai |
| Supabase | Stores the database and uploaded photographs, in Mumbai. Also holds voice summary audio until it is deleted (section 8) |
| Meta (WhatsApp Business Platform) | Delivers our WhatsApp messages. For a client, receives their phone number and everything section 5 lists for that message, and a code for its button. For a trainer, receives their phone number and their own schedule: session times, dogs' names, clients' first names and where each session is. Meta processes this in order to deliver the message, and we do not control how long Meta keeps it |
| Resend | Delivers the calendar invitation emails we are phasing out. Receives the recipient's email address and the session details |
| Signs trainers in, and returns their name and email | |
| Sarvam AI | Turns voice summary audio into text. Receives the audio and the names of the dogs in that session. Our Sarvam workspace has Zero Data Retention enabled, and we have opted out of Sarvam using our data to train its models |
| Anthropic | Turns the transcript, or a trainer's typed notes, into a draft summary. Receives that text, the dogs' names and the client's name. Never receives the audio. We use Anthropic under a commercial agreement with them; Anthropic's privacy policy is at anthropic.com/legal/privacy |
| Zoho Mail | Our own business mailbox, used for our correspondence. It does not send any of our application email |
Our database and application servers are in Mumbai, India. Some of the companies above are based outside India. Vercel and Google may process technical data such as IP addresses outside India. Meta receives the content of each message we send you, and may process it outside India in order to deliver it.
The images in our invitation emails are served from our own domain, so opening one sends nothing to any third party beyond your own email provider.
We keep data until someone asks us to delete it. The one exception is voice summary audio.
We delete our copy of the audio as soon as its transcript comes back. If that never happens, because the transcription failed or the trainer left part-way, an hourly clean-up deletes any audio older than 24 hours. The transcript and the draft are kept with the session's records, like everything else in this section.
One thing stated plainly rather than glossed: archiving a client deletes nothing. It hides the record from the trainer's everyday view. Every field remains stored, including photographs, past sessions and the record of messages we sent.
When we delete a client at someone's request, we also delete the record of messages we sent them and anything they sent to our number.
Under the Digital Personal Data Protection Act, 2023 you may ask us for a copy of the personal data we hold about you, ask us to correct or complete it, ask us to erase it, or nominate someone to exercise these rights on your behalf if you are unable to. You may also complain to the Data Protection Board of India.
How this works today, honestly. There is no self-service button that deletes an account or downloads your data. Every request is carried out by hand by the proprietor. We will acknowledge within 48 hours and complete the request within 30 days. We are building proper tools for this.
If you are a client of a trainer, please see section 3 and contact your trainer first.
Each trainer's data is separated so no trainer can see another's records, enforced both in the database and in the application. Connections use HTTPS. Sign-in cookies cannot be read by scripts in the browser. The code is in a private repository and only the proprietor has access to the production database.
One limitation you should know about. Photographs of dogs are currently stored at web addresses that do not require signing in. Those addresses are long and are not listed or published anywhere, but anyone who obtains one can open the image without an account. Photographs are also not deleted when a client is archived.
We are changing this. Until we do, please do not upload photographs showing people, house numbers, documents, or anything else you would not want stored this way.
Trainers' logos and UPI QR codes are stored the same way, at web addresses anyone who has one can open. That is needed for them to work: summary pages and receipts show the logo, and payment requests show the QR code, to people without an account.
Grievance Officer: Anish Kamlakar Hirlekar
Email: anish@leashloop.app
Location: Mumbai, Maharashtra, India
We acknowledge within 48 hours and respond within 30 days. If you are not satisfied with our response, you may complain to the Data Protection Board of India.
Reply STOP to any message we send you. We will stop sending WhatsApp messages to that number from Leashloop, for every trainer who uses Leashloop, and we will tell your trainer so they know to contact you another way. You can start again by replying START.
Stopping applies to our messages only. It does not cancel your sessions and it does not affect your own conversation with your trainer.
You can also ask your trainer to remove your number, or contact us using section 11.
Leashloop is for professional dog trainers and is not intended for anyone under 18. We do not knowingly hold data about children, and trainers are asked not to enter details of a person under 18. If you believe we hold data about a child, tell us and we will delete it.
We will update this policy as the product changes, and the date at the top will change with it. If a change materially affects you, we will say so.