Consent Notice

The notice and consent record under Sections 5 and 6 of the Digital Personal Data Protection Act, 2023 — shown in the app at sign-up and at each permission grant, and stored against your account.

Standalone by design: this document contains only what the DPDP Rules require a notice to contain and the specific consents Kawst asks for. It refers to, but does not repeat, the Privacy Policy and the Terms and Conditions. Every consent below is recorded server-side with the notice version, language, timestamp and source, and can be withdrawn from Profile → Privacy.

1. Who is asking, and how to reach them

Data Fiduciary: One Kom Labs Technologies LLP ("we", "Kawst"), A-414, SLV Central Park, Bidare Agrahara, Bandapura Road, Bengaluru, Karnataka 560067, India. Grievance Officer: Mandhir Singh, +91 91879 51284, privacy@kawst.in. Full details are in Section 12 of the Privacy Policy.

Consent is free, specific, informed and unambiguous. You give it by an affirmative action — ticking a box or tapping Allow — never by silence or by a pre-ticked box.
Each purpose below is a separate consent. Refusing an optional one does not stop you using the rest of Kawst.
Withdrawing consent is as easy as giving it: Profile → Privacy shows every consent you have given, with a switch to withdraw or re-grant each optional one (motion sensors, marketing). Job-seeker visibility and home-location sharing are switched in your job profile, and location access in your phone's app permissions for Kawst. Deleting your account (Delete my account, in Profile → Privacy or Profile → Account & role) withdraws all of them.
We record what you agreed to, which version of this notice you saw, in which language, and when. You can ask for a copy at any time.
If the law lets us process data without consent (for example to keep a GST invoice for the statutory period, or to respond to a court order), we tell you so in the Privacy Policy rather than asking for consent we do not need.

3. Consents requested

Each block is shown to you at the point where the feature needs it. Required consents are needed to provide the service you are asking for; optional consents can be declined.

A. Account and platform use — required for every role

Mobile number, name, role, profile photo, language; Google account email if used to sign in.

Purpose: Create and secure your account; show role-appropriate features; send account notifications.
Shared with: Google Firebase (India region).

Device model, app version, push token, crash and performance reports, anonymised usage events.

Purpose: Reliability, security and product improvement.
Shared with: Google Firebase.

☐ I have read the Privacy Policy and consent to the processing described in block A.

B. Location and motion tracking — required for drivers running tracked trips

Shown as a full-screen prominent disclosure before the system location permission is requested, and again before background location.

Precise GPS location of this phone.

Purpose: Live fleet map; trip distance, route and timeline; geofence and detention alerts; journey-plan billing; theft alerts.
When: While you are on duty or a trip is running, including in the background with the app closed. A persistent notification shows when tracking is on. Never outside a duty or trip.

Accelerometer and gyroscope readings (optional).

Purpose: Driving-behaviour score and safety feedback.
When: During trips only, and only if you allow it — we ask once, and trips work the same without it. Change it any time in Profile → Privacy.

☐ I consent to location tracking during duty and trips, including in the background.

☐ (Optional) I consent to motion-sensor collection during trips for driving-behaviour feedback.

Your employer (the fleet owner) and the supervisors they authorise can see your position during a duty or trip and your trip history. Your customer can see the vehicle's position during their trip only. No one can see your location outside a duty or trip.

C. Identity and licence verification — required to seek work or be assigned a vehicle

Driving licence number and image; date of birth.

Purpose: Confirm the licence is valid and matches you before you can apply for jobs or be assigned a vehicle.
Shared with: SurePass, which queries the Sarathi/VAHAN registries.

One government photo ID — Aadhaar, Voter ID or Passport — as an image or fetched from DigiLocker with your DigiLocker consent.

Purpose: Confirm identity; meet the owner's duty of care.
Shared with: SurePass (and DigiLocker if you choose it). Aadhaar numbers are stored masked; we never store your Aadhaar biometrics.

☐ I consent to verification of my driving licence and identity document as described in block C.

D. Photo and document uploads with AI reading — required when you use expense, fuel or damage features

Odometer, fuel-bill, expense-receipt and vehicle-damage photos.

Purpose: Extract readings and amounts; flag inconsistencies for the owner to review; record vehicle condition.
Shared with: Google generative-AI API, which may process the image outside India. Names and phone numbers are removed from the request where the task does not need them.

☐ I consent to AI-assisted reading of the photos I upload, as described in block D.

E. Employment and payroll records — for drivers and staff added by an owner

Your employer is the Data Fiduciary for your employment record and processes it under employment law. Kawst processes it as their processor. This block is a notice, not a consent request — you cannot be required to consent as a condition of employment. Data: attendance, leaves, salary structure, advances and loans, payslips, statutory deductions, ratings, custody and damage records. You can see your own record in the app at all times and can raise a correction with your employer or with us.

F. Job-seeker profile — optional, drivers only

Name, photo, experience, expected salary, licence class, rating.

Purpose: Let fleet owners find and hire you.
Visible to: Fleet owners searching for drivers in your area.

Home location (approximate, optional).

Purpose: Rank nearby jobs and let owners filter by distance.
Visible to: Only as a distance, never as a map pin, unless you switch on 'share home location'.

☐ (Optional) I want my job-seeker profile to be visible to fleet owners.

☐ (Optional) I allow my approximate home location to be shown to owners who view my profile.

G. Vehicle immobilisation — fleet owners fitting a compatible tracker

Immobilisation cuts the engine of a vehicle you own through a hardware tracker. Kawst only ever queues the command until the vehicle has been stationary for a safe interval, and only executes it on a request approved by the owner or an authorised superior with a PIN. By enabling it you confirm that you own or lawfully control the vehicle, that you have told every driver of the vehicle that it can be immobilised, and that you accept the responsibilities in the Terms and Conditions.

☐ I confirm the above and enable immobilisation for the vehicles I add a compatible tracker to.

H. Customer data you enter — fleet owners, supervisors and vendors

When you add a customer, client or lead, you are the Data Fiduciary for their data and Kawst is your processor. You confirm that you have the right to share it and have given them any notice you owe them. Kawst shows its own notice on every page a customer sees.

☐ I confirm I am entitled to enter the customer and staff data I add to Kawst.

I. Marketing and product updates — optional, all roles

Occasional SMS, WhatsApp, email or push messages about new features, offers and plans. Never more than four a month. Transactional messages about your account, trips and payments are not marketing and are sent regardless.

☐ (Optional) I would like to receive marketing messages from Kawst.

4. Consequences of not consenting

If you decline a required consent, the feature that needs it will not be available: without block B a driver cannot run a tracked trip; without block C a driver cannot apply for jobs or be assigned a vehicle; without block D you must enter expense figures by hand. You can still use every other part of Kawst. Declining an optional consent has no effect on the service.

Open Profile → Privacy to see every consent you have given and switch off the optional ones; job-seeker visibility and home location are switched in your job profile, and location in your phone's app permissions. Withdrawal takes effect immediately for new processing; data already collected is deleted or anonymised within 30 days unless the Privacy Policy explains why we must keep it. You also have the rights of access, correction, erasure, nomination and grievance redressal described in Section 10 of the Privacy Policy, and may complain to the Data Protection Board of India if we do not resolve your grievance.

The following is stored against your account for each consent you give or withdraw. It is the record we will produce to you or to the Data Protection Board on request.

Consent block

Value: A – I, as above

Notice version and language

Value: The version shown at the top of this notice (currently 2026-09-25); language shown to you

Granted at / withdrawn at

Value: Timestamp, IST

Source

Value: Sign-up screen, prominent disclosure, feature screen, or Profile → Privacy

Account

Value: Your Kawst user ID and registered mobile number

7. Signature block (for the printed form used when an owner onboards a driver in person)

Driver name: ______________________________ Mobile: __________________ Kawst ID: ______________

Consents given (tick): ☐ A ☐ B-location ☐ B-sensors ☐ C ☐ D ☐ F-profile ☐ F-home ☐ I

Signature: ______________________________ Date: ____ / ____ / ________ Language read in: ______________

Owner / witness name and signature: ______________________________________

The printed form is a convenience for owners onboarding drivers with limited phone literacy. It must be entered into the app by the driver on their own phone, or by the owner on the driver's behalf with the driver present, so that the server-side consent record exists. The paper copy is kept by the owner.