Legal
Privacy Policy
Last updated May 17, 2026
Who we are
LOV3 Comfort is an internal staff tool operated by Maurice Ragland on behalf of LOV3 Houston, a restaurant and bar located in Houston, Texas. The application is used by restaurant managers to apply custom heating and cooling schedules to Google Nest thermostats installed at the venue.
The application is not publicly available. Access requires a staff password and authorization on the underlying Google account.
What we collect
To function, LOV3 Comfort stores the following data on a private, access-controlled server:
- Google OAuth tokensissued by Google after the account owner signs in and grants access. These tokens permit the app to call the Google Smart Device Management API on the owner's behalf.
- Device identifiers and metadata returned by the Smart Device Management API — Nest device IDs, room labels, device types, and the structure they belong to.
- Thermostat state and setpoints read from the devices (current ambient temperature, mode, target setpoints, fan state) so the application can decide what command to send next.
- Schedule and override configuration entered by staff (recurring intervals, temporary overrides, notes).
- An application log of every command applied, including timestamps, success/failure status, and any error message returned by Google.
The application does notcollect: names, email addresses (other than the account owner's, which is implicit in the OAuth grant), payment information, location data outside of what is necessary to identify the venue's devices, contacts, calendar data, photos, audio, video, or any other Google account data.
How we use it
All data is used exclusively to operate the scheduling and override features of the application:
- Apply the configured schedule to thermostats every five minutes via an automated job.
- Display current thermostat state to staff so they can adjust comfort settings.
- Provide an audit trail of what command was applied to which device at what time.
We do not use the data for advertising, profiling, analytics shared with third parties, or any purpose unrelated to operating the thermostats at LOV3 Houston.
Who we share it with
We do not sell, rent, lease, or share the data with any third party. The data is transmitted only between:
- The application server (hosted on Vercel)
- The application database (hosted on Neon, a managed Postgres provider)
- Google's Smart Device Management and OAuth services, which the application authenticates against
Vercel and Neon process this data solely as infrastructure providers under their respective data processing agreements.
How long we keep it
OAuth tokens and device state are retained for as long as the connection to the Google account is active. If the account owner revokes access — at myaccount.google.com/permissions — the corresponding tokens are no longer usable, and they are purged from the database the next time the owner reconnects or on request.
Application logs (records of commands applied) are retained for operational troubleshooting and are not deleted on a fixed schedule. They contain no personally identifying information beyond device identifiers.
How we protect it
The application is gated by HTTP session authentication. All traffic uses HTTPS. OAuth tokens, the database connection string, and the application password are stored as encrypted environment variables on the hosting provider and are never exposed to the browser.
Your choices
The account owner can revoke the application's access to their Google account at any time by visiting myaccount.google.com/permissions and removing “LOV3 Comfort.” This immediately stops the application from being able to control the thermostats.
To request deletion of any stored data, contact us at the address below.
Compliance with Google API Services User Data Policy
LOV3 Comfort'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.
Changes to this policy
We may update this policy from time to time. The “Last updated” date at the top of this page reflects the most recent change.
Contact
Maurice Ragland
maurice.ragland@ipredictive.net