Frequently asked questions

AmbTrack is an emergency coordination platform that gives ambulance crews, control centres, hospitals, and traffic police one shared picture of an active response — from the moment a crew is assigned to the hospital handover.

Authorised personnel of emergency-response organisations. It is not a consumer app and is not open to the public. Members of the public should always call the official emergency number.

Not for general use. AmbTrack is in a closed pilot and we are in conversations with potential partners in Bengaluru. Features and availability can change during the pilot.

No. AmbTrack is a support tool. Dispatch authority, triage, clinical care, and traffic control stay with the responsible people and their protocols. If the app is unavailable or you doubt what it shows, fall back to approved radio and phone procedures — never delay a response waiting on the app.

Bangalore is the first focus. Another city would start with the same careful review of local workflows, partners, and operating needs before anything went live.

It is built and run by its founders and is currently an unincorporated project. See the About page. When it is incorporated, the legal pages will name the entity.

Your organisation enrols you, or you register with a valid role credential (vehicle registration number, badge number, hospital registration number, or a government authorisation code). Ambulance crew registration also needs a profile photo for identity verification.

There are no “normal” accounts — every account is an operational role with access to live dispatch data, ambulance locations, and patient-handover information. So every new account starts as pending and an administrator (and, where relevant, your organisation) approves it before you can sign in. This is a deliberate safeguard, not a delay we can waive.

It depends on your organisation and the administrator reviewing new accounts. You will be able to sign in once your account is set to active; until then, sign-in is blocked with a message saying approval is pending.

No. One account is one person. Shared or generic logins are not allowed, and an account can be signed in on only a limited number of devices at once.

Your organisation should tell us so the account is suspended. Accounts left inactive for a long period are suspended automatically and later deleted, subject to any records we must keep.

After registering you get an email with a six-digit code and a one-click “verify” link. Use either. The link opens a page with a confirm button so that automated mail scanners don’t consume it before you do.

Verification codes and links, and password-reset links, are valid only for a short time. That keeps a single-use secret from sitting live in an inbox. If it lapses, request a new one.

Sign-in is blocked with a message that your email isn’t verified. If your previous verification code has already expired, a fresh verification email is sent automatically and the message tells you so. Repeated sign-in attempts are rate-limited so they can’t be used to flood your inbox.

Use “forgot password”. You get a six-digit code and a reset link, both valid only for a short time. The link opens the set-a-new-password screen directly. Changing your password signs out all your other devices.

A security alert sent when your account is accessed from a device we haven’t seen before. It shows the device, IP address, approximate city, and time. If it wasn’t you, use the links in the email to review your sessions and reset your password, and contact support.

Crews see their assigned cases and their own location history. Hospitals see the clinical and logistical details of a patient assigned to them (not caller contact details). Traffic police see an approaching ambulance’s position and vehicle number when support is requested (no patient data). Control centres see active cases, ambulance positions, and hospital availability in their area.

Only while you are signed in and on active duty (available or assigned). It stops when you go off duty or sign out. High-frequency location points are kept only briefly and then removed, unless they are attached to a case, an SOS, a traffic alert, or a legal hold.

Return to your approved radio and phone procedures. The app caches a basic offline shell, but it is a coordination aid, not a dependency.

If you allow them in your browser, you get push alerts for time-sensitive updates such as a new assignment or an urgent case change. You can turn them off in your preferences.

For a registered user: name, email, Indian mobile number, role and organisation, your role credential, a crew photo where applicable, preferences, and security/audit logs. The full list and the reasons are in the Privacy Policy.

A dispatcher or crew enters the minimum a response needs — patient name, approximate age, gender (any can be blank), pickup location, caller contact, triage, and vitals. It is kept with the case and then deleted on the retention schedule, unless a legal hold applies. Caller contact details are shown only to the control centre and the assigned crew.

Case records and the audit trail are kept for as long as medical, operational, and legal record-keeping requires. Live operational data such as location updates is kept only briefly. Account data is kept while the account is active and for a limited period after it closes. Security and verification data is kept only as long as its security purpose needs. See Data retention in the Privacy Policy.

Yes. Email privacy@ambtrack.in from your registered address, or use the export and deletion options in your account settings. We acknowledge promptly and aim to complete within 30 days. Some records we are legally required to keep cannot be deleted early — we will explain any limit.

No. We do not sell, rent, or trade personal data, and we use no advertising or cross-site tracking cookies. See the Cookie and Local-Storage Notice.

A small number of vetted providers for hosting, database, storage, transactional email and messaging, bot protection, and maps. They process data only on our instructions. See Service providers in the Privacy Policy.

We aim to store personal data on infrastructure in India. Some providers (notably transactional email and the bot-protection challenge) may process limited data such as an email or IP address outside India under contractual safeguards. We do not transfer data to any country the Government has restricted.

We assess it without undue delay and notify affected people and the relevant authority as applicable law requires, including what happened and how to protect yourself.

Through our Grievance Redressal process. If you are not satisfied, you can approach the Data Protection Board of India.

An introductory conversation. We learn how your team works, discuss what information each role needs, and decide together whether to keep planning. It creates no commitment.

During the pilot the service is provided free of charge. Any future paid arrangement would be agreed separately in writing.

A willingness to walk us through your current workflow, a point of contact for enrolling authorised users, and your organisation’s own procedures for emergency response and records — which always take priority over the platform.

AmbTrack is the Data Fiduciary for the platform. Where your organisation controls certain data and AmbTrack processes it on your behalf, that is set out in a separate written agreement. Retention and access follow the Privacy Policy.

Use the “request a pilot briefing” form on the home page, or email info@ambtrack.in.

Email support@ambtrack.in with what you were doing, what you expected, and what happened.

Please report it privately to security@ambtrack.in before disclosing it anywhere else. We welcome good-faith research under coordinated disclosure and do not penalise good-faith reports.

Support: support@ambtrack.in · Privacy and rights requests: privacy@ambtrack.in · Formal grievances: grievance@ambtrack.in · Legal: legal@ambtrack.in · Pilot enquiries: info@ambtrack.in.