Acceptable Use Policy

1. Purpose and scope

AmbTrack exists to help authorised teams coordinate a live emergency response. This policy keeps the platform trustworthy, keeps sensitive data safe, and keeps everyone’s access limited to what their role needs. It applies to all use of the web application, field apps, APIs, and website.

2. Core principles

• Emergency use only. Use AmbTrack for coordinating real emergency response, not for anything else.
• Least access. Look at only the cases and data your current role and assignment require.
• Accuracy. Enter true, current information. Other people act on what you record.
• Confidentiality. Treat patient, caller, and responder data as confidential and keep it inside the response workflow.
• Don’t break the tool. No probing, scraping, overloading, or working around access controls.

3. Prohibited uses

You must not:

• use AmbTrack for personal, commercial, journalistic, research, training, or any other non-emergency purpose without our prior written consent;
• create a case, SOS, or alert that does not correspond to a real emergency, or run tests against the live system without authorisation;
• submit false, misleading, or deliberately incomplete dispatch, location, status, triage, or handover information;
• use AmbTrack to harass, intimidate, defame, or discriminate against any person;
• use AmbTrack in a way that breaks any applicable law or your organisation’s policies, or that would bring emergency services into disrepute;
• impersonate another person or misrepresent your role, organisation, or authorisation.

4. Data accuracy and integrity

• Record events (assignment, en route, on scene, transporting, handover, completion) promptly and truthfully.
• Do not back-date, alter, or delete records to hide what happened. The platform keeps an audit trail of significant actions.
• If you notice an error in a record, correct it through the normal workflow and, where the field cannot be corrected, tell the control centre or support@ambtrack.in.

5. Access and role boundaries

• Access data only for a case you are actively handling or supervising, and only for coordinating that response.
• Do not attempt to view cases, locations, or accounts outside your assigned area or role, or to escalate your own permissions.
• Do not use another person’s session, or leave your session open on a device others can use.
• Administrators must use elevated access only for legitimate operational and support tasks, and their actions are logged.

6. Patient and caller data

• Collect only the details the response needs; leave unknown fields blank rather than guessing.
• Do not screenshot, photograph, copy, forward, post, or discuss patient or caller data outside the response workflow, except where your clinical or legal duties require it.
• Do not use caller contact details to contact a patient or caller for any purpose other than the active response.
• Handle any patient information in line with your organisation’s medical-records, consent, and confidentiality rules.

7. Security and platform integrity

You must not:

• probe, scan, or test the vulnerability of AmbTrack, or breach or circumvent any security or authentication measure, without our prior written authorisation;
• access the Service by any automated means (bots, scrapers, crawlers) except an interface we provide for that purpose;
• reverse-engineer, decompile, or disassemble the Service, or attempt to derive source code, except where the law expressly permits;
• introduce malware, or interfere with or disrupt the Service, its servers, or connected networks (for example by flooding, overloading, or spamming);
• remove, obscure, or alter any notice, label, or identifier on the Service;
• use the Service to build or train a competing product, or to benchmark it for a competitor.

Good-faith security research is welcome under a coordinated disclosure arrangement — contact security@ambtrack.in first.

8. Accounts and devices

• One account per person. Do not share credentials or use a shared or generic login.
• Keep your password confidential and your devices reasonably secure; sign out on shared devices.
• Report a lost device or a suspected compromise immediately, and use your account settings to end sessions and change your password.
• Do not register accounts for people who are not authorised personnel, or keep accounts active for people who have left a role.

9. Messages and content

• Case messages are for short operational coordination. Keep them factual and relevant to the response.
• Do not post abusive, discriminatory, or unlawful content, or content unrelated to the case.
• Do not use case messages to share data with people who should not have it.

10. Reporting a concern

If you see misuse, a data-handling problem, or a safety issue, report it to your control centre and to support@ambtrack.in. For a security vulnerability, email security@ambtrack.in. For a formal complaint, use our Grievance Redressal process. We do not penalise good-faith reports.

11. Enforcement

Depending on the severity and circumstances, we may:

Where a breach is serious or a risk is immediate, we may act first and explain afterwards. You may contest a decision through the grievance process.

12. Changes

We may update this policy as the Service and its risks evolve. Material changes are notified to registered users by email at least 14 days before they take effect. The dates at the top of this page show the current version.