Back to HVAC OpsHub

Privacy Notice

Draft for review · November 11, 2026

1. Who this notice is for

This notice is prepared for the HVAC OpsHub app owner and describes the service’s current information flows. The operator is Logan M Taylor, reachable at hvacopshub@gmail.com; the business location must be added before launch. Subscribing companies are responsible for informing their workers and customers about the information they enter.

2. Information provided through the service

The service handles account emails and sign-in credentials, display names, company names, join codes and requests, team roles, time punches and breaks, timesheets, corrections, hourly rates and payroll reports. It also handles truck details and maintenance dates, stock and restock records, equipment identifiers and photos, warranty information, quotes, prices and optional customer phone numbers, addresses and emails.

Subscription information includes the company’s chosen plan, trial and subscription dates, status, customer and transaction references, and invoices. Operational notifications and audit records record activity such as submitted requests and changes to business records.

3. How information is used and shared

Information is used to provide company workspaces, sign-in, team approval, time and payroll calculations, inventory, quotes, warranty records, subscription management and troubleshooting. Company members see records according to their approved roles; company owners and managers have office functions. The app-owner billing dashboard shows company signup and subscription information and payment records.

Lovable Cloud provides the service’s hosting, authentication, record storage and photo storage. Google and Lovable receive information needed for their sign-in processes when you choose those sign-in options. Paddle receives checkout and billing information to process payments, manage subscriptions and provide invoices. The app receives payment references and subscription updates. Review each provider’s privacy terms when using its services.

4. Browser storage and other services

Sign-in session information is stored in your browser’s local storage so you can remain signed in. Temporary session storage records page-recovery attempts to avoid repeated reloads. These are distinct from visitor analytics. Signing out clears the app’s authentication session; your browser controls also allow you to clear local website storage.

The site loads its fonts from Google Fonts, which receives the network request and connection information needed to serve those fonts. Paddle’s checkout loads when you start a purchase; checkout and its customer portal may use their own storage or cookies under Paddle’s policies. OAuth sign-in similarly takes you through the selected provider’s processes.

5. Visitor analytics on the published website

Page visits and link/button clicks are recorded for every visitor on the published site; there is currently no consent banner connected to analytics. The editor preview is not counted. Analytics records pages visited, where visitors came from, country, browser, operating system, device type, time spent, page-loading speed and errors. Clicks are identified by their position, not their text.

Lovable’s visitor analytics uses no cookies, stores nothing on the visitor’s device, does not keep IP addresses and does not identify visitors. Page visits, time on page, page speed and errors are recorded without cookies and without identifying anyone. The app also reports page and loading errors; no additional custom business events are currently sent.

Detailed analytics data is kept for 90 days; daily summaries are kept for a year. Lovable collects this data for us. Lovable’s privacy policy explains how it handles it. The analytics storage description does not mean that sign-in, company records or payment services store nothing.

6. Retention, requests and cancellation

Subscription cancellation stops renewals; it does not automatically delete accounts or company records. A company-record retention period, deletion process and backup-retention schedule have not yet been established for this notice. The operator must confirm these before launch; analytics retention above is separate.

Workers should contact their company owner about corrections to company records. A privacy contact for account access, correction or deletion requests must be supplied before launch. Applicable privacy rights and exceptions depend on location; this draft does not establish a response-time promise.

7. Before publication

The operator must review provider arrangements, applicable legal grounds, international transfers, privacy-request handling and retention commitments with an adviser familiar with the locations served. This draft makes no certification or regulatory-compliance claim. Material changes to the final notice should be dated and communicated as required.