Where your code goes.
What MotionRepo touches, what it keeps, and what it does not.
How we reach your repositories
Through a GitHub App you install, not a personal token. Each run gets a short-lived access token. MotionRepo copies your repositories to read them and never writes to them. Webhooks from GitHub are signature-checked.
What the AI sees
To write scripts and documents, parts of your code are sent to Claude, Anthropic’s model. Document sessions get no tools at all. Video sessions work in a separate copy of the code, with rules against installing software, network access and reading secrets, and what they create is cleaned up afterwards. These are guard rails, not a sandbox.
Sign-in and accounts
Signing in with GitHub reads your name and picture once; the GitHub token is then thrown away. Each person sees only their own repositories, videos and credits, or their team’s on Max. New accounts are approved by hand.
Style references
When you give it a video or photo to copy the look of, the original is deleted after measuring. Only up to six stills and a written description are kept. Links to private network addresses are refused.
Self-hosted
Everything runs on your servers, on your own Claude account. Secrets stay in your own environment file and are never committed.
What we do not claim yet
No SOC 2 or ISO 27001 certification, no SSO or two-factor sign-in, and no log of who did what. If your review needs any of these, tell us.
Questions from your security review?