This policy explains what personal data the Target 720 app — on Android, on iPhone and on the web — collects, why we collect it, how long we keep it, and what you can ask us to do with it. It is written for India's Digital Personal Data Protection Act, 2023 (DPDP Act) and the DPDP Rules, 2025.
Target 720 is operated by Vidyn.AI (“we”, “us”). We are the Data Fiduciary for the data described below. You are the Data Principal.
1. What we collect
1.1 Your account
You sign in with Google, or with Apple on iPhone. Sign-in is handled by Firebase Authentication (Google LLC), which receives your name, email address and profile picture from that account and gives us a sign-in token.
In our own database we store a Firebase user identifier, your display name, your profile picture URL, your email address, and whether that address has been verified.
We store your email address so that we can contact you about your own account — for example to confirm a purchase, to acknowledge a report you have sent us, to confirm that a request to delete your account has been received, or to send you a referral voucher you have earned (see §1.7). We do not use it for marketing, and we do not share it for anyone else's marketing. It is kept for as long as your account exists and is erased with the rest of your account data (see §5).
1.2 What you tell us about your preparation
| Data | Why we need it |
|---|---|
| Date of birth (optional) | Only if you add it to your profile; earlier versions of the app asked for it during sign-up. We keep it so that we can tell whether you are under 18 when protections for students under 18 apply. We do not use it for anything else. |
| Class level (11, 12 or dropper) | To decide which part of the syllabus to show you |
| Target exam year | To pace your study plan |
| Subjects selected | To build your plan and homework |
| Daily reminder time | To time your study reminder |
1.3 Your learning activity
- Chapters and modules you have marked complete
- Questions you attempt: the answer you chose, whether it was right, and your score
- Self-checks you record
- Questions you bookmark in your mistake notebook
- Your study plan and daily homework sets
- Streaks and the goal you set
- Timestamped records of key actions in the app — for example a module being opened, a plan being created, homework being completed — tied to your account, so the app can show accurate progress and we can tell whether a feature works
1.4 Your subscription
If you buy a subscription, we store the plan tier, whether it is active, its expiry date, and the reference numbers of the subscription and its payments. A subscription bought in the app is paid for through Apple or Google in their own stores; one bought directly from us is paid for through Razorpay, our payment provider, under its own privacy policy. We never see or store your card, UPI or bank details.
1.5 What we do not do
- We show no advertising inside the app.
- We do not sell your personal data.
- We do not send your name, email address or date of birth to advertising companies.
- We do not ask for your address, phone number, government ID, or precise location. Our analytics tool derives an approximate city or region from your internet address; we cannot locate your device.
1.6 App analytics and crash reports
To see which parts of the app students actually use, and to find out when it breaks, the app sends usage and crash information to Google Analytics for Firebase and Firebase Crashlytics (both Google LLC).
| What is sent | Why |
|---|---|
| Screens you open, and actions such as starting a mock, opening a chapter, or completing a module — with your account identifier attached | To understand which features help students and which are ignored |
| Your subscription tier, exam class and exam year; how much of the syllabus you had already covered when you joined; whether you have allowed notifications; and whether you are one of our test users | To tell whether a feature works for the students it was built for, and to separate our own testing from real use |
| A device identifier, device model, operating system, app version, and an approximate city or region derived from your internet address | To reproduce faults and tell one device's session from another |
| If the app crashes: the error, the code path, and the screen you were on — with your account identifier attached | To fix the crash, and to tell whether it hit one student or thousands |
This information is linked to your account. It is not sold. Some of it is also used to measure our advertising, which is described separately in §1.8.
Retention. Usage data is kept for 14 months and then deleted automatically. Crash reports are kept for 90 days.
If you object. Email support@target720.com from your registered address. Deleting your account (see §6) stops any further collection, and the usage and crash data held against it is deleted — at the latest when the retention period above ends. Advertising data is different — see §1.8.
Google processes this data on our instructions, which may involve processing outside India under their own terms and safeguards.
1.7 Referrals
For the referral programme (Terms §14), we also process the following.
| Data | Why we need it |
|---|---|
| Your referral code — six letters and digits, created for your account the first time the app asks for it | So that a friend can tell us you referred them |
| When a friend enters your code: a record linking your account and theirs, with the code, the date, the reward shown in the app at that moment, and the referral's status | To know who referred whom, and whether a reward is due |
| Whether the friend you referred has made a first paid purchase, and whether any of their payments to us has been refunded, in whole or in part, including a refund of a duplicate charge — read from the subscription records in §1.4 | To work out whether the referral has earned a voucher |
| Whether your account and your friend's have been used on the same device, compared using a random identifier the app creates and keeps on your device — not a hardware identifier | To spot self-referral. It is a warning our staff look at, not an automatic decision |
| When we send a voucher: its value and supplier, the supplier's order reference (never the voucher code itself), the date, and which of our staff sent it | To keep a record of what we paid out, and never to pay twice |
| Notes our staff write on a referral — for example why a voucher was refused, or sent at a different value | To record decisions on a referral |
If you entered a friend's code, the same record covers your side of it: we check your own first paid purchase, and whether any of your payments to us has been refunded, for the same purpose.
Sending your voucher. We send it to the email address on your account (§1.1). If you signed in with Apple and chose to hide your email, that is the relay address Apple gave us.
Your first name on the image you share. When you share from Refer & earn, the app makes an image on your device showing your first name, your referral code and a QR code for your link. We do not upload or publish it. You choose whether to share it and where.
On Android: Google Play Install Referrer. Google Play keeps a note of where the app was installed from — for example, a friend's referral link. Each time the app opens, it asks Google Play for that note, until Google Play answers; it stops asking after the first sign-out on that phone. If the note holds a referral code, the app fills in the “Who referred you?” field for you. Our servers receive a code only when you continue with it in that field. On iPhone nothing is read — you paste or type the code.
Who sees what. The person who referred you never sees your name or email in the app. They see counts only — how many friends have joined, are in the 14-day wait, are ready for a voucher, or have been sent one — which can tell them that a friend they referred has bought a plan. Our staff see both names and email addresses in our admin tool, to check a referral and send the voucher.
If you are under 18, you take part in the referral programme only with the consent of your parent or legal guardian.
Your copy. Export my data (§6) includes your referral code, the status and value of the rewards for friends you referred (not who they are) and, if someone referred you, the code you entered and when.
1.8 Advertising and its measurement
We advertise Target 720 on other apps and websites, through Google Ads (Google LLC) and Meta (Meta Platforms, Inc. — Facebook and Instagram). To find out which adverts bring students to the app, the app shares some information with those two companies. This section applies to versions of the app released after 1 October 2026.
| What is shared | With whom |
|---|---|
| Your device's advertising identifier. On iPhone, only if you allow tracking when the app asks | Google Ads, Meta |
| That the app was installed and opened, that you finished setting up your account, that you started a checkout and for which plan, and that a subscription was started — with its plan and price | Google Ads, Meta |
| The app usage information in §1.6, which Google Analytics can pass to Google Ads | Google Ads |
We do not send your name, email address or date of birth to Google Ads or Meta.
What it is used for. To count how many installs and subscriptions each advert led to, and to show Target 720 adverts to you and to people similar to you on other apps and websites. To do this, Google and Meta may combine what the app shares with what they already know from other apps and websites. They also use it for their own purposes, such as improving their advertising systems, under their own privacy policies.
When it starts. On Android and on the web, from the first time the app is opened — before you create an account. On iPhone, Google's advertising use starts only if you choose Allow when iPhone asks whether the app may track you; if you do not, Meta still receives the events in the table above, but without your advertising identifier.
Your controls. There is no switch for this inside the app. On iPhone: Settings › Privacy & Security › Tracking. On Android: Settings › Google › Ads (the exact path depends on your phone), where you can delete your advertising identifier. These stop the advertising identifier being used; they do not stop the events in the table above being sent. There is no separate control on the web.
Keeping and erasing. Google and Meta keep this information for periods set by their own policies. Deleting your Target 720 account does not erase what they already hold, and we cannot erase it for you; use the controls in your Google and Meta accounts.
Google and Meta process this information outside India, under their own terms and safeguards.
1.9 Our website and the links we share
This covers target720.com and the links we put in adverts, social media posts and posters — the ones that start with get.target720.com/c/. You do not need an account to use either.
| What we collect | Why |
|---|---|
| When you open one of our links: a count of the visit — which link, the day, and whether it was opened on Android, on an iPhone or iPad, or on another device. We do not keep your internet address, your browser details, or anything else that could identify you | To know which of our links people actually use |
| On target720.com, through Google Analytics (Google LLC): the pages you view, which link or advert brought you there, your browser and type of device, an approximate city or region derived from your internet address, and a random identifier kept in a cookie in your browser | To see which pages and which of our campaigns bring students to Target 720 |
If you are signed in to the Target 720 web app: a cookie named t720_si, shared across target720.com addresses. It holds only the value 1 — no account identifier, nothing about you | So that one of our links can take you straight into the web app instead of our home page. It is removed when you sign out |
| If you install the app from one of our links: on Android, Google Play tells the app which link it was installed from, and Google Analytics for Firebase records that with the app usage in §1.6. On iPhone, Apple tells us only how many installs each link led to, in totals, and only for people who have allowed Apple to share analytics with app developers | To count how many installs each link led to |
Linked to your account? A visit to the website on its own is not. If you go on from the website to the web app and sign in, Google Analytics can connect that visit with the app usage in §1.6, which is linked to your account.
Visitors from Europe. If you visit from the European Economic Area, the United Kingdom or Switzerland, the website does not set Google Analytics cookies.
Retention. Website analytics is kept for 14 months and then deleted automatically. Link counts contain no personal data and are kept as totals.
Your controls. You can block or delete cookies in your browser's settings; the website still works without them. Signing out of the web app removes t720_si.
Google processes website analytics on our instructions, which may involve processing outside India under their own terms and safeguards.
2. Why we process it, and on what basis
We process your data on the basis of your consent, given when you create your account and accept this policy, and only for these purposes:
- To run the service — sign you in, show you the syllabus, save your progress and attempts across devices.
- To personalise your preparation — build your daily plan and your mistake notebook from your own progress and attempt history. This is automated, but it only decides what study material to put in front of you; it makes no decision with legal consequences for you.
- To support you — answer your emails and investigate faults you report.
- To run the referral programme — record who referred whom, work out whether a referral has earned a voucher, check for abuse, and send the voucher (§1.7).
- To keep the service working and safe — diagnose errors, prevent abuse, and keep the content secure.
- To advertise Target 720 and measure that advertising — see §1.8, including when it starts, and our website and links in §1.9.
- To meet legal obligations — including responding to your rights requests under the DPDP Act.
You can withdraw your consent at any time by deleting your account (see §6). Withdrawing consent means we can no longer provide the service to you. For advertising measurement, use the controls in §1.8 instead.
3. Who else touches your data
| Processor | What they do |
|---|---|
| Google LLC — Firebase Authentication | Verifies your sign-in and holds your name, email and profile picture |
| Google LLC — Google Analytics for Firebase, Firebase Crashlytics | Receive app usage events and crash reports, linked to your account (§1.6) |
| Google LLC — Google Analytics (website) | Receives website visits and which link or advert brought them (§1.9) |
| Google LLC — Google Ads | Receives advertising measurement data and uses it to show and measure our adverts (§1.8) |
| Meta Platforms, Inc. — Meta advertising tools | Receives advertising measurement data and uses it to show and measure our adverts (§1.8) |
| Apple Inc. — Sign in with Apple (iPhone) | Verifies your sign-in if you choose Apple |
| Apple Inc. / Google LLC — App Store, Google Play | Distribute the app and process any subscription payment. On Android, Google Play also keeps the details of a referral link the app was installed from (§1.7) |
| Razorpay Software Limited — web payments | Processes the payment for a subscription bought directly from us, and holds the payment and mandate details needed to take each yearly renewal |
| Our cloud hosting provider | Runs our servers and database |
These providers act on our instructions under contract, with one exception: Google Ads and Meta also use the advertising data they receive for their own purposes, under their own privacy policies (§1.8). Beyond them, we disclose personal data only where the law requires it.
4. Where your data is stored
Your account and learning data are stored and processed in India. Firebase Authentication and the app stores are operated by Google and Apple on their own global infrastructure, which may involve processing outside India, under their own terms and safeguards. The same is true of the analytics data in §1.6 and the advertising data in §1.8.
5. How long we keep it
| Data | Retention |
|---|---|
| Account, profile, learning activity, mistake notebook, plans | Kept while your account exists. Erased at the end of the recovery window — up to 30 days after you delete your account. |
| Activity event records | Kept while your account exists; erased with the account at the end of the recovery window. |
| Subscription records | Erased with your account at the end of the recovery window, except where tax or accounting law requires us to retain a purchase record. |
| Referral records (§1.7) | Kept while your account exists. When either account in a referral is erased, every record of that referral is kept, whether or not a voucher was sent, but without the link to the erased account, and our staff notes on it are erased. What stays is the code, the dates, the reward shown when the code was entered and, for a voucher we sent, its value, supplier, order reference and which of our staff sent it. A voucher we sent is kept because it is a record of money we paid out, and it still counts towards the yearly limit in Terms §14.4. A referral that led to no voucher is kept so that we can answer a later question about it. |
| Advertising data held by Google Ads and Meta (§1.8) | Kept by them under their own policies. Not erased when you delete your account. |
| Website analytics (§1.9) | 14 months, then deleted automatically. Link visit counts hold no personal data and are kept as totals. |
| Support emails | Kept up to 24 months after the issue is closed. |
Deleting your account happens in two steps. The account closes immediately: you are signed out on every device and cannot sign in again. Your data is not erased at that moment — it is kept for a recovery window of up to 30 days so that an accidental deletion can be undone. At the end of that window it is erased permanently.
During the window, email support@vidyn.ai from the address on the account and ask us to restore it. Signing in again will not restore it. Once the erasure has run, nothing can be recovered. See §6 for the rest of your rights.
6. Your rights
Under the DPDP Act you can ask us to:
- Access and take a copy — the app has an Export my data button under the gear icon → Data & account, which gives you your own data straight away. You can also ask us for a summary of what we hold and who we have shared it with.
- Correct or complete — fix data that is wrong or out of date. You can edit your profile in the app yourself; email us for anything you cannot reach.
- Erase — delete your account and everything we hold that is attached to it. This does not reach advertising data already held by Google Ads and Meta (§1.8). The same Data & account section has a Delete account button, or you can ask us. The account closes at once; your data is erased at the end of the recovery window described in §5. Step-by-step instructions: Delete your account.
- Withdraw consent — see §2.
- Nominate — name someone to exercise your rights if you die or become incapacitated.
- Complain — raise a grievance with us (§7), and escalate to the Data Protection Board of India if we don't resolve it.
For anything you cannot do in the app, email support@vidyn.ai from the address on your account. We respond within 30 days. We may need to confirm it is really you before we act on a request.
7. Contact us about your data
For any question, request or complaint about your personal data:
8. Security
Data is encrypted in transit (HTTPS/TLS) and at rest on our servers. Access to production data is restricted to the people who need it. No system is perfect; if a breach affects your data we will notify you and the Data Protection Board as the law requires.
9. Changes to this policy
If we change how we handle your data, we will update this page and change the version and date at the top.