Skip to content
Sri Sri Drishti
EventsFor teachersFor institutionsAboutContactLog inGet the app
Menu
EventsFor teachersFor institutionsAboutContactLog inGet the app

Privacy Policy

Sri Sri Drishti · Last updated 12 November 2026

This policy explains what Sri Sri Drishti collects, why, who it is shared with, and how to get rid of it. It describes what the app actually does today.

1. What we collect

Information you give us

  • Your phone number, when you sign in with a one-time code. This is how your account is identified.
  • Your Google account email and name, if you choose to sign in with Google.
  • Profile details you choose to add: full name, username, a short bio, a profile photo, and links to your own social media pages.
  • Content you create: event listings, event registrations, contact requests, ratings and reviews.
  • If you apply to be a teacher: the identification you upload for that review.

Information collected as you use the app

  • Which events you subscribe to or register for.
  • Who you follow and who follows you.
  • Precise location — only if you turn location on. Your exact coordinates are sent to us when you look for activities or members near you, so we can work out what is close. They are not stored. Your position is never saved to your profile and we keep no history of where you have been. Distances are recalculated on your phone as you move, and this only happens while the app is open in front of you — nothing runs in the background. You can turn location off at any time, and switching off “Discoverable” in Privacy Settings removes you from nearby results entirely.
  • A device token for push notifications, if you allow notifications. This identifies the installation, not you personally, and is deleted when you sign out or turn notifications off.
  • Basic technical and usage data, through Google Analytics for Firebase: app version, device type, which screens are opened, and a few actions — signing in and finishing sign-up, viewing, registering for or sharing an event, following someone, the category of a search (never the words you type), sending a report or blocking someone, applying to be a teacher, and ticking off a Daily Sadhana practice. These records carry an event’s ID where one is involved, but never who you followed, reported or blocked, and never your name, phone number or email address.
  • From store versions of the app only: crash reports, through Firebase Crashlytics, and performance measurements (how long the app takes to start and how long requests to our servers take, with any IDs removed from the addresses), through Firebase Performance Monitoring.
  • Who invited you, and activity on links you share — see section 3.

2. Contact sync — read this part

Contact sync is optional, off until you turn it on, and it is the one feature that touches data about people who are not our users. This is exactly what happens.

When you sync, your phone reads your address book on the device and converts each phone number into a one-way code (an HMAC-SHA-256 hash). Contact sync never sends us the full phone numbers of your contacts, and never stores them. Sharing one person you choose, so a teacher can contact them, is a separate step described in section 3B.

What is sent to us and stored, for each contact:

  • the one-way code of the number;
  • the name you saved for that contact in your phone;
  • a masked form of the number showing only the first two and last two digits, for example +91••••••••02, so you can recognise which contact a row refers to;
  • anything you add yourself, such as a relation or a note.

We use the codes to count how many other members have the same person saved. Other members are told only a number — “you have contacts in common” — never who. Your name is revealed to another member only when you choose to share a specific contact, one at a time. Full phone numbers are exchanged only after an introduction that both people have accepted.

You can delete a synced contact, or all of them, at any time from the Network tab.

3. Invite links, sharing and your community

Members can share an invite link, or a link to an event. This is what those links record.

  • Who invited you. When you join through a member’s link — by tapping it, through the Play Store install that followed it, because you left your number on that link’s page, or by typing their invite code in your first 7 days — we record that member as your inviter, and which link it was. Administrators can correct this; every change is logged.
  • Link activity. When someone opens a shared link we count what happens next: opened, viewed, tapped Join WhatsApp or Register, joined or registered. A visitor’s steps are tied together by a random ID — on the website a first-party cookie called sd_vid that lasts one year, in the app a random ID created for each installation. It is not your name or number, and it is linked to your account only if you are signed in. Your IP address is used only to limit abuse and is not stored.
  • People who are not members yet. The page behind a shared link lets a visitor leave their name and phone number, with this consent shown beside the form: “I agree that Sri Sri Drishti, the person who invited me, and an Art of Living teacher or volunteer may contact me on this number about Art of Living programmes.” We store the name, a masked number (for example +91••••••••78), a one-way code of the number so we can recognise the person if they join and credit whoever invited them, and the full number encrypted (AES-256-GCM). The person is then passed to one Art of Living teacher or volunteer: the member whose link it was if they are one, otherwise the nearest teacher or volunteer who invited that member. That teacher or volunteer sees the name and masked number and can view the full number to call; each time they do, it is recorded. The member whose link it was sees only the first name and how it is going. Sri Sri Drishti administrators can also see the full number, and each time one does, or exports a list, it is recorded against them. People who agreed to the earlier wording (“…and share my first name with the person who invited me”) are never passed on in this way. The number is used to contact the person about Art of Living programmes, as the consent says, and for nothing else.
  • WhatsApp groups. A link’s page can offer to join a WhatsApp group run by the event’s teacher or by Sri Sri Drishti. Joining takes you to WhatsApp, where WhatsApp’s own privacy policy applies and the group’s admins can see your WhatsApp number.
  • How far a share went. A member sees how many people opened each link they shared and how many joined or registered. Nobody who registered through a link is named. People who passed the link on are named only if the member invited them. An event’s teacher, and administrators, see the same counts for the event, with the names of the members who shared it.
  • Telling your inviter. When you join through someone’s invite, they get a notification with your name, for example “Amit joined Sri Sri Drishti”. They can turn these off.

3A. Teachers: the outreach portal and Gmail

Approved teachers can use the outreach portal at srisridrishti.com/dashboard to contact institutions about Art of Living programmes. A teacher can choose to connect their own Gmail account, so that emails to those institutions are sent from the teacher’s own address. Connecting Gmail is optional, and it gives us access only to the account of the teacher who connects it.

When you connect Gmail you grant two Google permissions: your email address, to show which account is connected, and permission to send email on your behalf. We do not ask for permission to read your email, and we do not read your inbox. This is how we use them:

  • Sending. We send only the outreach emails you set up in your campaigns, from your address, to the institutions in those campaigns. Every message carries a line that lets the recipient opt out.
  • Where replies go. Replies come back to your own inbox, as with any email you send. We see a reply only if you paste it on the dashboard or turn on the optional script described below.
  • Replies you tell us about. If an institution answers you somewhere else, such as in your own inbox or on a call, you can paste the reply on the dashboard, or mark that they replied or asked to stop. A pasted reply is handled like any other reply.
  • Optional script in your own Google account. If you choose, you can run a small script from the dashboard in your own Google account. It runs as you, with permission you give to it in Google, not to us. Every 10 minutes it looks for mail from the addresses of your institutions received in the last two days and sends only those messages to us; nothing else in your inbox is sent. You can turn it off on the dashboard, after which we accept nothing from it, or delete it in Google.
  • Replies from your institutions. For replies we store the sender, subject and text in your conversation history, so you can follow the conversation on the dashboard. We use them to stop all messages to anyone who asks to opt out, and to draft an answer on your behalf.
  • AI drafting. To draft that answer, the conversation with that institution is sent to Groq, our AI provider, which processes it on our behalf only.
  • Your access key. We store the access key Google issues for your account (an OAuth refresh token), encrypted with AES-256-GCM. You can disconnect Gmail on the dashboard at any time: we then revoke the key with Google and all access stops. You can also remove access from your Google Account at myaccount.google.com/permissions. To have stored conversations deleted, write to us at the address in section 13.

Sri Sri Drishti’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In particular, we do not use Gmail data for advertising, we do not sell it, we do not use it to train AI models, ours or anyone else’s, and no person reads it unless you ask us to about a specific message, it is needed for security such as investigating abuse, or the law requires it.

3B. Sharing someone who wants to hear about Art of Living

A member can pass on a person who would like to hear about Art of Living programmes (a “lead”) to a teacher, a volunteer or a team, so that they can contact them. The member types the person in or picks them with the phone’s own contact picker, which gives the app only the contacts picked, never the address book. Nothing is sent until the member ticks this confirmation, which we store with the share: “I confirm each of these people agreed that I share their name and number with Sri Sri Drishti, so an Art of Living teacher or volunteer can contact them about programmes.”

  • What we store: the person’s name, their phone number and email if given, a short note, and how the lead is going. The number and email are stored encrypted (AES-256-GCM), with a one-way code of each so we can tell when two members share the same person.
  • Who sees it: the teacher, volunteer or team it was shared with see the name and a masked number, and can view the full number to make contact; each view is recorded and the team can see it. The member who shared it sees how it is going. Another member who shares the same person is told only that someone is already in touch, or how many members know them, never who, unless that person agrees. Sri Sri Drishti administrators can see leads and their history.
  • The person themselves: the first WhatsApp message a teacher opens from a lead says it comes through Sri Sri Drishti and how to stop. If they ask not to be contacted, the lead is marked “Do not contact”, and no member can pass their number on again. If they join Sri Sri Drishti, they can choose whether to connect with the teacher who contacted them.
  • Erasure: the person can ask us, at the address in section 13, to erase their details. We then blank their name, number, email and notes and their one-way codes, and keep only a record that a lead existed and what happened to it, without anything that identifies them. If they also asked not to be contacted, we keep a one-way code of their number so that the request goes on working.

3C. Daily Sadhana

Daily Sadhana is optional. If you use it, we store the practices you plan, the days you tick them off, your streak, your reminder times, and for each of your devices whether reminders are scheduled, its time zone and whether notifications are allowed (used only to explain a reminder that did not arrive). Reminders are scheduled on your phone.

  • Private by default. Nobody sees your Sadhana until you share it with someone and they accept, or you approve their request.
  • Selected people see what you chose for each of them: a summary (each day done or missed, and your streak) or the practices too. A missed-day alert goes to someone only if you turn it on for that person.
  • Everyone on Drishti, if you choose it, shows signed-in members only your summary on your profile, never the practices and never alerts.
  • Stopping a share takes effect at once and the other person loses the history too. A notification already shown on their phone cannot be recalled.
  • Your Sadhana data is deleted with your account.

3D. Error reports and website analytics

Both of the services in this section are used only while we have them switched on. While one is off, nothing described under it is collected.

Error reports (Sentry)

  • When something fails on our servers, or on the website at srisridrishti.com, an error report can be sent to Sentry, a service that collects error reports so that we can find and fix the problem. A report contains the error, where in our code it happened, the kind of page or server address involved with any IDs replaced (for example /api/v1/users/:id), and technical details such as the browser, operating system and version.
  • Personal data is removed before a report leaves our systems: we take out what was sent in the request, cookies, the part of an address after “?”, sign-in headers, IP addresses and any user details other than an account number, and we blank out phone numbers, email addresses, names, messages and locations. We do not use Sentry’s session recording, so it never sees your screen.
  • The app reports its own crashes through Firebase Crashlytics instead; see section 1.

Website analytics (Google Analytics)

  • The website can use Google Analytics to count visits and a few steps people take: opening the app download link, tapping an app store button, starting and completing the teacher portal login, and a teacher’s first fetched lead and first campaign.
  • You choose. Google Analytics is not loaded, and sets no cookie, until you choose “Accept” on the website’s cookie notice. If you choose “Decline”, it is not loaded at all. Your choice is remembered in your browser, and you can change it at any time with “Cookie choices” at the foot of the website’s public pages.
  • What Google receives once you accept: the page you are on with anything identifying taken out (no part after “?”, every page of the teacher portal reported as /dashboard, and invite codes and IDs in addresses replaced), the steps listed above, your approximate location derived from your IP address (Google Analytics 4 does not store IP addresses), and your browser and device type. We never send your name, phone number, email address, any lead, campaign or message details, invite codes or search text. Google signals and ad personalisation are turned off.
  • Google keeps this data only for the retention period set in our Google Analytics account, after which it is deleted.
  • The Sri Sri Drishti app does not use the website’s Google Analytics or its cookie; the app’s usage data is described in section 1.

4. Why we use it

  • To run the service: sign you in, show your feed, register you for events, and deliver notifications you asked for.
  • To show you events and members that are relevant, including by distance if you enabled location.
  • To let members find people they already know, through contact sync.
  • To credit members who invite others, and show them how their shares travelled.
  • To keep the community safe: investigating abuse reports and enforcing the Terms of Service.
  • To fix problems and understand which parts of the app and website are used.

We do not sell your personal information. We do not use it for advertising, and we do not share it with advertisers or data brokers.

5. Who else handles your data

We use a small number of service providers, who process data on our behalf and are not permitted to use it for their own purposes:

  • Contabo — server and database hosting, in Mumbai, India, for the servers that run the app and store your account data.
  • Amazon Web Services (S3) — storage for the photos you upload, in the Mumbai region of India.
  • Google Firebase — sign-in, push notifications, analytics, crash reports and performance measurement.
  • 2Factor.in — sending sign-in codes by SMS. They receive your phone number for that purpose.
  • Google Maps — displaying maps and locations.
  • WhatsApp — only if you choose to join a group from a link’s page; see section 3.
  • Groq — drafting answers to institutions’ replies for teachers who use the outreach portal; see section 3A.
  • Sentry — error reports from our servers and the website, with personal data removed first, only while switched on; see section 3D.
  • Google Analytics — counting visits to the website, only if you accept it there; see section 3D.

We will also disclose information where the law requires it, or where it is necessary to protect someone’s safety.

6. What other members can see

Public on your profile: your name, username, photo, bio, teacher status, any social links you added, and your follower and following counts.

Not shown to other members: your phone number, your email address, and your synced contacts. Your phone number becomes visible to another member only after you have both accepted a contact request or an introduction.

If you switch off “Discoverable”, you will not appear in nearby results or people search. Approved teachers remain searchable, because being findable is the purpose of a teacher listing.

Your community: the member who invited you sees your name, photo, when you joined, whether you have been active recently, and how many people you have invited. Members further above you see only a count, unless you turn on “Show my name to everyone above me” in Privacy Settings. Nobody in your community sees your phone number. If your account is suspended only a count is shown, and if you delete it you appear as “a former member”; the people you invited stay where they are.

7. How long we keep it

We keep your information for as long as your account exists.

When you delete your account, it is hidden from other members immediately. Your personal data is erased 30 days after you delete the account. If you sign in again within those 30 days, your account is restored. The 30-day window exists so you can recover an account deleted by mistake. Your synced contacts are deleted along with your account.

Shared leads (section 3B) are kept while they are being followed up, so that the same person is not contacted twice and a “Do not contact” request keeps working. Their personal details are erased when the person asks us, as described there.

Leads — the name and number someone who is not a member left on a link’s page — are deleted 12 months after they last left it, whether or not they joined. They can ask us to delete them sooner at the address in section 13. Link activity is kept while the link’s owner has an account.

8. Security

Data is encrypted in transit. Sign-in tokens are held in the device’s secure storage. Access to production systems is restricted. No service can promise perfect security, but we take reasonable measures to protect your information.

9. Children

Sri Sri Drishti is not intended for children under 13, and we do not knowingly collect information from them. If you believe a child has given us information, contact us and we will delete it.

10. Your rights

  • See and edit your profile in the app.
  • Turn location and discoverability off in Privacy Settings.
  • Control which notifications you receive, including quiet hours.
  • Delete individual synced contacts or all of them.
  • Delete your account, and with it your data, from Settings.
  • Turn “Show my name to everyone above me” and join notifications on or off.
  • If you left your number on a link’s page, or a member shared your details with a teacher, and you want them deleted or do not want to be contacted, write to us at the address below.
  • Choose who sees your Daily Sadhana, and stop any share at any time.
  • Accept or decline website analytics, and change your choice at any time with “Cookie choices” at the foot of the website’s public pages.
  • In the app, version 1.2.33 and later, turn off sharing of usage analytics with “Share usage analytics” in Settings.

For a copy of your data, or any request we cannot handle in the app, contact us at the address below.

11. Where data is stored

Our database and servers are hosted in Asia, and our providers may process data in other countries. Where data leaves its country of origin, we rely on the protections our providers have in place.

12. Changes to this policy

We may update this policy. The “last updated” date above changes when we do, and we will give notice in the app if a change is material.

13. Contact

Sri Sri Drishti is operated by Collabdiary Private Limited.

Questions, requests, or privacy concerns: srisrisevaks@gmail.com.

See also the Terms of Service.

This page is the hosted copy of the policy shown inside the app under Settings → Terms & Privacy Policy. The two are kept identical.

Request deletion of your account and data

Sri Sri Drishti

Events, teachers and your community in one place.

EventsFor teachersFor institutionsAboutContact
info@srisridrishti.comWhatsApp +91 96992 24825
Operated by Collabdiary Private Limited. Privacy Policy · Terms of Service · Delete your account