Privacy policy
Last updated: 23 October 2026 · Private beta
This notice explains how FrameScope.cloud handles information in the FrameScope Windows application and on this website. FrameScope is a private beta. Some social integrations require test access, platform approval and your account consent.
Who to contact
The service is provided under the name FrameScope.cloud. For privacy questions, access, correction or deletion requests, contact support@framescope.cloud. Do not include passwords, API keys or social access tokens in your message.
Your FrameScope account
Registration requires a username, email and country, plus a password or a connected Google/Microsoft sign-in method. Organization and full address are optional. We store your profile, salted password hash, hashed single-use recovery code, account creation time, session expiry and device labels. Passwords and recovery codes are not stored in readable form. Email must be confirmed before Demo processing. Verification tokens are hashed, single-use and expire after 24 hours. Password recovery can use the recovery code you saved. An authorized administrator can also send a single-use password-reset link to a verified mailbox; it expires after thirty minutes and preserves enrolled administrator two-factor protection. Keep recovery codes and reset links private.
Google and Microsoft sign-in are optional alternatives to a FrameScope password. We receive the provider’s signed account identity and email, and store its provider name, issuer and stable account identifier linked to your FrameScope account. The provider processes your sign-in and connection information under its own privacy policy. FrameScope does not receive your provider password. Sign-in requests use an essential short-lived binding cookie and browser storage for an app approval request. Pending sign-in records expire within ten minutes and are removed on subsequent sign-in activity; completed one-use records are consumed. Provider access or refresh tokens are not retained for account sign-in. Connected identity records remain with your FrameScope account until deletion is requested. This connection does not upload media or grant publishing permissions; those are separate choices.
The website uses an essential Secure, HttpOnly session cookie and remembers your interface language in browser storage. Sessions last up to 12 hours, or 30 days when you choose to stay signed in. The Windows app can protect its session token using Windows account encryption; it does not save the account password. Signing in does not upload your local videos, transcripts, projects, AI keys or social credentials. You can revoke sessions in your account. Account records remain until you request deletion using the contact above; expired sessions are cleared during authentication activity. License sales and payment collection are not enabled.
Planned purchases through FastSpring
Live payments are not enabled. If our store is approved and checkout is launched, FastSpring will process contact, billing, payment and order information for purchases made through its checkout, under the FastSpring Privacy Statement. FrameScope would receive the order and customer details needed to provide license access, support and refunds; we would not receive full payment-card details. Payment records may be retained to meet tax, accounting and legal obligations. This planned checkout does not upload your video library or AI credentials.
Demo feature allowances
The app sends an installation identifier, feature name, opaque operation hash, attempt identifier and requested unit count to the account service. It records reservations, completion or release, server-controlled period dates and subtitle watermark decisions, and returns signed receipts. No media bytes, filenames, prompts or transcripts are sent by this check. Source hashes are part of the operation identity for video analysis and subtitles. Internet access is required for active-session and allowance checks. Changing the computer clock cannot advance the account period. Operation records remain with the account until deletion is requested; completed identities allow saved results to be reused without another charge.
An explicitly authorized administrator can view account profiles, verification and optional marketing status, Demo periods and license origin/expiry. Administrator access requires two-factor authentication. Single-use activation codes are stored as hashes; only a short suffix is shown in code lists. Administrative actions are audited. Gift activation is separate from payment and does not imply a purchase.
Security, verification and email preferences
Cloudflare Turnstile processes connection and browser signals to help prevent automated registration. Its separate privacy notice is available at https://www.cloudflare.com/turnstile-privacy-policy/. The account service validates the challenge on the server. Hosting and security providers also handle connection information to deliver and protect the service. Short-lived hashed authentication counters expire after 15 minutes and are cleared on subsequent activity; bounded in-memory connection limits do not store request contents.
Optional customer authenticator secrets and mandatory administrator authenticator secrets are encrypted on the server. Security audit records contain an internal account identifier, action and time and are retained for up to 180 days during service activity. Administrative audit and marketing-consent records remain with the account until deletion is requested. Recovery codes must be kept private; customer recovery does not remove mandatory administrator authentication.
Confirmation and security-change emails are sent through Resend (Plus Five Five, Inc.), which processes recipient addresses, subjects, message contents and delivery events. Its privacy policy is available at https://resend.com/legal/privacy-policy. Verification messages contain a short-lived confirmation link. Processing can take place outside your country; the selected sending region does not guarantee that all provider processing is limited to that region. A security-email queue stores destination, language, timing and delivery state for up to 30 days; failed delivery is retried for at most seven days. Security emails never include passwords, recovery codes, authenticator secrets or activation codes. An email change notifies the old verified address. These essential service messages are separate from marketing.
The optional marketing-interest checkbox starts checked, but it does not enroll you in marketing. Subscription requires a separate affirmative confirmation after email verification. We record that action and withdrawal with its time and notice version. You can unsubscribe from the account dashboard. No marketing campaign or payment collection is enabled in this release.
Videos and information on your computer
FrameScope stores imported video copies, extracted frames, analysis reports, transcripts, scripts, library information, settings and processing history in its application data folder on your computer. Local measurements do not require an AI service. Compatible local AI runs on your computer. Website hosting is not an automatic backup of your media or library. Shorts edits, subtitle files, voice references and their supplied transcripts, generated speech segments and alternate language exports also remain in the local application data folder. Voice cloning requires your confirmation that you own the voice or have permission to use it.
The Windows application may store API credentials that you choose to remember. Remembered credentials are protected using Windows account encryption. Session-only credentials are kept for that running application session. Locally saved reports and media are not all encrypted by FrameScope; protect access to your Windows account and storage.
When you choose an online service
Downloading from a URL contacts the source website or service. If you select cloud AI, FrameScope sends the material needed for that task to your chosen provider. Depending on the feature, this can include selected video frames, audio segments, recognized speech, prompts, reports and your instructions. The provider processes this material under its own terms and privacy policy. A local analysis does not authorize a separate cloud AI task.
Supported providers can include OpenAI, Google Gemini, Anthropic, xAI and a compatible endpoint that you configure. Only use a provider and endpoint you trust. An analysis or generation request can incur charges on your provider account. FrameScope does not control the provider's retention, training settings or processing locations.
Connected social accounts and publishing
When you choose Connect for an enabled integration, the platform asks you to sign in and authorize access. FrameScope uses the granted permissions to identify the account and available channels or Pages, prepare an upload, publish the content you select, and check or update its publishing status. Relevant data may include account and channel identifiers, display names, authorization tokens and expiry information, granted permissions, selected video and thumbnail files, titles, descriptions, visibility, scheduling choices and remote video identifiers.
FrameScope does not need your social account password. Saved social tokens on Windows are protected using Windows account encryption. The framescope.cloud connection broker processes Meta and TikTok authorization codes and tokens to complete the connection or refresh access. Provider app credentials remain on the server. Pending Meta tokens are encrypted until the desktop retrieves them, then removed from the transaction. Transactions expire after ten minutes and are deleted on a subsequent request; connection-rate records expire after one minute and are likewise cleaned up. The broker does not receive your video or voice media. A Google desktop exchange can be enabled through the same service after the owner authorizes its server credential; existing locally configured Google connections continue to work.
A publishing action sends your selected content and metadata to the platform. The platform's visibility settings, retention and other terms then apply. Disconnecting FrameScope does not delete videos already uploaded to a platform. Disconnection can leave local publishing history and calendar entries; see the deletion instructions for additional steps.
Website and diagnostics
This website currently serves product information and beta downloads. It does not use advertising trackers or analytics cookies. The hosting provider and security services necessarily handle connection information such as IP addresses and technical events to serve and protect the site. The server journal is configured with a maximum age of 14 days and a size limit; records may rotate earlier. This does not describe third-party providers' retention policies.
The Windows app records diagnostic stages and error categories to help investigate failures. A diagnostic export is designed to exclude source videos, transcripts, prompts, API credentials and raw provider responses. A support request, if sending is available and you choose to submit it, can contain your description, selected screenshots and an optional diagnostic archive. Review screenshots and anything you write before sharing it. Merely exporting a diagnostic file does not send it to the developer.
Use, recipients and retention
We use information to provide the requested functions, manage authorized connections, troubleshoot failures, prevent abuse and respond to requests. We do not sell your personal information or use connected social account data for advertising. Hosting and mail providers process the data needed to operate those services. Selected AI and social providers receive the material you choose to send to them and may process it in other countries.
Local project data remains on your computer until you remove it. Uninstalling FrameScope can leave its data folder so you can reinstall without losing your work. Developer-held correspondence is retained while needed to resolve your request and meet applicable obligations. You can ask us to remove it. If some data must be retained, we will explain the reason and applicable limits. We do not promise that a local deletion also erases data already sent to an independent provider.
Your choices and requests
You can use local features without connecting social accounts or choosing cloud AI, decline optional connections, disconnect an account, revoke permissions at the provider, and request access, correction or deletion of information held by the developer. Contact support@framescope.cloud and identify the relevant account or request without sending credentials. We may ask for proportionate evidence that the request relates to your account. Privacy and deletion requests do not require a paid FrameScope license.
The Data deletion page explains local removal, provider revocation and how to request deletion from the developer. The rights and response deadlines that apply to you depend on applicable law; nothing in these terms removes those rights.
Changes
We will update this page as the beta changes and show the revision date. Material changes to the data used by a newly enabled feature will be explained before you use that feature.