1. About This Policy
This policy explains the privacy practices specific to the Starbuzz MCP connector for Claude — an Instagram and YouTube engagement-rate lookup tool operated by Krisattva Private Limited ("Starbuzz", "we", "us") and made available through Anthropic's Claude connector directory.
It supplements, and does not replace, our main Privacy Policy, which governs the Starbuzz.ai website and platform and takes precedence over this summary where the two overlap.
Questions about this connector can be sent to contact@starbuzz.ai. We respond within one business day.
2. What This Connector Does
Starbuzz looks up Instagram and YouTube engagement rate data through natural conversation in Claude, retrieving results from Starbuzz.ai's engagement-rate service.
The connector exposes three read-only tools — get_instagram_engagement_rate, get_youtube_engagement_rate, and get_credit_balance. The credit-balance tool takes no parameters, checks only your own account's credit ledger, calls no external service, and does not use a credit. None of the tools post content, message creators, access private accounts, or modify anything in your Starbuzz account or on any social platform.
Starbuzz does not read Claude's conversation history, memory, or any other data beyond the single username you ask it to look up. A lookup call takes exactly one parameter and touches nothing else in the conversation.
3. Signing In and Tokens
Connecting uses OAuth 2.1 with the CIMD (Client ID Metadata Document) client-authentication mode. You sign in directly with Starbuzz on our own sign-in page — your password is never shared with Claude, never passes through Claude's systems, and is never stored anywhere outside Starbuzz.
Signing in or completing signup on that page is the act of granting access — there is no separate "Allow" screen afterwards. New signups must verify their email with a 6-digit one-time code, valid for 10 minutes, before the account is created.
Starbuzz requests a single permission scope, er:read, allowing engagement-rate lookups, credit-balance checks, and credit deduction. It does not permit account setting changes, campaign data access, or messaging, and it is checked on every tool call, not only at sign-in.
If you forget your password, a Forgot password? link on the sign-in page sends a 6-digit one-time code (10-minute validity) to your email — the response looks identical whether or not that email is registered, so the reset flow itself never reveals who has an account. Requesting or submitting a code is limited to 3 attempts per hour per email address. You can optionally sign out of every other active session as part of the reset, which also revokes every stored MCP refresh token for your account immediately, and a confirmation email is sent once your password has changed.
| Credential | Lifetime | Storage |
|---|---|---|
| Authorization code | 5 minutes, single-use | One-way hash |
| Access token | 1 hour | Signed; not stored server-side |
| Refresh token | 30 days; rotates on each use | One-way hash |
| One-time verification code (signup / password reset) | 10 minutes | Stored briefly against the email being verified; marked used immediately after signup or reset |
To disconnect, remove the connector in Claude under Settings → Connectors. Claude immediately stops sending your tokens. If you need tokens invalidated sooner — for example, a suspected compromised account — contact contact@starbuzz.ai and we will invalidate them directly.
4. Information We Collect
| Category | What it includes |
|---|---|
| Account data | Name, email, and a bcrypt-hashed password, held as part of your Starbuzz account on the main platform |
| Query records | For each engagement-rate lookup: the queried username, the platform, and the resulting metrics (display name, post count, average comments, average likes, average views, engagement rate), tied to your Starbuzz user ID. Credit-balance checks are not logged as query records, since they never touch the upstream service |
| Authorization artefacts | Authorization codes and refresh tokens, stored only as one-way hashes |
| One-time verification codes | Signup, password-reset, and re-verification codes, stored briefly against the email they were sent to |
Starbuzz does not sell user data, and does not use it for advertising or profiling.
5. How We Use This Information
A typical lookup follows this path:
- You ask Claude a question, e.g. "What's the engagement rate for @creator on Instagram?"
- Claude calls Starbuzz with an access token and the username.
- Starbuzz validates the request — rate limit, token signature and expiry, and the
er:readscope. - Starbuzz reserves one credit from your balance, atomically.
- Starbuzz queries its upstream engagement-rate service, with a 30-second timeout.
- Starbuzz returns the result to Claude, including your remaining credit balance — or, on failure, an error with the credit refunded.
- Claude presents the result in the conversation.
- Starbuzz logs the query against your account.
Query logging exists for usage visibility and abuse prevention. New accounts created through the connector receive a one-time trial credit allowance (10 credits by default) — or, if you already had a Starbuzz account before ever connecting through Claude, the same one-time allowance is granted automatically the first time you sign in through the connector. This allowance does not refill or reset on any schedule. Once your balance reaches zero, requests are rejected with nothing deducted, and every response includes your remaining balance so you can check it any time via get_credit_balance or the low-balance warning that appears once you have 10 credits or fewer. Failed lookups are never charged — a credit is reserved before the work begins and refunded if the upstream request fails or times out.
6. Data About Creators You Look Up
Engagement lookups necessarily involve metrics about third parties — the creators being looked up — who are not Starbuzz users. Starbuzz processes this data only through the partnerships described in Section 7, only in aggregate performance form, and only for the legitimate business purpose of creator evaluation for marketing partnerships.
No contact details, private content, or personal identifiers beyond the public account name are retrieved or retained. If you are a creator and wish to enquire about data held in relation to your account, contact contact@starbuzz.ai.
7. Where Creator Data Comes From
Starbuzz's engagement-rate data is sourced through official partnerships: Instagram data via Meta, and YouTube data via Google. The MCP server itself does not call Meta or Google directly — it calls Starbuzz's own internal engagement-rate service, which holds and executes those partner integrations. Starbuzz does not scrape social media platforms.
Starbuzz never accesses private accounts, direct messages, unpublished content, login credentials, or any data outside these permitted API channels.
8. Security Measures
- Credential handling — passwords hashed with bcrypt; authorization codes, refresh tokens, and one-time verification codes stored only as hashes or short-lived values, never as reusable plaintext secrets.
- PKCE on every authorization — a cryptographic proof ties each token exchange to the request that started it.
- Client verification via CIMD — the requesting client's return address is validated against its own published metadata document before we trust it.
- Token isolation — access tokens are signed with a secret dedicated to this connector and carry a distinct audience marker, so a token issued here cannot be used against the main Starbuzz application, or vice versa.
- No machine-to-machine backdoor — the
client_credentialsgrant is explicitly rejected; every access path requires a real person to sign in. - Single-use, short-lived codes that expire in 5 minutes and are marked consumed on first use.
- Refresh token rotation — each refresh retires the previous refresh token and issues a new one. A password reset with "sign out of all other sessions" enabled also revokes every stored refresh token for that account immediately.
- Scope enforcement per call — the
er:readscope is checked on every tool invocation, not only at sign-in. - Atomic credit control — credit reservation is a single locked database operation.
- Per-IP rate limiting on the connector endpoint, plus a separate per-email rate limit (3 per hour) on password-reset requests to prevent inbox-spam and OTP brute-forcing.
- Account-existence privacy on password reset — requesting a reset code returns the same response whether or not the email is registered; mail is only actually sent when a matching account exists.
- Allow-listed outbound calls to a fixed set of upstream hostnames, with enforced timeouts.
- Safe error handling — internal errors are logged server-side only; you receive generic, safe-to-retry messages rather than stack traces or database errors.
9. Data Retention
Authentication artefacts expire on the schedule in Section 3. Query records and used one-time verification codes (signup, password reset, and re-verification) do not currently have an automatic retention limit or scheduled cleanup — they are retained until you request deletion, as described in Section 10.
10. Your Rights
You can request access to, correction of, or deletion of your Starbuzz account data at any time by contacting contact@starbuzz.ai.
Account deactivation or deletion on the main Starbuzz platform is a soft action by default — your account is flagged inactive or deleted, with sign-in blocked, rather than an immediate hard-delete of every associated row. If you need query-log records or other associated data permanently purged rather than deactivated, say so explicitly in your request.
Our full Privacy Policy and Terms of Service set out these rights in detail and take precedence over this summary.
11. Changes and Contact
We may update this policy from time to time. When we make material changes, we will update the date at the top and notify you through the product or by email.
Krisattva Private Limited
contact@starbuzz.ai
Privacy Policy: starbuzz.ai/app-privacy
Terms of Service: starbuzz.ai/terms-and-conditions