Effective Date: October 27, 2026
This Privacy Policy describes how MetaMethod collects, uses, and protects your information when you use our dashboard and associated services.
When you create an account, you provide information such as a username, email, and password. Optionally, users may provide other details that may contain sensitive personal information. Dashboard contributions such as public logs and profile content may be visible to others.
We may disclose user information to comply with legal obligations, court orders, subpoenas, or enforce our rights and user protections.
We retain your data for as long as your account is active or needed for services. You may request account deletion at any time. Some anonymized data may be retained for auditing or service enhancement.
We may use your mailing address that is provided for for identity verification, compliance checks, or for confirming the legitimacy of submitted details. Your address is not shared with third parties unless legally required or essential for dispute resolution or fraud prevention.
We may revise this policy from time to time. The effective date will always be updated at the top. Substantial changes will be announced on the dashboard or via email.
MetaMethod Content Program uses YouTube API Services for the verified dashboard owner's MetaMethod channel connection. Google handles sign-in and permission approval; the dashboard does not receive the owner's Google password. The connection requests read-only YouTube and YouTube Analytics permissions. It does not request video upload, edit or deletion permissions or monetary analytics access.
When an authorized Content Program manager requests a report for an existing dashboard upload, we verify the video, channel and publication time with YouTube. We request daily views and engaged views for 30 calendar dates, beginning on the publication date in America/Los_Angeles. Reports show the period, retrieval time and available daily values, including missing-data notices. Manual reports are displayed for the request. When the owner enables automatic snapshots, the dashboard also collects and refreshes these daily values after the reporting window closes. Stored snapshots remain provisional, identify their retrieval time and missing dates, and do not initiate payments.
We use Google and YouTube information only to operate and secure this connection, verify authorization and channel ownership, retrieve requested reports and owner-enabled first-30-day snapshots, and process disconnection and deletion requests. These specific purposes and retention terms apply to Google and YouTube information instead of the policy's general improvement, personalization and anonymized-retention provisions. We do not sell Google or YouTube user data or use it for advertising.
We store encrypted access and refresh tokens, granted scopes, token expiry, connection status and timing information, session-security records, and short-lived report-request timestamps used to limit repeated requests. When automatic storage is enabled, we also store encrypted daily report values and their video, work, reporting-window and retrieval details. The encryption key is held separately on the dashboard server. The browser receives status and requested report results, not stored Google tokens. A secure session cookie supports dashboard login.
Connection controls are restricted to the verified dashboard owner. Reports and stored snapshots are available to signed-in accounts with current Content Program management authority, including the existing administrator override. Authorized infrastructure operators and hosting/database service providers may process the stored information to operate and secure the dashboard. DigitalOcean hosts the dashboard and the database recovery service. Google receives the requests needed for authorization, channel verification, reports, token refresh and revocation. Google's practices are described at https://policies.google.com/privacy.
After an accepted Disconnect request, the dashboard removes stored connection credentials from its live database, makes stored analytics unavailable, starts their deletion, and immediately asks Google to revoke the grant. If Google's response is uncertain, the page asks the owner to remove access in the Google Account and retains a nonsecret status record to prevent accidental reconnection. Local deletion does not itself confirm Google revocation. A currently active connection operation may require the owner to retry Disconnect after it finishes.
DigitalOcean provides a seven-day database recovery window. Recovery copies can contain encrypted connection records and analytics removed from the live database. Stored snapshots are retained for at most 12 months after their reporting window closes. The service checks authorization daily and refreshes video availability and stored values at least every 30 days; snapshots that cannot be refreshed expire and are deleted instead of remaining available. Missing or expired data is not treated as zero. Nonsecret disconnection/security records are retained to prevent accidental reconnection and support secure operation; short-lived report-rate-limit records are cleaned up during maintenance.
The dashboard periodically checks authorization for the permitted channel. Confirmed invalid authorization triggers credential removal and stored-analytics deletion. Failed verification suspends use; if no successful verification occurs for seven days, the next maintenance pass removes the credentials, normally within one further hour while the service and dependencies are available. Startup performs overdue cleanup before enabling the connection. Service, database or configuration outages can delay physical deletion.
The owner can delete stored analytics and stop automatic collection from the protected YouTube Analytics page. Deletion makes the data unavailable immediately and bounded maintenance finishes removal; outages can delay physical deletion. The owner can also disconnect from that page or remove access through Google's account permissions at https://security.google.com/settings/security/permissions. Google's instructions are available at https://support.google.com/accounts/answer/13533235?hl=en. Disconnection does not delete videos or other information held by YouTube. For deletion requests or questions about MetaMethod's handling, contact [email protected].
MetaMethod uses Meta’s APIs for the verified Dashboard owner’s @scproleplayofficial comments connection. Meta handles sign-in and permission approval; we do not receive Facebook or Instagram passwords.
The integration retrieves account and Page identifiers and usernames to verify the authorized association. When the owner requests a report, it reads bounded comments and replies. It exposes no publishing, replying, hiding, deletion or messaging operations, although Meta’s comment-management permission is broader.
For the business-owned SCP: Roleplay Page, the Facebook connection requests business_management to discover and verify the approved Page/account association. Meta’s permission permits Business Manager reads and writes, but this connector uses only fixed read-only requests and exposes no business, advertising, Page or account changes.
Access tokens are encrypted on the server. The verified long-lived Facebook User token is retained encrypted alongside the Page token only to verify authorization for the approved Page/account link and to read @scproleplayofficial’s posts, comments and replies for bounded reports. Short-lived Facebook User tokens are transient and are not retained. Both retained Facebook tokens are deleted on disconnect and share the same local expiry limit. Comment and reply text is processed in memory and displayed to the owner, not saved by this integration. Account/Page pins and limited authorization and rate-control state are retained to prevent unintended relinking and secure access. Authorized hosting and database operators may process stored connection information to operate and secure the service.
Disconnect deletes local tokens and stops reads; it does not delete Instagram content or revoke Meta’s grant. Remove that grant separately in Meta account settings. The Facebook connection has a finite local authorization period, normally at most about 60 days, and requires reconnection when it expires or access is revoked. Connecting Instagram through Facebook alone does not enable unattended collection or delegated Pixel/MCP access.
Separately, the verified owner may explicitly authorize a private Pixel connection to receive bounded post identifiers and links and comment/reply identifiers, text and timestamps for requested reports. Meta access tokens are never returned. This read-only Pixel grant is separate from Discord, cannot outlast the current Instagram authorization through Facebook, and stops on revocation, disconnect or expiry; reconnecting through Facebook does not restore it. Access tokens last at most 15 minutes; rotating refresh access ends at the original approved connection deadline displayed at consent. This integration does not save report content or collect it automatically. Reports delivered to Pixel are processed in the connected assistant conversation; publishing a report elsewhere requires the owner’s authorization.
An explicit zero expiry from Meta is treated as an unknown provider expiry, not permanent authorization. Local authorization lasts at most 60 days and is shortened by earlier verified expiry. Token validity, permissions and the approved account association are rechecked before reading comments.
For deletion requests or questions, contact [email protected].
For any privacy-related inquiries or data requests, please contact us at [email protected].