Privacy Policy
This Privacy Policy describes how vertOS ("vertOS", "we", "us", or "our") collects, uses, stores, and protects personal and organizational data when you access or use vertos.app, tenant subdomains, field mobile applications, and connected third-party integrations including Google Workspace, Microsoft 365 / Entra ID, and Intuit QuickBooks Online.
Scope & Overview
vertOS is a multi-tenant vertical operating system purpose-built for commercial elevator, escalator, overhead door, and entrance automation service organizations. In operating the platform, vertOS acts as a Data Controller with respect to direct account registration, billing, and marketing interactions, and as a Data Processor / Service Provider with respect to customer records, work orders, CRM communications, and accounting data ingested on behalf of our subscribing tenant organizations.
Information We Collect
- Account & Identity Data: Name, business email address, phone number, job title, organization affiliation, role permissions, and authentication identifiers provided at registration or via Single Sign-On (Google OAuth or Microsoft Entra ID).
- Operational & Field Service Data: Work orders, dispatch schedules, equipment registries, ASME/safety inspection records, CPQ quotes, field photos, technician notes, and uploaded OEM parts catalogs.
- Connected Integration Data: When explicitly authorized by a user or tenant administrator, OAuth tokens and scoped records from Google Workspace (Gmail & Google Calendar), Microsoft 365 (Outlook Mail & Calendar), and Intuit QuickBooks Online (chart of accounts, invoices, bills, payments, customers, and vendors).
- Telemetry, Device & Cookie Data: IP address, browser user agent, session identifiers, CSRF tokens, and first-party diagnostic logs as detailed in our Cookie Policy.
How We Use Information
- To provision, authenticate, and enforce Row-Level Security (RLS) across multi-tenant workspaces.
- To execute core service workflows including work order dispatch, compliance reporting, quoting, and invoicing.
- To synchronize user-authorized CRM emails, calendar appointments, and accounting ledger transactions.
- To monitor system uptime, prevent unauthorized access, and deliver transactional security notices and support responses.
Google API Services & Limited Use Disclosure
vertOS's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4.1 Google OAuth Scopes & Data Accessed
Depending on the features you explicitly choose to enable in vertOS, we request only the minimum Google OAuth 2.0 scopes necessary:
- Google Sign-In (openid, email, profile): Used solely to authenticate your identity, verify your email address, and populate your user profile name and avatar.
- Gmail CRM Activity Sync (https://www.googleapis.com/auth/gmail.readonly or metadata/compose scopes when explicitly connected): Accessed only when you explicitly connect your Google account inside the vertOS CRM module. Used solely to match email thread headers, timestamps, participants, and message bodies with known CRM contacts and opportunities within your organization's workspace.
- Google Calendar Sync (https://www.googleapis.com/auth/calendar.readonly / calendar.events): Accessed only when explicitly connected by a user to synchronize customer site visits, inspection schedules, and CRM meeting timelines.
4.2 Strict Limited Use & Zero AI Training Commitments
- Never Sold or Transferred for Ads: vertOS never sells Google user data to third parties and never uses Google user data for targeted advertising, ad retargeting, creditworthiness determination, or data broker enrichment.
- Never Used to Train Generalized AI/ML Models: Raw data obtained from Google Workspace APIs (including Gmail messages and Google Calendar events) is never used to train, fine-tune, or improve generalized artificial intelligence or machine learning models.
- Human Access Restrictions: No vertOS employee or contractor may read your Google user data unless (a) we have obtained your affirmative agreement to view specific messages for a support ticket, (b) it is necessary for security threat investigation or abuse prevention, or (c) it is required to comply with applicable law.
- Encrypted Storage: OAuth access and refresh tokens are encrypted at rest using AES-256-GCM and managed via HashiCorp Vault and PostgreSQL Row-Level Security (RLS) scoped strictly to your tenant organization.
Microsoft Identity Platform & Microsoft Graph Data Handling
When you authenticate via Microsoft Entra ID (formerly Azure Active Directory) or connect Microsoft 365 (Outlook Mail and Calendar) via Microsoft Graph APIs:
- Scoped Consent: We access only the Microsoft Graph scopes you or your tenant administrator explicitly grant (such as User.Read, Mail.Read, and Calendars.ReadWrite).
- Purpose Limitation: Microsoft Graph data is used exclusively to provide Single Sign-On and to log customer-facing CRM emails and appointments inside your isolated tenant workspace.
- Zero Third-Party Resale & Zero Model Training: Microsoft user data is never sold, leased, shared with advertising networks, or used to train foundation AI models.
- Revocation & Token Purge: Disconnecting your Microsoft integration in Dashboard → Settings → Integrations or via myapps.microsoft.com immediately revokes active tokens and stops background synchronization.
Intuit QuickBooks Online Financial Data
Organizations that connect Intuit QuickBooks Online authorize vertOS to exchange accounting records (chart of accounts, customers, vendors, invoices, bills, payments, and journal entries) via Intuit OAuth 2.0 APIs. QuickBooks credentials and Change Data Capture (CDC) payloads are isolated per tenant, encrypted in transit (TLS 1.3) and at rest, and governed by both this Privacy Policy and our End-User License Agreement (EULA).
Security, Encryption & Multi-Tenant Isolation
- Database Row-Level Security (RLS): Every tenant record in PostgreSQL is isolated at the database engine layer using cryptographic session context (app.current_organization_id).
- Encryption: All data in transit is encrypted via HTTPS/TLS 1.2+ (TLS 1.3 preferred). All persistent volumes, database backups, and OAuth secrets in HashiCorp Vault are encrypted at rest using AES-256.
- Session Security: Authentication relies on Better-Auth HttpOnly, Secure, SameSite=Lax cookies—never exposing raw session tokens to client-side JavaScript.
Data Sharing & Subprocessors
We do not sell personal information. We share data only with vetted infrastructure subprocessors bound by written Data Processing Addenda (DPAs) and strict confidentiality obligations (such as Google Cloud Platform for Kubernetes hosting and storage, Stripe for subscription billing, and Twilio for authorized voice/SMS dispatch), or when compelled by valid legal process.
Data Retention, Revocation & Deletion
We retain operational data for the duration of your organization's active subscription unless earlier deletion is requested.
- Revoking Google Access: You may disconnect Google Workspace at any time inside vertOS or revoke access directly at https://myaccount.google.com/permissions.
- Revoking Microsoft Access: You may disconnect Microsoft 365 inside vertOS or revoke access at https://myapps.microsoft.com.
- Account & Data Deletion Requests: You may request permanent deletion of your user account, connected OAuth tokens, and synced integration records by emailing privacy@vertos.app or support@vertos.app. Verified deletion requests are completed within 30 days (with OAuth token revocation executed immediately).
Your Privacy Rights (CCPA / CPRA / GDPR / UK GDPR)
Depending on your jurisdiction, you have the right to request access to, correction of, portability of, or erasure of your personal data, as well as the right to object to or restrict certain processing. California residents are further protected under the CCPA/CPRA: vertOS does not "sell" or "share" personal information for cross-context behavioral advertising.
Contact & Data Protection Inquiries
For privacy inquiries, Data Subject Access Requests (DSARs), OAuth data deletion requests, or security questions, contact our Privacy & Compliance team: