Catch My CallCatch My Call

Privacy Policy

Last updated: October 10, 2026

This Privacy Policy describes how MOTIF TECHNOLOGIES INC (“Catch My Call,” “we,” “us,” or “our”) collects, uses, stores, shares, retains, and deletes information when you use https://www.catchmycall.co and related services (the “Service”). Catch My Call is an AI phone receptionist for businesses: it answers calls, captures leads, checks calendar availability, and sends appointment requests that the business owner approves.

By using the Service, connecting Google Calendar, or providing contact information, you agree to this Privacy Policy. If you do not agree, do not use the Service or connect Google.

Google user data

Some business accounts optionally connect Google Calendar through Google OAuth so Catch My Call can check availability and create or update appointment events after the owner approves a request. This section explains how we handle Google user data and is intended to meet Google API Services User Data Policy and Limited Use requirements.

1. Google data we access

When you choose “Connect Google Calendar” in the Catch My Call dashboard, we request only these OAuth scopes:

  • https://www.googleapis.com/auth/calendar.events — create, update, and delete calendar events that Catch My Call manages for approved appointments (and related appointment changes you approve).
  • https://www.googleapis.com/auth/calendar.freebusy — read free/busy busy blocks so the AI receptionist can tell callers which times look open versus busy. We do not request full calendar read access to every event’s private details beyond what free/busy and events scopes provide for this booking workflow.
  • https://www.googleapis.com/auth/userinfo.email — read the Google account email associated with the connection so we can show which Google account is connected in the dashboard.

From those scopes, Catch My Call may access and process:

  • Your Google account email for the connected calendar
  • Free/busy availability intervals for times relevant to booking requests
  • Calendar events that Catch My Call creates or updates for appointments (title, time, description/notes needed for the booking, and Google event identifiers)
  • OAuth tokens (including a refresh token) required to call Google Calendar APIs on your behalf

We do not request Gmail, Drive, Contacts, Photos, or other unrelated Google Workspace products. Connecting Calendar is optional; the rest of the Service can run without Google access (with limited booking automation).

2. How we use Google user data

We use Google user data only to provide and improve user-facing Catch My Call features that are prominent in the product:

  • Show calendar connection status and the connected Google email in the dashboard
  • During live calls, check free/busy so the receptionist can suggest open times and avoid inventing availability
  • After the business owner approves an appointment request (via SMS or dashboard), create a Google Calendar event
  • After the owner approves a cancel or reschedule request, delete or update the related Google Calendar event when an event ID is on file
  • Diagnose connection health (for example, expired tokens) so we can ask you to reconnect

We do not use Google user data for advertising, selling data, credit decisions, or unrelated product analytics beyond operating the booking features above.

3. AI / machine learning and Limited Use

Affirmative Limited Use statement: The use of raw or derived user data received from Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. See also our dedicated page: https://www.catchmycall.co/limited-use.

Catch My Call uses AI voice systems (including third-party providers such as Vapi and OpenAI models routed through Vapi) to converse with callers. Those systems process call audio, transcripts, and business knowledge you configure (hours, services, greetings, FAQs) so the receptionist can answer the phone.

How Google Calendar data interacts with AI: Google OAuth tokens and Calendar API requests (free/busy and event create/update/delete) are handled on Catch My Call servers. For the live call only, a summarized availability tool result (busy vs open windows) may be passed into the voice AI conversation so the receptionist can speak accurate availability—this is a prominent user-facing booking feature. We do not send Google OAuth tokens to AI providers.

Limited Use commitments:

  • We do not use, transfer, or sell Google user data (including raw, aggregated, anonymized, or derived data) to create, train, or improve foundational or generalized machine learning or artificial intelligence models.
  • We do not allow our AI providers to use Google Workspace / Calendar user data obtained via our Google OAuth connection to train or improve their generalized AI/ML models.
  • Google Calendar free/busy and event data is used only to provide the booking workflow described in this policy (availability checks and creating/updating/deleting appointment events the owner approved).
  • Human review of Google user data, if any, is limited to security, abuse investigation, compliance with law, or providing the Service features you requested—not for building unrelated AI systems.
  • We do not use self-hosted / offline models that receive Workspace API data outside the third-party AI providers disclosed on /limited-use.

Call recordings/transcripts used by the voice AI are separate from Google OAuth Calendar credentials and are handled under the “Calls, SMS, and account data” section below. We still do not use Google Calendar data to train AI models.

4. Sharing of Google user data

We do not sell Google user data. We share Google user data only as needed to operate the Service:

  • Google — to authenticate and call Calendar APIs with your consent
  • Our hosting / database providers — to store OAuth tokens and related booking metadata securely
  • Service operators acting on our behalf under confidentiality obligations, only to provide Catch My Call
  • When required by law, legal process, or to protect rights, safety, and security

Free/busy results may be spoken to a caller in summarized form (for example, that a time looks open or busy) as part of the receptionist feature you enabled. We do not publish your Google Calendar publicly.

5. Data protection mechanisms

We use administrative, technical, and organizational measures designed to protect Google user data and other personal data, including:

  • Encryption in transit (HTTPS / TLS) for dashboard, APIs, and OAuth redirects
  • Access controls so calendar connections are tied to the authenticated Catch My Call account that connected them
  • Storage of OAuth refresh tokens in our application database with restricted production access
  • Least-privilege scopes (events + free/busy + email identity only)
  • Ability for you to disconnect Google Calendar at any time, which removes our stored refresh token for that connection

No method of transmission or storage is 100% secure. If you believe your account or Google connection was compromised, disconnect Calendar in the dashboard and contact us immediately.

6. Retention and deletion of Google user data

While connected: We retain the Google OAuth refresh token, connected Google email, and calendar identifiers for as long as your Catch My Call account keeps Google Calendar connected, so the Service can continue checking availability and managing approved appointments.

Booking metadata: When an appointment is approved, we may store limited event metadata in Catch My Call (for example, requested/confirmed times and a Google Calendar event ID) so we can update or cancel that event later if you approve a change. That metadata is retained with the related call/appointment record unless you delete the account or we purge it under our retention practices below.

Disconnect: You can disconnect Google Calendar in the Catch My Call dashboard at any time. Disconnecting deletes our stored Google refresh token (and related Calendar connection row) for your account so we can no longer access your Google Calendar through that connection. Events already created on your Google Calendar remain in Google until you delete them in Google Calendar (or approve a Catch My Call cancel request while still connected).

Account deletion / requests: To delete your Catch My Call account data, including any remaining Google connection tokens and associated booking records we control, email abidinouman@gmail.com from the email on your account with subject “Delete my Catch My Call data.” We will delete or irreversibly de-identify personal data we control within a reasonable period (typically within 30 days), except where we must retain limited records for legal, security, billing dispute, or fraud-prevention purposes. You can also revoke Catch My Call’s access in your Google Account security settings (Third-party access).

Calls, SMS, and account data

Independent of Google, we may collect and process:

  • Account information (name, email, password or Google sign-in identifiers, business profile, phone numbers you provision or save)
  • Call metadata, summaries, action items, quality labels, and recordings when enabled by our voice provider
  • Caller phone numbers, names, appointment preferences, and SMS consent markers
  • Transactional SMS content needed to alert owners and follow up with callers who consented
  • Billing/subscription status when you use paid plans

We use this information to operate the AI receptionist, show the call log, send consented transactional texts, provide support, secure the Service, and improve product reliability. We do not sell mobile numbers or personal information for third-party marketing.

SMS consent is collected with a short verbal yes/no on live calls (see SMS Opt-In), via an unchecked website checkbox on the demo form, or via an unchecked dashboard checkbox when a business owner saves a notify number. Rates and STOP language are included in the texts themselves. Twilio is used to deliver those texts. Message frequency is low. Message and data rates may apply. Reply STOP to opt out; HELP for help.

Cookies and similar technologies

We use cookies and similar technologies as needed for authentication, session security, and basic product operation. We do not use Google user data for third-party advertising cookies.

Children

The Service is directed to businesses and adults. We do not knowingly collect personal information from children under 13.

Changes

We may update this Privacy Policy from time to time. The “Last updated” date will change when we do. Material changes to how we use Google user data will be disclosed here, and where required we will prompt you to review and consent before using Google user data in a new way.

Contact

Questions about privacy, Google user data, or deletion requests:
MOTIF TECHNOLOGIES INC
Email: abidinouman@gmail.com
Website: https://www.catchmycall.co

Quick links for Google reviewers: Data access · Data use · Data protection · Retention / deletion · AI & Limited Use