Privacy Policy

This Privacy Policy explains how RankReactorAI, Inc. ("RankReactorAI," "we," "us") collects, uses, and discloses information about you when you use our website and services at https://www.rankreactor.ai.

RankReactorAI uses YouTube API Services so you can publish product-generated videos to your own YouTube channel, and the Blogger API so you can optionally publish RankReactorAI-generated articles to your own Blogger blogs. Use of those features is also subject to YouTube's Terms of Service and the Google Privacy Policy.

You can also optionally connect an AI assistant such as ChatGPT, Claude, Cursor, or Grok to one RankReactor project through our MCP server. That connection is described in the AI assistant section below.

Information we collect

When you contact us or sign up, we collect your name, company, work email, and any details you provide about your business and growth goals. When you connect your website, we access your site's public pages to power the RankReactorAI engine. If you connect Google (including YouTube or Blogger), we also receive the Google user data described below.

If you create a project API key or connect an AI assistant, we also collect the key record described below, the tool name and inputs needed to run each request, and any articles or videos those requests create.

How we use information

We use the information we collect to operate and improve our services, provide support, respond to inquiries, and communicate about our products. Google user data is used only as described in the Google sections of this policy.

If you connect an AI assistant, we use the project key and tool inputs only to authenticate that connection and to run the tools you asked for on that one project, as described below.

Google user data we access

You may optionally connect a Google account to RankReactorAI through Google OAuth. We request only the scopes needed for the features you turn on: YouTube upload, Blogger (manage Blogger account), and Google account email. We do not request unrelated Google scopes such as Drive or Gmail, and we do not request your Google password.

YouTube upload

For Connect YouTube, we request the YouTube Data API scope https://www.googleapis.com/auth/youtube.upload. That scope lets RankReactorAI upload videos to your YouTube channel. It does not grant full YouTube account management.

The Google user data involved is: (1) OAuth access and refresh tokens used to authenticate upload requests on your behalf; and (2) video metadata YouTube returns after an upload, such as video id, title, and status, so we can show you that the publish succeeded. We do not access unrelated Google account data.

Blogger

For optional Connect Blogger, we request the Blogger API scope https://www.googleapis.com/auth/blogger (manage Blogger account). That scope lets RankReactorAI auto-publish RankReactorAI-generated articles to Blogger blogs you own. It is used only for that publish feature.

The Google user data involved is: (1) OAuth access and refresh tokens used to authenticate publish requests on your behalf; and (2) publish-related blog and post metadata needed to create or update posts (for example blog id, post id, title, and status), so we can publish on your behalf and show you that the publish succeeded.

Google account email

We request https://www.googleapis.com/auth/userinfo.email (and related Google identity information as needed) to obtain your primary Google Account email so RankReactorAI can identify the signed-in user and account. This is self-explanatory identity use. We do not use this email for advertising, data sale, or to train unrelated AI or machine-learning models.

How we use Google user data

We use Google user data solely to operate the Google connections you enable:

YouTube — to authenticate with YouTube and to upload UGC-style videos that you request or that RankReactorAI generates to the YouTube channel you connect, and to provide, maintain, and improve that YouTube publish feature (for example, confirming upload success and reconnecting your channel if a token expires).

Blogger — to authenticate with Blogger and to publish RankReactorAI-generated articles to the Blogger blogs you connect, and to provide, maintain, and improve that Blogger publish feature (for example, confirming publish success and reconnecting if a token expires).

Google account email — to identify the signed-in user and associate Google connections with the correct RankReactorAI account.

We do not use Google user data for advertising, selling, data brokerage, credit or lending decisions, or to train unrelated AI or machine-learning models. We do not use this data to develop, improve, or train generalized or non-personalized AI/ML models.

Sharing of Google user data

We do not sell Google user data. We do not transfer Google user data to third parties for advertising, retargeting, or data brokerage.

We share Google user data only as needed to operate the Google features you enable: with Google / YouTube to perform the upload you requested; with Google / Blogger to perform the article publish you requested; and with processors who help us host and operate RankReactorAI under confidentiality and similar protections. Those processors are not permitted to use Google user data for their own purposes.

Data protection / security

We take steps to protect sensitive Google user data, including OAuth tokens. Data is encrypted in transit using HTTPS/TLS. OAuth tokens are stored securely with encryption at rest (or equivalent protection) and with access controls so that only systems and personnel who need them to provide the connected Google features (YouTube upload, Blogger publish, and account identity) can use them.

We apply least-privilege practices: we request only the Google scopes listed above, use tokens only for the feature you connected (uploading videos you request, publishing articles you request, or identifying your account), and limit internal access to connection records. No method of transmission or storage is completely secure, but these controls are designed to protect the confidentiality of Google user data in our possession.

Retention and deletion

We keep OAuth tokens and connection records only while the relevant Google connection remains active, so we can continue providing that feature. YouTube upload-related metadata (such as video id, title, and status) and Blogger publish-related metadata (such as blog id, post id, title, and status) are kept as needed to show publish results in the product. We keep your Google Account email as needed to identify your signed-in RankReactorAI account.

You can disconnect YouTube or Blogger in the product, or email rankreactor@mail.grokbot.com or DM us on X at @rankreactorai to request deletion of stored Google user data or your RankReactorAI account. When you disconnect or we process a deletion request, we delete stored OAuth tokens and connection records for that connection and revoke it so RankReactorAI can no longer upload to your YouTube channel or publish to your Blogger blogs.

You may also revoke RankReactorAI's access to your Google account at any time from Google Account permissions (Google's security settings page at https://security.google.com/settings/security/permissions). Revoking access there stops RankReactorAI from using your tokens; we then delete stored tokens and connection records associated with that authorization.

Video files uploaded through RankReactorAI live on YouTube under your channel. Disconnecting RankReactorAI or deleting stored tokens does not delete those videos. You control and delete them in YouTube. We do not delete videos from your YouTube channel on your behalf.

Articles published through RankReactorAI live on your Blogger account. Disconnecting RankReactorAI or deleting stored tokens does not delete those posts. You control and delete them in Blogger. We do not delete posts from your Blogger blogs on your behalf.

Project API keys are kept only while that key is active. We store a one-way hash of the key, a short prefix, when it was created, when it was last used, and a version we use to tell whether the key is still current. Regenerating a key replaces the previous record. Revoking a key, or deleting the project, removes that key record. Assistant access and refresh tokens are not stored on our servers; they expire on their own as described below. Articles and videos created through the assistant are kept as project content the same way dashboard-created items are.

Cookies

We use cookies and similar technologies to analyze site usage, improve performance, and personalize your experience. You can control cookies through your browser settings.

Sharing

We do not sell your personal information. We may share data with trusted service providers who help us operate RankReactorAI, and only as needed to provide our services, as described above for Google user data. We may also disclose information if required by law.

If you connect an AI assistant, we return the tool results needed to complete that request to the assistant you connected. The assistant platform processes the conversation under its own privacy policy.

AI assistant connections

You can optionally connect an AI assistant such as ChatGPT, Claude, Cursor, or Grok to one RankReactor project. The assistant talks to our MCP server using a per-project API key. Keys start with rr_live_. The assistant can do only what the tools for that one project allow.

What the integration can access

When you connect an assistant with that project's key, it can read that project's reactor status (plan, quotas, and recent article or video titles and status); read stored search and site-health metrics; list generated articles (title, status, and related details such as keyword); list generated short videos (title and status); start article generation; start short-video generation; and start a metrics refresh. Generation and refresh follow the same plan limits as the dashboard.

The key is limited to that one project. The assistant cannot use it to reach your other projects, publish articles or videos to YouTube, Blogger, or other destinations, delete project content, or change your account or billing.

Authentication

Each project can have one API key. You create it on the dashboard API Key page. The full key is shown once. We store a one-way hash of the key so we can check it later; we do not keep the full key after that. Generating a new key replaces the old one immediately. Revoking the key from that page removes it immediately. After you revoke or regenerate, the next assistant request is refused.

Some assistants, such as ChatGPT, connect through OAuth. You paste the same project key on our consent page. We then issue encrypted access and refresh tokens to the assistant. We do not store those tokens on our servers. Access tokens expire after 15 minutes. Refresh tokens expire after 30 days. Authorization codes expire after 10 minutes. When the assistant asks for it, we also issue a signed identity token with the same lifetime as the access token. Each request re-checks that the project key is still current, so revoking or regenerating the key stops the next request even if a token has not yet expired.

What we log from assistant requests

When a key is used, we update a last-used time on that project's key record. We do not write a separate log of every successful assistant request. If a request fails, we may record an error in our application or hosting logs. Those error records can include the tool name and, for some failures, the project. We do not automatically delete MCP-related records (the key's last-used time) or application error logs. You can email rankreactor@mail.grokbot.com or DM us on X at @rankreactorai to request deletion of logs tied to your account or project, and we will delete what we are able to from systems we control. Some request logs are kept by our hosting and cloud infrastructure providers, where we cannot delete individual entries; those follow the provider's own retention periods.

To run a request, we receive the tool name and the inputs needed for that tool (for example a keyword or a video prompt). If you start article or video generation through the assistant, we store those inputs on the generated item the same way we do in the dashboard.

Assistant platforms

The assistant platform (for example OpenAI or Anthropic) processes the conversation under its own privacy policy. We receive only the tool inputs needed to run each request. We do not use that data to train models, and we do not sell it.

Disconnecting and deletion

You can disconnect anytime by revoking the key on the API Key page, or by removing the connection in the assistant. You can also regenerate the key, which immediately invalidates the old one. For account deletion or other data requests, email rankreactor@mail.grokbot.com or DM us on X at @rankreactorai.

Contact

If you have questions about this policy, including how we handle Google, YouTube, or Blogger user data, or AI assistant connections, reach us at rankreactor@mail.grokbot.com or DM us on X at @rankreactorai.