Ajons MCP Server privacy policy
Product: Ajons MCP Server · Operator: Ajons Web Tools · Service: https://mcp.ajonswebtools.com · Last updated: 7 November 2026
Ajons MCP Server lets you manage your own YouTube channels from Claude. You sign in here, connect your channels with Google, and add the service to Claude as a connector. You (or your clients, via an invite link you create) connect a channel by signing in directly on Google’s page — we never see or collect Google passwords. This policy explains what Google and YouTube data we access, what we store, how we protect it, who it is shared with, how long it is kept and how you can revoke access and delete it.
Google and YouTube data we access
When you connect a channel, you grant these Google permissions:
- YouTube (youtube.force-ssl) — to read and manage your channel: videos and their metadata (titles, descriptions, tags, categories, privacy and scheduling, thumbnails, localizations), playlists, channel settings and sections, comments, and caption tracks.
- YouTube Analytics (yt-analytics.readonly) — read-only reports about your channel: views, watch time, audience retention, traffic sources, demographics and geography, and the YouTube Reporting API reports for thumbnail impressions and click-through rate.
- Basic profile (openid, email, profile) — the Google account's identifier, email address and name, so we know which Google account authorized which channel.
We only access the channels you connect, and only to answer the requests you make through Claude and to keep the information described below up to date.
What we store
- Your account: email, optional name, a salted scrypt hash of your password, and sign-in and security events with IP addresses.
- Google authorizations: for each Google account you connect, its Google account identifier, email and name, and an OAuth refresh token (encrypted, see below).
- Channel information: each connected channel's ID, title, handle and public statistics; if connected via a client invite, the client name you provided.
- Change history: a log of every change made through the service with the previous and new values (for example titles, descriptions, tags, settings, playlist entries, comment replies and edits), plus the previous thumbnail images, caption files, and banner, watermark and playlist images uploaded through the service, so you can review and undo changes.
- Reports and activity data: the daily thumbnail-impression reports YouTube provides for your channels, hourly snapshots of your videos' public view, like and comment counts with their titles and upload/publish times (used to show recent activity), and copies of caption text you have downloaded (so repeat requests don't use quota).
- Your settings: description snippets and channel rules you save, and previews of bulk edits you ask for (deleted after they expire unless used for an edit).
- Usage records: a record of each YouTube API call made on your behalf, for quota limits.
- Connection credentials for Claude: stored only as one-way hashes.
- Billing records: your plan, payment dates, amounts, currency and the payment provider's reference. Card and bank details are handled by Stripe or Paystack and never reach this service.
- Email records: which service emails we sent you (confirmation, password reset, receipts, reminders) and whether delivery succeeded.
Other YouTube Analytics reports and the comments, playlists and other data you ask Claude about are fetched from Google when you ask and are not stored, except where they become part of the change history above.
Aggregated and derived data
We calculate a few figures from your own channel's data, only to show them back to you:
- totals and impression-weighted click-through rates, and estimated clicks, from YouTube's daily thumbnail-impression reports;
- view, like and comment changes over the last hour, day, two days and week, and the publish times that worked best, from the hourly public-count snapshots;
- a readable transcript (duplicates removed, with time markers) from a caption file;
- the latest day YouTube Analytics has data for, and your API quota usage.
Derived figures are calculated per channel for the account that connected it and are never combined across users, sold or shared. The only service-wide figures we keep are counts of API calls and quota units, used to stay within YouTube's quota.
How each type of data is used
| Data | Used for |
|---|---|
| Google account identifier, email and name | Recognising which Google account authorized which channel, and showing it on your dashboard. |
| OAuth refresh token | Calling the YouTube APIs on your behalf when you ask, and for the scheduled report and snapshot updates of your connected channels. |
| Channel and video data (metadata, playlists, comments, captions, settings) | Answering your requests in Claude and making the changes you ask for, after checking the item belongs to your channel. |
| YouTube Analytics and Reporting data | Showing your channel's performance when you ask (impressions, click-through rate, views, watch time, retention, traffic sources, audience). |
| Hourly public-count snapshots | Showing recent activity and best publish times. |
| Change history (previous and new values, previous thumbnails and captions) | Letting you review what was changed and undo it. |
| Caption text copies | Answering repeat transcript requests without using quota again. |
| API call records | Quota limits, abuse prevention and troubleshooting. |
| Account, sign-in, billing and email records | Running your account, security, payments and service emails. |
Limited Use of Google user data
Ajons MCP Server's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- Google user data is used only to provide and improve the user-facing features of Ajons MCP Server that you use, as described in this policy.
- Google user data is not sold, and is not transferred to advertisers, data brokers, information resellers or other unrelated third parties.
- Google user data is not used for advertising, including targeted, personalized, retargeted or interest-based advertising.
- Google user data is not used to determine creditworthiness or for lending, and is not used to develop, improve or train generalized artificial intelligence or machine-learning models.
- Google user data is transferred only as needed to provide the features you use (see the next section), to comply with law, or for security, or as part of a merger, acquisition or sale of the service after notifying you.
- No person reads your Google user data unless you ask us to (for example in a support request), it is needed to investigate abuse or a security issue, or the law requires it.
This service uses YouTube API Services; see the YouTube Terms of Service and the Google Privacy Policy.
How and with whom data is shared
We share data only with these categories of service providers, and only as needed to provide the service:
- Your AI assistant — Anthropic (Claude): when you use this service from Claude, the channel information you ask for is returned to your own Claude conversation, where Anthropic processes it under its own terms and privacy policy. This happens only at your request.
- Hosting — Contabo: the server that runs the service and stores its database, including the stored data described above.
- Google: requests to the YouTube Data, YouTube Analytics and YouTube Reporting APIs made on your behalf.
- Email delivery — Resend: your email address and the content of service emails; the only Google user data in an email is a connected channel's name (for example in a reminder to reconnect it).
- Payments — Stripe and Paystack: your account email and payment details if you subscribe. They receive no Google user data.
We do not share data with other users, advertisers or data brokers. We disclose data otherwise only if required by law or to protect the security of the service and its users.
Data Security and Protection
- Encryption in transit: the website and the Claude connector are served only over HTTPS (TLS 1.2 or 1.3); plain HTTP is redirected to HTTPS and browsers are told to use HTTPS only (HSTS). All calls to Google APIs use HTTPS.
- Encryption at rest: Google OAuth refresh tokens are encrypted before they are stored (Fernet: AES-128 with HMAC-SHA256), with a key kept outside the database. Passwords are stored only as salted scrypt hashes. Sign-in sessions, Claude connection tokens and access tokens, and email confirmation and password-reset links are stored only as SHA-256 hashes, so the stored values cannot be used to sign in.
- Access controls: every stored record belongs to one account, and every request is limited to the signed-in user's own data; changes to a video, comment, playlist or caption are checked against the channel that owns it before anything is sent to YouTube. Sign-in is rate-limited, forms are protected against cross-site request forgery, and session cookies are secure and HTTP-only. Administrator sign-in requires a password and a time-based authenticator code.
- Secrets management: encryption keys, OAuth client secrets and other credentials are kept in server configuration files readable only by the service and its operator, and are excluded from source control; they are never written into source code or a public repository.
- Server and database access: the database accepts connections only from the server itself, using a dedicated database account for this service. The application runs as its own unprivileged system user with a restricted, sandboxed service configuration, and is reachable from the internet only through the HTTPS web server.
- Logging and audit records: we keep a security log of sign-ins and account changes, a record of every change made to your channels, and a record of API calls. Logs never contain passwords or complete tokens, and web-server logs omit URL query strings.
- Software maintenance: the server's operating system installs security updates automatically, and the application's open-source libraries are checked every day against published vulnerability advisories so that affected libraries can be updated.
- Your controls: you can revoke Google access, disconnect channels and Claude connections, and delete your account and data at any time, as described below.
No system is perfectly secure. If we learn of a security incident affecting your data, we will notify you as required by law.
Data retention and deletion
- Data about a connected channel (including its change history and reports) is kept while the channel is connected, so you can review and undo changes.
- Hourly public-count snapshots are deleted after 120 days.
- Encrypted thumbnail rollback snapshots created through inline image uploads are deleted after 120 days; the associated change-history metadata remains while the channel is connected.
- When you disconnect a channel, or its Google authorization is revoked or stops working, everything stored about that channel is deleted within 30 days.
- When you delete your account, your Google authorizations are revoked at Google and your account, connected channels, refresh tokens, Claude connections, change history, reports and caption copies are deleted immediately. Payment records (amounts, dates and provider references) are kept where needed for accounting and tax law, and API usage counts are kept without any link to your account.
- Expired sign-in sessions, links and temporary records are deleted automatically.
How to revoke access and delete your data
- Revoke Google access: at any time at Google Account → Security → Third-party connections. The service then stops working with that account's channels, and their stored data is deleted within 30 days.
- Disconnect a channel: on your dashboard. When no other connected channel uses the same Google authorization, it is revoked at Google straight away.
- Disconnect Claude: on your dashboard, or by removing the connector in Claude.
- Delete your account: on the Account page (you confirm with your email and password). This revokes Google access and deletes your data as described above.
- If you connected a channel via a client invite link, you can revoke access at myaccount.google.com → Security → Third-party access, or ask us to delete your data using the contact below.
- You can also ask us to delete your data or tell you what we hold by contacting us below.
Changes to this policy
When this policy changes, we update it on this page and change the date at the top.
Contact
Questions or deletion requests: support@ajonswebtools.com.