Privacy
Last updated 20 July 2026
Motio turns a written brief into a finished video. Part of that runs on a server and part runs on your phone, so this page is specific about which is which.
Sent off your device
- Your prompt. The text you type is sent to the AI service so it can plan the video.
- Photos you attach. If you add images to a brief, they are sent with it so the model can compose around them.
- Scene descriptions for generated imagery. Short phrases the model invents (“misty pine forest at dawn”) go to the image service.
Stays on your phone
- Every finished video. Rendering and encoding happen on the device. Exported MP4s are never uploaded.
- Your gallery. Motio only reads the images you explicitly pick.
- Your settings and logs. The API endpoint, key and diagnostic log live in the app's own storage.
What is never collected
No accounts. No advertising SDKs. No analytics or telemetry. No location, contacts or device identifiers. Motio has no login because it has nothing to log in to.
The AI service
By default Motio talks to an endpoint operated by the developer, which forwards requests to Google's Gemini models to write the plan and generate images. That service keeps a usage ledger — timestamps, model names and token counts, for cost accounting — and does not store your prompts or images beyond the lifetime of the request.
You can point the app somewhere else entirely: Settings accepts any
OpenAI-compatible base URL, API key and model name, including one you host yourself. Then nothing
reaches the developer's servers at all.
Children
Motio is not directed at children under 13 and collects no personal information from anyone.
Changes
If this policy changes, the date above changes with it. Material changes will be noted on the Motio page.
Contact
Questions, deletion requests or anything else: apps@whatamieatingtoday.com.