Privacy Policy | FrameToCover

Introduction

This Privacy Policy explains how FrameToCover collects, uses, shares, protects and deletes personal information.

Signing in with an external account

Where available, Google, GitHub and Microsoft sign-in give FrameToCover a provider account identifier and basic profile details such as your name, email address and profile image. We use them to identify your account and sign you in. Signing in with Google does not connect a YouTube channel. Signing in with GitHub does not grant FrameToCover access to your repositories. You can manage the sign-in grant from the provider's account settings.

Google user data and YouTube thumbnail publishing

Data we access. When you choose to connect YouTube, FrameToCover receives a temporary Google access token. With your permission, it reads the connected YouTube channel's ID and name, and the ID, title, channel ID and processing status of the video you select. You can use the editor and export covers without granting these permissions.
How we use it. The read permission identifies your channel, verifies ownership and checks that the selected video is ready. The upload permission lets FrameToCover send your chosen thumbnail to YouTube after you confirm replacing the cover on that video. After an accepted upload, we read back the video to check the target.
Who receives it. Google receives the authorization and YouTube API requests. Cloudflare hosts the app and its database on our behalf. We do not sell this Google user data, use it for advertising, or send it to AI providers or use it to train models. Google handles data it receives under the Google Privacy Policy.
Protection and retention. We encrypt the temporary access token before storing it with the channel ID and name. We remove that connection record when you disconnect or when it expires. We do not store a Google refresh token for this feature. We retain an upload receipt with the video ID, time and result for up to 30 days. The API lookup does not add the video's title or processing details to the receipt.
Revocation and deletion. Use Disconnect YouTube in the project, or revoke access from Google Account connections. Deleting your account removes its connection and upload receipts. Use account security or contact FrameToCover for deletion requests.

FrameToCover's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Information We Collect

We may collect the following types of information:

Personal Information: Name, email address, and contact details you provide when registering or contacting us.
Usage Data: Information about how you interact with our website, including pages visited and time spent.
Device Information: Details about the device you use to access our services, such as IP address, browser type, and operating system.

How We Use Your Information

We use your information for the following purposes:

To provide and maintain our services
To notify you about changes to our services
To provide customer support
To gather analysis or valuable information to improve our services
To monitor the usage of our services
To detect, prevent, and address technical issues

What happens to your covers

Files processed in your browser: The original video used for frame selection, and images used only in the free tools, are processed in the browser. Downloading a local cover does not require an account or an upload.
Free tool usage: To measure which tools are useful, we count the first successful interaction and whether that page initiated a download. We record the tool, time and a broad referral category. A random identifier for that page visit prevents duplicate counts. These records expire after 35 days. We exclude file names, images, titles, full referral URLs and account IDs. The measurement respects Global Privacy Control and Do Not Track.
Signed-in projects: We store the stills and images you use in a saved project, plus its titles, layers, brief, versions and job results. Cloudflare provides the app, database and private media storage. The original video is not uploaded as part of saving a project.
AI requests: When you choose to generate or edit an image or request cover feedback, FrameToCover sends the material listed on that screen to OpenAI. It may include a prompt, a selected still or the current cover preview. Saving a project alone does not send an AI request. See OpenAI’s API data controls for how the provider handles API data.
Review links: An active link shows the shared cover and video title for up to seven days, without access to the original source or editable project. The owner can allow anyone with the link to view it or restrict access to one verified account by email. We use the recipient address to check access and show the invitation in their review inbox. A named invitation includes the channel label if the project has one when the invitation is created. If the owner enables feedback, eligible viewers who are signed in with a verified email can leave comments visible to the project owner. Comments and positions are kept with the project review history; deleting the reviewer's account removes their account name from that history. Revoking a link or deleting the project stops new access. It cannot remove files a visitor already downloaded.
Team workspaces: Adding a project to a workspace lets current members view its saved covers and the images used in them. Members can comment or approve a version according to their role. We use the email entered for an invitation to match it to a verified account. Acceptance clears the address from the invitation record, and revocation, expiry cleanup or deletion of the recipient account removes pending invitations. Removing a member stops their access. Removing a project from its workspace clears that workspace's feedback and keeps the owner's project. If a member deletes their account, feedback in the team's history remains without their account name.
Project transfers: A transfer invitation matches a verified account using a hash of the email address. Accepting transfers the saved versions, project images, references and review history, including team feedback, to the new owner. Prior team and reviewer access ends, and images from active review links are retained privately with the project. Account keys, subscriptions, brand kits and usage limits stay with their account.
Channel research: We store the public channels you follow and the recent video titles, IDs and dates read from their feeds or imported from XML. Refreshing sends the public channel ID to YouTube, without your account or project material. Unfollowing clears the channel cache; references you already saved to a project can be removed from its board.
Project API: If you create a personal or team key, we keep its hash, ending characters, label, expiry and request counts. The full key is shown only when you create it. A team key reads only summaries for projects currently in its workspace. Revoking the key stops its access.
Project webhooks: If you add a receiver, saving a new revision sends its project ID, revision and time to the URL you supplied. Team events include the workspace ID. We keep the receiver URL and delivery status. Revocation stops new deliveries.

Export and deletion

Use account security to export an account record or request account deletion. Removing a project or account disables access to its affected review links and starts private storage cleanup. Keep a copy of any export you want to keep before deleting your project or account.

Data Security

We implement appropriate security measures to protect your personal information from unauthorized access, alteration, disclosure, or destruction.

Third-Party Services

Cloudflare hosts FrameToCover. OpenAI handles AI requests you choose to send. When paid checkout is available, it opens a Stripe payment page; FrameToCover receives information needed to manage the purchase, such as payment status and receipt references. Check the pricing page for current availability.

Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

Contact Us

If you have any questions about this Privacy Policy, please contact us.

Signing in with an external account

Google user data and YouTube thumbnail publishing

Data we access. When you choose to connect YouTube, FrameToCover receives a temporary Google access token. With your permission, it reads the connected YouTube channel's ID and name, and the ID, title, channel ID and processing status of the video you select. You can use the editor and export covers without granting these permissions.

How we use it. The read permission identifies your channel, verifies ownership and checks that the selected video is ready. The upload permission lets FrameToCover send your chosen thumbnail to YouTube after you confirm replacing the cover on that video. After an accepted upload, we read back the video to check the target.

Who receives it. Google receives the authorization and YouTube API requests. Cloudflare hosts the app and its database on our behalf. We do not sell this Google user data, use it for advertising, or send it to AI providers or use it to train models. Google handles data it receives under the Google Privacy Policy.

Protection and retention. We encrypt the temporary access token before storing it with the channel ID and name. We remove that connection record when you disconnect or when it expires. We do not store a Google refresh token for this feature. We retain an upload receipt with the video ID, time and result for up to 30 days. The API lookup does not add the video's title or processing details to the receipt.

Revocation and deletion. Use Disconnect YouTube in the project, or revoke access from Google Account connections. Deleting your account removes its connection and upload receipts. Use account security or contact FrameToCover for deletion requests.

FrameToCover's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Information We Collect

We may collect the following types of information:

Personal Information: Name, email address, and contact details you provide when registering or contacting us.

Usage Data: Information about how you interact with our website, including pages visited and time spent.

Device Information: Details about the device you use to access our services, such as IP address, browser type, and operating system.

How We Use Your Information

We use your information for the following purposes:

To provide and maintain our services

To notify you about changes to our services

To provide customer support

To gather analysis or valuable information to improve our services

To monitor the usage of our services

To detect, prevent, and address technical issues

What happens to your covers

Files processed in your browser: The original video used for frame selection, and images used only in the free tools, are processed in the browser. Downloading a local cover does not require an account or an upload.

Free tool usage: To measure which tools are useful, we count the first successful interaction and whether that page initiated a download. We record the tool, time and a broad referral category. A random identifier for that page visit prevents duplicate counts. These records expire after 35 days. We exclude file names, images, titles, full referral URLs and account IDs. The measurement respects Global Privacy Control and Do Not Track.

Signed-in projects: We store the stills and images you use in a saved project, plus its titles, layers, brief, versions and job results. Cloudflare provides the app, database and private media storage. The original video is not uploaded as part of saving a project.

AI requests: When you choose to generate or edit an image or request cover feedback, FrameToCover sends the material listed on that screen to OpenAI. It may include a prompt, a selected still or the current cover preview. Saving a project alone does not send an AI request. See OpenAI’s API data controls for how the provider handles API data.

Review links: An active link shows the shared cover and video title for up to seven days, without access to the original source or editable project. The owner can allow anyone with the link to view it or restrict access to one verified account by email. We use the recipient address to check access and show the invitation in their review inbox. A named invitation includes the channel label if the project has one when the invitation is created. If the owner enables feedback, eligible viewers who are signed in with a verified email can leave comments visible to the project owner. Comments and positions are kept with the project review history; deleting the reviewer's account removes their account name from that history. Revoking a link or deleting the project stops new access. It cannot remove files a visitor already downloaded.

Team workspaces: Adding a project to a workspace lets current members view its saved covers and the images used in them. Members can comment or approve a version according to their role. We use the email entered for an invitation to match it to a verified account. Acceptance clears the address from the invitation record, and revocation, expiry cleanup or deletion of the recipient account removes pending invitations. Removing a member stops their access. Removing a project from its workspace clears that workspace's feedback and keeps the owner's project. If a member deletes their account, feedback in the team's history remains without their account name.

Project transfers: A transfer invitation matches a verified account using a hash of the email address. Accepting transfers the saved versions, project images, references and review history, including team feedback, to the new owner. Prior team and reviewer access ends, and images from active review links are retained privately with the project. Account keys, subscriptions, brand kits and usage limits stay with their account.

Channel research: We store the public channels you follow and the recent video titles, IDs and dates read from their feeds or imported from XML. Refreshing sends the public channel ID to YouTube, without your account or project material. Unfollowing clears the channel cache; references you already saved to a project can be removed from its board.

Project API: If you create a personal or team key, we keep its hash, ending characters, label, expiry and request counts. The full key is shown only when you create it. A team key reads only summaries for projects currently in its workspace. Revoking the key stops its access.

Project webhooks: If you add a receiver, saving a new revision sends its project ID, revision and time to the URL you supplied. Team events include the workspace ID. We keep the receiver URL and delivery status. Revocation stops new deliveries.

Third-Party Services