Privacy Policy
Loco is a local-first iPhone app for turning your beat and visual into a YouTube publication. This policy explains exactly which information the app handles, where it goes, and how it is removed.
1. Operator and contact
Loco is operated by Ashot Grigoryans. For privacy, support, or data-deletion questions, email itsvossibaby@gmail.com or open a request in the public Loco support tracker. Do not send passwords, OAuth tokens, callback URLs, or private media in a public issue.
2. Information Loco collects and accesses
Information you provide on your iPhone
Loco stores the media and publication information you choose: imported audio and visual files, optional thumbnail, project settings, title, description, tags, category, audience, playlist choice, rendered video, upload progress, and recovery records. It also stores the selected Google account and YouTube channel identity needed to separate your projects by channel. This information stays in protected app storage on your device; Loco has no account database, cloud media library, or Loco server.
Information received from Google and YouTube
Only after you choose to connect Google, Loco receives the Google identity and YouTube channel you authorize. When you open a YouTube feature, it may request the data needed for that feature from the official YouTube Data API: channel identity, video categories, details from a video you select for reuse, playlists you select, upload and post-upload results, and processing status. Loco uses this data solely to show the requested UI, preserve the publication you started, and carry out the upload, metadata, thumbnail, playlist, or status action you explicitly choose.
Credentials
Google OAuth credentials are handled by Google Sign-In and protected device storage. Loco never asks you to type a Google password into the app, never embeds a client secret, and does not send OAuth credentials to a Loco server.
3. How information is used and shared
Loco uses your information to create a local project, render a video on your iPhone, resume interrupted work, and, only after your instruction, publish to the YouTube channel you selected. For a YouTube action, the relevant video, metadata, thumbnail, playlist request, or status request is sent directly to Google and YouTube through their official services under your authorization.
Loco does not sell, rent, or use Google or YouTube API Data for advertising, profiling, or analytics. It does not share that data with advertising networks, data brokers, social networks, or other third parties. Apple system services may process files, playback, protected storage, and background work on the device. Google and YouTube process the data sent to them under their own policies, including the Google Privacy Policy.
4. Device storage, cookies, and similar technology
The native Loco app stores project information and authorization state in protected local device storage and Keychain-backed authorization storage. It does not use its own cookies, trackers, advertising identifiers, or analytics SDKs. Google sign-in may open a Google-hosted authorization page; Google may use cookies or similar technologies there under Google’s policies. The Loco website does not intentionally set Loco analytics or advertising cookies, but your browser, GitHub Pages, and linked third-party sites may operate under their own policies.
5. Refresh, retention, and deletion of YouTube API Data
- Video categories, reusable-video details, and playlist choices are requested when you open the relevant selector. They are held only for the active app session and released when the session ends, the account/channel changes, or you disconnect.
- While YouTube is processing an uploaded video, Loco refreshes the processing state on a bounded schedule: 15 seconds, 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, 20 minutes, 30 minutes, and then no more than once per hour until the state is resolved or a retry is needed.
- Project data you created remains on your iPhone until you delete that project, remove the app, or use the storage controls. Deleting a project removes its app-owned media, render, metadata draft, and upload journals.
- Choosing Disconnect Google revokes Loco’s Google and YouTube authorization and deletes the app’s saved authorized data and transient YouTube session data. A failed revocation is shown as a failure; Loco does not report Disconnect as complete while the grant may still be active.
Disconnecting Loco or deleting a local project does not delete videos, playlists, or channel data already stored by YouTube. You can manage those items in YouTube Studio. You can also revoke access in Google Security Settings.
6. Your choices
- Use Loco locally without connecting Google.
- Cancel or retry an upload without rerendering when a retained render is available.
- Disconnect Google/YouTube access from Loco’s Account area.
- Delete a project and its app-owned files.
- Request deletion help by email or through the linked support tracker.
7. Children
Loco is not directed to children under 13 and does not knowingly collect personal information from children.
8. Changes to this policy
We may update this policy when Loco or its data practices change. The effective date at the top identifies the current version.
9. Contact
Email itsvossibaby@gmail.com for a privacy request. We use the contact details you provide only to respond to and process that request.