Effective Date: January 25, 2026 · Last Updated: September 25, 2026
HiLucy ("we," "our," or "us") operates a SaaS platform for hospitality and short-term rental management, including an AI-powered concierge service. This Privacy Policy explains how we collect, use, disclose, and protect your personal information when you use our services.
This policy applies to:
HiLucy
10205 S Komensky Avenue
Oak Lawn, IL 60453, USA
Contact for Privacy Inquiries: [email protected]
For EU residents: [email protected]
| Category | Examples | When Collected |
|---|---|---|
| Identity Data | Name, nationality, date of birth, ID document details | Guest check-in |
| Contact Data | Phone number, email address, WhatsApp ID | Registration, check-in |
| Location Data | Country/city of residence, shared location | Check-in, chat |
| Communication Data | Messages, requests, preferences | AI chat interactions |
| Payment Data | Card details (via Stripe), billing address | Service purchases |
| Booking Data | Check-in/out dates, room type, guest count | Reservations |
| Category | Examples | Purpose |
|---|---|---|
| Technical Data | IP address, browser type, device info | Security, analytics |
| Usage Data | Pages visited, features used, timestamps | Service improvement |
| Cookie Data | Session cookies, preference cookies | Authentication, UX |
| Prospect Activity | Pages viewed and sign-ins by business prospects, via the hl_pid cookie (see 9.1) | Sales follow-up |
| Purpose | Legal Basis (GDPR) |
|---|---|
| Provide AI concierge service | Contract performance |
| Process guest check-ins | Contract performance |
| Process payments | Contract performance |
| Send service notifications | Legitimate interest |
| Improve services | Legitimate interest |
| Comply with legal obligations | Legal obligation |
| Send marketing communications | Consent |
We share your data with the following categories of service providers:
| Provider | Data Shared | Purpose |
|---|---|---|
| OpenAI | Conversation content; PDFs and photos staff and operators import, including files picked from Google Drive (see 11.5) | AI processing, reading imported files |
| Meta (WhatsApp) | Phone, messages, including meeting times and Google Meet links sent to business prospects | Messaging |
| Stripe | Payment details | Payment processing |
| Google Cloud | Location, language | Translation, maps |
| Twilio | Phone number, message content, including meeting times and Google Meet links sent to business prospects | SMS delivery |
All subprocessors are bound by Data Processing Agreements (DPAs) and Standard Contractual Clauses (SCCs) where applicable.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Information sharing to subcontractors in support services, such as customer service, is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
We use your mobile number solely to deliver the messages described in our Terms of Service: one-time verification codes and notifications about your own stay or account. We do not sell mobile numbers, and we do not use them for marketing.
| Data Type | Retention Period |
|---|---|
| AI conversation history | 30 days |
| Guest check-in data | Booking duration + 30 days |
| User account data | Until account deletion |
| Payment records | 7 years (legal requirement) |
| Booking records | 2 years post-checkout |
| Technical logs | 30 days |
To exercise your rights, email [email protected]. We will respond within 30 days (GDPR) or 45 days (CCPA).
We protect your data through:
Our AI concierge (Lucy) uses OpenAI GPT-4o-mini to process your messages. AI-assisted routing and recommendations are not legally significant automated decisions. You may request human review of any AI interaction at any time.
This section covers the data HiLucy receives from Google when you use one of the four features below. Each one is optional, and each one starts only when you choose it and approve it on Google's own consent screen.
If you use none of these, HiLucy receives no data from your Google account and nothing in this section applies to you. Each calendar connection is made by one person, for one account, and can be undone at any time (see 11.8).
HiLucy asks Google only for the permissions below, and each one only when you use the feature that needs it.
openid, https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile
Let HiLucy confirm who you are and see your name, email address and profile photo. We use them to create your HiLucy account, sign you in, and show your name and photo in the app.
https://www.googleapis.com/auth/calendar.calendarlist.readonly
Lets HiLucy see the list of calendars on your account: each calendar's name and identifier. We use it to let you pick a calendar, and we read the address of your primary calendar to show you which Google account is connected. For CRM meetings we also use that address to add you as a guest on the meetings you book. This permission does not give HiLucy access to any events.
https://www.googleapis.com/auth/calendar.freebusy
Lets HiLucy see when you are busy. Google answers with the start and end times of busy periods inside the time window we ask about, and nothing else: no event titles, descriptions, locations, attachments or attendees. For CRM meetings we ask about the team's shared prospect calendar and your own primary calendar, so a new meeting does not clash with either.
https://www.googleapis.com/auth/calendar.events
Lets HiLucy create, update and delete calendar events. HiLucy uses it only for events it creates itself: meetings you schedule through the HiLucy CRM, which go on the team's shared prospect calendar with you added as a guest, and events for rental bookings made through HiLucy. We record the identifier Google returns for each event we create, and we act only on those identifiers. HiLucy does not list or read the other events on your calendars, and it never changes or deletes an event it did not create.
Rental calendar connections made before September 7, 2026 may still hold Google's broader calendar.readonly permission instead of the first two above. HiLucy uses it for the same two things only: the calendar list and busy times. Disconnecting and connecting again replaces it with the narrower permissions.
https://www.googleapis.com/auth/drive.file
Lets HiLucy open only the files you pick in Google's file picker, and nothing else in your Drive. The access token stays in your browser and is not stored on our servers. The files you pick are handled like an upload: HiLucy reads spreadsheets to fill in the import, and PDFs and photos are also sent to our AI provider, OpenAI, to read what they say (see 11.5).
We do not use Google user data for advertising, for building profiles, to train machine-learning or AI models, or for any purpose other than providing these features to you.
For Google sign-in, we keep your name, email address and profile photo as part of your HiLucy account, until the account is deleted (see section 6).
For a calendar connection, we keep:
We do not copy your calendar into our systems. We do not store your events, their contents, or your free/busy history. Free/busy data is requested when a scheduling screen needs it and is used to render that screen.
For Google Drive, we store nothing from Google. The access token stays in your browser and expires within an hour. We keep only what you choose to import, as your own records.
We do not sell Google user data, and we do not transfer it to third parties for advertising or any independent purpose. It is disclosed only:
Events HiLucy creates can be seen by the people invited to them and by anyone the calendar is shared with. For CRM meetings that includes the HiLucy staff who share the team's prospect calendar. That sharing is controlled in Google Calendar, not by HiLucy.
Apart from what a feature shows you and your team as part of using it (for example, the list of booked meetings in the CRM), no one at HiLucy reads your Google user data, except: when you ask us to look at a specific item (for example, a meeting that did not reach your calendar); when we need to investigate a bug, abuse or a security incident; when the law requires it; or when the data has been aggregated and anonymized for internal operations.
HiLucy'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.
Data passes between HiLucy and Google over encrypted connections. Tokens are held in our production database, access to which is restricted to the systems and staff that require it. Each connection is scoped to the person or property that created it, so one customer's connection cannot be used to reach another's calendar.
You can end a calendar connection in either of two ways, and either is enough:
Disconnecting does not delete calendar events HiLucy already created; those remain on the calendar, and you can delete them in Google Calendar. To ask us to delete the identifiers we kept for those events, or any other data described in this section, contact us using the details below and we will do so.
Google sign-in and Google Drive access can also be removed at myaccount.google.com/permissions. Removing sign-in there does not delete your HiLucy account; to delete it, contact us using the details below.
Questions about this section, or requests to delete data covered by it, can be sent to [email protected]. We respond within 30 days.
Our services are not directed to individuals under 16 years of age. We do not knowingly collect data from children.
We will notify you of material changes via email or in-app notice at least 30 days before they take effect.
Privacy inquiries: [email protected]
General support: [email protected]