Privacy policy

1. Who we are

Adamant Technologies Private Limited operates this website, adamanttech.in, and the applications described below, from its registered office at Flat No. 1406, Tower A, Lansum Oxygen Towers, Seethammadhara, Visakhapatnam, Andhra Pradesh 530013, India. For the purposes of the Digital Personal Data Protection Act, 2023 (“DPDP Act”) we are the Data Fiduciary for the personal data described here, and you are the Data Principal.

2. What this policy covers

This policy covers the corporate website and all three of our products. Each product collects different data because each does a different job, so they are described separately — read the section for the one you use.

Each application also shows you a consent notice, in plain language, before it asks for the data it needs. Where that notice is more specific than this policy, it is the more specific description that governs that product.

3. This website

No accounts, no tracking

The site has no login and no personalisation. It sets no cookies of its own, runs no advertising or analytics scripts, and does not build a profile of you. The typefaces are served from this site rather than from a font network, so reading a page does not announce your visit to a third party.

Hosting records

The site is served by Firebase Hosting (Google). Like any web server it records the requests it serves — IP address, page requested, time, browser and operating system, and the page you arrived from. We use those records only to keep the site available and secure.

What you send us

The form on the contact page opens a message in your own email application; it does not send anything through this site. When you write to one of our mailboxes we receive what you put in that message — typically your name, email address, organisation and the substance of your enquiry.

4. JurisBot

Account

Your email address and password, or the identifier from Apple, Google or phone sign-in, whichever you use. Your name, and the State whose law you want answers framed for.

Consent record

What you consented to at onboarding, and when. Kept so that both of us can tell what the position is.

Your questions

The threads and messages you exchange with the assistant, and the matters you group them into.

Documents

Files you upload for review, the metadata about them, and the findings produced from them. File contents are held in cloud storage; the findings sit against the document record.

Drafts

Notices, replies and applications generated for you, and the facts you supplied for them.

Consult requests

When you choose to contact an advocate, the request you send and its status. Nothing reaches an advocate unless you send it.

Plan and billing

Your plan, its period, and the payment identifiers returned by our payment gateway. We do not hold your card number.

Answer provenance

For each answer, a record of how it was produced: the prompt version, the model used, which source documents were retrieved, the citation-validator verdict, the scope verdict, and whether an escalation was triggered. This is what lets an answer be explained or defended later; it is about the answer, not about you.

JurisBot runs on Google infrastructure — Firebase Authentication for sign-in, Cloud Firestore for records and Cloud Storage for uploaded files.

A document you upload is processed to review it for you and is not used to train models for anyone else. Do not upload someone else’s personal data without a lawful basis for doing so.

Controls inside the app

Settings → Your data carries three controls: export my data, withdraw consent, and delete my account and data. Deleting removes your account, your threads, your matters and your uploaded documents, except anything we are required by law to retain.

5. Livio

Phone number

Your mobile number, and the one-time password sent to it, to sign you in. You can browse as a guest without giving it.

Profile

Your name, and a profile photo if you add one. Your notification preferences for order updates and for offers, each of which you can switch off.

Addresses

The delivery addresses you save, with any landmark or instruction you add to them.

Location

Your device location while you are using the app, to find stores that can serve you, estimate a delivery time, and place the pin the delivery partner drives to. If you allow background location, it is used to keep a delivery on track after you leave the app. You can refuse or revoke it and enter an address by hand instead.

A contact you choose

Only when you order for someone else: the name and phone number of the single contact you pick. Your address book is not uploaded, read in bulk, or kept.

Camera, photos and microphone

A photo you take to search for a product, an image you pick for your profile, and a voice search you start. Used for that action and not held afterwards, beyond an image you deliberately save to your profile or an order.

Orders

Your cart, orders, deliveries, refunds and the coupons you use — the record of what you bought and what happened to it.

Payments

Handled by our payment gateway. We keep a token for a saved method and the outcome of the payment; the card number itself never reaches us.

Device and session

A device identifier and the platform you are on, sent when a session is renewed, so a session can be bound to a device and a stolen token can be spotted.

Livio’s backend runs on Google Cloud. Address search and the map use Google Maps and Places. Sign-in codes are sent by SMS through a messaging provider. The app carries no advertising SDK and no third-party analytics. If that changes, this policy changes with it, before the change ships.

6. CementOnCall

CementOnCall is in development. When it launches it will process what a procurement platform needs to work: the account and contact details of the person ordering, the sites they order for and the addresses of those sites, the orders themselves, the delivery and challan records, the GST details needed to raise a valid tax invoice, and the payment identifiers from our gateway.

Its consent notice and the detail for this section will be published in the app and here before it is available to use.

7. Device permissions

A permission is a request, not a setting we control. Every one of these can be refused at the time it is asked for, or revoked later in your device settings — the app keeps working, with the feature that needed it turned off.

Location (Livio)

Finds stores that can reach you, estimates delivery time, and guides the delivery partner to the right door. Refuse it and you can still order by entering an address.

Background location (Livio)

Optional. Keeps a live delivery on track when the app is not in front of you. Never used when you have no order in progress.

Contacts (Livio)

Asked only when you tap to send an order to someone else, and only the contact you pick is used.

Camera (Livio)

Photographing a product to search for it, and taking a profile picture.

Photo library (Livio)

Choosing an existing image for your profile or an order, and saving a photo you have taken.

Microphone (Livio)

Voice search, while a voice search is running.

Notifications (Livio)

Order and delivery updates, and offers if you leave that switched on. Both are switchable in your profile.

8. How we message you

We send two kinds of message, and they are governed differently.

• Service messages — a one-time password, an order confirmation, a delivery update, a payment receipt, a security notice. These are part of the service you asked for and cannot be switched off while you are using it.
• Promotional messages — offers and reminders. These are optional, off unless you allow them, and switchable in the app at any time.

SMS

Sent through MSG91, which receives your mobile number and the message. Used for one-time passwords and transactional updates.

WhatsApp

Sent through the WhatsApp Business Platform operated by Meta, which receives your phone number and the message content. Optional — reply STOP, or tell us, and we move you to SMS and email.

Push notifications

Sent to your device only if you allow the permission, and separated in the app into order updates and offers so you can keep one and drop the other.

Email

Receipts, account notices and replies to what you write to us.

Message content sent over WhatsApp is carried on Meta’s infrastructure and handled under Meta’s own terms as well as ours. If you would rather not be reached there, say so and we will use SMS or email instead.

9. Why we process it

• To provide the product you asked for — answer a question, review a document, take an order, deliver it, take the payment, and support you afterwards.
• To keep accounts and payments secure — verify a phone number, bind a session to a device, detect fraud and abuse.
• To meet legal obligations — tax invoices and records, and anything a law, court or regulator requires us to keep or produce.
• To improve what we ship — using aggregate and operational data such as delivery times and error rates, not by reading your documents or your messages.

We do not sell, rent or trade personal data. We do not use anything collected through the website for advertising, and we do not run behavioural advertising in our apps.

10. Who else sees it

Only where it is necessary to run the service. Two kinds of recipient: the people who fulfil what you asked for, and the vendors whose infrastructure we run on.

• Stores, suppliers and delivery partners — the details needed to pick, pack and deliver an order: the items, the delivery address and a contact number. Not your account history, and not more than the delivery requires.
• An advocate you choose to contact — the consultation request you send through JurisBot, and only after you send it.
• Professional advisers and authorities — where we are required or lawfully permitted to disclose.

Our processors, and what each one handles:

Google — Hosting and infrastructure

Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Run and Firebase Hosting run our services; Maps and Places resolve addresses. Google Play distributes our Android apps, and Google sign-in is one way into JurisBot.

Apple — App distribution and sign-in

The App Store distributes our iOS apps, and Sign in with Apple is one way into JurisBot. Where a purchase is made inside an iOS app, Apple processes it.

Razorpay — Payments

Razorpay Software Private Limited processes payments, refunds and saved payment methods. Card and UPI details go to Razorpay and your bank, not to us.

MSG91 — SMS

MSG91 delivers the one-time passwords and transactional SMS we send to your mobile number.

Meta — WhatsApp messaging

Order and delivery updates sent over WhatsApp go through the WhatsApp Business Platform operated by Meta, which carries your phone number and the message content.

These providers process data on our instructions, under contract. Some operate infrastructure outside India, so data may be processed outside India in accordance with the DPDP Act and any restriction notified under it.

11. How long we keep it

• Your account and its content — while the account is open. Deleting it removes it, except what a law requires us to keep.
• Orders, invoices and payment records — for the period tax and company law require, which is longer than the account itself.
• Answer provenance records in JurisBot — kept so that an answer can be explained if it is ever questioned, then retired.
• Enquiries by email — while the conversation is live and for as long as we need a record of it. Writing to us does not add you to a marketing list.
• Server and hosting logs — a short operational period, then rotated out.

12. Security

• Everything travels over HTTPS, to our services and to our processors.
• Sign-in tokens are held in the device’s own secure store — Keychain on iOS, Keystore on Android — readable only on that device and only while it is unlocked.
• Card details are handled by the payment gateway and never stored on our systems.
• Access to production data is limited to the people who need it, and account access is protected by the usual controls.

No system is perfectly secure and we do not claim otherwise. If a breach affects you, we will notify you and the Data Protection Board as the DPDP Act requires.

13. Your rights

Under the DPDP Act you may ask us to:

• Confirm what personal data of yours we process, and give you a summary of it.
• Correct, complete or update data that is inaccurate or out of date.
• Erase data we no longer need for the purpose it was given, unless a law requires us to keep it.
• Withdraw a consent you have given, as easily as you gave it.
• Nominate someone to exercise these rights for you if you die or become incapacitated.
• Have a grievance heard and answered.

In JurisBot, export, withdrawal and deletion are in the app: Settings → Your data. For Livio, and for anything else, write to privacy@adamanttech.in and we will act within the period the DPDP Act allows. We may need enough information to be sure it is your data we are acting on.

14. Grievance redressal

If you are not satisfied with how we have handled a request or a complaint, escalate it to privacy@adamanttech.in, or by post to Adamant Technologies Private Limited, Flat No. 1406, Tower A, Lansum Oxygen Towers, Seethammadhara, Visakhapatnam, Andhra Pradesh 530013, India. If you remain dissatisfied you may complain to the Data Protection Board of India.

15. Children

Our website and applications are meant for people aged 18 and over, and we do not knowingly process a child’s personal data. If you believe a child’s data has reached us, write to privacy@adamanttech.in and we will delete it.

16. Changes to this policy

We will update this policy when what we collect changes — for example, when CementOnCall launches, or if an analytics or advertising component is ever added to an app. The version published here is the one that applies, and the date it was last updated is shown at the top of this page. Material changes are also notified in the product.

17. Contact

Privacy questions and data requests go to privacy@adamanttech.in. Anything else can go to info@adamanttech.in or +91 91208 91208.