Privacy Policy
Last updated August 2026 · version 2026-08-02
This policy describes how Motionpiece handles data during Early Access. It is grounded in how the product is actually built. Where a practice is still being finalized, we say so plainly rather than promise something we have not yet committed to.
The short version
To make your film, the contents of the repository you connect are transmitted to third-party AI providers for processing, along with material derived from it. Those providers process it to deliver the service. Motionpiece does not use your repository content or your films to train its own models.
Who controls your data
Vino, trading as Motionpiece, is responsible for the personal information described in this policy.
Questions about your data go to motionpieceai@gmail.com, which a person reads.
Account and authentication data
When you sign in we store the account information needed to authenticate you: your name and email address, and an identifier from your sign-in provider (Google) or your email and a securely hashed password. Sign-in is handled by our authentication layer; we do not store your Google password.
Repository access and metadata
You connect repositories through a GitHub App with read-only access to the repositories you select. We store the installation and repository metadata needed to operate the service (for example the installation id and the selected repository names). Access tokens used to read your code are short-lived and minted on demand for a single operation; we do not store long-lived repository access tokens.
Repository source processing
To understand your product, Motionpiece checks out your repository at a specific commit inside an isolated, disposable environment and analyzes it. From that analysis we store structured facts about your product, such as file and route names, component names, dependencies, design tokens, terminology, and a written product understanding. We do not run or install your application's own scripts during this process. A formal retention schedule for the transient working copy and the derived structured data is being finalized as a launch decision.
Generated content
The storyboards, scripts, narration audio, music, sound effects, video renders, poster images, and project intelligence produced for you are stored so you can view, share, and download your Motionpieces. Media artifacts are stored in private, per-account object storage and served through short-lived signed links.
Feedback
If you send feedback, we store your message together with your account id and email so we can understand and reply to it.
Payment data
Payments are processed by Stripe. We do not receive or store your full card number. We store order records: order state, amounts, timestamps, a Stripe customer or session identifier, and the delivery-target timestamps needed to track your order.
Analytics and cookies
We use a first-party session cookie to keep you signed in. We record product events (such as which steps you complete) to understand and improve the product. We aim to keep this minimal and first-party.
Service providers
Motionpiece relies on third-party providers to operate, including providers for authentication, database and cache hosting, AI model inference, narration, music, isolated code execution and rendering, object storage, email delivery, payments, and application hosting. These providers process data on our behalf under their own terms.
Use for model training
Motionpiece does not use your repository content or your generated Motionpieces to train its own models. Data you provide is processed by third-party AI providers to deliver the service, subject to each provider's terms; a consolidated statement of each provider's training and retention posture is being finalized as a launch decision.
How long we keep things
These periods are enforced by the system, not merely intended. Each one is implemented as a database expiry rule, a bounded queue, or a documented procedure with a named owner.
| Data | Kept for |
|---|---|
| Orders, payments, invoices, refunds and click-wrap acceptance records | 7 years |
| GitHub webhook delivery records | 7 days |
| GitHub App setup continuation tokens | 15 minutes |
| Rate-limit counters | The length of the rate-limit window |
| Background job history | The most recent 1,000 completed and 5,000 failed jobs |
| Email delivery records held by our email provider | As set by Resend |
| Database backups | As set by our database provider's backup rotation |
What we have not automated yet
We have not yet automated deletion for the categories below. Today we keep this data until you ask us to delete it, and we act on that request. We are implementing scheduled deletion for each of them, and we will state the period here once it is enforced rather than before.
- One-time email verification codes
- Abandoned drafts you never ordered
- Repository analysis and production working data
- Your delivered films and their stored files
- Your account
Two things worth stating plainly. Deleting your data does not reach into our database backups, which rotate on our provider's schedule. And we keep order, payment and agreement records for seven years regardless of a deletion request, because tax and dispute rules require it.
Deleting your data
You can request access to, correction of, or deletion of your data by emailing motionpieceai@gmail.com. We act on those requests by hand today — there is no self-serve account deletion yet, and we would rather say that than imply a button exists.
International processing
Our providers operate in the United States and other regions, so your data may be processed outside your country of residence.
Security
We use access controls, per-account scoping of stored artifacts, short-lived signed links, short-lived repository tokens, and isolated execution for untrusted code. No system is perfectly secure, and we cannot guarantee absolute security.
Your rights and contact
You can access, correct, or delete your data, and ask questions about this policy, by emailing motionpieceai@gmail.com. See also our Terms of Service.