LiftQuote ESESS
Sign in

Privacy Policy

Last updated: September 28, 2026

1. Scope

This policy explains how LiftQuote-ESESS handles personal information in account administration and in the business records processed through the Service. If your employer or service provider gave you access, that organization controls which customer and worker records it uploads and how it uses them. Direct requests about those records to that organization first; you may also contact our support team for help routing a request.

2. Information we collect

We process account and contact details; customer and worker records; jobs, quotes, invoices, equipment and inspection records; time and payroll information entered by your organization; uploaded files, photographs and signatures; support messages and AI conversations; and technical information such as IP addresses, request logs and error diagnostics. Stripe handles checkout payment details; the application stores subscription and payment-status references rather than your full payment-card number. When you enable technician location sharing and grant browser permission, location coordinates are sent while the technician dashboard is active and the technician is on shift, for authorized dispatch users to view. You can turn sharing off in the application or revoke browser location permission.

3. How we use it

To provide and secure the Service, process billing, send transactional email and notifications you enable, provide support, and improve the product. We do not sell personal information.

4. Sub-processors

We rely on trusted providers to operate the Service. Each processes data only as needed to deliver its function:

  • Vercel & Amazon Web Services — application hosting, API compute and the PostgreSQL database.
  • Stripe — payment and subscription processing.
  • Resend — transactional email delivery.
  • Anthropic or OpenAI — powers Otto, the AI copilot. The questions you ask, the prior turns of that conversation, and the operational records Otto looks up to answer them are sent to whichever provider your deployment is configured to use. Your administrator can confirm which one; ask us and we will tell you in writing. Provider processing, retention and any model-training permissions depend on the applicable provider agreement and account settings. We do not promise zero provider retention. Avoid submitting information you are not authorized to share through an AI feature.
  • Google (Web Speech API) — voice input in Otto uses your browser’s speech-recognition implementation, which may send audio to a browser-provider service such as Google for transcription. This applies only while you actively hold or toggle the microphone. See the voice-input note below.
  • Sentry — error monitoring and diagnostics.
  • Mapping & geocoding provider — Google Maps renders technician and route maps when a key is configured, and OpenStreetMap tiles (or CARTO's OpenStreetMap-based tiles, when the OpenStreetMap server refuses one) are used otherwise; map tiles are requested by your browser from that provider. To place customers and equipment on a map we also send their addresses (not names or contact details) to a geocoding service — Google when you have configured a Maps key, otherwise OpenStreetMap’s Nominatim. Results are cached to reduce repeated requests; an address may be sent again when it changes or a cached result is unavailable.
  • SMS & telematics providers — only where you explicitly enable those integrations.

5. Voice input

Voice commands in Otto use your browser’s built-in Web Speech API. In Chrome and some other browsers this API works by sending the captured audio to Google for transcription; the resulting text is then handled like any typed command. Voice input is optional — the microphone only activates when you turn it on, and every feature is fully usable by typing. If you prefer not to send audio to Google, do not use the microphone.

6. Tenant isolation & security

Data is logically isolated per tenant. We enforce role-based access controls, encrypt data in transit (HTTPS), and hash credentials. No method is perfectly secure, but we work to protect your data.

7. Data retention

Retention depends on the record’s purpose: company operational records support your ongoing account; billing, security and audit records may be needed for accounting, fraud prevention, legal obligations or disputes. Billing cancellation does not automatically erase company data. Contact support to request an export or deletion and identify the company and records concerned. We verify identity and authority before releasing or deleting records, and explain any applicable retention exceptions. Deleted information may remain in backups until those backups rotate out; backups are not a permanent archive. Browser drafts and cached records are separate copies on your device.

8. Your rights

Depending on the laws that apply to you, you may have rights to access, correct, delete or obtain a copy of your information, or object to or restrict particular uses. Send requests to support@liftquote-esess.com. We may need to verify your identity or refer an employment or customer-record request to the organization responsible for it. Where applicable, you may also complain to your data-protection regulator. Do not email passwords, full payment-card details or identity documents unless we arrange an appropriate verification method.

9. Contact

For privacy questions, email support@liftquote-esess.com.

This document is a general template provided for transparency and should be reviewed by your legal counsel before you rely on it. Questions: support@liftquote-esess.com.

Terms · Privacy · Cookies