Privacy Policy

1. Information We Collect

We collect the following categories of data:

• Google Identity Data: Profile information obtained during sign-in.
• YouTube Channel and Video Data: Metadata retrieved from a connected YouTube channel.
• Transcript Data: Text transcripts associated with videos from a connected YouTube channel.
• Map and Place Data: Locations and geographic information relevant to video content.
• AI-Derived Outputs: Generated summaries, captions, place analyses, routes, and similar outputs.
• Session and Cookie Data: Data used to maintain your authentication state.

2. Purposes of Processing

We process your data for the following purposes:

• Account Creation and Authentication: To verify your identity and manage your MVM account.
• Channel Linking: To connect and sync data from your connected YouTube channel.
• Map Generation and Related Product Operation: To create MVM-generated structural outputs.
• Service Security and Operations: To maintain the stability and safety of MVM.

3. Google API Data Use and Protection

MVM's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

MVM uses Google user data only to provide user-facing MyVideoMap functionality requested by the user, including Google sign-in, creator account identification, YouTube channel connection, YouTube video synchronization, and map/content workflow operation.

MVM does not sell Google user data. MVM does not use Google user data for advertising. MVM does not use Google user data to train generalized AI or machine learning models.

We use security procedures intended to protect the confidentiality, integrity, and availability of Google user data and other sensitive service data. These procedures include encryption in transit, restricted operational access, server-side OAuth handling, authenticated session management, and operational monitoring for security and abuse prevention.

MVM applies data protection mechanisms intended to protect Google user data and other sensitive service data, including:

• HTTPS/TLS for data transmitted between the user browser and the MVM service.
• Server-side processing of OAuth callbacks and Google API interactions.
• Cookie-based session handling using the mvm_session cookie for authenticated application state.
• Restricted access to production systems and stored service data based on operational need.
• Separation of authentication/session data from normal public website browsing.
• Operational logging for service security, debugging, and abuse prevention.

Google OAuth tokens and Google user data are used only for the purposes described in this Privacy Policy and are not disclosed to third parties except as necessary to operate the service, comply with law, or process user-requested service workflows.

4. Authentication and Session Management

MVM uses a session cookie to maintain authentication-related state. The current frontend authentication state is based on the mvm_session cookie. MVM currently uses cookie-based authentication state in the frontend experience.

During the authentication flow, MVM handles your google_id_token solely to verify identity and establish the mvm_session.

5. YouTube Integration Boundary

MVM uses read-only access to YouTube data for channel connection and related service functionality. We do not edit, upload, or delete videos on your connected YouTube channel.

6. AI Processing

MVM currently uses internal-only AI processing for covered AI functionality. Covered creator and user content is not sent to third-party AI providers in the current implementation. MVM processes covered AI functionality within its current internal-only processing model.

7. Data Storage and Retention

MVM retains certain service data for operational purposes while an account remains active. Where automated retention enforcement is not implemented, data may remain stored until removal through account lifecycle handling or contact-based deletion processing.

MVM stores AI-derived outputs that support map generation and related product functionality. AI-derived outputs may remain associated with an account until removed through contact-based deletion handling, unless a more specific removal flow is implemented.

Operational and security logs may be retained for operational and security purposes.

8. User Control and Deletion

MVM currently supports deletion requests through a contact/manual request process. Self-service deletion is not currently available.

To request the deletion of your account and associated data, please contact us at: support@myvideomap.com.