Security & data practices
Engagement Board helps YouTube and Instagram creators manage, analyze, and respond to comments. This page explains, in plain language, exactly which Google and Instagram permissions we request and why, what we store, and how we protect and delete the data from the accounts you connect.
🔒 Encrypted
✋ You stay in control
🗑️ Delete on demand
What happens when you connect a YouTube channel
- 1
Choose your Google account
You’re sent to Google’s own secure sign-in page. Pick the account that owns your YouTube channel — we never see your Google password.
- 2
Review the permissions Google shows you
Google lists exactly what you’re granting. The section below explains each permission and why we ask for it.
- 3
Click “Continue”
Google returns you to Engagement Board and hands us an access token, which we encrypt before storing.
- 4
Change your mind anytime
Disconnect from Settings → Integrations, or revoke access directly in your Google account — either one cuts off our access immediately.
What happens when you connect an Instagram account
- 1
Log in with Instagram
You’re sent to Instagram’s own login page. Sign in to your Instagram professional account — we never see your Instagram password.
- 2
Review the permissions Instagram shows you
Instagram lists what you’re granting. The Instagram section below explains each permission and why we ask for it.
- 3
Confirm
Instagram returns you to Engagement Board and hands us an access token, which we encrypt before storing.
- 4
Change your mind anytime
Disconnect from Settings → Integrations, or remove Engagement Board in Instagram under Settings → Website permissions → Apps and websites. Either one ends our access and deletes the Instagram data we store for that account.
Which Google APIs & permissions we use — and why
We request the minimum permissions (“scopes”) needed for the features you use. Here is every scope we request and the reason for it:
| Permission | What it lets us do |
|---|---|
youtube.force-sslSensitive | Read your comments, and — only when you approve an action — post replies, moderate comments, and update your own videos, thumbnails, and channel details. Google classifies this permission as sensitive, so it is reviewed as part of Google’s OAuth verification. |
yt-analytics.readonlyRead-only | Read your channel’s analytics (such as views and engagement) to power your dashboards. We never modify analytics. |
Why the write permission? Replying to comments, moderating, and updating your own content are core features, and the read-only YouTube permission cannot perform those actions. Because that capability can write to your channel, Google classifies youtube.force-ssl as a “sensitive” scope and requires an official verification review before an app may request it. Every write stays gated behind an action you take in the product — we never reply, moderate, or edit on your behalf automatically.
Which Instagram permissions we use — and why
We use the Instagram API with Instagram Login, provided by Meta Platforms, Inc. Here is every Instagram permission we request and the reason for it:
| Permission | What it lets us do |
|---|---|
instagram_business_basic | Read your account ID, username, account type, profile picture, follower and media counts, and your posts and reels, so we can connect the account and show your media. |
instagram_business_manage_comments | Read the comments on your own media and — only when you take the action — reply to, hide, or delete them. |
instagram_business_manage_insights | Read your account and post insights, including aggregate follower and engaged-audience demographics, for your analytics and for any Media Kit you create. |
We never post new content to your Instagram account, and we do not request access to your direct messages.
What data we access and store
- OAuth access & refresh tokens for your connected Google/YouTube account (encrypted).
- Your channel ID, channel title, and public channel statistics.
- Comments and comment threads on your videos, and video metadata.
- Caption tracks for your videos, where you use caption features.
- Channel analytics from YouTube Analytics.
- The access token for your connected Instagram account (encrypted).
- Your Instagram account ID, username, account type, profile picture, and follower and media counts.
- Your Instagram posts and reels, and the comments on them, including each commenter’s username and Instagram-scoped ID.
- Account and post insights from Instagram, including aggregate audience demographics. We never receive the identity of individual followers.
- Derived data we generate to power features: sentiment scores, intent labels, text embeddings for finding similar past replies, suggested replies, and content ideas.
How we protect it
Encryption at rest
Encryption in transit
Least-privilege access
Access controls
Disconnecting & deleting your data
Disconnect a channel and we revoke the OAuth grant with Google and delete that channel’s stored data — tokens, comments, videos, sentiment data, embeddings, and drafts.
Disconnect an Instagram account in Settings → Integrations, or remove Engagement Board in Instagram under Settings → Website permissions → Apps and websites, and we delete that account’s stored data — the access token, media, comments and commenter details, insights, sentiment data, embeddings, drafts, and Media Kits. Instagram has no API for an app to revoke its own access, so if you disconnect in Engagement Board, Engagement Board stays listed in your Instagram settings until you remove it there.
Delete your account in Settings → Privacy & Security → Danger Zone → Delete Account and we revoke your YouTube grant(s) with Google, delete your Instagram tokens, hard-delete your personal and content data, and anonymize your account record. We retain billing and cost records required for accounting and tax compliance, linked to the anonymized account record. Our Privacy Policy lists what we keep.
You can also independently review or remove Engagement Board’s access at any time from your Google account at myaccount.google.com/permissions.
Who we share data with
We do not sell your data, use it for advertising, or use your content to train generalized AI models. We share data with service providers that help us run the product, under confidentiality and data-protection obligations, and with people you choose to share it with:
- Google / Firebase — authentication and the YouTube API Services.
- Meta Platforms — the Instagram API with Instagram Login, for accounts you connect.
- OpenAI — YouTube and Instagram comment text and related context, for sentiment scoring, intent labels, reply drafts, embeddings, clustering for content ideas, voice tuning, and YouTube analysis tools (Gap Analysis and channel previews). Your replies, survey answers, and video transcript excerpts may also be sent. Sentiment scoring runs automatically on imported comments unless you turn it off. Our Privacy Policy has the details.
- Stripe — payment processing.
- Google Cloud — hosting and storage.
- Resend — transactional email.
Media Kits. If you create a Media Kit for an Instagram account, its page shows your username, profile picture, stats, selected posts, and aggregate audience demographics at a public, unguessable URL that you control. Anyone with the link can view it without signing in, and you can revoke it at any time.
The verification review
As part of Google’s requirements for the sensitive youtube.force-ssl permission, Engagement Board has completed Google’s OAuth verification review. Google reviewed our OAuth consent flow, our privacy policy, and how each requested scope is used, and confirmed our handling of your data complies with the Google API Services User Data Policy, including its Limited Use requirements. We keep our verification current on Google’s required schedule.
Questions?
We’re happy to answer anything about how we handle your data. Email info@secondlifesoftware.com.
See also our Privacy Policy and Terms of Service.