Bishop Machine
Bishop Machine
  • Home
  • Capabilities
  • Equipment
  • Request a quote
  • More
    • Home
    • Capabilities
    • Equipment
    • Request a quote
  • Home
  • Capabilities
  • Equipment
  • Request a quote

Hermes Business Integration Privacy Policy

Last updated: September 26, 2026

1. Who operates the application

Bishop Machine ("Bishop," "we," "us," or "our") operates Hermes Business Integration ("Hermes" or the "Application") for authorized business use with the Bishop intranet. This notice explains how we handle information in the Application's customer-onboarding and connected-business-system workflows. It is not a general privacy notice for unrelated Bishop website, employment, or manufacturing activities.

The Application is not a public customer account-registration service. Publishing this notice does not give anyone access to the intranet or connect a QuickBooks company. Features under development remain unavailable until separately enabled and authorized.

2. Information handled

Depending on the enabled workflow, the Application handles:

  • Business and contact information: company and contact names, business email addresses, phone numbers, and billing or other business addresses.
  • Customer setup records: payment-term selections, tax-treatment selections and review notes, customer identifiers, and possible duplicate matches.
  • Documents provided for onboarding, including customer applications, W-9s, and exemption certificates. Original documents may contain signatures, tax identification numbers, or other personal information even when that information is not extracted into separate fields.
  • Records from connected systems that are needed for the selected task, such as existing customer names, identifiers, addresses, payment terms, and tax settings.
  • User and activity information: the identity of the person performing an action, permissions, timestamps, submission status, document names, file sizes, integrity checks, and operational or security logs.
  • Connection information: the company identifier and authorization tokens needed to maintain an approved integration. QuickBooks authentication takes place with Intuit; do not provide your Intuit password in customer forms or to Bishop support.

Information comes from authorized users, documents supplied to Bishop, and connected services after the relevant authorization. Please provide only information needed for the business task. Do not upload payment-card information, passwords, unrelated personal records, or export-controlled technical data to this customer-onboarding workflow.

3. How information is used

We use this information to prepare and review customer setup, identify possible duplicate records, communicate about applications, establish reviewed customer defaults, carry out authorized record creation or synchronization, troubleshoot errors, maintain an activity history, and protect the Application. Document reading supplies suggestions; a person must review them. Receipt of a tax form does not itself verify its accuracy or establish a legal tax exemption.

The current customer-form reader processes PDF text in the user's browser. This workflow does not send uploaded customer or tax forms to an AI model for extraction. Other intranet tools are outside this notice's scope and may have different data flows.

We do not sell information handled through these workflows or use it for targeted advertising.

4. QuickBooks and other service providers

When the QuickBooks connection is enabled, a company administrator must authorize it through Intuit. Intuit's accounting permission can permit broader access than a single customer screen; the Application's business workflow limits the operations it performs. Authorization is not a promise that every feature is enabled, and it is not authority for unrelated accounting actions or payments.

For an enabled and approved workflow, relevant customer fields may be read from or sent to Intuit QuickBooks and Fulcrum. Original documents are stored with the saved review and are sent to a connected destination only where that workflow supports and authorizes attachments. Other providers may process information necessary for hosting, storage, authentication, email delivery, administration, or support. For example, the customer-forms email function uses Bishop's configured Google email service. Those providers' terms and privacy notices also apply to their services.

Access within Bishop is limited through the Application's permissions to authorized personnel and administrators. We may also disclose information when required by law, to respond to lawful requests, or as necessary to investigate misuse or protect rights and security. The public policy pages are hosted separately; their hosting provider may process ordinary website-visit information under its own notice.

5. Storage, security, and retention

The local review version stores submitted records and original documents on Bishop-controlled development infrastructure; a hosted deployment uses its configured storage. Saved documents are not public website assets. Access checks and document-integrity checks are part of the current workflow. These measures reduce risk but do not guarantee that all loss, unauthorized access, or service interruptions can be prevented.

We retain records for customer administration, audit and troubleshooting needs, and applicable accounting, tax, contractual, or legal obligations. The appropriate period depends on the record and purpose; there is no single automatic deletion deadline for every record. Administrators handle retention and deletion requests. Backups and records that must be retained may persist after an active record is removed.

6. Choices, corrections, and disconnection

You may contact Bishop to request information about records relating to you, correction of inaccurate information, or deletion where appropriate. We may need to verify your identity and authority. Legal obligations and other applicable exceptions can limit what we may disclose or delete; nothing in this notice limits rights available under applicable law.

A QuickBooks administrator can revoke the Application's connection using QuickBooks' connected-app controls. You can also contact Bishop for help disabling the integration. Disconnection stops the authorized connection; it does not automatically erase records already saved in Bishop's systems, QuickBooks, Fulcrum, email, or backups. Requests concerning records in another service may require action in that service as well.

7. Updates and contact

We may revise this notice as workflows change. The date above identifies the latest revision. Material changes affecting the authorized use of connected information will be communicated to affected users or administrators before the changed use is introduced, where required.

Questions, privacy requests, and suspected security issues should be directed to:

Bishop Machine — Administration
Email: admin@bishopmachineworks.com
Phone: 770-483-7673
Address: 1780 Iris Drive Southwest, Conyers, Georgia, USA

Do not include tax identification numbers, passwords, or complete tax forms in an initial support email. Ask for an appropriate way to provide any necessary sensitive information.

Copyright © 2026 Bishop Machine. All rights reserved. Photography is illustrative stock imagery.

  • Privacy Policy
  • Terms and Conditions
  • Hermes Privacy Policy
  • Hermes EULA
  • About Bishop

Powered by

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept