Privacy Policy

Nevora Ecovolt Private Limited ("Nevora", "we", "us") operates a residential electric-vehicle charging service for housing societies in India. Under the Digital Personal Data Protection Act, 2023 ("DPDP Act") and the rules made under it, Nevora is the Data Fiduciary for the personal data described here. Until the DPDP Act is fully in force, the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 also apply, and we follow both.

This policy covers:

• the Nevora CORE app for residents, on Android and iOS;
• the committee portal used by a housing society's resident welfare association (RWA);
• the operations portal used by Nevora's own staff;
• our website, and the charging hardware and gateway devices installed in a society that report to our servers.

It does not cover the housing society itself, your vehicle manufacturer, or any payment provider's own handling of your data, each of which has its own policy. Where this policy names one of them, we say what we send them and why.

We collect only what the service needs. The DPDP Act asks us to tell you each item and its purpose; this section is that notice.

2.1 Identity and sign-in

2.2 Where you live

2.3 Your vehicle

We do not connect to your vehicle manufacturer's account. If we offer that later, it will need your separate, explicit consent, and the tokens involved will be protected like payment credentials.

2.4 Charging and booking records

2.5 Technical data

What the app does not collect. No location tracking, no contacts, no photos or files, no advertising identifier, no fingerprinting. The app asks for the camera only when you open the scanner to read the sticker on a charger; the image is decoded on your phone and never uploaded. There is no analytics or advertising SDK in the app. If we add crash reporting later we will update this policy first.

2.6 Payments and your wallet

You pay for charging from a prepaid wallet in the app. Adding money opens Razorpay's checkout, a payment aggregator regulated by the Reserve Bank of India: the card number, UPI ID or bank sign-in you enter there go to Razorpay, never to us, and we neither see nor store them. What we keep: each top-up (the amount, when, and Razorpay's order and payment references), each charge to your wallet with its tax invoice, any credit note or refund, and your balance — in whole paise. We use them to charge you, give you invoices, settle disputes, return unused balance under the Refund Policy, and keep the books the law requires.

If a refund cannot go back to the payment method it came from, we ask — at that time, with your consent, and never as a condition of anything — for a bank account in your own name, and use it for that refund only.

2.7 Committee and operations users

If you sign in to the committee or operations portal, we additionally keep your role, the societies you may act for, your two-step verification secret, and an audit record of every privileged action you take — what changed, when, and the reason you gave — with the network it came from, kept beside the record for one year. Audit records cannot be edited or deleted, by anyone, including Nevora.

1. To sign you in and keep your account safe — the one-time code, tokens, rate limits.
2. To let your society decide who may charge — the committee sees your name, flat and masked mobile number to approve or refuse you.
3. To charge your car and share the building's power fairly — the load manager sets the current each charger may draw so that no electrical phase ever exceeds the board's safe limit (see §4).
4. To bill you correctly, when billing is enabled — meter readings, session totals, tariff and invoices.
5. To keep people and buildings safe — safety events, fault investigation, a permanent record when a limit was breached or a charger misbehaved.
6. To explain ourselves — why a session got the current it did, why a start was refused, why a booking was declined.
7. To communicate with you — sign-in codes now; service notices later.
8. To meet our legal duties — tax and accounting records once billing is live, lawful requests from authorities, and breach reporting.

We do not sell personal data, do not use it for advertising, and do not profile you for any purpose other than the fairness ranking described in §4.

This is the part of the service that acts on your data without a person in the loop, so we describe it plainly.

4.1 The safety rule

Every charger in a society is wired to a distribution board with a fixed safe limit per electrical phase, set by the electrician who surveyed it. Our load manager recomputes, for each board, how much current each active session may draw so that no phase ever exceeds that limit. Every active session is first guaranteed a minimum (6 A, the IEC 61851 floor), a safety margin is held back, and only the remainder is shared. This can mean your car charges more slowly than the charger's rating, or is paused briefly when the board is full. It never means the board is overloaded to serve you.

4.2 The fairness rule

When there is not enough current for everyone, sessions are ranked by a score built only from measured facts: energy delivered so far this session, time connected, your vehicle's battery capacity (from the catalogue), the charger's rating, and your flat's consumption over the last seven days. The charge level or deadline you type is used only to show you an estimated finishing time. It can never raise your rank — so nobody gains by typing an urgent number. Every decision is written to a log, with the score and each of its terms, so we can tell you in one sentence why your car got the current it did. You may ask for that explanation (§8).

4.3 What the software may never do

It may only ever set the current a charger delivers, within the board's limit. No AI or model writes a current value; a model may at most influence a priority score or a forecast. A charger that ignores its limit is budgeted at its full rating and, as a last resort, stopped — a safety measure, recorded as such.

• Consent (DPDP Act s.6) — given when you create your account, for the purposes in §3. You may withdraw it at any time (§8); the consequence is that we can no longer provide the service to you, and withdrawal does not undo processing already done.
• Certain legitimate uses (DPDP Act s.7) — data you volunteer for a stated purpose (a vehicle you add, a booking you make); compliance with law and lawful orders; and responding to a safety emergency at a charger.
• Where the IT Act and SPDI Rules apply, the same consent is the basis for handling sensitive personal data, and §6 describes our reasonable security practices.

6.1 Your housing society's committee

The committee portal shows your society's committee, for residents of that society only:

• to approve you: your name, flat, the last four digits of your mobile number, and when you asked, and whether another resident has claimed the same flat;
• once you are a resident: when you joined and who approved you; your car's make and model and a masked registration (the state and the last four digits, like "KA 51 •• 8842"); whether you are charging now; when and on which charger you last charged; and how many charges and how much energy this month;
• on each charger: its charges by flat — when each started and ended and the energy delivered — and its bookings by flat, including missed bookings and cars left plugged in after they finished.

They do not see your full mobile number, your full registration, your wallet, payments or invoices, the charge level you type, or anything about another society. They may report a charger as unsafe, and may stop a charge only on a ground our server checks (§4 of the Terms of Service), with a reason you see in the app.

6.2 Nevora's operations staff

Our staff can see everything in §2 for the societies they support, including your name and flat beside each session, because settling a dispute or investigating a fault requires it. Access is by role, needs two-step sign-in, and every privileged action is recorded in an audit log that cannot be altered. Mobile numbers are masked on every screen that does not need the full number.

6.3 Service providers (processors)

Each provider acts on our instructions under a contract. We do not send your data to anyone else, and we do not transfer it outside India except as shown above for code delivery, DNS, our email, and Nevora staff's use of the operations portal.

6.4 Authorities

We disclose personal data when a law, court or authority in India requires it, and only what is required. We keep a record of such requests.

• In India. Servers, database and backups are in the AWS Mumbai region.
• Encrypted in transit — TLS on every connection from the app, the portals, the chargers and the gateway devices.
• Encrypted at rest, field by field — mobile numbers, names, email addresses, vehicle registration numbers and any vehicle-manufacturer identifiers are encrypted with AES-256-GCM before they reach the database, under a key held outside the database. The server's disk is encrypted too.
• Sign-in codes are short-lived, limited to ten attempts, and rate-limited per network. Staff accounts need a password and an authenticator app.
• Two logs cannot be edited by anyone: the safety event log and the audit log. The database itself refuses the change.
• Backups are taken nightly to storage in Mumbai and kept for 30 days; an expired backup is deleted for good 30 days after that.
• Least data by design: the app holds no location, no contacts, no ads.

We keep personal data only as long as its purpose requires, then delete or anonymise it. The periods below are built into the software as scheduled deletion, not left to memory.

Under the DPDP Act you may:

1. Access — ask for a summary of the personal data we hold about you, the processing we do, and who we have shared it with.
2. Correct, complete or update — your name, flat, vehicle details. Most of this you can change in the app under Profile; the rest, ask us.
3. Erase — delete your account yourself in the app (Profile → Delete account; you confirm with a one-time code), or ask us. You are signed out of every device at once. Your personal details are erased after the 90-day grace period, subject to the retention holds in §8; signing in with your number before then lets you undo it. Step by step, with what is kept: Delete your Nevora account.
4. Withdraw consent — at any time, with the same effect as erasure. This does not affect what was lawfully done before.
5. Nominate — name a person to exercise these rights for you if you are unable to.
6. Grievance redressal — complain to us and receive a reasoned answer.
7. An explanation of an automated allocation — why your session got the current it did (§4.2). We hold the record and will tell you.

How: email the Grievance Officer (§13) from the mobile number or email on your account, or write to us. We will acknowledge within 48 hours and resolve it within one month. If you are not satisfied, you may approach the Data Protection Board of India once our internal process is exhausted. Requests that would reveal another person's data, or that we must refuse to meet a legal obligation, will be answered with the reason.

The service is for adults who own or drive an electric vehicle. You must be 18 or older to hold an account. We do not knowingly collect a child's data; if we learn we have, we delete it.

• The app stores your sign-in tokens in the phone's secure storage, and a few preferences (for example which screen you last used) locally. Nothing else. Uninstalling the app removes them.
• The portals keep your sign-in only in that browser tab's session storage, gone when the tab is closed, and your dark/light choice and the society you last opened in the browser's local storage. At the operations portal, Cloudflare Access also sets its own sign-in cookies for Nevora's staff (§6.3). No tracking cookies, no advertising cookies.
• The website uses no cookies unless a page says otherwise.

If personal data is lost, exposed or altered without authority, we will contain it, tell the Data Protection Board of India and the people affected in the form and time the DPDP Act and its rules require, report the incident to CERT-In within the time its directions require, and tell you what happened, what data was involved, and what we are doing about it. We will not wait for the investigation to finish before telling you.

Data Fiduciary: Nevora Ecovolt Private Limited Registered office: #198, CMH Road, Suite 3679, Indiranagar, Bengaluru 560038, Karnataka, India CIN: U46529KA2026PTC218860 · GSTIN: 29AALCN5148E1Z7

Grievance Officer (DPDP Act; IT Rules): Elvis J George, Director Email: [email protected] · Post: the registered office above Acknowledgement within 48 hours; resolution within one month.

You may escalate an unresolved grievance to the Data Protection Board of India.

We will change this policy when the service changes — for example when payments are enabled or a new provider is added. Material changes will be announced in the app before they take effect, with the date, and the previous version kept available on request. Continuing to use the service after the effective date means the new version applies; if you do not agree, you may withdraw consent (§9).

This policy is governed by the laws of India. Courts in Bengaluru, Karnataka have jurisdiction, without limiting your right to approach the Data Protection Board of India or a consumer forum.