Privacy Policy
- Version
- 1.1
- Effective
- 6 October 2026
- In force until then
- Version 1.0, 20 September 2026
Skygauge is an initiative of ANEX Advisory. This policy explains what personal data we collect when you use Skygauge, why we collect it, who else receives it, how long we keep it, and what you can require us to do about it.
It is written to be read, not filed. If something here does not match what the product actually does, the product is wrong and we want to hear about it.
1. Who we are
ANEX Advisory operates Skygauge at skygauge.anexadvisory.com. For the purposes of the Digital Personal Data Protection Act, 2023 (the “DPDP Act”), ANEX Advisory is the Data Fiduciary for the personal data described in this policy, and you are the Data Principal.
Our legal entity details and registered address are: [LEGAL ENTITY NAME AND REGISTERED ADDRESS].
The person who answers questions about how we process personal data is named in section 11.
2. What this policy covers
Skygauge has two surfaces and they are treated differently.
The public pages (the landing page, About, these policies, and the sign-in and registration pages) can be read without an account. We do not require you to identify yourself to read them. The map on the landing page is drawn from OpenStreetMap data and sends nothing to Google. Section 6 explains which third parties receive what, and when.
The tool itself (the height analysis workspace, saved analyses, and the analysis APIs behind them) cannot be used anonymously. It requires an account, an activated beta access status, and acceptance of the in product disclaimer. Everything in sections 3, 4 and 8 about account data applies to people who have registered.
3. What we collect and why
We collect only what the product needs to work. The list below is complete for the version of this policy you are reading.
3.1 Account and sign-in data
Held by our authentication service in the auth.users table.
| Data | Why we have it |
|---|---|
| Email address | It is your sign-in identifier, it is how we send you an invite code, and it is what an invite code is bound to |
| Password, stored as a one way hash | To authenticate you. We never store or see your password in readable form |
| Account creation, sign-in and update timestamps | Security, account support, and working out where an account is in the beta queue |
If you sign in with Google, Microsoft Entra or LinkedIn instead of a password, we do not receive or store a password. We receive the identity the provider returns, which is your name and email address, and we store the link between that provider identity and your Skygauge account.
3.2 Profile
Held in the profiles table, one row per account.
| Data | Why we have it |
|---|---|
| Full name | To address you in the product and in email |
| Organisation | To understand who the beta is reaching, and to support you when you write in |
| Self declared audience (architect, developer, planner, consultant, or other) | To prioritise which features we build and which cohorts we invite next |
| Avatar image URL | Displayed in the product header. Supplied by you or by your OAuth provider |
| Role (user or admin) | Access control for the administrative console. You cannot set this yourself |
| Access status (pending, active, or suspended) | Whether your account may open the tool. You cannot set this yourself |
| Invited at, activated at, created at, updated at | The record of your passage through the beta gate |
3.3 Saved analyses
Held in the saved_analyses table. Created only when you press save. If you never save an analysis, this table holds nothing about you.
| Data | Why we have it |
|---|---|
| Label you give the analysis | So you can find it again |
| Latitude and longitude of the point you analysed | It is the analysis |
| Site elevation and search radius | To reproduce the same result when you reopen it |
| Your notes | Free text you chose to write |
| Created and updated timestamps | Ordering your saved list |
Read this carefully: a saved analysis is a record that a named person at a named organisation was interested in a specific plot of land on a specific date. That can be commercially sensitive. It is visible only to you and to a database operator with direct server access. We do not use it to profile you and we do not disclose it.
3.4 Invite codes
Held in the invite_codes table. Created by us, not by you.
| Data | Why we have it |
|---|---|
| The code | To validate redemption |
| The email address it was issued to | So a code works only for the person it was sent to |
| Issue, expiry and redemption timestamps, and the account that redeemed it | To run the beta in controlled waves and to audit who was granted access |
3.5 Beta acknowledgements
Held in the beta_acknowledgements table. Written when you accept the beta and AAI disclaimer.
| Data | Why we have it |
|---|---|
| Your account identifier | To attribute the acceptance |
| The version of the disclaimer you accepted | So an old acceptance stays legible against the exact text you were shown |
| The timestamp of acceptance | To evidence when you accepted |
This is an append only record. Neither you nor we can edit or delete an individual row, because an audit trail that can be rewritten is not an audit trail. Section 8 explains what happens to it if you close your account.
3.6 Server logs
Our web server and reverse proxy write standard request logs: timestamp, source IP address, request path, response status, and user agent. We use them to investigate faults and abuse. They are not joined to your account and are not used to build a profile of you. Retention is [SERVER LOG RETENTION PERIOD].
3.7 How you use the product
Held in the usage_events table, and linked to your account. Written continuously as you use the tool, not when you choose to save something. This section takes effect on 6 October 2026.
| Data | Why we have it |
|---|---|
| Every analysis you run: the coordinate, the search radius, the ground basis, and the moment you ran it | To see which parts of the region are being examined and how, so we know what to build and what to fix |
| Which screens and tools you opened, in what order, and how long you stayed | To find where the product is confusing, and to see which features are never touched |
| Which map view you used, and whether the three dimensional view failed on you | To decide what to keep paying for |
| Whether you generated a report, and whether you saved the analysis afterwards | To tell a passing glance from real intent |
| Your account identifier against every one of the above | It is not anonymous. See below |
Read this more carefully than anything else in this policy.
Section 3.3 warns that a saved analysis is a record that a named person at a named organisation was interested in a specific plot of land on a specific date. This section is the same thing for every plot you look at — including the ones you dismiss in three seconds and never save, which is most of them.
Held over weeks, that is a map of what your organisation is considering, in what order, and how hard it looked. It is more revealing than your saved list, because your saved list is the small part you chose to keep. We are telling you this plainly rather than describing it as “usage data”, because “usage data” is what this would be called by someone hoping you would not think about it.
It is not anonymous and we are not going to claim it is. Every row carries your account identifier. We could have hashed it, or aggregated on write, and we have not, because we want to be able to answer questions about individual journeys through the product.
What we do with it: decide what to build, find what is broken, size our infrastructure, and enforce the fair use limits in your terms. What we do not do with it: sell it, share it, use it to advertise to you, or disclose it to anyone outside ANEX Advisory except where a law or a court compels us.
The risk you are accepting is commercial, not personal. If this record reached a competitor, a counterparty in a land negotiation, or anyone who could compel it from us, it would tell them what you are working on. We think the protections in section 9 are proportionate. You may not. Section 10 is how you leave.
3.8 What we do not collect
We want to be specific, because an earlier version of this policy was not.
- We use no third party analytics product. There is no Google Analytics, no Mixpanel, no PostHog, no Hotjar, no session recorder, no heatmap tool and no analytics SDK of any kind. Section 3.7 is recorded by our own code, into our own database, on our own server, and it goes nowhere else.
- We do not record your keystrokes, your mouse movements, or the contents of your screen.
- There are no advertising cookies, no tracking pixels, and no advertising of any kind.
- We do not sell personal data, and we do not share it with anyone for their marketing.
- We do not track you across other websites. Section 3.7 stops at the edge of Skygauge: we do not know where you came from, where you went, or what else is open in your browser.
An earlier version of this policy said there was no page view counter of any kind. That stopped being true on 6 October 2026, and section 3.7 is the replacement. We would rather point at the change than quietly drop the sentence.
4. Our lawful basis under the DPDP Act
We process your personal data on the basis of your consent under section 6 of the DPDP Act. This policy, together with the notice shown to you when you register, is the notice required by section 5: it tells you what personal data we process, for what purpose, how to exercise your rights, and how to complain.
Consent under the DPDP Act must be free, specific, informed, unconditional and unambiguous, and it must be limited to the data necessary for the stated purpose. We have tried to keep the list in section 3 to exactly that.
You can withdraw your consent at any time, and withdrawing it must be as easy as giving it. Write to us at the address in section 11. Because every item in section 3 is necessary to operate an account, withdrawing consent means we close your account and stop processing, rather than continuing with a reduced service. Withdrawal does not make our earlier processing unlawful.
We should be straight with you about section 3.7 in particular. Usage recording is not strictly necessary to serve you a height analysis; it is necessary to us, so that we can run and improve the product. During the public beta it is part of the service and there is no way to use Skygauge with it switched off. If you are not comfortable with that, the honest answer is not to register, or to close an account you already have. We would rather say that than offer a toggle that does nothing.
Where the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 apply, your password is treated as sensitive personal data or information. We handle it in line with those Rules: it is collected for the lawful purpose of authenticating you, it is stored only as a hash, and it is protected by the security practices described in section 9.
5. Cookies and browser storage
Skygauge sets no analytics or advertising cookies, and no new cookie was added for the usage recording in section 3.7. Do not read that as reassurance. We do not need a tracking cookie because you are signed in: the session cookie below already tells us exactly who you are, which is a stronger identifier than any cookie an analytics vendor would have set. The absence of a tracking cookie is a fact about our plumbing, not a limit on what we know.
| Item | Where it lives | Set by | Purpose | Lifetime |
|---|---|---|---|---|
sb-<project>-auth-token (and its numbered parts when the token is split across cookies) | Cookie | Supabase Auth, running on our own server | Keeps you signed in across page loads | Until you sign out or the session expires |
sg_beta_ack | Cookie, HttpOnly, SameSite Lax, Secure in production | Us | Records that this browsing session has accepted the current beta and AAI disclaimer, so you are not asked again on every page | Deleted when you close the browser. This is deliberate: you are asked again on each new sign-in |
theme | localStorage | Us | Remembers whether you chose the light or dark palette | Until you clear your browser storage |
sg_hero_explored | sessionStorage | Us | Counts how many landing page catchments you have previewed, so the preview limit holds within a visit | Cleared when the tab closes. Never sent to our server |
skygauge:map-provider | sessionStorage | Us | Remembers that the tool’s Google map failed in this tab, so we do not retry it and leave you staring at a blank map | Cleared when the tab closes. Never sent to our server |
| Google cookies and storage | Cookies and browser storage on Google domains | Serving and securing Google Maps Platform inside the tool | Set and controlled by Google, not by us. Signed in users only |
The two sessionStorage items are read and written entirely in your browser. They never reach us.
6. Third parties, and exactly what they receive
6.1 OpenFreeMap and OpenStreetMap
The three dimensional map of Mumbai on the landing page is built from OpenStreetMap data, served as vector tiles by OpenFreeMap. Your browser requests those tiles directly, so OpenFreeMap receives your IP address and the map tiles you request. It sets no cookies and no browser storage, and there is no account or advertising identifier involved. OpenStreetMap data is licensed under the Open Database Licence, which is why the credit appears in the corner of the map.
This replaced Google Photorealistic 3D Tiles on the landing page. A signed out visitor no longer causes any request to Google.
6.2 Google Maps Platform
Inside the tool, Skygauge uses Google Maps JavaScript, Photorealistic 3D Tiles, Places and Elevation.
When your browser draws a map, it talks to Google directly. Google receives your IP address, your approximate location as implied by that address, the map coordinates and camera positions you request, what you type into place search, and standard browser and device information. We do not control what Google does with that data. Google’s handling of it is governed by the Google Privacy Policy and the Google Maps Platform terms.
This happens only once you are signed in and using the tool. Simply reading the landing page or these policies causes no request to Google. If you do not want Google to receive map requests at all, block third party requests to Google’s map domains in your browser; the analysis will still run, because the height computation happens on our side, but the basemap will not draw.
6.3 Resend
Resend is our transactional email provider. It sends invite codes and access notices, and it is also the mail transport for authentication email such as sign-in confirmations and password resets. Resend receives your email address and the contents of those messages. It does not receive your saved analyses, your profile fields or your password.
6.4 Our database and authentication service
Skygauge runs Supabase, self hosted on infrastructure that we control. Your account data, profile, saved analyses, invite records and acknowledgements are stored on our own servers. They are not held by Supabase Inc. or by any managed database provider, and Supabase is not a third party processor of your data in this deployment. We are responsible for that infrastructure.
6.5 Source data
Skygauge is built on public record: AAI NOCAS data, AAI appellate proceedings, and the MCGM Development Plan 2034 layers. Those sources receive nothing from us about you. We do not send your queries, your coordinates or your identity to AAI, MCGM or anyone else.
6.6 Disclosure required by law
We will disclose personal data if we are legally required to, for example under a valid order from a court or a competent authority. We will tell you if that happens, unless we are prohibited from doing so.
7. Where your data is stored
Your account data, profile, saved analyses, invite records and acknowledgements are stored on our servers, which are located in [SERVER LOCATION / HOSTING REGION].
Google and Resend process data outside India on their own infrastructure. Section 16 of the DPDP Act permits transfer of personal data outside India except to territories that the Central Government restricts by notification. If a restriction is notified that affects a provider we use, we will change provider or change the feature.
8. How long we keep it
| Data | Retention |
|---|---|
| Account, profile and saved analyses | For as long as your account exists |
| Invite codes and their redemption record | For the duration of the public beta and for [INVITE RECORD RETENTION PERIOD] afterwards, as the record of who was granted access |
| Beta acknowledgements | For as long as your account exists. They are deleted with the account |
| Usage records (section 3.7) | [USAGE RECORD RETENTION PERIOD], then deleted. They are also deleted in full when you close your account |
| Server logs | [SERVER LOG RETENTION PERIOD] |
When you close your account, we delete your authentication record, your profile, every saved analysis attached to it, your usage records under section 3.7, and your acknowledgement rows. The deletion cascades, so nothing is left behind pointing at you. The invite code record survives with the link to your account removed, because we need to know that a code was issued and spent.
We do not keep dormant accounts alive indefinitely. If we introduce a dormancy rule we will state it here before we act on it.
9. Security
What we actually do:
- All traffic is served over TLS.
- Passwords are stored only as hashes, produced by our authentication service. We cannot read them.
- Every user table enforces row level security scoped to your account identifier. One signed-in user cannot read another user’s profile or saved analyses, even by crafting a request directly against the database API.
- Your role and your beta access status are permission boundaries. They are protected by database triggers that silently revert any attempt by an account to change its own, so a compromised client cannot grant itself access or admin rights.
- Invite code redemption happens in a single atomic server side operation, so a code cannot be redeemed twice by racing two requests. Invite codes are not readable by any non-admin account.
- The administrative console is role gated and is not reachable by a normal account.
- The analysis APIs enforce sign-in and active access status on every request, not just in the interface.
No system is perfectly secure, and we are a small team running our own infrastructure. If we become aware of a personal data breach we will notify the Data Protection Board of India and every affected Data Principal, as required by section 8(6) of the DPDP Act, and we will tell you what happened and what you should do.
10. Your rights as a Data Principal
Under the DPDP Act you have the following rights, and we will honour them.
Right to information (section 11). You can ask us for a summary of the personal data we hold about you and how we are processing it, and for the identities of anyone we have shared it with. Much of it is already visible on your profile page.
Right to correction and erasure (section 12). You can ask us to correct inaccurate or misleading data, to complete incomplete data, to update it, and to erase it. We will erase personal data on request unless retaining it is required by law. This includes your usage records under section 3.7: you can ask us to delete them without closing your account, and we will, within the timescale in section 11.
Right of grievance redressal (section 13). You can complain to us about anything in this policy or in how we have handled your data. Section 11 says how, and what we will do about it.
Right to nominate (section 14). You can nominate another individual to exercise these rights on your behalf if you die or become incapacitated. We do not have a form for this yet. Write to us and we will record the nomination.
You also have duties under section 15 of the DPDP Act, including not impersonating another person when registering, and not raising a grievance you know to be false.
How to exercise them
Write to [PRIVACY CONTACT EMAIL] from the email address on your Skygauge account. That is how we verify it is you. Tell us what you want: a copy, a correction, deletion of one saved analysis, or deletion of the whole account.
We will acknowledge within three working days and complete the request within thirty days. If we need longer, we will tell you why before the thirty days are up.
There is currently no self service delete button in the product. Until there is, deletion is a request to the address above and we perform it by hand. We will not make you justify it.
11. Grievance redressal
If you are unhappy with how we handle your personal data, contact:
[NAME OF PERSON RESPONSIBLE FOR ANSWERING QUESTIONS ABOUT PROCESSING][GRIEVANCE CONTACT EMAIL][POSTAL ADDRESS]This is the person we have appointed to answer questions from Data Principals about the processing of their personal data, as section 8(9) of the DPDP Act requires, and the grievance contact required by rule 5(9) of the SPDI Rules, 2011.
We will acknowledge your grievance within three working days and respond substantively within thirty days.
If you are not satisfied with our response, or if we do not respond, you may complain to the Data Protection Board of India under section 13(3) of the DPDP Act.
12. Children
Skygauge is a professional tool for people working on building projects. It is not intended for anyone under 18, and we do not knowingly create accounts for anyone under 18.
Section 9 of the DPDP Act requires verifiable parental consent before processing a child’s personal data, and prohibits tracking, behavioural monitoring and targeted advertising directed at children. We do none of those things to anyone. We also do not have a mechanism to verify age beyond asking, so if you are under 18, do not register.
If you believe a child has registered, write to us at the address in section 11 and we will delete the account.
13. Personal data inside the analysis
Skygauge shows you records drawn from public sources: AAI No Objection Certificates, appellate proceedings, and Development Plan layers. Those records can contain names of applicants, property descriptions and case references. That information is public record, published by the authorities that issued it.
If you are the subject of such a record and you want it corrected, the correction has to happen at the source, with AAI or with the planning authority. We can remove a record from Skygauge, but we cannot change the public record, and our copy will be repopulated on the next refresh unless the source changes. Write to us at the address in section 11 and we will explain what is possible in your case.
14. Visitors from the EU and the UK
The public pages are reachable from anywhere. If you are in the EU or the UK and you are browsing those pages, we want to be straight with you: Skygauge is built for and operated in India, and our compliance is built around the DPDP Act. We do not target the EU or the UK, we do not offer the tool there, and we have not built full GDPR compliance machinery. We have no EU or UK representative and no Data Protection Officer appointed under the GDPR.
What we will do is honour a request for access, correction or deletion from anyone, wherever you are, on the same terms as section 10. The map tiles described in section 6.1 are fetched from OpenFreeMap before any consent interaction. They set no cookies and no browser storage, so the ePrivacy storage rules are not engaged, but your IP address does reach that provider in the course of drawing the map. If that matters to you, do not load the site.
15. Changes to this policy
We will update this policy when the product changes. The version number at the top identifies the policy you are reading.
If a change materially affects how we handle your personal data, we will tell registered users by email before it takes effect, and we will ask for consent again where the DPDP Act requires it. We will not make a material change quietly and rely on you noticing a date.
16. Contact
For anything in this policy, including access, correction, erasure, nomination and grievances: [PRIVACY CONTACT EMAIL].
Skygauge is an initiative of ANEX Advisory.