1. Acceptance and authority
These Terms & Conditions (“Terms”) govern access to the Patrol Guard mobile application, web dashboard, backend API, and related services (the “Service”). By accessing or using the Service, you agree to these Terms and the Privacy Policy.
If you use the Service for an employer, client, contractor, or other organization, you confirm that you are authorized to act for that organization. If you do not agree or lack authority, do not access the Service.
2. Accounts and access
Accounts are created or provisioned by an authorized administrator. Users must provide accurate information, use only the account assigned to them, keep credentials and devices secure, and notify the organization administrator promptly of suspected unauthorized access.
Roles determine available functions. Attempting to bypass role restrictions, access another organization, impersonate another user, share a personal account, or extract provider credentials is prohibited. The organization is responsible for timely account changes when personnel join, change duties, or leave.
3. What Patrol Guard provides
Patrol Guard supports guard tour planning and execution, NFC checkpoint registration and scanning, location-based validation, offline event capture and later synchronization, schedules and assignments, incident and SOS workflows, monitoring, reports, audit events, and optional Google Sheets synchronization.
Features may depend on device hardware, permissions, configuration, connectivity, provider availability, and the subscribed or deployed version. A successful scan is operational evidence, not an unconditional guarantee that a person complied with every policy or that a site was safe.
4. Organization and administrator responsibilities
Each organization is responsible for:
- ensuring it has authority to create accounts and process workforce, location, device, incident, and patrol data;
- providing legally required notices and obtaining any required permission or consent;
- configuring sites, checkpoints, geofences, schedules, roles, escalation channels, retention, and access accurately;
- placing NFC tags safely and maintaining physical signs, devices, networks, and emergency procedures;
- reviewing exceptions and incidents using qualified personnel rather than relying only on automated status;
- managing its Google account and spreadsheet access, backups, sharing settings, and departing administrators;
- complying with employment, privacy, surveillance, safety, and other applicable requirements.
5. Acceptable use
You may use the Service only for lawful, authorized organizational operations. You must not:
- submit false scans, falsify locations or timestamps, clone identifiers, or deliberately defeat validation controls;
- probe, overload, disrupt, reverse engineer, scrape, or bypass the Service except where applicable law expressly permits it;
- upload malware, unlawful material, excessive personal data, secrets, or content you are not authorized to process;
- use the Service to harass, discriminate, unlawfully monitor, or endanger any person;
- access data outside your assigned organization, site, role, or operational purpose;
- remove notices or misuse Patrol Guard names, interfaces, or documentation.
6. Field operation, NFC, and location
Organizations and users must verify that supported devices, NFC tags, location settings, time settings, and connectivity are suitable before operational use. Location accuracy can be affected by buildings, hardware, interference, permissions, battery controls, and satellite or network conditions. NFC identifiers can be damaged, replaced, or in some cases duplicated.
Offline mode queues eligible events for later delivery. It does not guarantee immediate supervisor visibility, notification, escalation, or acceptance by the server. Users must follow the organization's independent emergency and communication procedures. Patrol Guard must not be the only method for contacting emergency services or protecting life and property.
7. Google Sheets integration
An authorized organization administrator may connect a Google account and grant the scopes displayed in the authorization flow. The organization is responsible for choosing an appropriate account, protecting it, reviewing spreadsheet sharing, maintaining sufficient quota, and complying with Google's terms.
Each connected organization may use a different spreadsheet. Connecting or disconnecting one organization must not authorize a user to access another organization's sheet. Revoking access or disconnecting stops future synchronization after the change is processed; it does not automatically delete existing spreadsheet content, Google backups, or previously exported files.
8. Data, exports, and backups
As between the Service and an organization, the organization retains responsibility for its submitted operational content and grants the permissions reasonably required to host, validate, synchronize, display, protect, and support that content.
The organization must review its retention needs and maintain appropriate independent backups, particularly for organization-owned Google Sheets and exported reports. Data can be changed or lost through administrator actions, provider changes, device loss, configuration mistakes, account revocation, corruption, or events outside the Service's reasonable control.
Exports may contain confidential or personal information. The person exporting or receiving a report is responsible for storing and sharing it securely.
9. Availability, maintenance, and changes
We aim to operate a useful and secure Service but do not promise uninterrupted, error-free, or permanently available access. Maintenance, security response, capacity limits, internet failures, provider outages, updates, or force-majeure events may affect availability.
Features, interfaces, limits, and supported platforms may change. Where practical, material changes that disrupt normal use should be communicated through an appropriate channel. Organizations should test important workflows after updates and maintain operational fallback procedures.
10. Intellectual property and feedback
The Service, software, interface, branding, and documentation are protected by applicable intellectual-property laws. These Terms provide a limited, non-exclusive, non-transferable, revocable right to use the Service for authorized operations; they do not transfer ownership.
If you provide suggestions or feedback, you permit us to use them to improve the Service without an obligation to compensate you, while excluding confidential information clearly identified as such.
11. Suspension and termination
Access may be restricted or suspended when reasonably necessary to address a security risk, suspected abuse, unlawful activity, material breach, unpaid service obligations where applicable, provider restriction, or harm to users or systems. An organization may deactivate its users. Termination does not remove provisions that by their nature should survive, including data responsibility, intellectual property, disclaimers, liability limits, and dispute terms.
Before ending use, the organization should export data it is entitled to retain and disconnect integrations. Post-termination retention or deletion follows the Privacy Policy, applicable instructions, backup cycles, legal duties, and technical constraints.
12. Disclaimers
To the extent permitted by applicable law, the Service is provided “as is” and “as available.” We disclaim implied warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation where such disclaimers are legally permitted.
13. Limitation of liability
To the maximum extent permitted by applicable law, neither Patrol Guard nor its operators, suppliers, or contributors will be liable for indirect, incidental, special, consequential, exemplary, or punitive loss; loss of profit, revenue, business, goodwill, or data; or harm caused by unauthorized configuration, user misconduct, third-party services, inaccurate device signals, failed connectivity, or failure to follow independent safety procedures.
Any total liability that cannot legally be excluded will be limited to the amount paid for the affected Service during the twelve months before the event giving rise to the claim, unless a different minimum remedy is required by law. Nothing in these Terms excludes liability that cannot lawfully be excluded.
14. Governing law and disputes
These Terms are governed by the laws of the Republic of Indonesia, without excluding mandatory protections that apply in another jurisdiction. Before filing a formal claim, the parties should attempt in good faith to resolve the matter by sending written notice describing the issue and requested resolution. If it is not resolved, the dispute may be brought before the competent court determined under applicable law, unless the parties have a separate written agreement.
15. Changes to these Terms
We may update these Terms to reflect Service, provider, security, business, or legal changes. The date above will be revised. Material changes should be communicated through the Service, email, an organization administrator, or another appropriate channel. Continued use after the effective date constitutes acceptance where permitted by law.
16. Contact
Questions about these Terms or the Service can be sent to:
These published Terms are a practical service document and are not legal advice to an organization. Organizations should obtain independent advice for their specific workforce, surveillance, safety, retention, and regulatory obligations.