PHONE AGENT / PRIVACY
Understand the connection.
This notice describes the current Lumerendia Phone Agent pilot and its Google Calendar integration. Last updated November 18, 2026.
Information handled
Owner setup can include business details, contact information, appointment rules and instructions. The setup acknowledgment records the entered name, exact acknowledgment version and text, and time of acceptance. Possession of an invitation and an entered name are not independent verification of identity.
When calls are enabled, the application can retain caller contact details, request summaries, intent, urgency and booking or delivery status. Its request store excludes raw call recordings and full transcripts. Voice providers separately process call audio and transcripts according to the business’s provider configuration. The current test-agent settings store call audio and retain conversations without a scheduled expiry. These settings are not an authorization to record customer calls.
Google data and purpose
You choose whether to grant access on Google’s own consent screen. The integration requests permission to read your calendar list and availability, and to read, create, change and delete events on calendars you own. Google’s event permission is broader than one calendar; appointment operations in this application are bound to the calendar selected for the business.
The application uses calendar identifiers, names and timezone information for selection; availability and event time/status/identifier fields for scheduling checks; and appointment-event details for creation and outcome verification. Occupancy checks request event time and identifier fields rather than unrelated event titles or descriptions. When enabled and confirmed, appointment data and the attendee email are sent to Google Calendar to create the event and request its invitation.
Storage and service providers
OAuth credentials are encrypted before being saved in the application’s persistent database. Calendar selection and operational records are also stored. This is not a claim that every stored record is individually encrypted.
The application is hosted on Render. Google provides Calendar authorization and scheduling APIs. Enabled telephone features use Twilio and ElevenLabs; enabled owner email alerts can use Resend. Information required for those features passes to the relevant providers. When the phone booking tools are enabled, Calendar-derived available times and booking/readback outcomes can be returned to ElevenLabs so the phone assistant can discuss them with the caller. Provider processing and retention also depend on the applicable service configuration and provider agreement; this notice does not guarantee a provider deletion deadline.
Authorized business staff can review the private request inbox and booking outcomes. Setup-only invitations do not grant caller-inbox access.
Retention and deletion requests
The current pilot retains saved setup, acknowledgment, call-summary and booking records in persistent operational storage. A fixed automatic purge interval for these records has not been implemented. Backups may contain copies. Email lumerendia@gmail.com to identify your business and request information about access or deletion; do not send passwords or access tokens.
Disconnecting Google
Local disconnection removes active stored Google credentials and the calendar selection. It does not delete existing Google Calendar events, remove other operational records or revoke Google’s grant. You can separately revoke access in your Google Account connections. Google authorization may also expire or become unavailable; a saved connection is not a promise of permanent access.
Controls and contact
Business access is scoped to authenticated sessions. A setup invitation is single-use and time-limited; it is not a permanent owner login. Connecting Google or saving setup information does not itself enable live booking or authorize call recording. Contact lumerendia@gmail.com about this notice or your business’s setup.