Privacy Policy
Effective date: November 3, 2026
This Privacy Policy explains how EngagementBoard LLC (“Engagement Board,” “we,” “us,” or “our”) collects, uses, stores, shares, and deletes information when you use the Engagement Board application and website (the “Service”). Engagement Board helps creators manage, analyze, and respond to comments and audience engagement on the accounts they connect — YouTube channels and Instagram professional accounts — with AI assistance.
1. YouTube API Services
Engagement Board uses YouTube API Services. By connecting your YouTube account, you agree to be bound by the YouTube Terms of Service. Your use of data obtained through these services is also governed by the Google Privacy Policy.
You can revoke Engagement Board’s access to your YouTube and Google data at any time via the Google security settings page: https://myaccount.google.com/permissions. You can also disconnect a channel from within Engagement Board (Settings → Integrations), which deletes the channel’s data from our systems as described in Section 8.
Engagement Board’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
2. Instagram API and Meta Platforms
Engagement Board uses the Instagram API with Instagram Login, provided by Meta Platforms, Inc. By connecting an Instagram professional account you also agree to the Instagram Terms of Use, and Meta’s handling of your data is governed by the Meta Privacy Policy.
We request only the permissions the features you use require: reading your profile and media, reading comments on your own media and, when you direct us to, replying to, hiding, or deleting them, and reading your account insights. We never post new content to your account, and we do not request access to your direct messages.
You can remove Engagement Board’s access at any time from within Instagram (Settings → Website permissions → Apps and websites), or by disconnecting the account in Engagement Board (Settings → Integrations). Either route ends our access and deletes the Instagram data we store for that account, as described in Section 8. Step-by-step instructions live on our data deletion page.
3. Information we collect
Account information. When you sign up we collect your name, email address, and authentication identifiers through our authentication provider. If you choose to provide them, we also store optional profile details (such as pronouns, birthday, and contact preferences). You are not required to provide optional sensitive details to use the Service.
YouTube data (accessed with your authorization). When you connect a YouTube channel, we access and store, on your behalf:
- OAuth access and refresh tokens for your Google/YouTube account (encrypted at rest);
- your channel ID, channel title, and public channel statistics;
- comments and comment threads on your videos, and metadata about your videos;
- caption tracks for your videos, where you use caption-related features;
- channel analytics (e.g., views and engagement metrics) via YouTube Analytics.
Instagram data (accessed with your authorization). When you connect an Instagram professional account, we access and store, on your behalf:
- the long-lived access token for that Instagram account (encrypted at rest);
- your Instagram account ID, username, account type, profile picture, follower count, and media count;
- your media (posts and reels): media IDs, captions, permalinks, thumbnails, media type, timestamps, and engagement counts;
- comments on your media, including the comment text, timestamp, like count, and the commenter’s Instagram username and Instagram-scoped user ID — people who comment on your posts are not Engagement Board users, and we store this only so you can read and reply to them in Engagement Board;
- account insights, including aggregate follower and engaged-audience demographics (age ranges, gender, city, and country). Meta provides these only in aggregate form; we never receive or store the identity of individual followers.
Derived data. To power features, we generate derived data such as comment sentiment scores, intent labels, text embeddings used to find similar past replies, suggested replies, content ideas, and engagement analytics.
Billing data. If you subscribe to a paid plan, our payment processor collects and processes your payment details. We retain subscription status, credit balances, and usage records.
5. How we use information
- To display, organize, and analyze your YouTube comments and channel engagement.
- To display, organize, and analyze the comments on your Instagram media, and to show you audience insights (including aggregate follower demographics) for your Instagram account.
- To generate AI-assisted reply suggestions, sentiment signals, and content recommendations.
- To post, reply to, moderate, update, or delete comments on your behalf only when you direct us to(for example, by approving a reply or applying a moderation action).
- To update video and channel metadata or thumbnails when you explicitly request it.
- To build a Media Kit for an Instagram account, if you choose to create one, so you can share your account’s stats with people you select (see Section 7).
- To operate, secure, maintain, and improve the Service, and to provide customer support.
- To process payments and manage subscriptions.
We do not use YouTube or Instagram data for advertising, and we do not sell your personal information, YouTube data, or Instagram data. We do not use your data or content to train generalized AI/ML models.
6. AI processing
Our AI provider is OpenAI. We send it comment text and related context from both YouTube and Instagram, as follows:
- Sentiment scoring and intent labels. Comment text, with the title or caption of the video or post it belongs to, is sent automatically when comments are imported or arrive, not only when you take an action. You can stop this by turning off Sentiment Analysis in your AI Preferences.
- Reply drafts. When you ask for a suggested reply, we send the comment text, the title or caption of the video or post, and your voice settings. If you enable Use Commenter Name, the commenter’s username or display name is also sent. Unless you turn off Use Similar Replies, similar past comments and your replies to them are also sent.
- Embeddings. Comment text is sent to create text embeddings, which we use to find similar past replies when drafting a reply.
- Voice tuning. When you scan your reply history or fill in the voice survey, your past replies, the comments they answered, and your survey answers are sent to build your voice profile.
- Clustering for content ideas. When you use content ideas, audience questions from your comments are sent to group them into topics and to generate ideas and post drafts from those topics.
- YouTube analysis tools. Gap Analysis and channel previews also send comment text and, for Gap Analysis, a transcript excerpt from the video. These tools are not available for Instagram.
People who comment on your posts are not Engagement Board users, and their comment text is included in the data above. We send only the data these features need. Our AI provider processes this data to return results to us and does not use it to train their models on our behalf. Replies are never posted without your approval.
8. Data retention and deletion
Ongoing retention of YouTube data. In line with the YouTube API Services Developer Policies, we do not keep stale copies of YouTube data. Stored YouTube data (such as videos and comments) is automatically refreshed from the YouTube API at least every 30 days, or else deleted from our systems. A daily process keeps your recent and active content current and removes older data that is not refreshed within that window. If your connection stops working (for example, access is revoked and not restored), the associated stored data is deleted after a short grace period.
Disconnecting a channel. When you disconnect a YouTube channel, we revoke the OAuth grant with Google and delete that channel’s stored data from our systems, including the OAuth tokens we hold, comments, videos, sentiment data, embeddings, drafts, and related records.
Ongoing retention of Instagram data. Stored Instagram data (media, captions, comments, and insights) is refreshed from the Instagram API on a rolling basis so that what you see reflects the account as it is now; data that is no longer available from Instagram is removed on the next refresh. If an Instagram connection stops working and is not restored, the associated stored data is deleted after a short grace period. We keep the connection record (your username, profile picture, follower count, and the encrypted token) so you can reconnect, until you disconnect the account.
Disconnecting an Instagram account. When you disconnect an Instagram account in Engagement Board (Settings → Integrations), or when you remove Engagement Board from your Instagram account settings, we delete that account’s stored data from our systems: the access token and connection record, your media and captions, the comments and commenter details we cached, account insights, sentiment data, embeddings, drafts, Media Kits, and related records.
Deleting your account. When you delete your account, we revoke your YouTube OAuth grant(s) with Google, hard-delete your personal and content data (profile, social handles, YouTube and Instagram tokens and content, Media Kits, sync state, notifications, and preferences), and anonymize your account record. We delete your authentication account with our auth provider. We retain billing and cost records (e.g., invoices, credit ledgers, usage counters), linked to the anonymized account record, as required for accounting, tax, and legal compliance.
What we keep. Deletion covers the data described above, not every record we hold. We keep:
- billing and cost records (subscription status, credit balances and ledgers, usage counters, and AI usage logs), for accounting, tax, and legal compliance. AI usage logs record token counts and cost, and can include a channel or Instagram account ID, but not comment text;
- a record that an Instagram removal or data deletion request was completed, without the account ID. For a data deletion request this holds the confirmation code and status, so the request can be confirmed later;
- server logs, which can include channel or Instagram account IDs, for security and troubleshooting.
Revoking at Google. We revoke Engagement Board’s access automatically when you disconnect a channel or delete your account. You can also review or remove access yourself at any time at https://myaccount.google.com/permissions.
Removing access at Instagram. The Instagram API has no server-side revoke endpoint, so removing Engagement Board under Instagram → Settings → Website permissions → Apps and websites is how you end our access there. Instagram notifies us when you do, and when we receive that notification we delete that account’s stored data, including the access token, as described above. If you disconnect in Engagement Board instead, we delete the same data, but Engagement Board stays listed in your Instagram settings until you remove it there.
How to request deletion. You can request deletion at any time by using the in-app account deletion control (Settings → Privacy & Security → Danger Zone → Delete Account), by following the steps on our data deletion page, or by emailing us at info@secondlifesoftware.com.
9. How we protect your data
We use industry-standard safeguards, including encryption in transit (TLS) and encryption of stored YouTube and Instagram access tokens at rest. Access to production data is restricted. No method of transmission or storage is completely secure, but we work to protect your information and review our practices regularly.
10. Your rights
Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. To exercise these rights, contact us at info@secondlifesoftware.com. We will respond consistent with applicable law (including the GDPR and CCPA/CPRA where they apply).
11. Children
The Service is not directed to children under 13 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal information from them.
12. Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version here and revise the “Effective date” above. Material changes will be communicated as required by law.
13. Contact us
EngagementBoard LLC
San Diego, CA, USA
Email: info@secondlifesoftware.com
This Policy is governed by the laws of the State of California, USA, without regard to conflict-of-laws principles.