Privacy Policy
How Dhru Flux handles personal data.
Last updated
On this page
In short
- Each repair shop decides what is kept about its customers. We keep it and work on it for the shop, and for nothing else.
- Records are stored on Amazon Web Services in Mumbai, India.
- A device passcode is kept only with the customer’s permission, encrypted, and erased when the device is handed back.
- Repair updates go to customers by email and, where the shop has the customer’s consent, by WhatsApp. Online payments are not switched on yet; we will update this policy before they are.
- Unless a shop switches AI drafts off, what its staff say, type or photograph for an AI action goes to OpenAI to make a draft that staff check. Contact details and long numbers in typed words are hidden first, and Dhru Flux does not keep the words, photos or recordings. Once a day, a summary of what needs attention, with every detail hidden, is also made when an owner or manager opens Overview; that summary is kept with the shop’s records.
- We do not sell personal data or show advertising. This website sets no cookies and uses no analytics or advertising trackers.
1.About this policy
Dhru Flux is software for repair businesses, run by Dhru Cloud Private Limited (“we”, “us”). This policy explains how we handle personal data in the Dhru Flux dashboard (dashboard.dhruflux.com), the booking and repair-tracking pages we host for each shop, and this website (dhruflux.com).
Your Dhru account, the sign-in page at login.dhru.com and buying a subscription at dashboard.dhru.com are part of Dhru’s central account service, run by the same company. The dhru.com Privacy Policy covers them.
This policy is written to India’s Information Technology Act, 2000 and its rules on reasonable security practices and sensitive personal data (the SPDI Rules, 2011), and to the Digital Personal Data Protection Act, 2023 and its Rules. Shops outside India may have duties under their own laws as well.
2.Who decides: the shop, or us
For a shop’s customers, the shop decides. When a shop records its customers, their devices and repairs, sales and payments, the shop is the data fiduciary (in some laws, the controller): it decides why the data is collected and what is kept. We are its data processor: we store the data and work on it only to run Dhru Flux for that shop, as it instructs. If you are a shop’s customer, the shop is responsible for your records and is the first place to go with a question or request about them.
For our own users, we decide. For the people who run shops on Dhru Flux (owners and their teams), for visitors to this website, and for anyone who writes to us, we are the data fiduciary.
3.What is collected
About shops and their teams
- The shop’s details: business name, address, phone, email, website, any tax or registration numbers it prints on its documents, currency, time zone, locations and opening hours.
- Each team member’s name and email address, from their Dhru account or the shop’s invitation, with their role and the locations they work at.
- An activity log of who did what in the shop’s workspace and when, including each time someone opens a device passcode.
- The suppliers and their details that the shop records.
- What you tell us when you write to us.
About a shop’s customers, kept for the shop
- Name, phone number and email address, and any limit the shop sets on what the customer may owe it.
- Repairs: the device, its IMEI or serial number, the fault, accessories and condition, notes, estimates and the customer’s approval or refusal, parts used, warranty, and each repair’s history.
- Sales, invoices, credit notes, payments, refunds, store credit and gift card balances. A payment keeps its amount, method and time. Dhru Flux does not take or store card numbers.
- A device passcode, PIN or unlock pattern, only if the customer allows it (see Device passcodes).
- Booking requests made on the shop’s booking page: name, email, phone, the device and the problem, with the customer’s agreement to be contacted about the request.
On this website
This website sets no cookies and uses no analytics, advertising or tracking tools. Its fonts come from our own servers.
4.How we use it
We use a shop’s data only to run Dhru Flux for that shop:
- to store it and show it to the shop’s team, as their roles and locations allow;
- to print the documents and create the links the shop issues, such as intake receipts, invoices and repair-tracking links;
- to help the shop when it asks us for support, and to keep the service running, secure and backed up.
A few of our staff can reach the servers and the database directly, to run the service and to help shops that ask. They use that access only for those reasons. We do not sell personal data, use it for advertising or profiling, or use shops’ records to train AI models.
We use the details of shop owners and teams to run their access to Dhru Flux, keep the service secure, answer them, and tell them about the service.
5.Device passcodes
When a device comes in, the shop can record its passcode, PIN or unlock pattern so that the repair can be tested. Dhru Flux keeps one only when the shop records that the customer allowed it. It is:
- encrypted (AES-256-GCM) and kept apart from the rest of the repair record;
- shown only to the shop’s owners and managers and to the technician assigned to the repair, and each time someone opens it is recorded in the activity log;
- erased when the device is handed back to the customer. A passcode typed in for a repair that is never created expires after 24 hours.
A new repair that has not been saved yet is kept in that browser tab so that it is not lost, but never with its passcode.
6.Booking pages and repair-tracking links
A shop can have a booking and repair-tracking website at its own address on dhruflux.com. A customer who books there gives their name, email, phone, the device and the problem, and agrees to be contacted about the request. The request goes to that shop only.
A shop can give a customer a private link to follow one repair. The link carries a long random code that we keep only in scrambled (hashed) form. It works once, in the first browser that opens it, and expires 7 days after the shop creates it. The page shows the shop’s name, the repair’s reference, the device, the problem, its status and dates, the estimate and invoices, and lets the customer approve or decline the estimate. It does not show the customer’s own contact details.
7.Messages to customers, and online payments
A shop can send its customers updates about their repair: when the device is received, when an estimate is ready or approved, when the device is ready and handed back, and when an invoice is issued or a payment received. The shop chooses which of these go out, and staff can also send a link to the estimate or invoice.
- Emails go to the email address the shop has for the customer, through Amazon Simple Email Service in Mumbai, from the shop’s name. The shop can switch emails off for a customer.
- WhatsApp updates go from Dhru’s WhatsApp Business sender through Gupshup, only to customers whose consent the shop has recorded. Withdrawing consent stops them.
- A message may carry a private link to the repair page. It expires after 7 days and opens only that repair.
- We keep a record of each message (what was sent, to which repair, and whether it was accepted) so the shop can see it on the repair.
Online payments are built but not switched on yet: nothing is paid through them today. When they are, payments will go through the shop’s own account with a payment provider; the customer enters card details on the provider’s page and Dhru Flux never receives card numbers. We will update this policy before then.
8.AI drafts
AI drafts are on for every shop, and its owner can switch them off. Staff can speak, type or add a photo, and AI suggests a draft: a filled-in check-in, lead, task, expense, estimate or purchase order, a customer update, a technician’s note, a supplier bill read line by line, or a tidier note. Nothing is saved until a staff member checks the draft and saves it. The one exception is the daily summary, described below.
- Each action sends OpenAI only what it needs. Before typed words, or the words written down from a recording, are sent to make a draft, phone numbers, email addresses, links, long numbers (such as an IMEI) and passwords are replaced with placeholders, and put back only in the draft the staff member sees.
- A photo or a voice recording is sent as it is, so staff are asked to leave out names and passcodes. Photos, bills and recordings are not kept by Dhru Flux.
- For each action we keep a record of who used it, when, at which location and on which repair, which kind of draft it was, its size and cost, and whether it was used, but not the words, photos or recordings themselves. The daily summary is the one exception.
- The daily summary: the first time each day that a shop’s owner or a manager opens Overview, Dhru Flux works out from the shop’s own records what needs attention at that location, such as repairs past their promised date, invoices past their pay-later date or parts to reorder. It sends OpenAI only the kinds of things that need attention, with every number, repair reference, device, item name, date and amount replaced by a placeholder, and never a customer’s name or contact details. AI only orders and words them; the details are put back by Dhru Flux. Each day’s summary is kept with the shop’s records, and Overview shows that day’s summary to the shop’s owners and managers at that location. The owner can switch the daily summary off on its own.
- We do not use shops’ records or AI requests to train AI models.
10.Where data is stored
Dhru Flux’s servers, database and backups are on Amazon Web Services in Mumbai, India (ap-south-1). Pages and data reach your browser through Amazon CloudFront’s worldwide network, which is set not to keep copies of them. Practice mode’s sample data stays in the browser of the person practising and is never sent to our servers.
11.How we protect it
We follow security practices we consider reasonable, including these:
- The database itself keeps each business’s records to that business (row-level security), and the application’s database logins cannot switch this off.
- Everyone signs in with their own Dhru account. Each person has a role and the locations they work at, and sees only what those allow.
- The sign-in cookie cannot be read by scripts, is sent only over HTTPS, and ends 7 days after sign-in; we store only a hash of it. The tokens from your Dhru account are encrypted (AES-256-GCM).
- Device passcodes are encrypted, and each time one is opened is recorded.
- Changes in a workspace are written to an activity log, which the shop’s owners and managers can review.
- Browsers reach Dhru Flux over HTTPS (TLS 1.2 or later), our content network reaches our servers over HTTPS only, and the application reaches the database over TLS with a verified certificate.
- The application server’s disk is encrypted. The database is backed up every day to private, encrypted storage in Mumbai.
- Sign-in, repair-tracking links and booking requests are rate-limited.
No system is perfectly secure. If you find a weakness, please tell us (see Contact) and do not use it.
12.How long data is kept
- A shop’s records are kept while it uses Dhru Flux. When its subscription ends, no one can open the workspace, but its records are not deleted automatically, so renewing gives the team its data back.
- Deleting. The dashboard does not yet let a shop delete a customer or a repair. When a shop needs data erased, for example after accepting a customer’s request, or when it leaves Dhru Flux, its owner writes to us and we erase it, except what the law requires us or the shop to keep. Erased data can remain in backups until they are replaced.
- The activity log, the record of each AI action and each day’s summary are kept as long as the shop’s records.
- Device passcodes are erased when the device is handed back.
- Sessions end 7 days after sign-in and are then deleted. An unfinished sign-in is deleted after 30 minutes. The counters that rate-limit sign-in, tracking links and booking requests use a keyed hash in place of your IP address and are deleted after 10 minutes.
- Repair-tracking links stop working 7 days after the shop creates them.
- Team members removed from a shop can no longer open it; their name stays in the records they worked on.
13.Your rights
Under India’s Digital Personal Data Protection Act, 2023 you can ask:
- for a summary of your personal data being processed and of how it is processed;
- for your personal data to be corrected, completed, updated or erased;
- to withdraw consent you gave, for what is based on it;
- to have a grievance answered; and to name someone to act for you if you die or cannot act yourself.
The law where you live may give you similar rights; we answer requests as the law that applies requires.
Customers of a repair shop: ask the shop that keeps your records, which decides on your request. A shop can correct your details itself; if a request needs our help, such as erasing data, the shop asks us and we carry it out. If you write to us instead, we will pass your request to the shop. Some records, such as invoices, may have to be kept by law even after a request to erase them.
Shop owners and teams: write to us, as in Contact and Grievance Officer. Your Dhru account itself is covered by the dhru.com Privacy Policy.
14.Children
Dhru Flux is for businesses and the adults who work in them; we do not knowingly let a child use the dashboard. A shop may keep records of customers who are children, usually given by a parent or guardian; the shop is responsible for any consent of a parent or lawful guardian the law requires.
15.If something goes wrong
If we learn of a breach of personal data we hold, we will act to contain it and tell the shops affected without delay, with what we know, so they can inform their customers and the authorities, and we will help them do so. We report cyber security incidents to CERT-In as Indian law requires. For data we hold as data fiduciary, we inform the people affected and the Data Protection Board of India as the Digital Personal Data Protection Act and Rules require.
17.Changes to this policy
We update this policy when Dhru Flux or the law changes. The date at the top shows the latest version. If a change affects how shops’ data is handled, we will tell shop owners before it takes effect.
18.Contact and Grievance Officer
Questions or complaints about personal data go to our Grievance Officer, who also answers questions on our behalf under the Digital Personal Data Protection Act. We acknowledge a complaint and resolve it within one month of receiving it.
- Email: privacy@dhru.com
- Post: Grievance Officer, Dhru Cloud Private Limited, Dhru Base, 80 Foot Road, Anand 388001, Gujarat, India
If you are a shop’s customer, please go to the shop first (see Your rights). If we do not settle your complaint, you can take it to the Data Protection Board of India once its complaint process applies.