YouTube subscription import: when you request an import in channel settings and grant Google read-only access, we save subscribed channel IDs, names and images to your account interests. They persist across page reloads and sign-ins. You choose feed connections separately, subject to your plan limit. Kakao members can connect without changing their Vigest sign-in account. We do not change your YouTube subscriptions or use features accessing watch history or private videos. We also retain your choice to exclude removed channels from future imports.

Vigest is a video analysis service operated by PROLIKE (프로라이크).

Privacy contact: Vigest Operations · contact@vigest.io. This contact handles requests for access, correction, deletion, and restriction of processing.

• Account and authentication: your Google or Kakao account identifier, name, email, Google profile image (Kakao profile photos are not requested or stored), sign-in session, and authentication records such as tokens issued by the authentication provider. At sign-up or sign-in, we record the accepted Terms version, acknowledged Privacy Notice version, language, and timestamps. When checkout starts, we record the applicable subscription-conditions version and checkout reference. A Privacy Notice acknowledgement does not replace consent where separate consent is required.
• Usage: connected channels, interests, saved videos, analysis requests, result views, resource clicks, and language settings.
• Sign-up source: when service analytics is active (see the country rules under Service analytics), the campaign values of your first visit (utm_source, utm_medium, utm_campaign), the domain of the previous site and the visit time are recorded once on your account when you sign up. Campaign values are accepted only as lowercase letters, digits and a few symbols up to 64 characters; we do not store the full address or path of the previous site, search text or other URL values.
• Analysis: selected video titles, descriptions, links, captions, and generated summaries, Video Flow, resources, translations, and digests.
• Operations: request identifiers, processing stages, timestamps, errors, model usage and cost, credit reservations, use and returns, trial or access records, mission completion dates, summary-view records, feedback messages, and reward grants and expiry.
• Support: your reply address, message, and attachments when you contact us.
• Subscriptions: when requesting a Pro subscription, your account email, member-to-customer reference, transaction and subscription identifiers, billing country, currency, amount, status, funded period, cancellation/refund reason, policy version, analysis credit usage/reservations, and review/processing results. Vigest does not store full card numbers or CVCs.

We store access and refresh tokens on the server for imports and authorization checks. Personal subscription lists and tokens received from Google are not used for advertising, sale, external AI inputs or model training. AI processing of selected public video information and captions follows the separate analysis disclosures. Our use and transfer of Google user data adheres to the Google API Services User Data Policy, including Limited Use requirements.

Revoking YouTube access in Settings or requesting account deletion stops further Vigest access and removes imported interests, feed connections created from that source, related authorization tokens and import exclusions. Manually added interests and original YouTube subscriptions remain. We also request token revocation from Google. If communication fails, only the token needed for revocation is retained separately in encrypted form for retries for up to seven days, then deleted. Pending revocation is shown in Settings; you can also revoke directly in your Google account. Other permissions granted to the same Google project may also be revoked, requiring consent at your next Google sign-in.

We periodically check access and refresh previously imported channel information without automatically adding newly subscribed channels. Confirmed revocation causes related data cleanup; temporary network failures alone do not delete the list. Imported channel information is refreshed or deleted within 30 days, including related interests and feed connections from that source when they cannot be refreshed. Revocation in Google account settings is detected periodically and related data is cleaned up within 30 days.

• Google API Services User Data Policy
• Manage Google access

• Sign-in, account management, channel connections, personalized feeds, and saved videos
• Requested analysis, translation, digests, and reuse of results
• Credits, trials, access management, and prevention of duplicate requests
• Subscription billing, cancellation, refunds, and checking the refund period from the payment date
• Troubleshooting, security, abuse prevention, usage and cost statistics, and support
• Usage and paid-conversion statistics by sign-up source, and measuring the effect of promotion channels

We use HTTPS/TLS to protect transfers of Google account information, YouTube subscription channel information and authorization tokens between our production website and Google APIs. Communication between Cloudflare Workers and the D1 database is also protected by TLS.

Google user data and authorization tokens stored in our production D1 database are automatically encrypted at rest using Cloudflare's AES-256 storage encryption. Cloudflare manages the encryption keys for this storage layer.

Our server verifies the signed-in session for subscription imports and access-management requests and processes data within that member's account. Google access and refresh tokens are stored and used on the server and are not returned to the browser in subscription-list API responses. YouTube authorization uses state and PKCE checks to bind authorization requests to their responses.

Access termination and data deletion following revocation or account deletion follow the YouTube access and data cleanup section above. If a Google token-revocation request cannot be completed because of a communication failure, the token needed for retries is separately encrypted and retained only for the limited period described there.

• Cloudflare D1 data security

With your consent, we use your email, signup time, language and consent record only for the official launch announcement. We delete it after sending the announcement; you can withdraw beforehand at contact@vigest.io. Signup does not mean your email has been verified or an announcement sent.

Feedback is anonymous by default. Only choosing to include account information associates your member identifier and shows your name and email to administrators. Account deletion removes the association.

Vigest processes selected video information and available captions. Caption availability and accuracy can limit analysis or cause errors.

For analysis, translation, and digests, we may send necessary video information, captions, existing analysis, and processing instructions to external AI APIs. We do not include account email addresses or sign-in credentials in analysis inputs, but source content may contain information about people.

Analysis of the same video may be reused for requests from multiple users. This does not make your account information or individual usage records public to other users.

Provider retention, safety-review, and training practices depend on the agreement, service tier, and settings. Vigest does not guarantee zero retention or exclusion from model training across all providers.

When caption fallback is enabled, failures such as access blocking, timeouts, or unavailable captions during retrieval for a requested video may cause Vigest to send the video ID and caption language to TranscriptAPI (Zero Point Studio d.o.o., Croatia) to request captions. Account emails, member IDs, sign-in credentials, and payment information are not included in this caption request.

Under its Privacy Policy, TranscriptAPI may process the Vigest server's IP address, requested video IDs and languages, and API usage, error, and performance records. We do not forward the visitor's browser IP address. The API key is used only for server authentication. Data may be processed outside your country; provider retention and subprocessors are governed by that policy. Vigest uses caption provenance and fallback outcomes for requested analysis and incident investigation.

• TranscriptAPI Privacy Policy

This list distinguishes the connected provider from candidates. Production analysis inputs are not sent to candidates. Before adding a provider or changing processing scope, we will update these disclosures and provide notices or obtain consent where required.

The data importer identified in Cloudflare’s Data Processing Addendum is Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA. Its data protection contact is legal@cloudflare.com. This is the recipient’s address and does not mean that all service data is processed or stored exclusively in the United States.

Google or, where enabled, Kakao sign-in is used to identify accounts and obtain basic profile information. Vigest does not request permission to read or delete users’ Gmail messages. Google and Kakao provide sign-in authentication, and YouTube API Services provide video and channel information. Cloudflare provides infrastructure for website delivery, server requests, database storage, caption-processing containers, and real-time status updates. Request and connection information, execution logs, and error logs are processed for service operation and security.

Depending on provider infrastructure, data may be processed or stored outside your country of residence. Changes to providers, agreements, or processing scope will be reflected in our disclosures and any legally required procedures.

When you open YouTube or a resource link, that site processes information under its own policies. You can also manage permissions granted to your Google account through Google account settings.

• Google Privacy Policy
• Manage Google account connections and permissions
• Cloudflare Privacy Policy
• Cloudflare Data Processing Addendum
• Cloudflare sub-processors

Paddle handles payments and billing for paid subscriptions. The processing below applies when checkout is available; a Coming soon label means subscriptions are not yet open.

Selecting Pro creates or finds a Paddle customer by your signed-in email and links that billing record to your Vigest member account. A Paddle customer is not a separate Vigest sign-in account. A customer record may exist before payment completes.

Paddle processes name, email, billing address, country and payment information entered in its checkout under its own policies. Vigest manages subscription access using verified payment notifications. Price localization uses the country inferred from the visitor IP or confirmed at checkout. Refund eligibility is checked against the payment date and payment information of the transaction.

Cancellation and refund requests submitted in Settings are handled on the server after checking the Paddle customer, subscription and payment linked to your signed-in account. We retain the refund reason, applied policy, analysis credit usage/reservations and review/processing results. Payment-method management uses Paddle's customer portal; Vigest does not retain the temporary management link. Do not send card numbers or CVCs in inquiries.

Paddle acts as an independent data controller for sales and payment purposes. Processing may involve transfers to Paddle entities and payment providers in other countries. Its customer and transaction records may persist under its policies and legal, accounting or dispute obligations. Deleting a Vigest account does not immediately delete Paddle records. Privacy requests concerning records controlled by Paddle may also be submitted to privacy@paddle.com. Information needed for customer linking, checkout and subscription management is transmitted to Paddle over encrypted network connections. Paddle identifies its controller entities and their contact details in its Privacy Policy. Its global operations and payment providers may process data outside your country, subject to the transfer safeguards and retention criteria described there. Vigest does not store full card numbers or CVCs.

• Paddle Privacy Policy
• Subscription terms

Cloudflare infrastructure processes requests and service data when the site and its features are used. Authentication information is exchanged during Google or Kakao sign-in, and lookup requests are sent to YouTube API Services when video information is retrieved. Inputs are sent to external AI APIs as needed for analysis, translation, and digests. Billing providers process data during customer linking, checkout, and subscription management; email providers process inquiries during sending, forwarding, and replies.

Requests to restrict or stop processing, including international transfers, may be sent to contact@vigest.io. We review the requested scope and applicable grounds. Features requiring that processing, such as sign-in, analysis, or billing, may be unavailable, and records subject to statutory retention may not be deleted immediately.

Contact links open your email application. When you send an inquiry, mail delivery and receiving services process sender and reply addresses, the subject, message, and attachments. Support inquiries are currently forwarded through Cloudflare Email Routing to the operator’s Google Gmail inbox. This is separate from access to a user’s Gmail account. Google’s global infrastructure may process this information outside the user’s country under its Privacy Policy and Terms of Service.

Deleting a Vigest account does not automatically delete previously sent inquiry emails. Requests to access or delete inquiry records may be submitted to the same contact address. Records subject to a separate retention basis, including payment or dispute records, are handled according to that basis. Do not send passwords, verification codes, card numbers, or CVCs.

• Google Privacy Policy

We use Google Analytics 4 and Google Tag Manager to measure visits, screen changes, sign-in starts and completions, content expansion, and the outcomes and waiting times of search, channel connections and loading more. When analytics starts, Google processes cookie-based browser identifiers and request and device information. Vigest does not put account IDs, email addresses, search text or video titles into these analytics events. Original URL queries are excluded, except that records on the first screen of a visit include the utm_source, utm_medium and utm_campaign values normalised as described above, to identify where the visit came from. We do not use Google signals or user-provided data features. Advertising consent settings are denied, and account data sharing for Google products and services is disabled.

The policy uses the connection country estimated by Cloudflare. In Korea and the US, service statistics start without an initial consent dialog, and you can opt out using the analytics cookie settings below. In the EU/EEA, UK and other countries, analytics starts after you select Allow. An unknown country also requires prior permission. In countries requiring permission, Google analytics tags stay unloaded before permission or after rejection. A saved rejection, browser GPC or Do Not Track signal turns analytics off in every country.

You can change your choice through the analytics cookie settings below. The choice is saved in this browser for 180 days. Rejection clears analytics cookies and stops subsequent collection without affecting service access. Google's global infrastructure may process data outside your country under the Analytics processing terms and the property's retention settings. Contact us to request deletion of previously collected records.

• Google Privacy Policy
• Google Analytics data processing terms
• Google Analytics opt-out add-on

• Cookies maintain sign-in sessions, authentication protection, and language preferences.
• When service analytics is active, a cookie (vigest_first_touch) holds the campaign values, previous site domain and time of your first visit for 30 days and is not overwritten by later visits. It is deleted when sign-in completes or when you refuse analytics.
• localStorage may hold language and interface settings. You can remove it through your browser settings.
• sessionStorage may hold viewing state and your intention to resume checkout after sign-in in this tab. The checkout marker is consumed once and expires after 30 minutes. Tab closure clears sessionStorage; account records remain separate.

• Reply addresses, messages, and attachments for general inquiries are retained for one year after the inquiry is resolved, then removed through retention cleanup. Payment, refund, consumer complaint, and dispute records are classified separately and retained for the period required by applicable law. Where a separate retention basis remains, such as an ongoing dispute, only the necessary records are retained until that basis ends.
• Account-linked connections, saved videos, credits and sign-up source are retained while the account exists and deleted on account deletion. Payment and refund ledgers may remain with the member link removed for legal retention or disputes.
• To prevent repeated free benefits through deletion and re-registration, we separately retain server-keyed hashes of the authentication provider identifier and verified email, the original usage-period anchor, free credit usage, whether the free Digest allowance was used, the time of the most recent automatic refund, mission signup anchors, completed days and reward grants, and campaign-scoped hashes of viewed summaries for 90 days after deletion. This prevention record contains no original email, authentication token, saved videos, or channel list. Re-registration within retention keeps the original renewal schedule and usage; outstanding free reservations at deletion count as spent. Expired records are deleted by scheduled cleanup.
• Source captions expire 30 days after acquisition or verification and are deleted by scheduled cleanup. Request-level processing-stage logs are also cleaned up based on a 30-day retention period. Actual deletion time depends on when cleanup runs.
• Shared video analysis, translations, and digests are retained separately from source captions and are not all deleted solely because the requesting account is deleted. Requests concerning personal information or infringement are reviewed separately.
• Records needed for legal retention duties, disputes, or security incidents may be retained for the period necessary for that purpose. External providers’ records are subject to their applicable agreements and processing terms.

Contact contact@vigest.io to request access, correction, deletion, or restriction of personal information. You can also request account deletion in Settings. We may request the minimum information needed to verify identity and will explain applicable legal limitations.

• Privacy and rights request guidance

Material processing changes will be reflected here with an updated date, with in-service notices and legally required notice or consent procedures where applicable.