Privacy notice

Who operates BlueTac

BlueTac Management LLC provides BlueTac. Contact accounts@BlueTac.com for privacy questions and requests. This notice covers the BlueTac website and web app. The public demo uses fictional records; actions in that demo do not send invitations, payments or report uploads. Business mailing address: BlueTac Management LLC, 2810 N Church St, PMB 881576, Wilmington, DE 19802, United States.

Information used to provide the service

Account information includes names, verified email addresses, roles, company membership, invitations, availability and qualifications. Companies may provide sites, shifts, pay rates, time and break records, gear records, employment documents, termination records, reports, photos and videos. We also process subscription selections, consent records, usage quantities, payment-provider identifiers, limited card details such as the last four digits and expiry, notification delivery results and security records. Stripe collects full payment-card information; BlueTac does not ask you to enter full card numbers into its own forms.

BlueTac uses this information for company operations, scheduling, eligibility checks, notifications, timekeeping, reports, authorized document retrieval, billing, customer support and security. Your employer or service provider controls its workplace records, account permissions and operational settings. BlueTac processes those company records to provide the contracted service and handles its own account, billing and security administration.

Clock-in location and attendance review

A company can require a current browser location reading when a guard clocks in at a configured site. The guard must grant browser permission. BlueTac checks the reported coordinates, accuracy and timestamp against that site's permitted clock-in area. This feature requests one reading at clock-in and does not start ongoing location tracking. The public demo uses fictional coordinates and never requests your real location. Browser location may be inaccurate or spoofed; a successful area check is not proof of physical attendance.

The reading is available only to the employee and authorized management within that company. It is excluded from client portals, payroll CSV exports, routine notifications and Blue's automatic AI context. Raw device coordinates are removed from active clock records by scheduled maintenance after 30 days; the time record and the location-check outcome remain. Restricted disaster-recovery copies can retain prior versions until their recovery retention expires. If location fails, the employee must contact company management to record actual worked time or correct a missed punch; a technical clock-in failure does not erase actual work or waive wages.

Call-out records can include assignment acknowledgement, notice time, ordinary attendance points and audited management corrections. Guards can request company review of an urgent absence or rating. Protected or company-excused records are excluded from the ordinary point calculation and self-service allowance. BlueTac does not deduct pay or automatically make employment decisions from these records. Do not enter medical details in operational review notes; arrange any necessary sensitive documentation through the company's appropriate private process.

Guards or company managers may provide a usual base ZIP code, and companies may provide site ZIP codes, for approximate travel-distance and city-area staffing estimates. BlueTac resolves these using a locally stored public postal reference; individual ZIP lookups are not sent to an outside geocoding provider. A postal centroid is not a street address, actual current location, road route or traffic estimate. Guard base areas are visible to the employee and company management and are excluded from client portals. Base-area collection does not start continuous tracking. Company managers can view employee rankings based on recorded work, ordinary assessed call-outs, approved arrivals, client reviews, performance points and observed offer acceptance counts. Sparse history is labelled, source counts are shown, protected/excused outcomes are excluded from the relevant measures, and missing offer history is not invented. Rankings are decision-support summaries, not proof of future availability or automatic employment decisions.

The company Map view shows guard base ZIP areas, company-entered site coordinates and office records to authorized management. Base-area markers are approximate and do not represent continuous or current guard tracking. When a map is viewed, the browser requests background tiles for its visible geographic area from OpenStreetMap; that provider receives the viewer's IP address, browser information, referring origin and requested map tiles. BlueTac does not send employee names, company labels or report contents with tile requests. Company office records are excluded from guard and client portals. Optional Google Maps navigation links send the selected destination to Google only when clicked; Google controls its own location permission and navigation services.

Assigned patrol guards provide a fresh device location reading when checking in and checking out at each client stop. BlueTac checks location freshness, accuracy and proximity to the company-entered site point, records server timestamps and shows exceptions to authorized company management. Route requirements are saved with assignments; submitted reports and media are retained separately. Guard access is restricted to their assigned patrols and own visit evidence; client accounts cannot open company patrol routes or device GPS history. Corrections preserve an audit reason and never fabricate GPS evidence. Raw patrol device coordinates, including original device readings retained after a correction, are hidden immediately after 30 days and removed by bounded scheduled maintenance; visit times and correction records remain. This feature does not start continuous location tracking, prove physical attendance or automatically determine pay or employment.

Company sales records

Company owners and authorized administrators can keep prospect companies, business contacts, opportunities, follow-ups, notes, contract-pricing assumptions, dated wage-listing observations, quote versions and sales documents in their private CRM. Employees and client accounts cannot access this section. These records and attachments use the organization’s storage allowance, including archived records retained for recovery. CRM data and its private document attachments are stored in Cloudflare’s database; the separate report and employment-document workflows may store originals in the dedicated private Google Drive.

BlueTac does not automatically contact prospects from the CRM. Job-listing observations are supplied by company management and are not independently verified. Displayed competitor multipliers are planning assumptions, not obtained competitor quotes. Private sales documents and CRM notes are not automatically included in Blue’s AI context.

Company and employee access

A user may access only information allowed by that user's organization, role and site permissions. Private employment documents require the appropriate employment-record access. A client account does not receive another client's sites, private employee documents or company billing information. The company's authorized administrators can access its workplace records and manage its accounts. Contact that company first about workplace-record corrections or employment decisions; contact BlueTac if you need help identifying the appropriate request route.

Google Drive and other service providers

BlueTac's private server connection uses the dedicated storage account and Google's drive.file permission for files the app creates or the operator selects for it. It does not request unrestricted access to every file in a Google account. The operator authorizes the designated private BlueTac folder. Report originals, report archives, employee qualification files and authorized employment-document originals may be created and retrieved there. Company folders are separated by organization; customer access is provided through authenticated BlueTac routes rather than shared Drive access. Disconnecting authorization stops future Google API operations; it does not itself delete existing records.

Configured providers include Cloudflare for hosting, database and app storage, Google Drive for document storage and report archives, Brevo for transactional email and Stripe for payment services. When AI features are configured, limited work-task context or submitted report evidence needed for that feature may be sent to the configured AI provider: Cloudflare Workers AI for Blue, issue triage and supported report-photo comparisons, or OpenAI when separately configured. Report-photo comparisons use only the submitted company evidence selected for comparison; they do not identify people or decide employee honesty, misconduct or employment suitability. Blue's automatic workspace context contains limited company scheduling identifiers and names and excludes employee pay, private contact details, employment files and report contents. Text entered in a work request is also sent to the selected provider. Private employment-document files are excluded from Blue's work-assistant context. Features awaiting configuration are not active merely because they appear in a demo.

Google API data is used only to provide the disclosed BlueTac features, maintain security and meet legal obligations. It is not sold, used for advertising or lending decisions, or used to train generalized AI models. Human access to Google API data is limited to specifically authorized support, necessary security or legal purposes and other access permitted by Google's applicable user-data policies.

Public demo AI and usage limits

The public demo uses fictional records. Supported demo work requests are processed by Cloudflare Workers AI using a bounded projection of the demo schedule with synthetic employee and site aliases. Local tours, scope checks and date clarification can run without AI. Do not enter real employee information, private documents, credentials or personal details into the public demo. AI plans can change only the fictional workspace in that browser; they cannot access customer organizations or send real invitations, report uploads, messages or payments.

An essential signed cookie identifies a 30-minute demo AI session with up to ten requests. We also apply network-address and daily service limits to prevent abuse. BlueTac retains only purpose-bound cryptographic identifiers, attempt counts, expiry times and request/input hashes for these anonymous limits; the demo endpoint does not save prompts or transcripts in BlueTac's database. Failed AI attempts may count toward the allowance. The app's manual demo controls remain available when AI usage is exhausted.

Retention, security and your choices

Retention depends on the record category, company instructions, contract and applicable obligations. BlueTac's employment-document workflow uses a default seven-year retention calculation with category-specific date anchors, holds and extensions. Termination does not immediately delete documents. Employers must choose appropriate retention settings and preserve records they are required to keep. Retained files continue to count toward company storage. Deletion may be delayed by a hold, a dispute, a required retention period or a recovery process; revoking Drive access does not erase files.

We use authenticated access, organization and role checks, encrypted transport and protected provider credentials. No system can promise that every security incident or data loss is impossible. Only provide documents and permissions needed for your company's work, and protect your sign-in email account.

Depending on the law that applies to you, you may have rights to access, correct, export, delete or restrict use of personal information and to appeal a denied request. Send requests to accounts@BlueTac.com; we will verify identity and authority, coordinate with the company responsible for workplace records and apply required exceptions and response periods. We do not sell personal information or share it for cross-context behavioral advertising. Lending and affiliate offers are not enabled in this release.

Browser storage, age and changes

BlueTac uses essential sign-in cookies and browser storage for authentication, security and application preferences. The demo can store its fictional setup in the browser until reset or cleared. The service is intended for adult business users and is not directed to children under 13. Providers may process information in countries where they operate; additional arrangements may be needed before serving a jurisdiction with specific transfer requirements.

This page identifies its notice version. Material changes to data practices will be disclosed before the changed processing begins, with renewed permission where required. Annual price notices are a separate billing process.

Email campaign attribution

We use a first-party, secure browser cookie lasting up to 90 days to connect a first website visit, demo start and later verified company signup. We record the four UTM link labels (source, medium, campaign and content) and the server time first seen. When a new identity verifies its email, those labels become a one-time extension of its account record; later logins do not rewrite them. Do Not Track and Global Privacy Control signals disable this collection. Browser counts are not proof of unique people, and the public demo still uses fictional business records.

Private marketing analytics combine aggregate demo, signup, activated-trial and reconciled-payment counts with campaign and sending-inbox statistics read from Instantly. These views do not read customer business documents or email contents and do not change campaigns or send messages. Only authorized BlueTac administration and holders of a separately issued read-only analytics token can access the marketing report. A daily rotating keyed network identifier limits tracking abuse without retaining the raw network address in this analytics data.

AI credits and payment reconciliation

BlueTac keeps company-scoped AI usage and payment audit records: source, request and receipt identifiers, frozen usage rates, measured token quantities, pending reservations, billing month, included and purchased credit balances, separately accepted overage terms, reviewed pack orders, payment verification and refunds or disputes. Supplier receipts are restricted server-side; customer billing views show normalized credits and retail amounts. Unknown outcomes retain their reservation until reconciliation and do not create a guessed charge. These records support exact billing, recovery, support and fraud prevention; they do not grant another company access to your work.

The prospective monthly offer does not yet provide automatic visual comparison of company report evidence. Permitted originals and exact-file duplicate checks remain available. A list of a provider or future integration in this notice does not activate an unavailable feature. Existing signed agreements and processing choices are retained; changed customer charges require the appropriate separate authorization.

Who operates BlueTac

BlueTac Management LLC provides BlueTac. Contact accounts@BlueTac.com for privacy questions and requests. This notice covers the BlueTac website and web app. The public demo uses fictional records; actions in that demo do not send invitations, payments or report uploads. Business mailing address: BlueTac Management LLC, 2810 N Church St, PMB 881576, Wilmington, DE 19802, United States.

Information used to provide the service

Account information includes names, verified email addresses, roles, company membership, invitations, availability and qualifications. Companies may provide sites, shifts, pay rates, time and break records, gear records, employment documents, termination records, reports, photos and videos. We also process subscription selections, consent records, usage quantities, payment-provider identifiers, limited card details such as the last four digits and expiry, notification delivery results and security records. Stripe collects full payment-card information; BlueTac does not ask you to enter full card numbers into its own forms.

BlueTac uses this information for company operations, scheduling, eligibility checks, notifications, timekeeping, reports, authorized document retrieval, billing, customer support and security. Your employer or security provider controls its workplace records, account permissions and operational settings. BlueTac processes those company records to provide the contracted service and handles its own account, billing and security administration.

Clock-in location and attendance review

A company can require a current browser location reading when a guard clocks in at a configured site. The guard must grant browser permission. BlueTac checks the reported coordinates, accuracy and timestamp against that site's permitted clock-in area. This feature requests one reading at clock-in and does not start ongoing location tracking. The public demo uses fictional coordinates and never requests your real location. Browser location may be inaccurate or spoofed; a successful area check is not proof of physical attendance.

The reading is available only to the guard and authorized management within that company. It is excluded from client portals, payroll CSV exports, routine notifications and Blue's automatic AI context. Raw device coordinates are removed from active clock records by scheduled maintenance after 30 days; the time record and the location-check outcome remain. Restricted disaster-recovery copies can retain prior versions until their recovery retention expires. If location fails, the guard must contact company management to record actual worked time or correct a missed punch; a technical clock-in failure does not erase actual work or waive wages.

Call-out records can include assignment acknowledgement, notice time, ordinary attendance points and audited management corrections. Guards can request company review of an urgent absence or rating. Protected or company-excused records are excluded from the ordinary point calculation and self-service allowance. BlueTac does not deduct pay or automatically make employment decisions from these records. Do not enter medical details in operational review notes; arrange any necessary sensitive documentation through the company's appropriate private process.

Guards or company managers may provide a usual base ZIP code, and companies may provide site ZIP codes, for approximate travel-distance and city-area staffing estimates. BlueTac resolves these using a locally stored public postal reference; individual ZIP lookups are not sent to an outside geocoding provider. A postal centroid is not a street address, actual current location, road route or traffic estimate. Guard base areas are visible to the guard and company management and are excluded from client portals. Base-area collection does not start continuous tracking. Company managers can view employee rankings based on recorded work, ordinary assessed call-outs, approved arrivals, client reviews, performance points and observed offer acceptance counts. Sparse history is labelled, source counts are shown, protected/excused outcomes are excluded from the relevant measures, and missing offer history is not invented. Rankings are decision-support summaries, not proof of future availability or automatic employment decisions.

The company Map view shows guard base ZIP areas, company-entered site coordinates and office records to authorized management. Base-area markers are approximate and do not represent continuous or current guard tracking. When a map is viewed, the browser requests background tiles for its visible geographic area from OpenStreetMap; that provider receives the viewer's IP address, browser information, referring origin and requested map tiles. BlueTac does not send employee names, company labels or report contents with tile requests. Company office records are excluded from guard and client portals. Optional Google Maps navigation links send the selected destination to Google only when clicked; Google controls its own location permission and navigation services.

Assigned patrol guards provide a fresh device location reading when checking in and checking out at each client stop. BlueTac checks location freshness, accuracy and proximity to the company-entered site point, records server timestamps and shows exceptions to authorized company management. Route requirements are saved with assignments; submitted reports and media are retained separately. Guard access is restricted to their assigned patrols and own visit evidence; client accounts cannot open company patrol routes or device GPS history. Corrections preserve an audit reason and never fabricate GPS evidence. Raw patrol device coordinates, including original device readings retained after a correction, are hidden immediately after 30 days and removed by bounded scheduled maintenance; visit times and correction records remain. This feature does not start continuous location tracking, prove physical attendance or automatically determine pay or employment.

Company sales records

Company owners and authorized administrators can keep prospect companies, business contacts, opportunities, follow-ups, notes, contract-pricing assumptions, dated wage-listing observations, quote versions and sales documents in their private CRM. Guards and client accounts cannot access this section. These records and attachments use the organization’s storage allowance, including archived records retained for recovery. CRM data and its private document attachments are stored in Cloudflare’s database; the separate report and employment-document workflows may store originals in the dedicated private Google Drive.

BlueTac does not automatically contact prospects from the CRM. Job-listing observations are supplied by company management and are not independently verified. Displayed competitor multipliers are planning assumptions, not obtained competitor quotes. Private sales documents and CRM notes are not automatically included in Blue’s AI context.

Company and employee access

A user may access only information allowed by that user's organization, role and site permissions. Private employment documents require the appropriate employment-record access. A client account does not receive another client's sites, private employee documents or company billing information. The company's authorized administrators can access its workplace records and manage its accounts. Contact that company first about workplace-record corrections or employment decisions; contact BlueTac if you need help identifying the appropriate request route.

Google Drive and other service providers

BlueTac's private server connection uses the dedicated storage account and Google's drive.file permission for files the app creates or the operator selects for it. It does not request unrestricted access to every file in a Google account. The operator authorizes the designated private BlueTac folder. Report originals, report archives, guard credential files and authorized employment-document originals may be created and retrieved there. Company folders are separated by organization; customer access is provided through authenticated BlueTac routes rather than shared Drive access. Disconnecting authorization stops future Google API operations; it does not itself delete existing records.

Configured providers include Cloudflare for hosting, database and app storage, Google Drive for document storage and report archives, Brevo for transactional email and Stripe for payment services. When AI features are configured, limited work-task context or submitted report evidence needed for that feature may be sent to the configured AI provider: Cloudflare Workers AI for Blue, issue triage and supported report-photo comparisons, or OpenAI when separately configured. Report-photo comparisons use only the submitted company evidence selected for comparison; they do not identify people or decide employee honesty, misconduct or employment suitability. Blue's automatic workspace context contains limited company scheduling identifiers and names and excludes employee pay, private contact details, employment files and report contents. Text entered in a work request is also sent to the selected provider. Private employment-document files are excluded from Blue's work-assistant context. Features awaiting configuration are not active merely because they appear in a demo.

Google API data is used only to provide the disclosed BlueTac features, maintain security and meet legal obligations. It is not sold, used for advertising or lending decisions, or used to train generalized AI models. Human access to Google API data is limited to specifically authorized support, necessary security or legal purposes and other access permitted by Google's applicable user-data policies.

Public demo AI and usage limits

The public demo uses fictional records. Supported demo work requests are processed by Cloudflare Workers AI using a bounded projection of the demo schedule with synthetic employee and site aliases. Local tours, scope checks and date clarification can run without AI. Do not enter real employee information, private documents, credentials or personal details into the public demo. AI plans can change only the fictional workspace in that browser; they cannot access customer organizations or send real invitations, report uploads, messages or payments.

An essential signed cookie identifies a 30-minute demo AI session with up to ten requests. We also apply network-address and daily service limits to prevent abuse. BlueTac retains only purpose-bound cryptographic identifiers, attempt counts, expiry times and request/input hashes for these anonymous limits; the demo endpoint does not save prompts or transcripts in BlueTac's database. Failed AI attempts may count toward the allowance. The app's manual demo controls remain available when AI usage is exhausted.

Retention, security and your choices

Retention depends on the record category, company instructions, contract and applicable obligations. BlueTac's employment-document workflow uses a default seven-year retention calculation with category-specific date anchors, holds and extensions. Termination does not immediately delete documents. Employers must choose appropriate retention settings and preserve records they are required to keep. Retained files continue to count toward company storage. Deletion may be delayed by a hold, a dispute, a required retention period or a recovery process; revoking Drive access does not erase files.

We use authenticated access, organization and role checks, encrypted transport and protected provider credentials. No system can promise that every security incident or data loss is impossible. Only provide documents and permissions needed for your company's work, and protect your sign-in email account.

Depending on the law that applies to you, you may have rights to access, correct, export, delete or restrict use of personal information and to appeal a denied request. Send requests to accounts@BlueTac.com; we will verify identity and authority, coordinate with the company responsible for workplace records and apply required exceptions and response periods. We do not sell personal information or share it for cross-context behavioral advertising. Lending and affiliate offers are not enabled in this release.

Browser storage, age and changes

BlueTac uses essential sign-in cookies and browser storage for authentication, security and application preferences. The demo can store its fictional setup in the browser until reset or cleared. The service is intended for adult business users and is not directed to children under 13. Providers may process information in countries where they operate; additional arrangements may be needed before serving a jurisdiction with specific transfer requirements.

This page identifies its notice version. Material changes to data practices will be disclosed before the changed processing begins, with renewed permission where required. Annual price notices are a separate billing process.

Email campaign attribution

We use a first-party, secure browser cookie lasting up to 90 days to connect a first website visit, demo start and later verified company signup. We record the four UTM link labels (source, medium, campaign and content) and the server time first seen. When a new identity verifies its email, those labels become a one-time extension of its account record; later logins do not rewrite them. Do Not Track and Global Privacy Control signals disable this collection. Browser counts are not proof of unique people, and the public demo still uses fictional business records.

Private marketing analytics combine aggregate demo, signup, activated-trial and reconciled-payment counts with campaign and sending-inbox statistics read from Instantly. These views do not read customer business documents or email contents and do not change campaigns or send messages. Only authorized BlueTac administration and holders of a separately issued read-only analytics token can access the marketing report. A daily rotating keyed network identifier limits tracking abuse without retaining the raw network address in this analytics data.