Privacy Policy
Last updated: September 18, 2026
This policy explains how Artificial Idiots handles information through our website, AI receptionist workspace, and optional Google Calendar connection.
For privacy questions or requests, contact info@artificialidiots.io. When a business runs its own receptionist workspace, that business also controls the information it collects and should provide its own privacy notice.
Information we process
- Leads and appointments: names, email addresses, phone numbers, requested appointment times, and information you provide when contacting us or booking an assessment.
- Receptionist conversations: live voice input, generated voice responses, text transcripts, service requests, location or address details you provide, and operator notes and follow-up status.
- Connected calendar information: the configured calendar identifier, busy time ranges, available appointment times derived from those ranges, and assessment event information, including event identifiers, dates, times, attendee email addresses, and booking links.
- Connection and technical information: Google authorization tokens, application settings, and technical information processed by hosting and service providers to deliver and secure the service.
How we use information
We use this information to answer leads, operate the receptionist, collect and review service requests, arrange requested assessments, send configured notifications, and support and protect the service. AI responses can contain mistakes; the business operator should review important details.
Chat, sales and customer support
Website chat saves the name, contact details, selected request type, consent choices and conversation. Approved business guidance is used for automated general support answers. Questions requiring an account decision or information outside that guidance are referred to the team. Support requests, owner notes, reviewed answers, email drafts and delivery records are stored in the private workspace. Sales emails require a recorded contact permission; scheduled sequences contain messages approved by the operator in advance.
If the operator enables mailbox import, the application reads new messages from the configured mailbox folder after activation. It matches replies using the sender address and email thread identifiers. Unmatched, large or unsupported messages need operator review. Attachments are not stored by the workspace; the original email remains in the mailbox. Import does not mark messages read or delete them. Replies stop scheduled sales follow-ups. Mailbox credentials are kept in server settings.
Google Calendar access
Connecting Google Calendar is optional and requires authorization from the account holder. The current integration checks free/busy information on the configured calendar and creates an Artificial Idiots assessment only after the requested time and contact details are confirmed. It also retrieves an event associated with a booking request to check whether that booking already succeeded and avoid duplicates.
Google's calendar events permission can allow viewing and editing events on calendars accessible to the account. The current application uses it for the assessment workflow described here; it does not implement general event deletion. When booking synchronization or scheduled sales is enabled, it checks event status and attendee email addresses in the configured assessment calendar, from 30 days before through 90 days after the check, to stop follow-up for people who have booked. Use a dedicated business assessment calendar. Event titles and descriptions are not requested by this synchronization. It does not request access to Gmail messages, Google Drive files, or Google Contacts.
The event may include the attendee's name, phone number, email address, and assessment time. Google receives these details to create the event and send the requested invitation. Calendar owners and people with access to the event may see its contents according to the calendar's sharing settings.
Artificial Idiots uses Google Calendar data only to provide the connected scheduling features. We do not sell that data, use it for advertising or credit decisions, or use it to train general-purpose AI models. Our handling of Google API data is subject to the Google API Services User Data Policy and its Limited Use requirements.
Service providers and sharing
- OpenAI: live voice and conversation content are processed to generate receptionist responses and transcripts. Text chat, approved support guidance and selected lead or reply context are also processed to prepare answers and sales drafts. Text requests use the API store=false setting; provider processing and retention terms still apply. When scheduling is requested through voice, the available time options and booking result are passed to the AI to continue that conversation. Google access tokens and raw busy event data are not passed to the AI.
- Google: processes calendar access, assessment events, and invitations. The website's booking button opens Google's appointment scheduling service.
- Hosting and email providers: Hostinger hosts our public website. The provider used for a hosted workspace and the configured email provider process information needed to run that service and deliver notifications.
- Business operators and recipients: the authorized workspace operator can review collected leads and transcripts. Enabled email notifications share lead details with the configured recipient. Appointment details are shared with the calendar and invited attendee.
We do not sell personal information. Google-derived data is shared only as needed for authorized scheduling, for security purposes, or as required by law. Human access to that data is limited to the authorized user-facing workflow, your affirmative permission for assistance, or a security or legal need allowed by Google's policy. Other service providers also apply their own privacy terms to their services.
Storage, security, and retention
The workspace stores leads, text transcripts, settings, support requests, sales histories, imported email text and delivery records in its private data directory. Website chat access expires after 24 hours; the session copy is removed after approximately 30 days when new sessions are created. Copies saved as leads or support requests remain until removed by the operator. Private daily backups retain the seven most recent snapshots. Exported copies and off-site backups must also be managed by the operator. The workspace does not save an audio recording file, although its voice provider processes audio under that provider's terms.
A Google refresh token is stored in the workspace's private data directory so the connection can continue without signing in for every request. Temporary access tokens and offered appointment slots are held in server memory. Google communications use HTTPS. Access to stored files depends on the security of the computer or hosting account; those files are not intended to be publicly served. No service can guarantee absolute security.
The current workspace does not automatically expire stored lead, transcript, or notification records. They remain until removed by the operator. The stored Google connection remains until its local token is removed; revoking access in Google prevents further authorized access even if a local token file remains. Events and invitations already created remain in Google Calendar or recipient mailboxes until managed there. Provider logs and backups follow the applicable provider's retention settings.
Your choices and deletion requests
You can remove Artificial Idiots' access through your Google Account connections. This stops future calendar access but does not delete existing appointments or workspace records.
To request access, correction, or deletion of information controlled by Artificial Idiots, email info@artificialidiots.io. We may need to verify the requester's identity. If a separate business controls the workspace, contact that business to remove its stored records, connection token, and relevant backups. Copies already sent to another recipient or provider must be handled with that recipient or provider. Information may be retained where required by law.
Cookies and audience
The current public homepage does not include advertising trackers or analytics scripts. The workspace uses a temporary sign-in cookie to protect the Google authorization flow. Google and hosting providers may use their own cookies or technical logs. This service is intended for business use and is not directed to children.
Changes to this policy
We will update this page when our practices change. A new use of Google data outside the purposes described here requires an updated disclosure and the account holder's consent before that use begins.