Privacy Policy

Information you give us.

• Account: your name, your email address, and your password stored only as a bcrypt hash. An account created with Google has no password at all.
• Sign-in history: the time, address and browser or device of each sign-in, kept 180 days, shown to you under Settings, Security and used to email you when your account is signed in to from somewhere new.
• Messages to us: what you write through the contact page, Help in the studio or Get help in the app, with the address to reply to, the page it was sent from and, when you are signed in, your workspace. Kept to answer you and to see what keeps coming up; deleted with your account, and included in your data export.
• App notifications: if you allow notifications in the ViewGC app, we keep that phone's push token, to tell you when a storyboard, film or video you started is ready. Signing out of the app, signing out everywhere or resetting your password deletes it, and so does removing the app.
• Two-step sign-in: if you turn it on, we keep the authenticator key, encrypted, and your recovery codes only as one-way hashes, to check the codes you type. Turning it off deletes them.
• Sign in with Google: if you choose to sign in or sign up with Google, Google tells us your Google account ID, your email address and whether Google has verified it, and your name. We ask Google for nothing more (only the "openid", "email" and "profile" permissions): we cannot read your Gmail, contacts, files or calendar, and we never post or act on your Google account. We keep your Google account ID and the email it gave, to recognise you the next time you sign in; your name fills in your ViewGC profile, which you can change. Google does not send us your Google password. You can disconnect ViewGC at any time in your Google Account under Security, third-party connections; if you want a password as well as Google, ask us and we will set one up for you. We use what Google shares only to sign you in and run your account, never for advertising, and we do not sell it. ViewGC’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Single sign-on: if your workspace signs in through its own identity provider, that provider tells us your account identifier there, your email address and your name, and we keep the identifier to recognise you. The workspace’s owners choose the provider; we store its client secret encrypted.
• Workspace: the workspace name, its billing email, and the people you invite with their roles.
• Digital twin photographs: if you build an actor from a real person, the photographs you upload of them, and a consent record holding who agreed, their relationship to you, the exact wording they agreed to, and when. See "Digital twins and likeness" below, which is the most important section of this policy.
• Creative content: actors and their descriptions, outfits, locations, products, scripts, reference images and audio you upload, and the videos and images generated from all of it.
• Payments: your card details go directly to our payment processor, Stripe, and never reach our servers. We keep the amount, the status, the plan, and what Stripe tells us about the card type and its last four digits.
• Support: messages you send us, and anything you choose to include in them.

Information collected automatically.

• Crash reports: when the studio or the app breaks, it sends us the error message, where in the code it happened, the page or screen (without any query string) and the app version, with your account id when you are signed in. Kept in our server logs for 30 days, to find and fix the fault.
• Usage and device information: the pages and API endpoints you call, your browser and device type, and your IP address, kept in server logs for security, rate limiting and reliability.
• Generation records: which actor, outfit, location, product and model produced each video, what it cost in credits, and which provider ran it. We keep which AI model made which part of a clip because platforms increasingly require AI-content disclosure, and that record is what such a disclosure needs.
• Administrative audit trail: when someone with platform administrator access renames, archives, deletes or re-tiers something, we record who did it and when.

A digital twin is an actor built from photographs of a real person. This is the only place the Services hold images of an identifiable living person, and it is treated differently from everything else.

• Consent is a stored record, not a checkbox. Before a twin is created we store the exact wording the person agreed to, who they are, their relationship to you, and the time. The wording is served by our API rather than copied into the app, so the record can never claim someone agreed to words they were never shown.
• You must have the person’s permission. Uploading photographs of someone who has not agreed is a breach of our terms, and it may be unlawful where you are. We cannot tell from a photograph whether consent was given; that responsibility is yours.
• Consent can be withdrawn. Withdrawing it archives the twin so it can no longer be used in a new generation. Videos already produced are not retroactively deleted by that action; ask us and we will delete them.
• We do not sell or license a twin. A twin belongs to the workspace that created it and is never added to the shared actor library, which is made only of generated identities that are not based on a named individual.
• Photographs are checked, not understood. An automated check rejects a screen photograph, an illustration or an image with no visible face. It does not and cannot tell whether the face belongs to the person who consented.

You can connect your own YouTube channel or TikTok account to a workspace so a finished film can be posted from ViewGC. Connecting is always your choice, and it is separate from signing in.

• What we ask for. From YouTube, permission to upload videos ("youtube.upload") and to read your channel’s name and picture ("youtube.readonly"), so we can show you which channel is connected. From TikTok, your display name and picture ("user.info.basic") and permission to upload videos to your account ("video.upload", and "video.publish" only where direct posting is offered). We cannot delete, edit or comment on anything already on your account, read your messages, or see your analytics.
• What we do with it. We upload the film you choose, with the title and caption you see before you press Post, only when you or someone in your workspace presses Post. Nothing is ever posted automatically. YouTube uploads are marked as altered or synthetic content and direct TikTok posts are labelled as AI-generated, because every ViewGC film is made with AI. A draft sent to your TikTok inbox is labelled when you finish it in TikTok, and every file we deliver says it is AI-generated in its own metadata.
• What we keep. The account’s ID, name and picture, the access and refresh tokens the platform issues, which we encrypt (AES-256-GCM) before storing and never show to anyone, and a record of each post: which film, when, its title and caption, and the link the platform returns.
• Who can use it. Anyone in the workspace that connected the account can post a finished film to it. The person who connected it, or a workspace admin, can disconnect it.
• Disconnecting. Disconnect in Settings, Connected accounts: we revoke our access with the platform and delete the stored tokens at once. You can also revoke access on Google in your Google Account under Security, third-party connections, or in TikTok under Settings, Security, Apps and services. Films already posted stay on your account until you remove them there.

We use what YouTube and TikTok share only to post the films you ask us to post and to show you which account is connected. We do not use it for advertising, we do not sell it, we do not use it to train AI models, and no person at ViewGC reads it except to fix a problem you report to us, or where the law requires. ViewGC’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. ViewGC uses the YouTube API Services; by connecting a YouTube channel you also agree to the YouTube Terms of Service, and Google’s handling of your information is described in the Google Privacy Policy. TikTok’s handling of your information is described in the TikTok Privacy Policy.

• To run your account, your workspace and its members, and to sign you in.
• To generate what you ask for, which means sending the relevant prompt and reference images to the AI providers named below.
• To bill you, meter credits, and show you what an action cost before you spend.
• To keep the Services working and secure: rate limiting, abuse prevention, debugging, and the audit trail above.
• To check what you ask us to make, and every picture or video you upload, against our terms before anything is generated. The check is automated: requests are read by a language model through our gateway, pictures by a Google model on Vertex AI. A refused request or upload is recorded in your workspace activity log with its reason, and a refused upload is deleted.
• To contact you about your account where we need to, such as a security or billing matter.
• To comply with law, and to enforce our terms.

We do not use your content to train our own models, and we do not sell personal information.

We use other companies to run the Services. Each receives only what it needs for its own part.

• AI generation providers. Prompts, actor descriptions and reference images are sent to the provider that runs a given generation: Google (Vertex AI, for video and image generation), Runway, ElevenLabs (voice), sync.so (lip sync), Higgsfield (character images) and BytePlus. What each one retains is governed by its own terms.
• YouTube (Google) and TikTok, only for an account you connect, and only the film and post text you choose to post.
• Expo, with Apple and Google, to deliver app notifications: the push token and the notification's title and text.
• Stripe, for payments and subscriptions. Your card details go to Stripe and not to us.
• Cloudflare, which stores and delivers generated media and serves our sites.
• Hetzner, where our servers and databases run, in Germany and Finland.
• A self-hosted language model gateway on our own infrastructure, for the writing and planning steps. Those prompts do not leave our servers except to the providers above.

We also share information when the law requires it, and if the business is ever sold or merged, in which case this policy continues to apply to the information transferred.

• Your account and workspace, and the content in it, for as long as the account exists.
• Generated videos and images, until you delete them or delete the account. Some items refuse deletion while something else still depends on them, and the message says which.
• The credit ledger, for as long as its workspace exists. Invoices and payment records are kept by our payment processor, Stripe, for as long as the law requires financial records to be kept.
• Tokens for a connected YouTube or TikTok account, until you disconnect it, or until it stops working and is not reconnected. A record of each post, for as long as the workspace exists.
• Server logs, for a short period for security and reliability.
• Consent records for digital twins, for as long as the twin exists and afterwards as proof that consent was given, because deleting the record would destroy the only evidence of the thing it exists to prove.

• See and correct. Your account and workspace details are editable in the app; ask us for anything you cannot reach.
• Delete. Delete your account yourself in Settings, Security on the web or Account in the app. It removes your account and sign-in at once and closes every workspace where you are the only member, with its content and files; any plan on such a workspace is cancelled. A workspace with other members carries on without you, and if you are its only owner you are asked to make someone else an owner first. Digital twin consent records are kept as described above, and Stripe keeps its own payment records.
• Export. Download a copy yourself in Settings, Security: your account and everything in your workspaces as one file, with links to every video and image that work for 7 days.
• Disconnect Google. In your Google Account under Security, third-party connections. You can then sign in with a password instead.
• Disconnect YouTube or TikTok, in Settings, Connected accounts, at any time.
• Withdraw consent for a twin, in the app, at any time.

Depending on where you live you may have further rights, including under the GDPR or the CCPA, such as objecting to a particular use or asking us to restrict it. Contact us and we will answer.

Passwords are stored only as bcrypt hashes. Sessions are httpOnly cookies that browser code cannot read. Generated media lives in a private bucket and is served through short-lived signed links, never a public URL. Public showcase assets live in a physically separate bucket, and there is no path from a private workspace into it. Administrator actions are recorded. API keys are stored only as hashes and carry scopes that are actually enforced.

No system is perfectly secure, and we do not claim otherwise. If you believe you have found a vulnerability, contact us before disclosing it publicly.

Our servers are in Germany and Finland. The providers listed above may process information elsewhere, including in the United States. Where we transfer personal information out of the EEA or the UK we rely on the standard contractual clauses.

The Services are not for anyone under 18, and we do not knowingly collect information from anyone under 18. Do not upload photographs of a child to build a digital twin. If you believe a child has given us information, contact us and we will delete it.

We will update this page when this changes and move the date at the top. If a change materially affects how we handle your information, we will tell you by email before it takes effect.

Rykon Technologies Inc, operating ViewGC. Write to us at privacy@viewgc.com, or through the contact page.