Privacy Policy

AeroDeck GIS · Aerialair · version 2026-11-16 · effective 16 November 2026

The short version

1. About this policy

1.1 This Privacy Policy explains how Aerialair (we, us) collects, uses, shares and protects personal data when you use AeroDeck GIS (the Service), including this website, the sign-in and registration pages, the public pricing page and the web app. You means a visitor, or a person who has an account, whether you registered yourself or an organization owner or administrator added you.

1.2 It is our privacy policy under rule 4 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, and our notice under the Digital Personal Data Protection Act, 2023 (the DPDP Act). It forms part of our Terms and Conditions: by using the Service you accept it, and by registering you give the consent described in it.

1.3 Two roles. For account, billing, security and support data we decide why and how the data is used: we are the “Data Fiduciary”. For Customer Data, meaning the files, features, results and other content you or your organization put into the Service, the organization decides why and how it is used, and we process it only on its behalf and for the Service, as the Terms and Conditions say. Section 10 explains what that means for you.

1.4 Words in bold such as Customer Data have the meaning they have in the Terms and Conditions.

2. What we collect

InformationWhat it includesWhere it comes from
AccountFull name, email address, username, password (kept only as a salted one-way hash, never in plain text), and the optional job title, phone number, country, industry and team size you give when you register. Whether you ticked the box for product updates.You, when you register or change your account
Organization and billingOrganization name, legal name, address, country, GSTIN or tax ID, billing email, logo and brand colour (if your plan allows them), your role, the plan and its status, and the people who belong to the organization with their roles.You, the organization’s owner or administrators
PaymentsWhich plan was bought, the amount, currency, dates and status, and the provider’s customer, subscription and payment reference numbers. We never receive or store card, UPI, bank or wallet details.The payment provider
Customer DataEverything you upload or create: orthomosaics, elevation models, point clouds, coordinates, drawings, features, labels, results, exports and the saved view of your workspace (camera position, visible layers and tool settings). It can show places, vehicles and people.You and the people you invite
SupportYour tickets and messages, files you attach, your rating, and, only if you choose to send them, technical details: browser, language, time zone, screen size, graphics renderer and the page you were on.You
Acceptance recordThe version of the Terms and Conditions you accepted, the date and time, and your IP address.Created when you register
Technical and security recordsIP address, browser type, date and time, the address requested and the result, in our server logs; sign-in, sign-out and failed sign-in events; and an audit log of important actions in an organization (who created, changed, deleted, uploaded or paid, when, from which IP address).Your browser and our systems

2.1 What we do not collect. We do not ask for or use your device’s location, contacts, microphone or camera, we do not use advertising identifiers or fingerprinting, and we do not collect your card or bank details. Coordinates inside your survey files are Customer Data about the places you survey, not a record of where you are.

2.2 Sensitive personal data. The only item the 2011 Rules classify as sensitive personal data that we hold is your password, stored as a one-way hash. If you have to give us anything else sensitive, for example in a support ticket, do so only if it is needed to help you.

2.3 Giving us data is your choice, but we cannot create an account, bill you or secure it without the account, organization and technical data above. You may refuse to give optional details, and you may withdraw consent at any time (section 9).

3. Why we use it

3.1 We use personal data only for the purposes below, and not for anything incompatible with them.

PurposeData usedBasis
Create and run your account, sign you in, keep you signed inAccount, session cookieYour consent, and our agreement with you
Provide the Service: store, prepare, show and analyse your data; apply your plan’s limitsAccount, organization, Customer Data, workspace settingsOur agreement with you, on the organization’s instructions
Bill you, record payments, issue invoices, handle taxOrganization and billing, paymentsOur agreement with you; our legal duties (tax and accounting)
Keep the Service and your data secure; prevent abuse, fraud and unauthorized accessTechnical and security records, audit log, reCAPTCHA resultOur legal duty to keep reasonable security safeguards; the legitimate uses the DPDP Act permits
Support you and answer your requests and complaintsAccount, support data, technical details you sendOur agreement with you; your request
Send service emails: verification, password reset, security and billing notices, support repliesAccount, organization, billing contactOur agreement with you
Send product updates and newsName, email, your opt-inYour consent only (you can withdraw it at any time)
Meet legal duties, answer lawful requests from authorities, establish or defend legal claimsAny of the above, as neededOur legal duties and the legitimate uses the DPDP Act permits

3.2 We do not sell personal data. We do not use Customer Data for advertising, and we use it only to provide the Service to you and the people you authorize, and to support and protect it. We do not make decisions about you by automated means that have legal or similarly significant effects.

4. Cookies and browser storage

4.1 We use only what the Service needs to work. We use no advertising or tracking cookies and no analytics service, and the fonts and scripts of the Service are served from our own address, except those named below.

NameWhat it doesHow longNeeded?
sessionidKeeps you signed in. Not readable by scripts, sent only over HTTPS.Up to 12 hours, or until you sign outYes
csrftokenProtects your actions from forged requests.Up to 1 yearYes

4.2 Your browser’s own storage (local and session storage) remembers conveniences on your device: the reference of an unfinished upload so it can resume, snapping and navigation settings, editing-tool values, the fields of the report form (client, reference, prepared by), your choices on the pricing page, a plan you chose before registering (kept for 14 days), the state of the project list and a marker used when you return from a payment page. It is not used to track you. You can clear it in your browser settings; the Service then starts with defaults.

4.3 Google reCAPTCHA. Where the operator has switched it on, it loads from Google on the sign-in, registration and password-reset pages to tell people from bots. Google then receives your IP address and browser and interaction information, and may set its own cookies, under Google’s own privacy policy and terms.

4.4 Payment pages. When you choose to pay with Paddle, its checkout script is loaded from Paddle. Other payment providers send you to their own pages. Those pages are theirs and are covered by their policies.

5. Who we share it with

5.1 We share personal data only as follows, and only as much as is needed.

WhoWhyWhat they receive
Hosting: Oracle Cloud InfrastructureRuns the servers and the database of the ServiceAll data held in the Service, as our hosting provider
File storage: Cloudflare R2Stores uploaded files, prepared copies, exports and support attachmentsYour files. Your browser sends and fetches files directly using short-lived signed links, so the storage provider also sees your IP address and which files are requested
Email delivery: our email (SMTP) providerDelivers verification, password-reset, security, billing and support emailsThe recipient’s name and email address and the message
Payments: the providers offered at checkout (currently among Razorpay, PayPal, Paddle, Dodo Payments, NOWPayments and BTCPay Server)Take payment, run subscriptions, issue invoices, handle refunds and taxYour name, email, organization and billing details, the plan and the amount. You enter card, UPI, bank, wallet or crypto details on their pages, not ours. Each is responsible for what it collects; Paddle and Dodo Payments act as merchant of record for their payments
Google reCAPTCHA (when switched on)Stops automated abuse of sign-in and registrationIP address, browser and interaction data

5.2 Inside your organization. The owners and administrators of your organization can see who its members are, their roles and the organization’s activity log, and manage plan and billing. Members see what the project roles allow. Another organization never sees your data: every request is checked against the roles of the person asking.

5.3 Our own staff can reach customer data only through the operator console, which requires two-factor sign-in, limits access by role and records what is done. Aerialair’s staff use it to run, secure and support the Service.

5.4 Authorities and the law. We disclose personal data to courts, law-enforcement and government agencies, and the Indian Computer Emergency Response Team, where the law requires or allows it, and to protect rights, safety and the Service. If a payment is disputed with a bank or provider, we give it the records needed to answer the dispute.

5.5 Business changes. If we merge with, are acquired by or sell the Service to another business, personal data may move with it, under this policy or one that protects it at least as well, and we will tell you.

5.6 We do not sell, rent or trade personal data, and we do not share it for advertising. Providers named above work under their own terms and duties of confidentiality and may process data only to provide their service to us. We may change providers; we keep this list current.

6. Where data is processed

6.1 Our servers and our providers’ systems may be in India or in other countries. We transfer personal data outside India only as the DPDP Act and the rules under it allow, and we choose providers that protect it.

6.2 If you use the Service from outside India, you understand that your data is handled under Indian law. If the law of your country gives you additional rights that apply to us, write to us and we will tell you how we apply them.

7. How long we keep it

DataHow long
Account and profileWhile your account is open. After it closes, only what we must keep for the law or to handle a dispute.
Customer DataUntil you or your organization delete it, or the account ends. After a subscription ends or an account is closed you can export your data for at least 30 days, after which we may delete it permanently, as the Terms and Conditions say.
Items you deleteRemoved from the Service and from file storage when the deletion is confirmed. Copies inside our database backups, which hold records but never survey files, are replaced as backups age out: daily backups are kept 14 days, and the Sunday backup 60 days.
Billing and tax recordsAs long as tax, accounting and company law require.
Audit log and security recordsAs long as needed to keep the Service secure and to meet the law.
Support ticketsWhile needed to help you and to answer follow-up questions or disputes.
Server logsFor a limited time, for security and fault-finding.
Sign-in sessionUp to 12 hours.
Your consent to product updatesUntil you withdraw it.

7.1 When we no longer need personal data for a purpose and the law does not require us to keep it, we erase it or remove what identifies you.

8. How we protect it

8.1 We use reasonable security practices and procedures suited to the Service, in line with rule 8 of the 2011 Rules. They include:

  • encrypted connections (HTTPS) for the web app and the API;
  • an authorization check on every request, so that a person reaches only the organizations, projects and files their role allows;
  • short-lived signed links for uploading and downloading files, so that files are not publicly addressable;
  • passwords stored only as salted one-way hashes, with checks on weak passwords and limits on repeated sign-in attempts;
  • two-factor sign-in, idle time-outs and audit logs for our operators;
  • regular backups of the database, tested for restoring;
  • payment secrets and file-signing keys kept only on our servers, never in your browser.

8.2 No system is completely secure. Keep your password secret, use a strong and unique one, sign out on shared computers, and tell us at once if you suspect your account is being used by someone else.

8.3 If a personal-data breach affects you, we will inform the Data Protection Board of India and the affected people as the DPDP Act and the rules under it require.

9. Your rights and choices

9.1 Under the DPDP Act you may:

  • ask for information: a summary of the personal data we process about you and what we do with it, and the identities of those we have shared it with and what we shared;
  • ask us to correct, complete or update personal data that is wrong or out of date (you can also change many details yourself, such as your password on the Account page and your organization’s details in its settings);
  • ask us to erase your personal data, unless we need to keep it for a stated purpose or because the law requires it;
  • withdraw consent at any time, as easily as you gave it, for example for product updates. Withdrawing does not undo what we did lawfully before, and if the data is needed to run your account we may then have to close it;
  • nominate another person to exercise these rights for you if you die or cannot act;
  • complain to our Grievance Officer, and, if our reply does not resolve it, to the Data Protection Board of India.

9.2 How to ask. Write to the Grievance Officer at the address below, or open a ticket under Support in the app. Tell us who you are (use the email of your account, so that we can check it is you), and what you want. We acknowledge your request within 24 hours and resolve it within 15 days of receiving it.

9.3 You are asked to give accurate information, not to impersonate anyone, not to hide material facts, and not to make false or frivolous complaints, as the DPDP Act expects of every person it protects.

9.4 To stop emails that are not service emails, withdraw your consent as above. We cannot stop service emails (for example a password reset you requested, or a billing notice) while you have an account.

10. Customer Data that contains personal data

10.1 Imagery and point clouds may show people, vehicles, homes or other property, and drawings and labels may contain names. The organization that uploads such data decides why and how it is used and is responsible for having the right to capture and process it, for giving notices, for getting consent where needed, and for answering the people it shows.

10.2 We process Customer Data on the organization’s behalf, only to provide the Service, under the Terms and Conditions and with the safeguards in this policy. We do not look at it except to run, secure, support or repair the Service, or where the law requires. If you are a person shown in an organization’s data, ask that organization first. If you write to us, we pass your request on to the organization and help it answer.

11. Children

11.1 The Service is for professional and business use and is not for anyone under 18. We do not knowingly collect personal data of children. If you think a child has given us personal data, write to the Grievance Officer and we will erase it.

12. Changes to this policy

12.1 We may update this policy, for example when we add a provider or a feature that handles personal data. The version and date are shown at the top. For a material change we will tell you by email or in the Service before it takes effect, and where the law requires, we will ask for your consent again. Older versions are available on request.

13. Contact and Grievance Officer

Aerialair
[email protected]

Send requests and complaints about your personal data, or questions about this policy, to the Grievance Officer. We acknowledge a complaint within 24 hours and resolve it within 15 days of receiving it.

Sign in · Create an account · Pricing · Terms and Conditions · Refund and Cancellation Policy