Skip to Content

Privacy Policy

Last updated: September 16, 2026

Boundary Waters Construction ("BWC," "we," "our") is a DBA of InvigorIT Corp, a Minnesota corporation. This Privacy Policy explains what information we collect through our website and through the Boundary Waters Construction Personal Assistant application (the "Application"), how we use, store, share, and delete it, and how you can revoke access.

The Application

The Boundary Waters Construction Personal Assistant is an internal business tool. It is used exclusively by Boundary Waters Construction personnel (owners and admin staff) operating on their own Google Workspace accounts on the bwcmn.com domain. It is not distributed to customers, vendors, or the general public. Its purpose is to help BWC personnel manage their own email correspondence, calendar scheduling, and routine administrative work related to the operation of Boundary Waters Construction.

What Google user data the Application accesses

The Application uses OAuth 2.0 to request access to a specific set of Google API scopes on the authorizing user's own account. Access is granted only after the account holder signs in and explicitly authorizes each scope on Google's consent screen. The exact scopes requested and the features they support are listed below.

Gmail scopes

1. https://www.googleapis.com/auth/gmail.modify

What it permits: reading messages, threads, drafts, labels, and metadata in the authorized user's Gmail account; composing and sending mail as the authorized user; creating and modifying drafts; and applying, creating, or removing labels on messages the user owns. It does not allow permanent account deletion.

Why the Application needs it: to read business email so the user can ask the Application to summarize, search, draft, and send replies from within their assistant workflow. Without this scope the Application cannot function as an email assistant.

2. https://www.googleapis.com/auth/gmail.settings.basic

What it permits: reading and modifying the user's basic Gmail settings, including labels, filters, forwarding addresses, and vacation responder.

Why the Application needs it: to let the user manage labels and filters (for example, adding a "BWC Jobs" label, or creating a filter for a specific client) through the assistant rather than by opening Gmail's settings screen.

Calendar scope

3. https://www.googleapis.com/auth/calendar

What it permits: reading, creating, updating, and deleting events on the authorized user's Google Calendar, and reading calendar metadata (calendar list, sharing settings).

Why the Application needs it: to answer scheduling questions ("what's on my calendar Tuesday"), create events based on user requests ("add a site walk with Dan Carlson Thursday at 10"), and update or cancel events the user already owns.

How the Application uses Google user data

The Application uses Google user data exclusively to provide the specific personal-assistant features the authorized user has requested in real time. Concretely, when the user asks the Application to do something (for example, "summarize my inbox," "reply to that email from Jimmy," "book a meeting Tuesday"), the Application:

  1. Calls the relevant Google API with the user's OAuth token to fetch or write the specific data needed to fulfill the request.
  2. Sends only the fetched data (plus the user's instruction) to the Application's underlying processing service provider for that one instruction (see "Third-party service providers" below).
  3. Returns the result to the user in their assistant interface.

We do not use Google user data for any of the following purposes:

  • To serve targeted or personalized advertising.
  • To sell, rent, or transfer to data brokers or other information resellers.
  • To train, develop, improve, or fine-tune generalized machine models. We do not permit any service provider used by the Application to train models on Google user data.
  • To make credit determinations or lending decisions.
  • To build databases unrelated to providing the personal-assistant features the authorized user requested.

Third-party service providers

The Application relies on the following service providers to interpret user instructions and produce responses. When the user issues an instruction that requires reading or writing Google user data, the specific data fetched from Google is sent to one of these providers for the sole purpose of processing that one instruction:

Data sent to these providers is limited to what is needed for the specific requested instruction. It is not retained by the Application beyond the immediate response and is not sent to any provider not listed above without a further update to this policy.

How we share Google user data

Beyond the service providers named above, we do not sell, rent, or trade Google user data. We may disclose it only:

  • When required by law, subpoena, or valid legal process.
  • With the explicit consent of the account holder.

How we protect Google user data

  • All Google API traffic uses HTTPS/TLS in transit.
  • OAuth 2.0 access and refresh tokens are stored on the authorized user's own workstation, in a directory readable only by that user's operating-system account. We do not centralize tokens on a company server.
  • Access to the Application is limited to authorized BWC personnel on a need-to-know basis.
  • Application access is promptly revoked when a person leaves BWC or no longer needs the Application. Revocation is performed both in Google (per the section below) and by deleting the local token file.
  • The scopes requested by the Application are reviewed periodically and reduced when a scope is no longer needed for a feature.

How long we keep Google user data

The Application does not maintain a persistent secondary copy of Google user data outside of Google's own services. Data fetched from Google to satisfy a user instruction is held in memory only for the duration of that instruction and its response, and is then discarded. OAuth tokens are retained until the user revokes access or leaves BWC, at which point they are deleted from local storage.

Data collected through our website's contact form is retained while the customer relationship is active plus seven years for Minnesota business records requirements, and is then deleted.

How to revoke access or request deletion

To revoke the Application's access to your Google account at any time:

  1. Visit https://myaccount.google.com/permissions
  2. Find "Boundary Waters Construction Personal Assistant" in the list.
  3. Select Remove access.

Because we do not store a persistent copy of Google user data, no further action is needed to delete Google user data from our systems. To request deletion of any other information we hold about you (such as a contact-form submission), email privacy@bwcmn.com with the subject line "Privacy Deletion Request." We will respond within 30 days.

Website visitors

Separate from the Application, our website (bwcmn.com) collects the following:

  • Cookies used to personalize navigation and to help us understand how the site is used (via Google Analytics).
  • Contact form submissions containing information you provide when you request an estimate: name, email, phone, project address, and project details.

We use this only to respond to your inquiry, prepare an estimate, schedule work, communicate with you about your project, and improve the site's usability. Website contact-form submissions are never sent to the service providers listed above.

Links to other websites

Our website may contain links to third-party sites. We are not responsible for the content or privacy practices of those sites. Please review the privacy policy of each site you visit.

Contact

Questions about this Privacy Policy or about the Application:

Boundary Waters Construction (InvigorIT Corp)
Attn: Privacy
privacy@bwcmn.com
(651) 592-3111
Minnesota, USA

Changes to this policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page reflects the most recent change. Material changes will be communicated on our website. Any addition of a new OAuth scope or a new third-party service provider will be reflected here before the change is deployed to the Application.