StoreSure · Legal
Privacy Policy
Written against what the software actually does. Every category below corresponds to real fields in the StoreSure database, and every third party listed genuinely receives data.
Effective 31 August 2026. Last updated 31 August 2026.
Draft — not yet in force
The registered entity name, address and seat of jurisdiction have not been filled in, so this document identifies no legal person and cannot be relied on. Set them in src/app/legal/legal.tsx and have both documents reviewed by a lawyer qualified in India before charging a customer.
1. Who this is about
StoreSure is operated by [REGISTERED ENTITY NAME], a [proprietorship / private limited company] at [REGISTERED ADDRESS, CITY, STATE, PIN] (“we”, “us”). We provide site material-control software to construction businesses (“Customer”) at storesureapp.in.
Two different relationships matter here, and confusing them is the usual mistake in a policy like this:
- For your own account data — the person who signs up, is billed, and corresponds with us — we are the Data Fiduciary and decide the purposes.
- For the site records your team creates — your storekeepers, engineers, contractors and their entries — we act as a Data Processor on your instructions. The Customer is the Data Fiduciary for that data. We do not decide what your team records, and we do not use it for our own purposes.
If you are a storekeeper, engineer or site admin using StoreSure because your employer provides it: your employer controls your account and the records you create. Requests about your data should go to them first. Our contact is in section 10 and we will assist them.
2. What we collect
We collect only what the product needs to record a material movement, prove it happened and reveal a variance. There is no advertising, no profiling and no tracking across other websites.
| Category | Specific data | Why |
|---|---|---|
| Identity and login | Full name, mobile number, and a PBKDF2 hash of your PIN. Staff accounts use an email address and password hash instead. | To create your account, sign you in, and attribute every entry to a real person rather than a shared login. |
| Location of an entry | GPS latitude and longitude captured on the device when a movement is recorded, and whether it fell inside the site boundary. | To evidence that a delivery or issue was recorded at the site. This is the most sensitive item we hold about a field user and is explained separately in section 3. |
| Device identifier | An identifier for the device that created an entry, stored on the record and in the audit log. | To trace a disputed or duplicated entry back to the device that made it. |
| Photographs | Challan and bill photographs, and damage photographs, held in private storage. Whether the image was captured by camera rather than chosen from a gallery. | As evidence supporting an entry. Images may incidentally contain handwriting, signatures, vehicle numbers or people who happen to be in frame. |
| Entry content | Material, quantity, unit, rate, challan and vehicle numbers, contractor or agency name, work activity, receiver name and phone, and free-text remarks. | This is the material record itself, and the basis of every stock balance and variance. |
| Commercial records | Vendor names, phone numbers and GSTIN, purchase orders, bills and amounts, stock values and rates. | To match what was ordered, received and billed. |
| Security logs | PIN login attempts against a mobile number, including failures. | To rate-limit and detect attempts to guess a PIN. |
| Audit trail | Every change to a document, with who made it and when. Every occasion our staff opens a Customer site. | The record is meant to be defensible later. Our own access to your data is logged too. |
We do not collect financial account details, government identity numbers of individuals, biometrics, health data, or any special category of personal data. We do not knowingly collect data about children; StoreSure is a workplace tool provisioned by an employer.
3. Location, specifically
When someone records a movement, the app asks the browser for a GPS fix and stores the coordinates on that entry. This exists so that a receipt can be shown to have been recorded at the site rather than elsewhere. Three things are worth stating plainly:
- It is captured only at the moment an entry is created. There is no background tracking, no location history, and nothing is recorded while the app is closed or idle.
- It is optional in practice. If the device refuses or cannot get a fix, the entry still saves and is simply marked as carrying no location evidence. The app never blocks a record for want of a location.
- It is visible to site management, not to the wider team. Location evidence is part of what a site admin and owner review.
4. Why we process it (and our lawful basis)
- To provide the service you asked for — recording movements, computing stock, flagging variance, and showing your team what their role permits. Processed to perform our contract with the Customer, and as a legitimate use under the Digital Personal Data Protection Act, 2023 for data voluntarily provided for that purpose.
- To keep accounts secure — PIN verification, rate limiting, and audit logging.
- To support you — diagnosing a problem you report, which may require our staff to open your site data. Every such access is logged.
- To bill you and to meet our own tax and accounting obligations.
- To keep the platform working — an automated nightly check for data integrity and configuration problems across the platform.
We do not sell personal data. We do not share it for anyone else’s marketing. We do not use your site records to train any AI model — see section 6.
5. Where it is stored
StoreSure runs on Supabase (PostgreSQL, authentication and file storage) in the ap-south-1 region, Mumbai, India. Your material records, photographs and account data are held there. The web application is served by Vercel.
Access is restricted at the database level, not merely in the interface. Row-level security ties every record to a site membership, so one Customer cannot read another’s data even with a valid login, and a storekeeper cannot read variance data their role excludes.
6. Artificial intelligence, and what leaves the platform
Two features send data to OpenAI, our AI provider, and both are triggered by a deliberate action. Nothing is sent in the background.
| Feature | What is sent | When |
|---|---|---|
| Reading a challan or bill | The photograph itself. | Only when a user taps scan on that document. |
| Answering a question in Intelligence | The already-calculated summary figures behind the answer — material names, quantities, balances, forecast days and flag counts for that site. Not photographs, not phone numbers, not your team's details. | Only when a site admin, owner or auditor types a question and submits it. |
This is a transfer outside India. The Digital Personal Data Protection Act, 2023 permits transfer to countries other than those the Central Government restricts by notification; we will stop such transfers if OpenAI’s location becomes restricted.
The AI never decides anything. Every quantity, rate and balance is calculated by StoreSure itself, not by a model. A scanned document only pre-fills a form for a person to check and save; it can never post an entry on its own. An answer in Intelligence is an interpretation of figures already computed, offered with citations so you can verify it. Damage still requires approval by a second person.
7. Who else we share with
| Recipient | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication and file storage | India (ap-south-1, Mumbai) |
| Vercel | Serving the web application | Global edge network |
| OpenAI | Reading documents; interpreting figures for answers — see section 6 | Outside India |
| Professional advisers and authorities | Only where we are legally required, or to establish or defend a legal claim | As applicable |
Our staff can reach Customer data in order to provide support and operate the platform. That access is limited to named platform administrators and is written to an access log with the site and the time.
8. How long we keep it
- Material records, ledger entries and audit trail: for as long as your subscription is active, and then for 90 days after it ends so you can retrieve them. These records are deliberately append-only — a posted entry is never edited or deleted, and a correction is recorded as a reversal alongside the original. That is the point of the product, and it means an individual entry cannot be erased without destroying the integrity of the record it belongs to.
- Photographs: alongside the record they support, on the same timetable.
- Account and login data: until the account is removed by the Customer, plus any period we must retain for legal or tax purposes.
- Security logs: a rolling short window sufficient for rate limiting.
- Platform health records: 90 days, then deleted automatically.
- AI answer caches: a short window (30 minutes for a question, one day for a daily brief), then superseded.
After the 90-day window following termination, Customer data is deleted from the live system. Ask us in writing if you want it deleted sooner.
9. Your rights
Under the Digital Personal Data Protection Act, 2023 you may ask us to:
- confirm what personal data we hold about you and how it has been processed;
- correct anything inaccurate, or complete anything incomplete;
- erase personal data where it is no longer needed for the purpose it was collected for — subject to the record-integrity limit described in section 8, and to any legal obligation we have to keep it;
- nominate another person to exercise these rights on your behalf in the event of death or incapacity;
- have a grievance heard, using the route in section 10.
If your account was created by your employer, we will normally direct your request to them as the Data Fiduciary, and tell you that we have done so. You may also complain to the Data Protection Board of India.
10. Grievance redressal
Dhruv Desai is responsible for grievances under this policy and can be reached at dhruvdesai80@gmail.com, or by post at [REGISTERED ADDRESS, CITY, STATE, PIN].
We acknowledge a grievance within 7 working days and aim to resolve it within 30 days. Say clearly what you are asking for and, if you are a site user, name your employer’s site so we can locate the records.
11. Security, and its limits
PINs and passwords are stored only as salted hashes and are never recoverable in plain text — not even by us, which is why a forgotten PIN is reset rather than retrieved. Access is enforced in the database, transport is encrypted, and file storage is private. Our own access to Customer data is logged.
Two honest limitations, because a policy that only lists strengths is not useful:
- Offline capture on the web is best-effort. Entries made without a network are held in the browser’s own storage until they sync. A browser can clear that storage, so the queue is a short buffer and not a store of record. Sync as soon as you have signal.
- A web browser cannot guarantee a photo came from the camera rather than the gallery. Records carry a flag showing whether camera capture was assured, so management can tell the difference rather than assume.
If a personal data breach occurs we will notify the Data Protection Board of India and affected users as the Act requires.
12. Changes
If we change this policy we will update the date at the top and, where the change is significant, tell Customers by email before it takes effect. Continuing to use StoreSure after that means you accept the updated policy.