Giving your assistant access to Google: what those warnings mean
Whenever you connect a new Google service — your Calendar, Contacts, or Drive — Google will try hard to scare you off. You’ll see warnings like “Google hasn’t verified this app” and a link that literally says “unsafe.” This is normal and expected. Here’s what you’ll see, why Google shows it, and why it’s safe in your case. Please read this before you start.
The short version: You are using your ownprivate app, in your own Google account, approved by exactly one person — you — to let your own assistant reach your own calendar, contacts, or files. Google’s warnings are aimed at public apps that thousands of strangers might use. Because yours is private to you, the warnings don’t apply the way they sound — there is no one to be “unsafe” toward but yourself.
Good news: it’s the same app you already set up
These tasks reuse the same Google project and app you created when you connected email. You don’t need to make a new one, and you don’t need to re-publish anything. Each task just turns on one more Google service (for example, the Calendar API) and asks you to approve one new permission.
What you’ll see, and when
After you paste your Client ID and Secret and click Connect Google, Google shows, in order:
- “Google hasn’t verified this app.” A full-page warning. There’s a small Advanced link — click it, then click “Go to launchmy.ai (unsafe).” Yes, it really says “unsafe.” It isn’t — it’s your app.
- The permissions screen — it names the exact access you’re granting (for example, “See your calendars” for read-only, or “See, edit, and delete” for read & write). Approve it to continue.
Read-only vs. read & write
When you choose a read-only task, the permission Google grants physically cannot change anything — your assistant can look but not touch. A read & write task grants the ability to make changes (add a calendar event, save a file). Pick the level you’re comfortable with; you can always start read-only and upgrade later.
You’re always in control
The access lives on your server, tied to your Google account. You can revoke it any time at myaccount.google.com/permissions, and we never keep a copy of your login — it’s handed to your assistant once and then discarded from our side.
Who’s responsible for what your assistant does
You are. With read & write access, your assistant can create, change, and permanently delete the data in the service you connect — acting on its own, using your account. Assistants can make mistakes. LaunchMy.ai gives you the tools but does not operate, direct, or monitor your assistant, so you are solely responsible for what it does, and we are not liable for any data that’s changed, deleted, or lost. Keep your own backups of anything important, grant only the access you’re comfortable with (read-only where you can), and see the full Terms of Service for the details.