Privacy Policy — Humanize.ai

This Privacy Policy explains how simplibot.ai L.L.C. (“Humanize.ai,” “we,” “us,” or “our”) collects, uses, and shares information about you when you use the Humanize.ai platform, website, and related services (the “Service”). By using the Service, you agree to the collection and use of information in accordance with this policy.

Google API Services — Limited Use

Humanize.ai's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. We do not use, transfer, or sell Google user data — raw, aggregated, or derived — to develop, train, improve, or fine-tune any generalized or foundational artificial intelligence or machine learning model, whether our own or a third party's. Section 3 sets out exactly which Google permissions we request and what we do with the data.

1. Information we collect

We collect the following categories of information:

Account information — name, email address, phone number, company name, and password (stored as a salted hash) that you provide during registration.
Google Sign-In information — if you sign in with Google, we receive your name, email address, Google profile picture, and a unique Google account identifier. We use this only to authenticate you and create or link your Humanize.ai account. Signing in with Google gives us no access to your Gmail, Calendar, Drive, or any other Google service.
Connected calendar and mailbox accounts — if you or a member of your team chooses to connect a Google or Microsoft account so the AI agent can book meetings or send follow-up material, we store that account's email address, the permissions you granted, and the OAuth access and refresh tokens issued to us, encrypted at rest. See Sections 3 and 4.
Campaign data — lead lists, scripts, call recordings, transcripts, and outcomes that you or your team upload or generate while using the Service.
Usage and device data — IP address, browser type, pages visited, timestamps, and diagnostic logs collected automatically to operate and secure the Service.
Cookies and similar technologies — we use first-party cookies and local storage to keep you signed in and remember your preferences.

2. How we use information

To provide, maintain, and improve the Service.
To authenticate you and secure your account.
To send transactional emails (password resets, campaign completion notifications, account alerts).
To run voice campaigns on your behalf using the contact lists you upload.
To offer and book meeting times on a calendar you have connected, and to send follow-up material from a mailbox you have connected, when a call calls for it.
To monitor, detect, and prevent fraud, abuse, and violations of our Terms of Service.
To comply with legal obligations.

3. Google user data, permissions, and Limited Use

Humanize.ai requests access to your Google account in three separate places, each one initiated by you and each one limited to a specific feature. Below is every Google permission (OAuth scope) the Service requests, and precisely what we do with it.

3.1 Permissions we request and why

Sign in with Google
openid · https://www.googleapis.com/auth/userinfo.email · https://www.googleapis.com/auth/userinfo.profile
Used only to authenticate you. We receive your name, email address, profile picture, and Google account identifier, and use them to create or sign you into your Humanize.ai account. This grant gives no access to any other Google service.
Google Calendar — offering and booking meeting times
https://www.googleapis.com/auth/calendar.freebusy · https://www.googleapis.com/auth/calendar.events
Requested only when a member of your team explicitly connects a calendar under Settings → Calendar, so that the AI agent can offer real open times during a call and book the meeting before the call ends. We request one permission for each of the two things we do, and nothing wider:
- Free/busy lookup (calendar.freebusy). We query the Calendar free/busy API for the connected account over the booking window. That API returns busy time intervals only — never event titles, descriptions, attendees, locations, attachments, or any other event content — and we use it solely to work out which times are free to offer.
- Creating the meeting (calendar.events). When a call results in a booking, we create a single event on the connected primary calendar with the prospect added as an attendee, so that Google sends the invitation from your own account.
We do not list, open, edit, or delete any other event on your calendar, and we do not copy your calendar into our systems. We deliberately do not request the broader Google Calendar permission that would let us see, edit, share, or delete your calendars, because nothing we do requires it.
Gmail — sending follow-up material you asked us to send
https://www.googleapis.com/auth/gmail.send
Requested only when a member of your team explicitly connects a sending mailbox under Settings → Email, so that material a prospect asked for during a call (for example a brochure or price list) arrives from your own mailbox rather than ours. This is a send-only permission: it does not allow — and is technically incapable of allowing — reading, searching, listing, labelling, or deleting anything in your mailbox. We never read your email.

These are the only Google permissions Humanize.ai requests. We request no Drive, Contacts, Photos, Chat, or Gmail-reading permissions of any kind.

3.2 How we handle Google user data

We use Google user data only to provide and improve the user-facing features described in Section 3.1.
We never sell Google user data, never use it for advertising or ad targeting, never use it to build advertising profiles, and never use it for credit-worthiness or lending purposes.
Humans at Humanize.ai do not read your Google user data, except: with your explicit consent (for example, when you ask our support team to investigate a booking that failed); where necessary for security purposes, such as investigating abuse; to comply with applicable law; or where the data has been aggregated and anonymised so that it no longer identifies you or your organisation.
We transfer Google user data only to the service providers listed in Section 6, acting on our behalf under confidentiality obligations and only as necessary to provide or improve the feature you asked for, to address security threats, or to comply with applicable law. Should we ever be part of a merger or acquisition, we would transfer Google user data only after obtaining your explicit prior consent.

3.3 Google user data and AI/ML models

Humanize.ai uses AI models to conduct conversations on your behalf, so we state our position explicitly:

We do not use, transfer, or sell Google user data — raw, aggregated, or derived — to develop, train, improve, or fine-tune any generalized or foundational artificial intelligence or machine learning model, whether our own or a third party's. Our use of raw or derived user data received from Google Workspace APIs adheres to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

For transparency, there is exactly one point at which data derived from a Google Workspace API reaches an AI model, and it exists only to deliver the feature you enabled. When a call is placed for a campaign with booking enabled, the candidate meeting times computed from the connected calendar's busy intervals — together with the name of the team member who would take the meeting — are included in the instructions given to the conversational model that runs the call, so that the agent can offer those times out loud and book the one your prospect picks.

No calendar event content, no message content, and no mailbox content is ever sent to an AI model. The free/busy API does not return event content, and our Gmail permission cannot read mail.
Follow-up emails drafted by the agent are written from the call itself and the material your organisation uploaded — never from anything in your mailbox.
Our AI providers process this data only to generate the agent's responses during that call, under API terms that prohibit using it to train or improve their models. We retain no training corpus of any kind built from Google user data.

3.4 Retention and deletion of Google user data

OAuth access and refresh tokens are encrypted with AES-256-GCM before they are stored, and are decrypted in memory only to make a call to Google on your behalf.
Busy intervals fetched from your calendar are used in memory to compute the times the agent may offer and are not kept as a copy of your calendar. What we retain is the booking we made: the meeting time, the invitee, and the identifier and link of the event we created.
For a connected mailbox, we retain a record of the messages we sent on your behalf — recipient, subject, timestamp, and the identifier Google returned — so that the call's follow-up items can show what was delivered.
Disconnecting an account deletes the stored tokens for it immediately. Deleting your Humanize.ai account deletes all connections, tokens, and associated Google user data.

3.5 Revoking our access

In the Service, go to Settings → Calendar or Settings → Email and choose Disconnect on the account. We delete the stored tokens immediately and stop using that account.
You can also review and revoke Humanize.ai's access at any time from your Google Account at myaccount.google.com/permissions.
To have all of your data deleted, contact us at connect@simplibot.ai.

4. Microsoft 365 and Outlook connections

The calendar and mailbox features described in Section 3 are also available on Microsoft 365. When a member of your team connects a Microsoft account, we request only the Microsoft Graph permissions those features need: openid, profile, email, offline_access, User.Read, and then Calendars.ReadWrite plus Mail.Send for a connected calendar (Microsoft only emails a meeting invitation to attendees when the sending permission is present), or Mail.Send and Mail.ReadWrite for a connected mailbox, because Microsoft Graph requires a draft to be created and uploaded to before a message with a large attachment can be sent.

We use these permissions only to check availability, create the meeting you booked, and send the follow-up material requested on a call. We do not read, search, or otherwise process your other mail or calendar entries, and every commitment in Sections 3.2 to 3.5 — including that we never use this data to train AI or machine learning models — applies equally to data received from Microsoft.

5. Artificial intelligence and machine learning

Humanize.ai uses third-party AI models to conduct voice conversations, transcribe and summarise calls, and draft follow-up messages. Today those providers are Google (Gemini) and Anthropic (Claude).

We do not use your data — including call recordings, transcripts, lead lists, and anything received from Google or Microsoft APIs — to train, fine-tune, or improve any foundational or generalized AI or machine learning model, our own or a third party's.
Our AI providers receive this content only to produce the response required at that moment in the call, under API terms that prohibit using it to train their models.
We do not sell your data to, or share it with, any AI developer for model development.

6. How we share information

We do not sell your personal information. We share information only with the following categories of recipients:

Service providers acting on our behalf under confidentiality agreements, including:
- Google Cloud Platform — application hosting and infrastructure.
- Google OAuth — sign-in and identity verification.
- Google Workspace APIs (Calendar, Gmail) and Microsoft Graph — only for accounts you have connected, and only as described in Sections 3 and 4.
- Resend — transactional email delivery.
- Twilio and Exotel — telephony and voice call delivery.
- Google AI Studio (Gemini) and Anthropic — voice and language model processing.
- Stripe — payment and subscription processing.
Legal authorities when required by law, subpoena, or to protect the rights, property, or safety of Humanize.ai, our users, or the public.
Successors in the event of a merger, acquisition, or sale of assets, subject to the same privacy commitments; Google user data would be transferred only with your explicit prior consent.

7. Data retention

We retain account information for as long as your account is active. Campaign recordings and transcripts are retained for 12 months by default, or longer if required by law or contract. Data received from Google and Microsoft is retained as described in Section 3.4. You may request deletion of your account and associated data at any time by contacting us at the email below.

8. Security

We use industry-standard measures including TLS encryption in transit, encryption at rest for sensitive fields — including AES-256-GCM encryption of every OAuth token we hold — salted password hashing, and least-privilege access controls. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

9. Your rights

Depending on your jurisdiction (including GDPR and India's DPDP Act), you may have the right to:

Access the personal information we hold about you.
Correct inaccurate or incomplete information.
Request deletion of your information.
Object to or restrict certain processing.
Port your information to another service.
Withdraw consent where processing is based on consent, including by disconnecting any Google or Microsoft account you have connected (see Section 3.5).

To exercise these rights, contact us at connect@simplibot.ai.

10. Children

The Service is not directed to children under the age of 16, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will take steps to delete it.

11. International transfers

We operate from the United States and India. Your information may be processed in either country. Where required, we rely on Standard Contractual Clauses or equivalent mechanisms to lawfully transfer data.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date and, for material changes, notify you by email or via the Service.

13. Contact us

simplibot.ai L.L.C.
Email: connect@simplibot.ai
Offices: Chicago, USA · Mumbai, India