CarLens
Privacy policy
Effective 10 October 2026 · Last updated 13 November 2026 · Read with our Terms of use
CarLens is an Android app for people buying a car in India. It is made by Shokeen Studio (Shivam Shokeen, Delhi, India), which is responsible for the data described here: under India's Digital Personal Data Protection Act, 2023, we are the "Data Fiduciary" and you are the "Data Principal". Questions: [email protected].
The short version
- You can browse, search, filter and price every car without an account.
- AI comparisons and recommendations need an account with a verified email. An account holds your email, a name and a picture. It exists so the free AI results cannot be abused.
- We keep your city, never your exact location.
- If you join a community discussion, other members see your message, display name and picture. Every message is moderated, and is kept privately for 180 days after it leaves the app, as Indian law requires.
- Notifications are off until you turn them on, and you choose which kinds you get.
- We measure how the app is used and when it crashes, with PostHog, hosted in the EU. Passwords, codes, sign-in tokens and email addresses are stripped out on your phone before anything is sent. You can switch it off in the app at any time.
- Free users see ads from Google. Where the law requires it, Google asks for your consent first. Premium has no ads.
- The camera is used only when you tap "Take photo": for a Premium profile picture, or to share a photo of your own car.
- We do not sell your data.
- You can delete your account inside the app, or by emailing us.
1. Without an account
Browsing, searching, filtering, on-road prices, the loan calculator and building a comparison list need no account. The following is kept only on your phone and is not sent to us:
- your wishlist, recently viewed cars, recent searches, compare list, quiz answers and filters;
- the city you chose, the app language, and display settings such as text size, nav-bar style and festival decorations;
- the email addresses typed into the sign-in screen on this phone, used only to slow down repeated wrong passwords;
- a short on-device log of app errors, which you can open and share yourself from the Diagnostics screen. It leaves the phone only if you share it.
Uninstalling the app removes all of it. Signing out with "Forget this device", or deleting your account in the app, clears everything above except text size, which tips you have already seen and the error log. Those describe the phone, not you, and stay until you uninstall. CarLens turns off Android's app backup, so none of this is copied to a cloud backup.
Analytics (section 4) and, for free users, ads (section 8) run whether or not you have an account.
2. Your account
You need an account, with a verified email, to see any AI comparison or recommendation, including ones already saved. When you create one we store:
- Email address and password. Handled by Supabase Auth. Your password is stored only as a one-way hash; nobody, including us, can read it.
- Display name, which you type when you sign up and can change later.
- Profile picture. Free accounts choose one of our preset pictures. Premium accounts can instead use their own photo: chosen through Android's photo picker (which needs no permission and shows the app only the photo you pick), or taken with the camera. The app asks for camera permission only when you tap "Take photo", never at start-up, and uses the camera for nothing else except a car photo you choose to share (section 6A). The photo is cropped and shrunk on your phone, then stored in a storage folder named after your account; anyone who has its web address can open it.
- Verification details. To verify your email we send a short code by email. We keep a hash of the code (never the code itself), the address it went to, when it expires and how many wrong attempts were made.
- A one-way hashed device identifier. After you sign in we store a one-way hash of your phone's identifier (the raw identifier never leaves your phone and cannot be recovered from the hash), linked to your account. We use it only to allow one account per phone, to stop the free AI limit being abused with extra accounts, and to keep one active sign-in per account (next item). It is not used for ads or tracking, and it is deleted with your account.
- Which sign-in is the active one. Each time you sign in we store, for your account, the random ID of that sign-in session, the time, and the same one-way hashed device identifier (if your phone provided one). We keep only one such record per account: a new sign-in replaces the old one. We use it only to keep one active sign-in per account and to tell which of your devices holds it: when CarLens is opened on another of your devices with an internet connection, it checks this record and signs itself out if it is no longer the active one. It is not used for ads or tracking, is not shared with anyone, and is deleted with your account. It is not stored for administrator accounts.
- AI usage record. Each AI result shown to you: what kind (comparison or recommendation), when, and which saved result it was. This applies the free limit (3 results in a rolling 24 hours) and gives you your last three results to reopen.
- Ad rewards, if you choose to watch a rewarded ad for an extra AI result (section 8): Google's transaction ID for the reward, which ad unit it came from and when.
- Premium status, if you subscribe: the Google Play purchase token, the product, and the date your Premium runs until (section 8).
- Help requests you send from the Help screen: the category, subject and message you write, the email on your account, the app version and a short device description (Android version and phone model), and the request's status and our reply.
- A screenshot or short screen recording on a help request, only if you add one. You pick it with Android's photo picker, which shows the app only that file. A picture is shrunk and has its hidden details (such as where and when it was taken) removed on your phone. A recording has its sound removed and its hidden details (such as location, phone model and recording date) removed on your phone before it is sent; a recording we cannot clean this way is not sent. The picture on screen is sent as recorded, so please check it shows nothing private. It is stored privately in a folder named after your account, with no public web address; only you and our administrators can open it, and only to deal with your request. It is not sent to any AI service. At most 3 a day.
- Your in-app notifications: the messages shown under the bell on Home, such as a reply to your help request, a bonus AI result or Premium being turned on, and whether you have opened them.
- Feedback screenshots, only if you add one. When you send feedback or report a translation while signed in, you can attach one picture from your gallery, usually a screenshot of the problem. It is optional: you pick it with Android's photo picker, which shows the app only that picture. Before it leaves your phone the app removes the hidden details a photo can carry, such as where and when it was taken and the camera model. It is stored privately in a folder named after your account, with no public web address; only you and our administrators can open it, and only to deal with your report. It is not shared with anyone else and is not sent to any AI service. Please do not attach a picture that shows other people's details.
- Videos you email us, only if you send one. You can email a video of a problem to [email protected], along with your message and the email address you send from. The video is stored privately, with no public web address; only our team can open it, and only to deal with your request. It is not shared with anyone else. Please do not send a video that shows other people's details.
- Photos of your car, only if you send one. How they are checked, stored and shown is explained in section 6A.
- Account role (ordinary user or administrator).
We do not ask for your phone number. A phone check exists in the code but is switched off.
Your sign-in session is stored on your phone in encrypted storage. If you turn on fingerprint or face unlock, the check is done by Android; the app is told only whether it succeeded. Your biometric data never reaches the app or us.
3. Location
CarLens uses your city to work out road tax and on-road prices. You can pick a city by hand. If you tap "Use my location" instead:
- the app asks for approximate location only. It does not request precise or background location;
- your phone's location service finds a rough position, and your phone's geocoding service turns it into a place name. On most Android phones both are provided by Google Play services. If no geocoder is available, the app compares the position with its own list of cities, on the phone;
- the coordinates are then discarded. They are never sent to our servers or to analytics, and never written to a log;
- only the city (and its state) is kept, after you confirm it.
The city you chose is attached to analytics events (section 4), so we can learn, for example, which cars people in Delhi look at most. Separately, Google's ad services may estimate a general location from your IP address (section 8).
"Find a showroom near you". On a car page, this link opens a Google Maps search for the brand's showroom and your city (or just the brand, if you have not chosen one). Tapping it sends that search to Google because you asked for it; Google's own privacy policy applies from there. CarLens does not read your location for this and keeps no copy of the search text. We record only that the link was tapped and which brand, together with the city you chose, as on every analytics event (see above and section 4). CarLens has no agreement with, or payment from, any dealer or manufacturer.
4. Analytics and crash reports
We use PostHog, on its EU cloud, to understand how the app is used and to find crashes. It records:
- What you do in the app: app opened, screens viewed (including which car page), cars saved and unsaved, searches (the first 40 characters of what you typed, with anything that looks like an email address or a long number removed, and how many results it found), filters changed, comparison and quiz steps, sign-up, sign-in, verification and password-reset outcomes, Premium screen and purchase outcomes, ads shown or failed (which placement and format, whether it was a video and whether the video played to the end, never anything about you), rewarded-ad outcomes, the category of any help request (never its text), and account deletion.
- Your city and state, as above.
- Failures: which of our services a failed request went to and its status, when a screen could not load, when you tapped "Try again", and the web address of any car photo that failed to load.
- Crash reports: the type of error, the place in our code where it happened, and the error message, for errors in the app's JavaScript and in its native code.
- Device and app details the PostHog library collects by default, such as phone model, Android version, app version, screen size and language.
Every event, including crash reports PostHog captures automatically, passes through one filter on your phone before it is sent. It removes passwords, sign-in tokens, verification codes and the part of any email address before the @. If an event cannot be cleaned, it is dropped rather than sent.
Before you sign in, events are tied to a random identifier created on your phone. After you sign in, they are tied to your account's random ID. We do not send PostHog your email address or name. Like any web service, PostHog receives your IP address when the app connects to it.
Switching it off. Menu → Appearance → Privacy → Usage analytics. Off stops this phone sending anything to PostHog, crash reports included, signed in or not, and stays off after you sign out. You can turn it back on the same way.
5. AI comparisons and recommendations
The app never talks to an AI service directly. Requests go to our own server functions, which check your account and free limit and then, if the answer is not already saved, call Google's Gemini API.
- Comparison: we send the details of the cars you chose, taken from our catalogue, plus any priorities you set.
- Recommendation: we send your quiz answers: budget, fuel, car types and how you will use the car.
We do not send your name, email or account ID to Google. Results are saved and shown to other people who ask the same question. Saved results are stored against the cars or the answers, never against you; the record of which results you were shown is your AI usage record (section 2). Google's terms for the Gemini API allow Google to use content sent through it to improve its services; what we send is car data and quiz answers, not personal details. Some comparisons and recommendations are written in advance by AI (Anthropic's Claude) from our car catalogue alone, using no user data, and are saved and shown in the same way.
Invite codes ("Bring a buyer"). Your account has an invite code made of 8 random letters and digits; it contains nothing about you. If a friend signs up with it, we record that link between the two accounts, the date, and whether a bonus AI verdict was given to each of you. To stop a person rewarding themselves, we also keep a one-way hash (SHA-256) of the push-notification token of the phones involved, never the token itself, and compare only hashes. We never read or upload your contacts, and your friend's name or email is never shown to you. If you shared a link, the app on your friend's phone may keep the code until it is used.
6. Community discussions
Signed-in members with a verified email can discuss a car, or an AI comparison, with other members. Nothing here is needed to use the rest of the app. Before your first post you accept the community guidelines.
- What other members see: your message, your display name and your profile picture, and when you posted. Never your email address or account ID. After you delete your account, your remaining messages show as "Former member".
- What we store: each message with your account ID, the discussion it belongs to and the time; the moderation result (allowed, held or removed, with the reason); when you accepted the guidelines and which version; members you blocked; and, if you break the rules, strikes and posting pauses.
- Moderation: every message is checked on your phone and on our server by automatic filters (for phone numbers, links, abuse and similar), then by Google's Gemini API, which receives the message text only, never your name, email or account ID. Once a day the messages that were held, removed or reported are summarised again by Gemini and emailed to our moderator (the Grievance Officer) for a person to confirm or reverse. Under Google's Gemini terms, Google may use text sent through it to improve its services, so do not put personal details in a message; the guidelines forbid it anyway.
- Reports and complaints: if you report a message we store who reported it, the reason, any note you add and a copy of the message. A complaint to our Grievance Officer stores your account (or the email address you give), the category, your description, a copy of the message concerned, and our outcome. We email you an acknowledgement and the outcome through Resend.
Messages cannot be edited or deleted by their author in this version of the app. To have one of your messages removed, report it or email us.
6A. Photos of your car
We are introducing this gradually, so you may not see it yet. A signed-in member with a verified email can send a photo of their own car to replace an outdated photo on that car's page. It is optional and nothing else in the app needs it.
- On your phone: you pick a photo or take one (the camera is asked for only when you tap "Take photo"). The app shrinks it and removes the hidden details a photo can carry, such as where and when it was taken and the camera model, before it is sent.
- What you agree to: that you took or own the photo and it shows your own car; that no faces and no readable number plate are in it; and you give CarLens a free, non-exclusive licence to show, crop and resize it in the app and on this website, credited as "Photo by a CarLens user". Your name is never shown with it. We record that you agreed, when, and to which wording.
- The check: our server sends the photo to Google's Gemini API, without your name, email or account ID, to check that it is safe and that it shows this car's current model. A photo that fails is not stored at all. A photo that passes is kept privately (never at a public address) until someone at CarLens reviews it. Nothing is shown to anyone else until a person approves it and chooses it for the car's page. Under Google's Gemini terms, Google may use what is sent through it to improve its services.
- Unsafe photos: a sexual, violent or hateful photo, or one that endangers a child, is discarded at once and photo sharing is turned off for that account. We keep a record of what happened and why (never the photo) for one year, and may report illegal content to the authorities as Indian law requires. If you think we got it wrong, email us.
- What we store: for each photo, your account ID, the car, its status (waiting, approved, shown, not accepted) and the reason, the result of the check, and your agreement. You can see the status of your photos in the app.
- Limits: up to 3 photos a day.
- Reporting a photo: anyone signed in with a verified email can tap "Report this photo" under a photo a CarLens user shared. The report is a help request in your name (section 2), so you can follow it; we record which photo, the reason you picked, any note you add, and when. The person who shared the photo is never told who reported it. When three different people report the same photo it is hidden from everyone at once (the car's earlier photo comes back) until someone at CarLens reviews it and either shows it again or removes it for good. Up to 5 photo reports a day.
- Photos nobody reviews: a photo that is not reviewed within 30 days of being sent is deleted automatically, together with its record, and we email you to say so. We keep a short record that it was deleted (never the photo) for one year.
7. Emails and notifications
Emails
Verification codes and password-reset emails are sent through Resend, from
[email protected]. Resend receives your email address and the message
in order to deliver it. The acknowledgement and outcome of a complaint to our Grievance Officer
(section 6) go the same way. We do not send marketing email.
Push notifications
The app never asks for notification permission when you first open it. It explains what notifications are for first (after you sign in, or when you open Settings → Notifications), and Android's own permission question appears only if you tap "Turn on notifications". This works with or without an account. If you turn them on, we store, for this phone:
- A push token: the address Google (Firebase Cloud Messaging) or Apple gives your phone so notifications can reach it. It is sent through Expo's push service, which passes it to Google or Apple.
- App details: the platform (Android or iOS), the app version, your phone's language setting and the language you chose in the app.
- The city and state you chose in CarLens, so an announcement can be sent to one city or state. Never your location or coordinates.
- Your account's random ID, while you are signed in on this phone. Signing out unlinks the phone from your account.
- Your choices: which kinds of notification you want (product announcements, feature status, watched-car alerts (not sent yet), community replies, help desk updates).
- Notification analytics: for each notification we send, whether it was accepted for delivery, and whether the app reported that it arrived, that you opened it or (on iOS) that you dismissed it, with the time. The same events go to PostHog (section 4), tagged with the notification's ID and kind, never its text.
You can switch any kind off in Settings → Notifications, or all of them in Android's settings. A phone that uninstalls the app, or whose token Google reports as no longer valid, is switched off automatically. Notifications never carry advertising.
8. Ads and payments
Ads
Free users, signed in or not, see ads served by Google AdMob through the Google Mobile Ads library. Premium users see no ads.
- Consent first. Before any ad is requested, the app runs Google's User Messaging Platform. Where the law requires consent (for example in the European Economic Area or the UK), it shows Google's consent form, and no ad is requested unless your answer allows it. In most of India it shows nothing.
- What Google collects. To show and measure ads and to prevent fraud, Google's library collects your device's advertising ID, your IP address (from which Google may estimate a general location), information about the app and your device, how you interact with ads, and crash and performance data about the ad library. Ads may be personalised where you have allowed it. Google explains how it uses this data at policies.google.com/technologies/partner-sites.
- Your controls. You can reset or delete your advertising ID in Android's settings (Settings → Privacy → Ads, or Settings → Google → Ads, depending on the phone).
- Rewarded ads. When your free AI results are used up, the app may offer an optional short ad for one more result. It plays only when you tap the button. So that the reward reaches the right account, your account's random ID is passed to Google with that ad, and Google tells our server when you have watched it. Nothing else about you is passed.
We do not give advertisers your name, email or city.
Premium and payments
CarLens Premium is a monthly subscription bought through Google Play Billing. Google handles the payment; we never see your card, UPI or bank details. When you subscribe or restore a purchase, our server checks the purchase with Google and stores the purchase token, the product and the date your Premium runs until, against your account. Google also tells our server when a subscription renews, is cancelled or ends, so that date stays correct.
We also keep a log of each purchase attempt and its outcome (Google's order ID, a one-way hash of the purchase token, the product, the result and the app version), to fix payment problems and answer billing questions. When you delete your account, the log is unlinked from you; the order record itself is kept for our accounts.
The app also contains a one-time "support the developer" tip through Google Play Billing. It is switched off.
9. Who processes your data
| Service | What for | Where |
|---|---|---|
| Supabase | Accounts, database, profile photos, car photos you share, help requests with their screenshots and recordings, feedback screenshots, in-app notifications, our server functions | Mumbai, India |
| PostHog | Analytics and crash reports | European Union |
| Expo (push service) | Relaying push notifications to Google or Apple | United States |
| Google (Firebase Cloud Messaging) | Delivering push notifications to Android phones | Google's infrastructure |
| Expo (app updates) | Delivering updates to the app's code; it sees your IP address, the app version and platform | United States |
| Cloudflare | Our website, a cache that speeds up loading the public car catalogue (it sees your IP address, never your account), and forwarding mail sent to support@ | Its global network |
| Resend | Sending verification and password emails, complaint acknowledgements, and the daily moderation summary to our moderator | Its own infrastructure; our sending domain is set up in its Tokyo region |
| Have I Been Pwned (Troy Hunt), reached through our server function and Cloudflare | Checking a new password against a public list of leaked passwords. It receives only the first 5 characters of a one-way hash of the password, never the password, your email or your account | Cloudflare's global network |
| Google (Gemini API) | Writing AI comparisons, recommendations and festival greetings, moderating community messages, and checking car photos you share | Google's infrastructure |
| Google (AdMob and User Messaging Platform) | Ads for free users, and the consent form where required | Google's infrastructure |
| Google (Play Billing) | Premium subscription payments | Google's infrastructure |
| Google (Play Integrity) | Checking that a request comes from a genuine copy of the app on a genuine device (section 13) | Google's infrastructure |
| Google (Play services) | Approximate location and place names, on your phone, only if you tap "Use my location" | Google's infrastructure |
| Anthropic (Claude API) | Writing some comparisons and recommendations in advance from our car catalogue. It receives car data only, no user data | United States |
| Anthropic (Claude API) | Helping our team look into a help request: it receives the subject and text of the request only, never your name, email, account ID, screenshots or recordings. A person decides what is done | United States |
Help requests, including emails, screenshots and videos you send us, are handled by our team and may be processed by the service providers above, only to deal with your request.
Some car photos load from Wikimedia Commons, which, like any website, sees the IP address of the phone that loads them.
We do not sell or rent your data, and we share it with no one else except where the law requires us to.
10. How long we keep it
- Account data (section 2), including your AI usage record, ad rewards, Premium status, help requests and the record of your active sign-in, is kept until you delete your account.
- Feedback screenshots are deleted automatically 90 days after you send them, or within a day if the report they were meant for was never sent, and straight away if you delete your account. The text of the report itself stays with your help requests. The same applies to a screenshot or recording you add to a help request.
- In-app notifications are deleted automatically 180 days after they are sent, and straight away if you delete your account.
- Photos of your car (section 6A): a photo that fails the check is never stored. One we decide not to use is deleted when we decide. One waiting for review is kept privately until it is reviewed, and is deleted if it is not reviewed within 30 days. One we show on a car's page stays there until we replace it or you ask us to remove it. All of them, and their records, are deleted straight away if you delete your account (the car goes back to its earlier photo). The record of a blocked unsafe photo (never the photo itself) is kept for one year, no longer linked to you once your account is deleted.
- Videos you email us are deleted automatically 90 days after you send them, and straight away if you delete your CarLens account that uses the same email address you sent them from.
- Push tokens and notification preferences are kept while notifications are on for that phone; a token that stops working is switched off automatically. Notification analytics (section 7) are kept with the notification they describe, and are deleted when we delete that notification's record.
- Unverified accounts are deleted automatically if the email is still not verified 7 days after sign-up.
- On-phone data (section 1) stays until you uninstall, sign out with "Forget this device" or delete your account in the app (text size and the error log stay until you uninstall).
- Analytics and crash data stay in PostHog for as long as our PostHog project keeps data, or until you delete your account: deleting it also erases the analytics and crash reports tied to your account (PostHog completes this in the background, usually within a few days). Analytics from a phone where you never signed in are tied only to a random ID made on that phone, and cannot be found from your account.
- Verification codes: the hash of each code, and the address it went to, are deleted a day after the code expires.
- Request counters (section 13): salted hashes only; each expires after about an hour and is then deleted by regular clean-up.
- Ad data collected by Google is kept under Google's own policies.
- Invite codes and invite records are kept until you delete your account. When either account in an invite is deleted, that person's side of the record goes with it; bonus verdicts already given to the other person stay theirs.
- Saved AI results are kept, because other people read them. None of them identifies you.
- Discussion messages stay in the app for 48 hours. After that they leave the app and are kept privately for 180 days, with their moderation record, because India's IT Rules 2021 require us to keep them for investigations. Then they are deleted. Reports and moderation records are kept for 180 days, and complaints for 180 days after they are resolved. Blocks, strikes and your guidelines acceptance are kept until you delete your account.
11. Deleting your account
In the app: Account → Delete my account, then type DELETE.
Without the app: email us. Both are explained, with exactly what is removed, on
shokeenstudio.com/carlens/delete-account.
Deleting your account removes your Premium record with it, but it does not cancel a Google Play subscription. Cancel it in Google Play first (Play Store → Payments & subscriptions → Subscriptions) so you are not charged again.
Community messages you posted are not erased by deleting your account: they stay in their discussion as "Former member" until their 48 hours are up, and are then kept privately for 180 days (section 10), as the law requires. Your push token stays on the phone's record but is no longer linked to you.
12. Your rights
We use your personal data on the basis of your consent, given when you create an account, turn on a feature such as notifications or location, or use the app after reading this policy, and for the purposes described above only. Under India's Digital Personal Data Protection Act, 2023 you can:
- see a summary of the personal data we hold about you and what we do with it, and who we have shared it with (section 9);
- correct, complete or update it; your name and picture you can change in the app at any time;
- have it erased, in the app (section 11) or by email;
- withdraw your consent as easily as you gave it: switch analytics off (section 4), turn notifications off (section 7), pick your city by hand instead of using location (section 3), or delete your account. Withdrawing does not undo what was lawfully done before it;
- nominate someone to exercise these rights for you if you die or become unable to, by emailing us their name and contact details;
- complain to our Grievance Officer (below). If you are not satisfied with the answer, you can complain to the Data Protection Board of India.
For any of these, email [email protected] from the address on your account. We aim to answer within 30 days.
Complaints about content, or about how we handle your personal data, can also go to our Grievance Officer, Shivam Shokeen, at [email protected] (subject "Grievance") or from the app's Help desk. How it works, and the time limits, are on shokeenstudio.com/carlens/grievance.
13. Security
All traffic between the app and our services is encrypted (HTTPS). Passwords and verification codes are stored only as hashes. Database rules limit each account to its own records. Your sign-in session is kept in encrypted storage on your phone, and the app's data is excluded from Android backups.
Genuine-app checks. When the app asks for an AI result, posts in a discussion, claims an ad reward or registers for notifications, it also asks Google Play's Integrity service whether the request comes from a genuine copy of CarLens on a genuine Android device. We store Google's answer (pass or fail labels, never a device identifier), which feature asked, the time and, if you are signed in, your account's random ID, for 90 days, to stop the free AI limit and the community being abused. It is unlinked from you when you delete your account.
Leaked-password check. When you choose a password to create an account or to set a new one after a reset, your phone turns it into a one-way hash (SHA-1) and sends only the first 5 characters of that hash to our server function, which asks the public Have I Been Pwned list for every leaked password that starts the same way. Your phone then compares the answer itself. The password, the full hash, your email and your account are never sent, and we do not store the 5 characters. If the list cannot be reached, you can still continue. You are asked to pick another password only when yours appears in the list.
Request counters. To stop one account or one network address flooding our servers, we count how many requests each makes to each of our server functions in an hour. There are two counters: one keyed by a salted one-way hash of your sign-in token, the other by a salted one-way hash of your network (IP) address, never the raw values. Each counter expires after about an hour and is deleted by our regular clean-up after that.
No system is perfectly secure. If a personal data breach happens, we will tell the Data Protection Board of India and every person affected, as the law requires: what happened, when, what it may mean for you, what we are doing about it and what you can do to protect yourself.
14. Children and the 18+ rule
CarLens is intended for adults aged 18 and over. It is not directed at anyone under 18. By creating an account or signing in, you confirm that you are 18 or older. The app does not ask for your age or date of birth.
Indian law treats anyone under 18 as a child, whose data may be used only with a parent's verifiable consent. CarLens does not collect that consent, so it is not for under-18s. If you believe someone under 18 has an account, email [email protected] and we will delete it.
15. Changes
If we change what we collect, we will update this page and the date at the top before the change reaches the app.