Privacy Policy

1. Controller and scope

The controller is Individual Entrepreneur KAITOV RASUL KHALITOVICH, Tax ID (INN) 091600553711, Registration ID (OGRNIP) 319774600693600. Contact: support@reelshunter.io. This policy covers Reels Hunter at reelshunter.io, app.reelshunter.io, mcp.reelshunter.io and reels-hunter.ru, including connected accounts and publishing.

2. Account and service data

For registration and workspace access we process your name, email, password hash or Google/Telegram sign-in identifier, language and preferences. We store projects, materials you provide, links to public publications, analysis results, scripts, operation history, plan, token balance and order records. Security processing includes IP address, request time and browser information.

3. Purposes and legal bases

Data necessary for the contract is processed to sign in, provide selected features, administer subscriptions, support users and prevent abuse. Payment and accounting records are also processed to comply with legal duties. Consent-based processing is limited to the stated purpose. Marketing requires a separate voluntary choice.

4. Payments and processors

Payments take place on T-Bank payment pages. Reels Hunter does not receive the full card number or CVV. Payment, renewal and receipt processing uses payment, order and payment-method identifiers, amount, status and receipt email. Google or Telegram processes the sign-in method you choose. Materials for AI features you explicitly launch are sent to configured processing providers, including OpenAI and OpenRouter, only as needed for the request. Do not submit confidential third-party information without a valid basis. Details of the processor used for a request are available from support.

5. Cookies and optional analytics

Necessary cookies maintain sessions and protect sign-in. Language and theme preferences may be stored in your browser. If analytics is allowed, Yandex Metrica counter 112574159 processes public-page views and interface interactions; Webvisor may run on public pages. Workspace contents, payment forms, passwords and private fields are excluded from recording. You can change the choice using Analytics settings at the bottom of the site. Refusing analytics does not prevent registration or payment. Yandex processes technical information under its own terms and privacy policy.

6. Retention

Account data is retained while you use the service, then only as needed for obligations, support requests or applicable legal requirements. Server-side Studio videos are retained for 72 hours, with active processing materials protected until a task finishes. Download your results in advance. Files saved on your device are unaffected. Technical copies and legally required records are removed after the applicable retention period.

7. User requests

You may request information about processing, correction, restriction or deletion and withdraw consent by contacting support@reelshunter.io. Account ownership may need to be verified. Withdrawal does not end processing supported by another lawful basis. Marketing can be disabled in workspace settings.

8. Security and changes

Measures include HTTPS, protected sessions, user/project access separation, payment-notification validation and restricted access to service keys. The current version is published here. Material changes requiring new consent do not replace your existing choice.

9. Connecting Meta and Instagram

TikTok and YouTube crossposting is available to service users. Instagram public access is coming soon; Instagram connection remains limited to admitted review accounts. To connect an Instagram professional Business or Creator account, you authorize it on the official Meta/Instagram screen. Reels Hunter does not request or store your Instagram password. Connecting Instagram is optional for features that do not require publishing to that account.

10. Instagram data and use

Within the permissions you grant, we process the connected professional account ID, username, account type and available profile information; access token, expiry and permissions; media you select, caption, publication settings, time and time zone; created container/publication IDs, link, publishing status and technical errors. This data identifies the connected account in your workspace, executes your selected publication or schedule and displays the result. instagram_business_basic identifies the account; instagram_business_content_publish enables publishing content you approve. Connecting an account is not an instruction to publish.

11. Sharing and limits on Meta data

For a publication, selected media, caption and settings are transmitted to Meta/Instagram. Infrastructure processors may handle necessary data to host the service, store/deliver the file and execute your request, with access limited to those tasks. Access tokens are not made public or exposed to other users. Data obtained through the Meta connection is not sold or used to manage ads, send independent marketing or serve unrelated purposes. AI processing of material you explicitly submit is described above; connecting Instagram does not authorize the use of its access token for AI processing or general model training.

12. Disconnecting and deleting Meta data

You can use Disconnect in Crossposting and revoke access in Instagram/Meta settings. Cancel unwanted scheduled publications before disconnecting. Revoking access and erasing previously stored data are separate actions. To delete tokens, connected-account identifiers, related jobs and other integration data, email support@reelshunter.io. Data is processed only while needed for the selected feature; a verified deletion request is fulfilled without undue delay, subject to mandatory legal requirements. Restricted backup copies and mandatory accounting records are not used for new publications. The instructions and exceptions are at /legal/data-deletion. Deletion from Reels Hunter does not remove posts already published on Instagram.

13. Rights and international processing

You can request access, correction, erasure, restriction and withdrawal of consent; objection and portability rights apply where required by law. Contact support@reelshunter.io. Selected features may transfer data to countries where Meta and necessary processors operate their infrastructure, subject to applicable transfer requirements and restrictions. The controller can explain applicable grounds, recipients and safeguards upon request. You may contact the competent data protection authority.

14. Other connected platforms

If YouTube, TikTok or another platform connection is available and you separately choose it, publishing processes the selected channel/account identifier and name, granted permissions/tokens, selected file, text, privacy/publication settings, schedule, publication ID/link, status and errors. Availability and data scope depend on platform permissions and capabilities. Data is transmitted to your selected platform for the action you confirm, not unrelated purposes. Disconnection, permission revocation and support-based erasure apply separately to each integration. Identify the platform in your request; erasing data from Reels Hunter does not remove posts from the platform.

15. AI assistant connections (Claude, ChatGPT)

You can connect Reels Hunter to Claude (Anthropic) or ChatGPT (OpenAI) through our connection server mcp.reelshunter.io. A connection is created only after you sign in to your Reels Hunter account and choose a project; you can disconnect it in the assistant's settings at any time, which revokes access.

Only the data you request in the chat (feed videos, reports, scripts, content plan records, edit progress and results) is sent to the assistant, and only from the selected project.

The connection server stores an encrypted authorization for your account and its session; records you ask it to save (scripts, goals, content plan, results, edit drafts); and a technical request log (tool name, account ID, time, duration, status) without conversation text. The server does not receive or read your chat history, the assistant's memory or any of your files other than those you pass for editing.

Videos passed for editing are processed for that task and kept on the server for the periods stated in section 6; finished videos are available in Studio Projects. Paid actions run only after you confirm the exact price in RH tokens. Connection permissions last until revoked or until the session expires.

The assistant provider (Anthropic or OpenAI) processes the conversation under its own terms; Reels Hunter does not send it data beyond what you request in the chat.

Google and YouTube connections

Reels Hunter uses YouTube API Services to let you connect your own channel and publish videos you select. Connecting YouTube is optional. Authorization takes place on Google's official consent screen; we do not receive or store your Google password. Google sign-in for a Reels Hunter account and permission to publish to YouTube are separate choices.

Data accessed and its purpose

The YouTube connection accesses the channel ID and channel name; the permissions you grant; access and refresh tokens and their expiry; and the IDs, links, privacy and processing status of videos submitted through Reels Hunter. When you request available statistics for those publications, we read the counts returned by YouTube, such as views, likes and comments. These data identify the destination channel, authorize the operation, display upload progress and results, and show the requested publication statistics in your workspace.

youtube.readonly is used to identify your connected channel and read the status and available statistics of your submitted videos. youtube.upload is used to upload the video you approve to that channel. We do not request access to Gmail, Google Drive, contacts or calendars for this connection. We do not use it to download videos from YouTube.

You provide the video file, title, description and publication settings, including visibility, whether the video is made for children, and applicable synthetic-content disclosures. We send these to YouTube only after you confirm the publication or schedule. Connecting a channel alone does not authorize a publication. Platform processing may continue after transfer has finished.

Storage, security and recipients

Selected upload files are stored temporarily on Reels Hunter servers and automatically deleted within 72 hours from upload start, including failed, incomplete and cancelled uploads. This deadline does not restart on retry. Tokens are encrypted and retained while the connection is active; Disconnect removes the local tokens and cached statistics and cancels transfers that have not started. Channel details and publication history are separate from the temporary video file and can be erased through a verified deletion request. Service and accounting records unrelated to YouTube authorization remain subject to the general retention provisions above.

Google/YouTube receives the selected content and metadata needed to perform your confirmed operation. Hosting and infrastructure processors handle only data necessary to operate the service, under restricted access. We do not sell Google user data or use it for advertising, credit decisions or unrelated marketing. Data obtained through the Google/YouTube authorization is not sent to generative AI providers or used to train generalized AI models. AI features that you separately initiate with your own submitted materials are described in section 4; connecting YouTube does not initiate an AI task.

Human access to Google user data is limited to your affirmative agreement to view specified data for support, necessary security investigation, or applicable legal obligations. Reels Hunter's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Revocation and deletion

Use Disconnect for the YouTube account in Crossposting, or revoke the Reels Hunter connection through Google's account permissions settings. Disconnect requests revocation from Google; if that request cannot be completed, revoke the grant in Google settings. To erase remaining authorized channel data and publication history, email support@reelshunter.io from your account email, identifying YouTube and the channel. Do not send passwords or tokens. Requests are handled after ownership verification, without undue delay and within applicable YouTube deletion deadlines. If you revoke access in Google settings, also notify support so stored integration data can be removed promptly.

Removing our data does not delete videos already on YouTube; manage those in YouTube Studio. See the data deletion instructions, Google Privacy Policy and YouTube Terms of Service. Contact support@reelshunter.io for questions about these practices.

AI assistant connection and producer memory

At your choice, Reels Hunter connects to a supported AI assistant through MCP and Reels Hunter authorization. The assistant receives data returned by available tools within the authorized account and project, such as library materials, reports, scripts, allowances and editing-project information. The connection does not give Reels Hunter access to every conversation or the assistant’s hidden memory. Data you supply to the assistant is also processed under that service’s terms.

Memory retention and deletion

For enabled accounts, relevant blogging facts, preferences, goals, next steps, content records and observations are stored separately in the selected project. Record contents are encrypted at rest. Hypotheses and observations are not verified platform metrics. Active memory remains until you delete it; age and inactivity alone do not trigger automatic deletion. Available tools let you inspect, correct and delete individual records. Do not store passwords, access tokens or unrelated confidential information.

MCP technical copies and audit logs

Private producer-memory verification backups and user-related MCP technical audit logs are retained for no more than 30 days and expire automatically. Audit logs contain limited event, tool, status, time, user identifier and duration metadata; note bodies, passwords and access tokens are not recorded in them. This period applies to these MCP technical copies and logs, not active memory, and does not set a general retention period for other service data. Copies are not automatically restored to the live store. After a record is deleted, a closed backup copy may remain until this retention period expires.

Disconnection and deletion requests

Disconnecting or revoking an MCP connection stops access through it but does not delete existing memory. To request deletion of all records, contact support@reelshunter.io from your account email and specify the project or entire account. Do not send passwords or tokens. Support verifies account ownership and request scope. Deleting a reference record does not itself delete the referenced file, report or published post; specify those materials separately.