> For the complete documentation index, see [llms.txt](https://amast-einvoice.gitbook.io/amast-servicehub-mobile/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amast-einvoice.gitbook.io/amast-servicehub-mobile/amast-servicehub-privacy-policy.md). # AMAST ServiceHub Privacy Policy Last updated: 24 September 2026 This policy describes how AMAST ServiceHub handles information for workspace admins, technicians, and customers who use the web app and the mobile app. Information we collect * Account details: name, email, phone number, role, and company. * Workspace records: customers, sites, assets, service requests, schedules, quotations, invoices, and notes entered by your team. * Field work: job status, checklist answers, photos, signatures, and reports. * Location: technician location while the mobile app is used for assigned jobs. * Billing: subscription and payment status. Card details are handled by the payment provider. ServiceHub does not store full card numbers. How we use it * To run the workspace, assign and track jobs, and produce reports. * To sign you in, send operational messages, and support the account. * To bill the subscription and keep a record of invoices. Who can see it * People in your workspace, according to their role. * Providers that host the service, send email, or process payments, only as needed to run ServiceHub. * We do not sell personal information. How long we keep it * While the workspace is active, and for as long as needed for operations, billing, and legal records. * You can ask us to delete an account or workspace record that we are not required to keep. Contact AMAST Sdn Bhd --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://amast-einvoice.gitbook.io/amast-servicehub-mobile/amast-servicehub-privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.