Privacy Policy
This Privacy Policy explains how Betterman Labs LLC, doing business as ("d/b/a") ClayStage ("ClayStage", "we", "us", "our") collects, uses, shares, and protects information when you use our marketing website, the ClayStage application, and related services (together, the "Service"). By using the Service, you agree to the practices described here.
1. Who we are
ClayStage is a multi-tenant software-as-a-service ("SaaS") product for creating 3D content — staging scenes, generating photoreal renders, animating without keyframes, posing characters, and producing video and product shots. For privacy questions or to exercise your rights, contact us at our email.
2. Information we collect
Information you provide
- Account & identity data. When you create an account with an email and password, we collect your email address and a securely managed credential (passwords are hashed and stored by our authentication provider — we never see or store your plaintext password). If you sign in with Google (OAuth), we receive your basic profile from that provider, such as your email address and account identifier, used to create and authenticate your ClayStage account.
- Organization & team data. ClayStage is organized into isolated workspaces ("organizations" or "studios"). We store your organization name, your role within it (owner, admin, or designer), and — for invitations — the email address an admin enters to invite a teammate.
- Content you create. The clay scenes, projects, text prompts, reference images you upload, photoreal renders, animations, and videos you make on the stage, along with associated metadata (titles, project structure, library items, and settings).
- Payment information. When you subscribe to a paid plan, payment is processed by our payment provider, Stripe. Stripe handles your card details directly; we do not collect or store full card numbers. We receive limited billing information such as your plan, subscription status, and partial card details (for example, the last four digits).
- Communications. Messages you send us for support, and any email you submit to our launch/waitlist form.
Information collected automatically
- Usage and device data. Pages and features used, generation activity, browser and operating system, IP address, and approximate location derived from your IP.
- Session tokens. To keep you signed in, the application stores an authentication session (access and refresh tokens) in your browser's local storage. These tokens identify your session to our authentication provider and expire/refresh automatically.
- Cookies and similar technologies. Essential storage to run the Service and keep you signed in, plus — only with your consent — a limited amount of analytics. See "Cookies and analytics" below.
3. How your content is processed to generate output (AI)
ClayStage's core feature turns your staged scenes and prompts into images and video using a third-party generative-AI provider, Runway. To produce your output, ClayStage sends the necessary inputs — your text prompts, reference and scene images, and exported viewport clips — to Runway's API for the sole purpose of generating the render, animation, or video you requested. The generated output is returned to ClayStage, stored in your private workspace, and made available to you.
As between you and ClayStage, you own the inputs you provide and the outputs generated from them, subject to our Terms of Service and to the terms of the underlying model provider. We do not claim ownership of your projects, and we do not use your private content to train our own or any third party's foundation models without your explicit, separate opt-in. Runway processes your inputs as our sub-processor to perform the generation; its handling of submitted content, and its own rights to use submitted inputs and outputs to operate and improve its models, are governed by Runway's Terms of Use and privacy practices.
Please note that outputs are produced by AI models and are not guaranteed to be accurate, original, or unique — because of how generative AI works, the same or similar outputs may be generated for other users. Your use of generated content is also subject to the acceptable-use and content rules described in our Terms of Service, which incorporate Runway's prohibitions on unlawful, infringing, and harmful content.
4. How we use information
- To provide, operate, and improve the Service — including authenticating you, running your workspace, generating renders/animations/video from your input, and storing your projects.
- To process payments, manage subscriptions and credits, and administer your plan.
- To enforce per-tenant isolation so each organization's data stays separate and private.
- To communicate with you about your account, security, updates, and (where permitted) product news.
- To monitor for abuse, enforce our Terms, secure the Service, and comply with legal obligations.
- To analyze aggregate usage so we can make the Service faster and better. We do not sell your personal information.
5. Sub-processors (who we share data with to run the Service)
We rely on a small set of vendors ("sub-processors") to operate the Service. Each processes data only as needed to provide its function and under contractual confidentiality and security obligations. Our current sub-processors are:
| Sub-processor | Purpose | Data it touches | Region |
|---|---|---|---|
| Supabase | Authentication, application database (Postgres), and object storage for your uploads and generated files. | Account email & hashed credentials, OAuth identifiers, profile/org/role data, projects, prompts, generation metadata, and stored images/videos. | United States |
| Runway | Generative-AI API that produces images and video from your inputs. | Your prompts, reference/scene images, and exported viewport clips submitted for generation. | United States |
| Vercel | Application and website hosting, serverless API, and content delivery (CDN). | Requests to the Service, including IP address and standard request/usage metadata. | United States / global edge |
| Stripe | Payment processing and subscription billing. | Payment card details (handled directly by Stripe), billing contact, plan and transaction data. | United States |
| Google (OAuth) | Optional "Continue with Google" sign-in. | Basic profile (email, account identifier) shared only if you choose Google sign-in. | United States / global |
We may also disclose information for legal and safety reasons (when required by law, to enforce our Terms, or to protect rights, safety, and security) and in connection with a business transfer (such as a merger, acquisition, or sale of assets, with notice to you).
6. Where your data is stored
Your account data, projects, prompts, generation metadata, and stored renders/uploads are held in our Supabase Postgres database and Supabase object storage, hosted in the United States. The application and API are hosted on Vercel. If you access the Service from outside the United States, your information will be transferred to and processed in the United States and other countries where our sub-processors operate.
7. Data retention and deletion
We keep your account and content for as long as your account is active or as needed to provide the Service. You can delete individual projects, generations, and uploads at any time from within the app, which removes the associated records and stored files. You may also request deletion of your entire account by emailing us; on account deletion we remove or anonymize your personal data and content, except where we must retain limited records for legal, tax, accounting, or security purposes. Backups are rotated on a regular cycle and purged in the ordinary course.
8. Your rights and choices
Depending on where you live (for example, under the EU/UK GDPR or the California CCPA/CPRA), you may have rights to access, correct, export, delete, or restrict the processing of your personal information, and to object to certain processing. To exercise these rights, contact us. You can also opt out of non-essential analytics at any time via the cookie banner or your browser settings. We will not discriminate against you for exercising your rights.
9. Cookies and analytics
We use essential cookies and local storage to keep you signed in and run core features — these are always on because the Service can't function without them. With your consent, we use a small amount of analytics to understand and improve usage. You can accept or decline non-essential analytics in the cookie banner ("Essential only" keeps analytics off), and you can change your choice later. Declining does not affect core functionality.
10. Security
We protect your information with industry-standard safeguards, including encryption in transit (TLS/HTTPS) and encryption at rest for our managed database and storage, strict per-tenant isolation enforced by Postgres row-level security and organization scoping, role-based access controls, and careful handling of secrets and API keys. No method of transmission or storage is perfectly secure, but we work to protect your data and to notify you of material incidents as required by law. For more detail, see our Trust & Security overview or write to us.
11. International transfers
We may process and store information in countries other than your own, including the United States. Where required, we use appropriate safeguards (such as standard contractual clauses) for cross-border transfers.
12. Children
The Service is not directed to children under 16, and we do not knowingly collect their personal information. If you believe a child has provided us personal information, contact us and we will delete it.
13. Changes to this policy
We may update this policy from time to time. We will post the new version here and update the effective date; material changes will be communicated where appropriate.
14. Contact
Questions about privacy? Email us, or write to ClayStage at [Mailing address — to be added].