1. Who operates Receptionistant
Receptionistant is currently operated by an individual sole proprietor in Albania. References to “Receptionistant,” “we,” “us,” or “our” in this policy refer to that operator. No separate United States corporation is represented by this policy.
2. Information we handle
Depending on how the service is used, we may handle:
- Account information: names, email addresses, organization names, authentication records, and account preferences.
- Business configuration: services, service areas, hours, qualification questions, scheduling rules, transfer destinations, and escalation instructions.
- Call information: phone and call metadata, call outcomes, transcripts, and recording metadata or recordings where recording is enabled and applicable.
- Customer workflow information: caller contact details, service requests, qualification answers, leads, appointment details, addresses, and follow-up states.
- Integration information: the connected Google account email, selected calendar details, authorization scopes, encrypted authorization credentials, availability results, and event identifiers needed to synchronize appointments.
- Technical information: device, browser, security, audit, diagnostic, and usage information needed to operate and protect the service.
- Payment information: if paid subscriptions are enabled, billing and transaction information may be handled by a payment provider. Complete payment-card details are expected to be handled by that provider rather than stored by Receptionistant.
3. How we use information
We use information to provide and secure accounts; configure receptionist behavior; answer and route calls; create call records, leads, and appointments; synchronize selected calendars; provide support; diagnose failures; prevent misuse; maintain records; and meet legal obligations. We do not use connected Google data to access unrelated Google services.
4. Google Calendar data
Google Calendar access is optional and is initiated by an authenticated business user. Receptionistant requests only the following access for the stated purposes:
| Google access | Operational purpose |
|---|---|
openid and email | Identify the Google account being connected. |
calendar.calendarlist.readonly | List calendars the connected account can access so the business can select a calendar. |
calendar.events.freebusy | Inspect busy and available times for appointment scheduling. |
calendar.events | Create, update, and cancel appointment events on the selected calendar. |
Receptionistant uses this access to identify the connected Google account, list and select calendars, inspect availability, and create, update, or cancel appointment events. It does not request access to Google Drive, Gmail, contacts, or unrelated Google account data.
Authorization tokens are stored in encrypted form and used server-side to perform authorized calendar actions. A business can disconnect Google Calendar from Receptionistant settings. Disconnecting stops future synchronization and removes the active connection credentials from use; users may also manage Receptionistant access through their Google Account.
Receptionistant does not sell Google user data. Our use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements.
5. Service providers and disclosures
We may use hosting, database, communications, telephony, AI, calendar, monitoring, and payment providers to operate the service. These providers may process information for us under their own contractual and security obligations. We may also disclose information when required by law, to protect rights or safety, to investigate misuse, or as part of a legitimate business transfer subject to appropriate safeguards.
We do not sell personal information or Google user data. We do not authorize service providers to use connected Google data for their own advertising.
6. Call recording and customer responsibilities
Call-recording and notification rules differ by location. Businesses are responsible for configuring and using Receptionistant lawfully, including providing notices and obtaining consent where required. Recording availability may depend on the configured service and telephony provider.
7. Security
We use general administrative, technical, and organizational controls designed to protect information, including authenticated access, customer-workspace separation, encrypted sensitive integration credentials, verified provider events, controlled service actions, and audit records. No system is completely secure, and this policy does not promise absolute security or uninterrupted availability.
8. Retention and deletion
We retain information for as long as reasonably needed to provide the service, maintain account and transaction records, resolve disputes, enforce agreements, meet legal obligations, and protect the service. Retention may vary by data type and customer configuration. When information is no longer required, we may delete or de-identify it, subject to backups and legal retention requirements.
Account holders may request access, correction, export, or deletion of applicable information through their Receptionistant support channel. Prospective users may use the Book a demo page to request operator contact details. We may need to verify identity and authority before acting on a request.
9. International processing
Receptionistant is operated from Albania and may use service providers in other countries. Information may therefore be processed outside the country where a user or caller is located, subject to applicable law and the safeguards available for the relevant service.
10. Changes to this policy
We may update this policy as the service, providers, or legal requirements change. We will post the revised policy on this page and update the date above. Material changes may also be communicated through the service when appropriate.
11. Contact
For privacy, deletion, or account questions, use the support channel provided with your Receptionistant account. If you do not yet have an account, use the Book a demo page to request the operator’s current contact details.
