Privacy policy
This policy describes how Frame Studio at www.studio.smarttradehubsolutions.com handles information when you sign in, create media or buy credits.
Updated 16 November 2026
Information used for Google sign-in
We use your Google account identifier, email address and basic profile name to authenticate you, display your account and associate your projects and credits with the correct user. Google verifies the sign-in; Frame Studio does not receive or store your Google password.
The app requests only openid, email and profile permissions. It does not request Gmail messages, Drive files, Calendar data or contacts. Google sign-in information is used for account access and ownership, not sold or used for targeted advertising.
Email and password accounts
Google Cloud managed authentication handles email/password registration, verification and password recovery. Passwords are submitted directly to Google over HTTPS; Frame Studio does not store them. We keep your verified email, authentication identifier and server-session records to associate access, projects and credits with your account.
Email verification is required before account access and the welcome-credit grant. Linking another sign-in method requires proof of both identities. Password resets and disabled managed accounts invalidate their previous email-authenticated studio sessions.
Projects, media and generation requests
We store the briefs, scripts, settings, workflow connections, reference images, generated results and status information you save or create. To perform a generation, we send the prompt and relevant content or references to the supported provider selected for that step.
Providers can include Google AI, OpenAI, Runway and Kling, depending on your model choice. Their handling of submitted content is governed by their own service terms and privacy policies. Do not submit information you do not want processed by the selected provider.
API keys and account security
Personal model keys and administrator platform keys are encrypted on the server. The app does not return saved plaintext keys to the browser. Personal connections are scoped to their account; administrator settings are restricted to the verified studio owner.
Essential cookies keep you signed in, protect the Google sign-in flow and secure personal API connections. Browser storage also keeps workspace preferences and download/request recovery information. Signing out revokes the studio session. Blocking essential cookies can prevent sign-in or connected features from working.
Credits and payments
We store credit balances, generation reservations and charges, purchase quotes, Stripe payment identifiers and payment status so that credits can be added and deducted correctly. Refund and dispute status can adjust the balance.
Stripe handles hosted card checkout. Frame Studio does not collect or store your complete card number or card security code. Stripe may collect payment and billing information directly from you.
Storage and retention
The app is hosted on Google Cloud. Server video access ends seven days after the video is created, and background cleanup removes the server copies. This does not remove files you downloaded or copies held by a generation provider under its own policies.
Account, project, image, credit and transaction records have separate retention from video files. Database backups retain records for recovery; they do not extend access to expired server videos. Records may also be retained where needed for security, accounting or applicable obligations.
Sharing and service operation
Information is processed by the services needed to run the features you use: Google sign-in and cloud hosting, your selected generation provider, and Stripe for checkout. The site also loads its interface fonts from Google Fonts.
Project access is scoped to your account. Authorized server operations may process stored information to maintain the service, investigate failures or respond to your support request. We may disclose information when required by applicable obligations.
Your choices and requests
You can choose the content you submit, the supported model provider, platform keys or BYOK, and whether each workflow step needs approval. Disconnecting a personal API connection stops that saved connection from being used for new steps.
For account, access, correction or deletion requests, contact leonwong@fulhive.com from the email associated with your account. We may verify ownership before changing private records. Security, transaction records and backups may need separate handling.
Changes to this policy will be published on this page with an updated date.
Support: leonwong@fulhive.com