Effective date:
Operator and purpose
Autobus DaHua operates DaHuaMonitor for authorized internal review of quotation and operational correspondence. This policy describes information handled by the monitor. Questions and privacy requests can be sent to op.dahua@gmail.com.
Information accessed
Depending on the authorized feature, the application accesses email identifiers, conversation identifiers, dates, subjects, message headers, and selected message text from the designated company mailbox. Correspondence may contain customer names, contact information, pickup and destination addresses, travel dates, passenger counts, quotations, and booking details.
The scheduled subject-triage trial accesses subjects and dates. Separately authorized pilot reviews have processed selected message texts and their conversation context. Attachments are excluded from the current pilot review workflow.
For the separate private notification account, the application requests permission to send email and verify the account's identity. OAuth credentials support the authorized connections.
How information is used
Information is used to organize relevant correspondence, compare details within a conversation, identify potential matters for review, display supporting evidence, record human corrections, and support approved private notifications. Review notes may be included as context in subsequent reviews of the same conversation.
The application does not sell Google user data, use it for advertising, or use mailbox content to train a generalized AI model.
Service providers and sharing
Google provides Gmail access, account authorization, and delivery through the approved private sender.
When AI-assisted review is explicitly enabled, selected email text and relevant context are sent to the OpenAI API for analysis. Those excerpts can contain customer and trip information. Company vocabulary and customer-facing rate references may accompany the request. Internal driver-pay reference notes and attachments are excluded from the current cloud review workflow.
The pilot requests use response storage disabled. Provider security and abuse-monitoring retention may still apply. Processing may occur outside Canada, subject to the provider's applicable services and terms. Authorized staff should consider this before enabling a review involving personal information.
Private notifications, when enabled, are delivered only to the configured approved recipient. Customer correspondence and operational information are accessible to authorized personnel as needed for the application and its support.
Storage and safeguards
Selected source texts, review results, human corrections, and processing records are stored on the authorized Windows computer. Windows account permissions restrict access to the application folder. OAuth credentials and the API key are stored in Windows Credential Manager. Network communication with Google and OpenAI uses HTTPS.
Local message and review data is currently retained until an authorized administrator deletes it. Automatic retention cleanup is not configured. Copies in backups or provider systems may follow separate retention practices. Contact the operator to request a review of stored information and its deletion where applicable.
Your choices and requests
Authorized account holders can revoke the application's Google access in their Google Account settings. Revocation stops future access using that authorization. It does not automatically delete data already stored locally.
For access, correction, deletion, or other privacy requests concerning monitor data, contact op.dahua@gmail.com. The operator may need to verify your identity and authority to handle a request. Deletion requests are reviewed alongside applicable legal and operational recordkeeping requirements.
Google API user data
DaHuaMonitor's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Changes
This policy will be updated when the application's data practices change. Material changes to data access or use will be disclosed before the affected feature is enabled, with renewed authorization where required.