Skip to content
AZOTOS
Privacy

Privacy Policy

How Azotos collects, uses, protects and handles information across the website, platform and mobile applications.

Last updated: 17 July 2026

Scope and covered apps

Azotos App Studio Pvt. Ltd. ("Azotos", "we", "our" or "us") provides enterprise software, websites, web applications and mobile applications for infrastructure and field-intensive organizations. This Privacy Policy applies to Azotos-branded apps, customer-specific Azotos apps, internal enterprise apps published by Azotos, related websites, dashboards, APIs, support channels and services unless a separate app-specific policy says otherwise.

This policy is designed to support Google Play and Apple App Store publication disclosures for multiple Azotos apps. Not every app, customer deployment, platform, module, role or feature collects every data type described below. The actual collection depends on the app, enabled modules, user role, organization configuration, device permissions and workflow used.

If you use Azotos through your employer, contractor, customer, principal, vendor, site owner or another organization, that organization may control the business records submitted through the platform. In those cases, we process the information according to our agreement with that organization and applicable law.

Developer and privacy contact

Developer and service provider: Azotos App Studio Pvt. Ltd..

Privacy contact: info@azotos.in.

Website: https://azotos.in.

Users can submit privacy, access, correction, deletion, account deletion and data export requests through the Data Deletion page at /data-deletion or by contacting the email address above.

Data types we may collect

  • Contact information: name, company name, designation, employee or contractor ID, email address, phone number, business address and inquiry details.
  • Account and authentication information: username, user ID, password or password hash, OTP status, login history, role, department, project, branch, organization, device session and access permissions.
  • Profile and employment-related information: attendance status, shift, team, supervisor, reporting manager, site assignment, work allocation, leave, payroll or reimbursement references where enabled by the customer.
  • Precise or approximate location: GPS, network-based location, geo-tagged site records, route points, check-in/check-out location, task location and location timestamps where enabled and permitted.
  • Photos, videos and files: site images, asset images, work proof, installation evidence, ticket attachments, document scans, invoices, forms, reports, drawings and other files uploaded by users.
  • Audio or microphone data: voice notes, call-related recordings or audio evidence only when a specific app feature enables it and the user or organization permits it.
  • Operational and user-generated content: tickets, tasks, remarks, comments, approvals, rejections, inspection notes, measurements, warehouse entries, material movement, assets, finance workflows, customer records, vendor records and dashboard inputs.
  • Financial and commercial workflow data: expense claims, invoice references, payment status, billing records, purchase order references, tax fields, reimbursement details and settlement information where enabled. We do not publicly disclose financial or payment information.
  • Identifiers: app user ID, customer ID, device ID, push notification token, session ID, resettable advertising ID only if a future app feature explicitly uses it, and other technical identifiers needed for account, security, notifications and diagnostics.
  • Device, app and network information: device model, operating system, app version, browser, language, IP address, time zone, connectivity status, crash logs, diagnostics, performance data and security logs.
  • Usage data: app launches, screen views, taps, feature usage, sync status, errors, workflow timestamps, audit actions and support diagnostics.
  • Communications and support data: emails, calls, WhatsApp or chat messages, support tickets, screenshots, recordings shared for troubleshooting and feedback.
  • Cookies and website data: website visits, form submissions, analytics events, browser data and cookie identifiers used for website functionality, security and analytics.

Store disclosure mapping

For Apple App Privacy and Google Play Data Safety purposes, Azotos apps may include the following broad data categories depending on the app: Contact Info, Location, User Content, Identifiers, Usage Data, Diagnostics, Financial Info, Search History, Other Data and app-specific business records.

Common purposes include App Functionality, Analytics, Security, Fraud Prevention, Account Management, Product Personalization, Customer Support, Legal Compliance and Enterprise Reporting. Azotos does not use personal and sensitive user data for sale to third parties. Azotos does not use data for third-party advertising or cross-app tracking unless a separate app-specific disclosure and consent flow expressly says so.

How we use data

  • Provide, operate, maintain, secure, troubleshoot and improve Azotos websites, apps, platform modules, APIs, dashboards and support services.
  • Authenticate users, manage accounts, enforce role-based access controls, maintain audit trails and prevent unauthorized access.
  • Enable attendance, task management, field tracking, ticketing, asset management, warehouse, HRMS, finance, approvals, reporting, notifications and other configured workflows.
  • Verify field activity through timestamps, photos, documents, location, device data, approvals and workflow evidence where enabled.
  • Respond to inquiries, schedule demos, prepare proposals, onboard customers, train users and provide customer support.
  • Monitor reliability, analyze crashes, diagnose sync failures, improve performance and protect against fraud, misuse, spam, malware and security incidents.
  • Generate dashboards, reports, logs, exports and management views for authorized customer users.
  • Meet contractual, legal, tax, accounting, audit, regulatory, safety and compliance obligations.

Sharing and processors

We do not sell personal and sensitive user data. We share data only as needed to provide the services, support customer instructions, comply with law, protect rights and security, or complete a legitimate business transaction.

  • Customer organization: administrators, owners, managers, supervisors, approvers, auditors and authorized users of the organization that provides or authorizes your access.
  • Service providers: hosting, cloud infrastructure, databases, storage, messaging, email, SMS, push notifications, analytics, crash reporting, support, security and implementation vendors under appropriate confidentiality and data protection obligations.
  • Third-party integrations: customer-approved ERP, HRMS, payment, ticketing, maps, identity, storage, BI, AI, communication or workflow tools when enabled by the customer or user.
  • Legal and safety recipients: professional advisers, auditors, insurers, regulators, law enforcement, courts, government authorities or affected parties where required or permitted by law.
  • Business transfers: acquirers, successors or counterparties in a merger, acquisition, restructuring, financing or transfer of business assets, subject to lawful notice and safeguards.

Third-party SDKs, APIs and AI tools

Azotos apps may include third-party SDKs, APIs or services for maps, push notifications, crash reporting, analytics, authentication, cloud storage, communication, payment status, document handling, security, AI-assisted support or similar app functionality. We review these tools for policy fit and data handling before use.

Where a third-party SDK or integration collects data, its collection must be reflected in the relevant Google Play Data Safety form, Apple App Privacy responses, Apple privacy manifests where applicable, in-app disclosures and this policy or an app-specific disclosure.

Permissions and sensitive access

Azotos apps request device permissions only when needed for app functionality or customer-enabled workflows. The app may request runtime permission and, where required, provide a prominent in-app disclosure before accessing sensitive data.

  • Location permission may support attendance, live field tracking, route tracking, task verification, site proof, dispatch, safety, SLA monitoring and geo-tagged records.
  • Camera, photos and video permissions may support site evidence, work completion proof, document scan, material proof, asset verification, profile image and ticket attachments.
  • Microphone permission may support voice notes, support recordings or audio evidence only when enabled.
  • Files and storage permissions may support document upload, export, report download, offline records and attachment handling.
  • Contacts, calendar, SMS, phone, call log, Bluetooth, nearby devices, notification, background location, package visibility, accessibility, health, biometric or other restricted permissions are used only if a specific app feature requires them, the store listing and in-app flow disclose them, and the app meets platform policy requirements.

Location and background data

Some enterprise field apps may collect location while the app is in use. Background location is used only when a customer-enabled feature requires ongoing route tracking, field duty tracking, safety visibility, SLA monitoring or live operations control, and only after the required platform permission and disclosure flow.

Users can disable location permissions in device settings. Disabling required permissions may limit attendance, tracking, task evidence, ticket closure, dispatch or other features that depend on location.

Security safeguards

We use reasonable technical, organizational and administrative safeguards designed to protect information from unauthorized access, misuse, loss, alteration and disclosure. These safeguards may include HTTPS or equivalent encryption in transit, access controls, authentication, authorization, audit logs, backups, monitoring, environment separation and restricted administrative access.

No system can be guaranteed to be completely secure, but we work to keep controls proportionate to the nature of the data and services. Users and customer administrators are responsible for protecting credentials, devices, network access and role assignments.

Retention and deletion

We retain information for as long as needed to provide services, meet customer instructions, comply with legal obligations, resolve disputes, enforce agreements, preserve audit trails, support security and maintain business records. Customer operational data may be retained, exported, archived or deleted according to the applicable customer agreement and configured retention requirements.

If an app allows account creation, users can request account and associated data deletion from within the app where available and through the external Data Deletion page at /data-deletion. Some records may be retained where required for legal, accounting, fraud prevention, security, audit, dispute, contractual or enterprise recordkeeping purposes.

User choices and rights

Depending on applicable law and customer configuration, users may request access, correction, export, deletion, restriction or objection for personal information. If your information is controlled by your organization, we may route the request to that organization or require authorization from that organization before completing the request.

Users may manage device permissions such as location, camera, photos, microphone, notifications and files through device settings. Some app features may not function if required permissions are disabled.

Children and restricted audiences

Azotos enterprise apps are intended for business users and are not directed to children. We do not knowingly collect personal information from children for consumer services. If an organization assigns app access to a minor or apprentice as part of lawful business, training or field operations, the organization is responsible for obtaining required permissions and complying with applicable child, labor, safety and privacy laws.

Cookies, analytics and web views

Our websites and services may use cookies or similar technologies for functionality, security, analytics, form handling and user experience. Browser settings may allow users to block or delete cookies, though some features may be affected.

If an app uses web views for Azotos pages, customer portals, help articles, dashboards or embedded workflows, data collected through those web views is handled according to this policy or the policy shown in that web view.

International processing

Data may be processed in India and other locations where Azotos, customer infrastructure, cloud providers, service providers or support teams operate. We use contractual, technical and organizational safeguards where required for cross-border processing.

Policy changes

We may update this Privacy Policy to reflect product, legal, operational, store policy or security changes. The updated date at the top of the page shows the latest revision. For material changes, we may provide additional notice through the website, app, customer administrator, email or other appropriate channel.

Contact

For privacy questions, requests or concerns, contact Azotos App Studio Pvt. Ltd. at info@azotos.in.