Privacy Policy

This privacy policy explains how the Dvaitam Android application (package com.dvaitam) handles information. It covers the app and nothing else.

Our website is a separate product with separate data practices — cookies, analytics and an enquiry form, none of which exist in the app. Those are described in our website privacy policy.

We are an engineering and clean energy contractor, not an advertising or data business.

The app is a work tool for Dvaitam field staff, not a consumer app. Its tools are behind a sign-in and are usable only by staff we have issued credentials to. Anyone else can read its public Home, Features, Help and Privacy pages, but cannot reach the tools.

Its purpose is to read a customer's electricity bill and prepare a solar proposal on the spot, including at homes with no usable signal. Everything it does — reading the bill, sizing the system, generating the proposal PDF — happens on the phone itself.

Most of what the app holds is not about the member of staff using it. It is about the CUSTOMER whose bill is being analysed: their name, mobile number, site address, electricity account details, the bill image or PDF itself, and the consumption figures read from it.

Staff enter this on the customer's behalf, with the customer's knowledge, and it is held under this policy like any other project record.

Everything the app holds is written to its own private storage on that handset, which Android keeps isolated from other applications.

To attach a bill, the app asks Android to open the camera, the photo picker or the file picker. Android hands back only the single photo or file chosen, at the moment it is chosen.

Bill text is recognised by a model bundled inside the app, running entirely on the handset. Bill images and their contents are not sent to Google, to us, or to any other service for processing.

An uploaded bill is copied into the app's private storage so it stays available for checking against the proposal it produced. Deleting the proposal deletes the bill and the PDF stored with it.

Signing in is checked on the handset. There is no authentication server, no sign-in API and no sign-in information transmitted anywhere.

The password itself is never stored — only a one-way value derived from it using a deliberately slow, memory-hard algorithm, held in the Android keystore and impossible to turn back into a password. Repeated failed attempts are progressively slowed down. Signing out clears the session immediately, and the session is never written to disk.

The app has no registration, no password reset and no account recovery. Credentials are issued by Dvaitam.

The app is deliberately inert when it comes to data collection. It contains no third-party software development kits for any of the following.

The only time information leaves the handset is when a member of staff chooses to share a finished proposal. The PDF then travels through whichever application they pick — WhatsApp, email or anything else installed — and that application's own privacy policy governs what happens to it next.

Nothing is shared automatically, and nothing is shared with us.

A proposal and the bill stored with it stay on that handset until someone deletes them.

What staff enter into the app is used for one thing: preparing and delivering the solar proposal the customer asked for, and the record-keeping that comes with a project we go on to deliver.

The app shares nothing automatically, with anyone. It has no network calls that transmit customer data.

A proposal is shared only when a member of staff deliberately sends it — normally to the customer it was prepared for. If a project goes ahead, the ordinary project sharing described in our website privacy policy applies: suppliers and subcontractors get only what a specific job needs, and government bodies, DISCOMs or scheme portals get what a connection or approval requires.

We do not sell, rent or trade personal information, and we never share it for anyone's advertising.

Under India's Digital Personal Data Protection Act, 2023, we process a customer's personal data on the basis of the consent they give when they ask us to prepare a proposal, and for the legitimate uses that Act permits, including performing a contract and complying with the law.

Consent can be withdrawn at any time. Withdrawing it does not affect processing already carried out, and it may mean we can no longer progress the proposal or support work already delivered.

The app holds its data locally rather than sending it to us, so its protection is the device's. Data lives in the app's private storage, which Android isolates from other applications, and the app is configured so that storage is not copied into device backups.

Sign-in passwords are never stored — only a one-way value derived from them using a deliberately slow, memory-hard algorithm, kept in the Android keystore.

We should be straight about the limit of this. An application on a device that can be lost or handed to someone else cannot offer absolute security. Staff are required to keep the device under its own screen lock and to sign out before letting anyone else use the phone.

You can ask us at any time to tell you what personal data we hold about you and how it is being used, to correct anything inaccurate, to erase data we no longer need to keep, or to withdraw consent you previously gave. You may also nominate someone to exercise these rights on your behalf in the event of death or incapacity.

To make a request — including a request to delete your data — email dvaitamventures@gmail.com or call +91 91193 17319 with enough detail for us to identify your records. We will respond within a reasonable period, and in any case within the time the law allows. If you are not satisfied with how we have handled a privacy concern, you may raise it with the Data Protection Board of India.

The app is a work tool issued to our staff. It is not designed for, marketed to, or intended to be used by children, and we do not knowingly collect personal data from children through it.

We will update this page when the app changes in a way that affects privacy — for example if it were ever to request an additional permission, add a third-party service, or begin transmitting data. The date below always reflects the current version, and material changes will be described here rather than made silently.