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 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.
• 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.

• 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.

• 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 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.
• 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 ask us to delete the account. Some items refuse deletion while something else still depends on them, and the message says which.
• The credit ledger and billing records, for as long as we are required to keep financial records.
• 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. Ask us and we will delete your account and its content, except what we must keep for law or accounting.
• Export. Ask us for a copy of your content.
• Disconnect Google. In your Google Account under Security, third-party connections. You can then sign in with a password instead.
• 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.