App Policy

This App Policy explains how authorized users should use mobile and web applications provided by Azotos App Studio Pvt. Ltd.. It applies to Azotos-branded apps, customer-specific enterprise apps, white-labeled operational apps and internal business apps published or maintained by Azotos unless a separate app-specific policy says otherwise.

It applies to field users, employees, contractors, supervisors, managers, administrators, customers, vendors, auditors and support users who access an Azotos app through an organization. This policy should be read together with our Privacy Policy, Terms and Conditions, Data Deletion page, customer agreement and any project, HR, safety, site or standard operating procedure issued by your organization.

Because this policy supports multiple apps and store publications, not every feature, permission or data type listed here applies to every app. Each app store listing, in-app permission flow, Google Play Data Safety form, Apple App Privacy response and Apple privacy manifest should match the actual behavior of that specific app.

Azotos apps request permissions only when needed for the app feature being used or for a customer-enabled workflow. Permission names and availability differ by Android, iOS, iPadOS and browser platform.

When an app accesses personal or sensitive data in a way that users may not reasonably expect, including background location or restricted APIs, the app should show a clear in-app disclosure before permission access. The disclosure should describe what data is collected, why it is needed, how it is used or shared, and provide an affirmative choice before collection begins.

Store descriptions, website policies and terms are not a substitute for required in-app permission prompts or prominent disclosures. Users must be able to decline optional permissions, and the app should degrade gracefully where a feature can operate without that permission.

Location-enabled workflows are intended to improve operational visibility, evidence, safety, accountability, dispatch, attendance accuracy and service quality. Your organization decides which users, roles, projects and workflows require location capture.

Background location is used only when a specific app and customer workflow requires ongoing field-duty tracking, route tracking, dispatch visibility, SLA monitoring or safety supervision. If background location is enabled, the app must disclose this clearly before permission access and comply with the applicable Google Play and Apple review requirements.

Users must not tamper with device location, use mock-location tools, disable required permissions during active field work, submit proxy attendance, manipulate timestamps, bypass tracking controls or falsify operational evidence.

Some app features may support offline capture where network connectivity is limited. Offline data should be synchronized as soon as connectivity is restored. Users are responsible for checking whether important records, images, approvals or task updates have synced successfully.

Apps may include customer-approved or Azotos-approved SDKs, APIs and services for maps, push notifications, analytics, crash reporting, cloud hosting, authentication, communication, storage, AI-assisted support, document handling and security. These tools must be used only for policy-conforming purposes and reflected in store privacy disclosures where applicable.

App teams must review SDK data practices before adding or updating SDKs. For Apple submissions, privacy manifests and required reason API declarations must match app and SDK behavior. For Google Play submissions, SDK data handling must align with the User Data policy and the app Data Safety form.

If an app allows account creation, users must be able to request account and associated data deletion from within the app where available and through the external Data Deletion page at /data-deletion. The same page can be used as the privacy choices URL for app store submissions.

Some customer-controlled records, legal records, audit trails, security logs, tax records, accounting records, fraud prevention records or dispute records may be retained when required by law, contract or legitimate enterprise recordkeeping obligations.

Azotos enterprise apps are intended for business and operational users. They are not directed to children and should not be configured as child-directed consumer apps. If a customer uses an app for apprentices, trainees or minors in a lawful work or training context, the customer must obtain required permissions and comply with applicable child, labor, safety and privacy laws.

Azotos enterprise apps are not designed for third-party advertising or sale of personal and sensitive user data. Apps must not track users across third-party apps or websites for advertising or advertising measurement unless a separate app-specific implementation, App Tracking Transparency flow where applicable, store disclosure and lawful consent process is approved before release.

Azotos may release app updates for security, reliability, compatibility and feature improvements. Some features may require users to update to the latest supported version. Support requests should include relevant details such as user ID, organization, project, device type, app version, screenshot and issue timing where appropriate.

Violation of this App Policy may result in restricted access, account suspension, data correction, audit review, customer escalation, app configuration changes, disciplinary action by the user organization, legal action, store remediation or other action permitted by law and contract.

We may update this App Policy to reflect app functionality, customer requirements, security controls, laws or Google Play and Apple App Store policy changes. The updated date at the top of this page shows the latest revision.

For app policy questions or support routing, contact Azotos App Studio Pvt. Ltd. at info@azotos.in.