Privacy Policy

Last updated:

Joe's Help is operated by Applied Agentic Systems LLC. This policy explains how we handle Google sign-in information, how we access, use, store, and share Google account and Calendar data for scheduling, how we process calls and summaries, and how we handle information for our SMS/MMS notification program.

Google Sign-In

Creating an account or signing in with Google is separate from connecting Google Calendar. That sign-in asks Google for your OpenID identifier, email address, and basic profile. We use it to recognize you, create or open your Joe's Help account, and store a name for that account.

When Google sign-in is first linked, we store the Google account identifier, the email address, whether Google reports that email as verified, and the name provided at account creation. We also store the ID token claims from that sign-in. Those claims can include your name, a profile photo URL, and given and family names when Google includes them. We do not receive or store your Google password. Ordinary sign-in does not store a Google access token or refresh token, and it does not authorize Calendar access.

We keep this sign-in record with your account. To request deletion, contact us as described below. We may need to confirm your identity and authority before processing the request. Information required for applicable legal or security obligations may need to be retained.

Google Account and Calendar Data

Connecting Google Calendar is optional. When a workspace owner connects an account, Google asks them to authorize access. We receive the Google account identifier and email address, granted permissions, and access and refresh credentials that allow the integration to work while the owner is away. We do not receive the account's Google password.

With that authorization, we can list calendars the account can access, including names, identifiers, descriptions, access roles, and time zones, and we can see when those calendars are busy. For scheduling, we read events on the selected shared booking calendar. Authorized workspace members can see that calendar, including titles, descriptions, locations, and start and end times. Event requests can include additional fields returned by Google, such as attendees. Calendars selected only for conflict checks provide busy times; their titles, descriptions, and attendees are not shown to other workspace members. We request permission to see the account email, list calendars, see busy times, and view and change events.

The owner chooses a shared booking calendar and any additional calendars used to check conflicts. Availability checks compare busy times with the configured appointment rules and service-area coverage.

How We Use Calendar Data

We use this data to connect the selected account, display the shared calendar, check availability, scheduling conflicts, and service-area coverage, and create, reschedule, update, or cancel appointments requested through Joe's Help. Authorized workspace members can access shared-calendar features according to their permissions. The owner separately controls whether the voice assistant can book appointments.

We store connection information, calendar selections, time zones, and records of appointments managed through the service. These records may include Google calendar and event identifiers, appointment times and status, the reason for the visit, service address, and customer contact details supplied for the booking.

Sharing Calendar and Appointment Data

We exchange calendar and appointment data with Google Calendar to carry out the scheduling actions you request. The selected shared calendar and appointment information are available to authorized members of your business workspace. Amazon Web Services (AWS) stores and processes the data needed to run these features.

ElevenLabs provides our voice AI service. ElevenLabs and the model providers used by that service process live conversations to answer callers and handle their requests. When assistant booking is enabled, this data includes the booking conversation, contact details, service address, proposed appointment times, and booking results needed to complete the requested booking. Our no-training policy below applies to these conversations and to the AI providers that process them.

Google Maps receives service addresses and locations used to identify and check service-area coverage. This application does not keep a stored cache of those map results after the search.

We do not sell Google user data, use it for advertising or credit decisions, or use it, including data derived from it, to create, train, or improve generalized AI or machine-learning models. We do not use call transcripts or conversation data to train AI models, and we do not permit our AI service providers, including OpenAI, ElevenLabs, and the model providers used by ElevenLabs, to use that data to train or improve their models. We use their services to process calls and generate summaries, with model-training data sharing disabled where that setting is offered.

Call Records and Post-Call Summaries

We store call records, which may include transcripts, caller contact details, service requests, summaries supplied by the voice service, and analysis results. These records help the business review calls and follow up with callers. Where call recording is enabled, recordings may also be retained by the voice service.

We send call transcripts, including personal details and Google Calendar or appointment information discussed during the call, to OpenAI to generate summaries, extract the caller’s name when provided, identify the reason for calling, and assess urgency when enabled. OpenAI is not permitted to use this data to train its models.

The summary describes the conversation. Raw calendar tool responses, access credentials, and stored appointment records are not included as additional inputs to the OpenAI summary request. Only information spoken during the call remains in the transcript, including appointment details.

Storage and Security

Google access and refresh credentials are encrypted before they are stored. Communication with Google APIs uses HTTPS. Workspace permissions restrict access to calendar features and connection management.

Retention, Disconnecting, and Deletion

We retain account and connection information, call records (including transcripts and summaries), analysis results, and appointment records while needed to provide the requested service, support call follow-up and appointment management, handle deletion requests, and meet applicable legal and security obligations. Recordings, where enabled, and other data processed by service providers are also subject to the applicable service settings and retention terms. A model-training opt-out is separate from retention: it does not automatically delete data or mean that calls and recordings are never stored.

The workspace owner can disconnect Google Calendar in Calendar settings. Disconnecting removes the stored access and refresh credentials from the connection, disables assistant booking, and attempts to revoke those credentials with Google. You can also remove Joe's Help's access directly from your Google Account connections.

Disconnecting does not automatically delete existing events in Google Calendar or call, appointment, and account records already stored by Joe's Help. To request deletion of stored Google-related data, transcripts, recordings where available, summaries, appointment records, or account records, contact hello@joeshelp.com from the email address associated with your account and identify the workspace and data concerned. We may need to confirm your identity and authority over the workspace before processing the request. Information required for applicable legal or security obligations may need to be retained.

Google API Limited Use

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements. We use Google user data to provide the scheduling features described here. Transfers are limited to providing those features with your consent, necessary security purposes, or compliance with applicable law.

SMS and Mobile Messaging

Business owners and designated staff who opt in receive operational SMS/MMS notifications about incoming calls and customer inquiries received by their business's Joe's Help receptionist.

We collect the notification recipient's mobile phone number and messaging preferences to deliver the notifications they request. Notifications may include a caller's name, callback number, and request summary. We process this caller information on behalf of the business the caller contacted and deliver it to that business's authorized recipients. Calling a subscribing business does not enroll the caller in this SMS/MMS notification program.

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Mobile information and messaging consent are not shared with third parties or affiliates for marketing or promotional purposes.

We may provide information to service providers only as necessary to operate Joe's Help and deliver the communications requested by subscribers. This operational use does not permit sharing mobile information or messaging consent for marketing or promotional purposes.

Message frequency varies based on incoming-call activity. Message and data rates may apply.

Reply STOP to unsubscribe from Joe's Help SMS/MMS notifications. Reply HELP for assistance, or email hello@joeshelp.com.

Additional information is available in our SMS Messaging Terms.

Contact Us

For privacy questions or data requests, contact Applied Agentic Systems LLC at hello@joeshelp.com.