Skip to main content
HiveSync compliance

HiveSync by Bizmonger Inc Privacy Policy

Learn what HiveSync collects, why it is used, and how to manage sign-in, SMS, YouTube, and account data choices.

Effective August 1, 2026

HiveSync is operated by Bizmonger Inc. HiveSync helps clients and contractors coordinate project requirements, work progress, completion evidence, and report review. This policy explains the personal information we collect, how we use it, and the choices available for transactional SMS messages and the invite-only YouTube creator import.

Information We Collect

  • Account and contact information, such as name, organization, email address, and phone number.
  • When you choose Google or Meta sign-in, the provider account identifier, name, and email address returned for authentication. HiveSync does not receive or store your provider password.
  • Questions sent through the public contact form, including the name, email address, organization, role, topic, message, and HiveSync page supplied with the question.
  • Project information, including client requirements, contractor responses, status updates, completion evidence notes, attachments, and report review decisions.
  • Photos, videos, audio memos, signatures, and documents that you choose to capture or attach to field work, evidence, or project records.
  • Precise device location only when you choose the current-location action. HiveSync converts it to a job location or address and may store it with the project record.
  • SMS consent records, message preferences, delivery status, opt-out status, and support requests.
  • Security, app interaction, installation, device, integrity-verdict, and log data needed to operate the service, synchronize queued work, prevent misuse, and troubleshoot support issues.
  • Billing or plan information when a paid web feature is used. Payment card details are handled by payment processors, not stored by HiveSync.
  • With your separate YouTube consent, the connected channel identifier, name, and thumbnail; the selected owned video's identifier, title, and thumbnail; the read-only scope you granted; and an encrypted OAuth refresh credential.

How we use information

  • Provide the HiveSync app, web workspaces, client requirements and work agreement workflows, completion evidence records, and report review features.
  • Send opted-in transactional delivery notification SMS messages from HiveSync by Bizmonger Inc about delivered project requirements, contractor-accepted requirements, WRAP completion evidence, completion reports, client requirements and work agreement links, and delivery status changes.
  • Maintain security, audit history, support, troubleshooting, delivery reliability, and service analytics.
  • Reply to public questions, guide visitors to an appropriate product path, limit spam, and investigate misuse of the contact form.
  • Apply plan limits, account controls, and safety checks before private reports or completion evidence records are shared.
  • Synchronize account-backed jobs, evidence, media, handoffs, reports, and operational status when you use connected features.
  • Use YouTube API Services only to confirm that the connected channel controls one selected video. A private Blueprint is created only from the title and timestamped chapter notes the creator enters, and it still requires review.

Mobile Permissions, Local Work, and Sync

Core mobile field work can be used without signing in. Google or Meta sign-in is optional and is requested when you choose account-backed sync, TeamSync, community, or another protected feature. Local-only work remains on the device unless you choose or enable a connected action that sends it to HiveSync.

Camera, microphone, photo or video library, file, and precise-location access are requested only when you start the matching action. Media, audio, documents, and location that you choose to attach may be sent to HiveSync so the selected job, evidence, handoff, or report can synchronize. You can deny a permission and continue using unrelated parts of the app.

Information sent between the mobile app and HiveSync services is encrypted in transit using HTTPS/TLS. HiveSync does not use the Android advertising identifier and does not use mobile field data for third-party advertising.

YouTube API Services and Your Google Data

HiveSync uses YouTube API Services only after you select the unchecked consent box and complete Google's authorization screen. HiveSync requests the read-only youtube.readonly scope. It reads your owned channel identity and metadata for the exact video you choose only so the server can verify ownership. That API data is not copied into or used to derive Blueprint titles, chapters, tasks, branding, links, or other Blueprint content. HiveSync does not download or store the YouTube video or captions, post to YouTube, change YouTube content, or request YouTube write access.

When YouTube API metadata is shown in the creator import, it is displayed only to the authorizing account to confirm the selected channel and video. Blueprint content shown alongside it is entered by the creator and is part of HiveSync, not data from YouTube. Stored channel and video API metadata is refreshed or deleted as soon as it is no longer needed and no later than 30 calendar days after retrieval, even while consent remains active.

The encrypted refresh credential and API data are available only to the authorizing HiveSync account and the service providers needed to host, secure, and operate this workflow. We do not sell YouTube API data, share it with advertisers, use it for advertising, or use it for an undisclosed secondary purpose. Necessary authentication and security cookies may be stored in your browser to maintain your signed-in HiveSync session; they are not used to serve ads from YouTube data.

Your use of this integration is also subject to the YouTube Terms of Service and the Google Privacy Policy.

Disconnect, Revocation, and Deletion

Use Disconnect YouTube in the creator import to stop future checks and request revocation of HiveSync's provider access. HiveSync asks Google to revoke the token. Separately, HiveSync removes the stored credential and authorized YouTube API data. That credential and API data cleanup begins immediately; if a retry or support intervention is required, it will be completed as soon as possible and no later than 7 calendar days after the in-app revocation.

Blueprint cleanup is a separate HiveSync action. It deletes only account-owned ReviewRequired YouTube import drafts that remain in this invite-only pilot and preserves separately approved or converted Blueprint records. If Google revocation or server cleanup cannot be confirmed, cleanup remains pending and an operator must complete manual recovery in Google.

You can also revoke access from Google's security settings. HiveSync rechecks authorization when the connection is opened or used and removes API data after an invalid credential is detected. For an external Google revocation, contact support for immediate cleanup; related API data will be deleted as soon as possible and no later than 30 calendar days after revocation. This revocation deadline is separate from the recurring 30-day refresh-or-delete limit that applies while consent remains active.

You may request deletion of stored YouTube-related data at support@bizmonger.net. We complete a verified request as soon as possible and no later than 7 calendar days. Deleting HiveSync data does not delete or change your videos, channel, comments, or other content on YouTube; manage that content directly in YouTube.

SMS Privacy

HiveSync SMS is transactional. We do not send marketing or promotional text messages through the HiveSync by Bizmonger Inc Delivery Notification SMS program.

Mobile phone numbers, SMS consent records, and SMS opt-in data are not sold, rented, or shared with third parties or affiliates for marketing or promotional purposes. We may share SMS-related data with service providers, such as our messaging provider, only as needed to deliver, secure, support, and operate the transactional messaging service.

When information is shared

We may share information with service providers that help us host, secure, message, analyze, support, or operate HiveSync. We may also share information when required by law, to protect rights and safety, or as part of account-authorized project collaboration.

We do not sell personal information. We do not share mobile phone numbers or SMS consent data for third-party marketing.

Your Choices

You can opt out of SMS messages at any time by replying STOP. You can request help by replying HELP. You can also contact support to update contact details, request access, or ask for deletion where applicable.

For general product questions, use the Ask HiveSync form. Do not include passwords, payment card details, health records, or private client information.

Contact: support@bizmonger.net

Delete your HiveSync account

Use the canonical Delete my HiveSync account page and sign in with the Google or Meta identity connected to HiveSync. If self-service deletion is unavailable, contact support@bizmonger.net from the email address associated with the Google or Meta account you use to sign in. Never send your Google or Meta password or authentication token.

A verified full-account request deletes the active HiveSync account profile and account-linked project workspaces, workflow progress and sync state, uploaded evidence and media, team or community content, notification preferences, and other mobile or web app data controlled by HiveSync. You may use the same address to request deletion of specific account-linked data without deleting the entire account; identify the project, upload, community content, or other data you want removed.

After final confirmation, HiveSync disables account access immediately. Eligible account data is removed from active systems within 30 days, while recovery-only sign-in remains available. Encrypted backup copies age out within 90 additional days. Limited transaction, security, fraud-prevention, legal, and audit records may be retained longer when required by law or needed to resolve an active dispute. Those retained records are access-restricted and are not used to continue providing the deleted account.