VoVo Privacy Policy
Key points, quoted from this page
-
"we do not sell personal information"
Read Section 11 -
"When you delete your account, we will delete or anonymize your personal information within 90 days, except where retention is required for legal compliance."
Read Section 5 -
"To exercise these rights, submit a support ticket and say it is a privacy request."
Read Section 7
On this page
1. Introduction
Jag Journey, LLC ("we," "us," or "our") operates the VoVo platform. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service.
Please read this Privacy Policy carefully. If you do not agree with the terms of this Privacy Policy, please do not access the Service.
2. Information We Collect
2.1 Information You Provide
We collect information you voluntarily provide when you:
- Create an account: Name, email address, password, organization name
- Subscribe to a plan: Billing address, payment card information (processed by Stripe)
- Use the Service: Content you create, upload, or manage
- Contact us: Messages, feedback, support requests
- Participate in surveys or promotions: Responses and preferences
2.2 Automatically Collected Information
When you access the Service, we automatically collect:
- Device information: Browser type, operating system, device identifiers
- Log data: IP address, access times, pages viewed, referring URLs
- Usage data: Features used, interactions, preferences
- Visit activity: Clicks, scrolling, form starts and completions, technical errors, page speed, and session recordings. See Section 8.3
- Cookies and tracking: See our Cookie Policy section below
2.3 Information from Third Parties
We may receive information from:
- Payment processors (Stripe) for billing verification
- Analytics services for usage patterns
- Social login providers if you choose to connect accounts
2.4 Optional Calendar Connections
If an appointment host chooses to connect Google Calendar, VoVo asks Google for permission to see the host's Google account identity and email address, see the list of calendars the host is subscribed to, see busy times on the host's calendars, and add and remove calendar events. With these permissions we receive that host's Google account identifier and email address, the identifiers, names and access roles of calendars available to that account, and busy time intervals from the calendars the host selects. We use busy intervals to check appointment availability. We do not read, list or change the titles, descriptions or other details of events in the host's calendars. Busy-check results may be cached for up to 45 seconds.
We store the host's calendar choices, connection status and check timestamps, and the access and refresh tokens, which are encrypted before they are stored, so the connection can keep working. When the host chooses a writable calendar for new bookings, we send Google the appointment type, start and end times, invitee name and email, phone number if provided, and meeting or location details to create the event. We may remove that VoVo-created event when its booking is cancelled. Google receives and processes these details under Google's Privacy Policy.
VoVo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use information received from Google APIs only to provide the appointment features the host selected. We do not sell it, transfer it to advertising platforms, data brokers or information resellers, use it to serve ads, use it to decide creditworthiness or lending, or use it to create, train or improve any artificial intelligence or machine learning model. We transfer it only as needed to provide the feature with the host's consent, for security, to comply with the law, or as part of a merger, acquisition or sale of assets with the host's prior explicit consent. Our staff do not read it unless the host asks us to in a support request, it is needed to investigate security or abuse, or the law requires it. This section controls how we handle information received from Google APIs; the general uses and sharing in Sections 3 and 4 do not expand it.
Google Calendar access is optional. A host can disconnect in Calendar Connections at any time. We then stop synchronizing and delete the stored Google access and refresh tokens right away, keeping only the host's calendar choices so a later reconnection restores them; those choices are deleted with the account as Section 5 describes. A host can also remove VoVo's access from their Google Account at myaccount.google.com/connections. Disconnecting does not itself remove existing Google events or VoVo booking records. To request access to or deletion of related data, submit a privacy support ticket.
If an appointment host chooses to connect Microsoft Outlook, we receive that host's Microsoft account identifier and available account name or email, the identifiers, names and editability of calendars available to that account, and the start, end, availability and cancellation state of events on calendars the host selects. We use those event fields to block occupied appointment times, not to read event titles or descriptions. Busy-check results may be cached for up to 45 seconds. We store the host's calendar choices, connection status, check timestamps and encrypted access and refresh tokens.
When the host chooses a writable Outlook calendar, we send Microsoft the appointment type, start and end times, invitee name and email, and meeting or location details to create the booking event. Microsoft may send the invitee a calendar invitation. We may remove a VoVo-created event when its booking is cancelled. Microsoft processes those details under its Privacy Statement. Outlook access is optional; the host can disconnect in Calendar Connections to stop future synchronization and delete the stored Outlook tokens. Disconnecting does not itself remove existing Outlook events or VoVo booking records. To request access to or deletion of related data, submit a privacy support ticket.
2.5 Copyright Notices on VoVo Live
When you send a copyright notice through a VoVo Live channel, we keep what you wrote, any files you upload, and a record of where it came from: your network (IP) address and any forwarding addresses, its approximate location and network provider, which we may check with an IP reputation service, your browser and device, and the time. We use this to handle your notice and to prevent false and abusive notices. We keep it for at least three years, and longer while a notice, counter-notice or legal claim is open, and we may share it with the channel's owner, with courts and with law enforcement, as our copyright policy describes.
If you verify your identity for a notice, Stripe checks your ID and selfie under its own privacy policy and tells us whether they matched, the name on the ID, the kind of document and the country that issued it. We do not receive or keep images of your ID or its number.
2.6 YouTube Channel Connections
VoVo uses YouTube API Services in two ways: VoVo staff upload VoVo's own videos to VoVo's own YouTube channel, and a client's owners and administrators can connect the client's own YouTube channel in Social Media and upload the client's videos to it. Anyone who connects a YouTube channel through VoVo agrees to be bound by the YouTube Terms of Service, and Google handles information under the Google Privacy Policy. A channel's owner can remove VoVo's access at any time in the Google Account security settings at myaccount.google.com/permissions, as well as by disconnecting the channel as described below.
VoVo's own channel. Only VoVo's central administrators can connect VoVo's channel or upload a video to it, and every upload is approved by the staff member who made the video after watching it. When a staff member connects the channel, Google asks them to allow VoVo to upload videos, to manage the channel's videos, thumbnails and playlists, to add captions and, if they allow it, to view YouTube Analytics reports for the channel, read only. With these permissions we store the channel's OAuth refresh token, encrypted before it is stored; the short-lived access token is kept only in memory and is never stored. We also store the channel's ID, title, picture address and uploads list, which staff member connected it and when, and, for each video we upload, its YouTube video ID, address, upload and processing status and visibility. We keep our own record of each upload: the title, description, tags and settings we sent, which staff member approved it and when, and how much of our daily YouTube quota it used. We use this information only to upload and manage our own videos, to make sure a video is never uploaded twice, and to show our staff the status of each upload. We do not sell it, use it for advertising, or share it with anyone; the only information we send is the video and its details and our replies to comments, which go to YouTube, and a comment a staff member asks an AI assistant to draft a reply to, as described below.
For each video we uploaded we also read its view, like and comment counts and, when the YouTube Analytics permission was allowed, its estimated minutes watched and average view length, and we read the public comments left on it: the comment, its author's YouTube display name and when it was posted. Our staff see these on an internal admin page to see how each video is doing and to answer comments. A staff member may have an AI assistant we use under our own accounts draft a reply, which the staff member reviews before it is posted to YouTube. A new comment opens an internal support ticket that names the video but holds neither the comment nor its author.
Every day we read the channel's details and the status, counts, watch time and comments of each video we uploaded from YouTube again, so YouTube data we store is refreshed or deleted within 30 days. When the channel is disconnected, we ask Google to revoke our access and delete the stored token, the channel details and the YouTube details of uploaded videos right away; videos already on YouTube stay there until they are deleted on YouTube. Our audit log records who connected or disconnected the channel and who approved or deleted an upload, and when, without YouTube data.
A client's own channel. A client's owner or administrator, signed in to VoVo as themselves, can connect one YouTube channel to the client's account in Social Media > YouTube. VoVo staff cannot connect a client's channel or upload to it, including when they help inside the client's account. The person signs in on Google's own page, so VoVo never receives their Google password. Google then asks them to allow the one YouTube permission we request, which Google describes as letting an app see, edit and permanently delete their YouTube videos, ratings, comments and captions. We use it only to upload the videos the client approves, to read the channel's ID, title, picture and uploads list, and to read the upload status and visibility of the videos we uploaded. We do not change or delete the channel's other videos, ratings, comments or captions, and we do not read the channel's analytics or comments.
When the channel is connected we store its OAuth refresh token, encrypted before it is stored; short-lived access tokens are kept only in memory and are never stored. While the person finishes connecting, the sign-in result is held encrypted for up to 10 minutes and can be used only by the person who started it. We also store the channel's ID, title, picture address and uploads list, and which person connected it and when. A video is uploaded only after an owner or administrator chooses one of the client's finished videos on VoVo, writes its title, description and tags, chooses who can watch it (Private unless they choose otherwise) and approves the upload after watching it. We send YouTube the video and those details, with a short reference line added to the end of the description so the same video is never uploaded twice. We tell YouTube the video is not made for kids and, for tutorial videos VoVo made for the client, which are narrated with an AI voice, that it contains altered or synthetic content. Before an upload starts we read the channel's most recent uploads, up to 50, only to look for that reference line, and we do not store them. For each upload we keep our own record: the video it came from, the title, description, tags and visibility sent, who approved it and when, its progress, how much of our daily YouTube quota it used and, from YouTube, its video ID, address, upload status and visibility.
We use this information only to connect the channel, upload the videos the client approves, make sure a video is never uploaded twice and show the client's owners and administrators how each upload went. We do not sell it, use it for advertising, or share it with anyone other than YouTube.
Every day we read the connected channel's title, picture and uploads list and the upload status and visibility of each video we uploaded again, so YouTube data we store is refreshed or deleted within 30 days. If Google no longer accepts our access or the channel can no longer be found, we disconnect the channel and delete its details. When an owner or administrator disconnects the channel in Social Media > YouTube, we ask Google to revoke our access and right away delete the stored token, the channel's details and, for each upload, its YouTube video ID, address, status and visibility; unfinished uploads stop. We keep our record of what was approved: each upload's title, description, tags, chosen visibility, the video it came from, and who approved it and when. Videos already on YouTube stay there until they are deleted on YouTube. If the channel's owner removes VoVo's access in the Google Account security settings instead, our next daily check deletes the channel's details the same way. To ask about this data, submit a privacy support ticket.
3. How We Use Your Information
We use collected information to:
- Provide, operate, and maintain the Service
- Process transactions and send billing information
- Send you technical notices, updates, and support messages
- Respond to your comments, questions, and requests
- Improve and personalize your experience
- Monitor and analyze trends, usage, and activities
- Detect, investigate, and prevent fraudulent or unauthorized activity
- Comply with legal obligations
5. Data Retention
We retain your information as long as your account is active or as needed to provide services. We may retain certain information for legitimate business purposes or as required by law.
When you delete your account, we will delete or anonymize your personal information within 90 days, except where retention is required for legal compliance.
6. Data Security
We implement appropriate technical and organizational measures to protect your information, including:
- Encryption in transit (TLS/SSL) and at rest
- Access controls and authentication
- Regular security assessments
- Employee training on data protection
However, no method of transmission over the Internet is 100% secure. We cannot guarantee absolute security.
7. Your Rights and Choices
Depending on your location, you may have rights to:
- Access: Request a copy of your personal data
- Correction: Update inaccurate information
- Deletion: Request deletion of your data
- Portability: Export your data in a common format
- Opt-out: Unsubscribe from marketing communications
- Restriction: Limit how we process your data
To exercise these rights, submit a support ticket and say it is a privacy request.
9. Children's Privacy
The Service is not intended for children under 16. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately.
10. International Data Transfers
Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place for such transfers.
11. California Privacy Rights (CCPA)
California residents have additional rights under the CCPA:
- Right to know what personal information is collected
- Right to delete personal information
- Right to opt-out of sale of personal information (we do not sell personal information)
- Right to non-discrimination for exercising privacy rights
12. European Privacy Rights (GDPR)
If you are in the European Economic Area, you have rights under GDPR including:
- Right to access, rectification, and erasure
- Right to restrict processing
- Right to data portability
- Right to object to processing
- Right to withdraw consent
- Right to lodge a complaint with a supervisory authority
13. Third-Party Links
The Service may contain links to third-party websites. We are not responsible for the privacy practices of these sites. We encourage you to review their privacy policies.
14. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email or through the Service. Your continued use after changes constitutes acceptance.
15. Contact Us
If you have questions about this Privacy Policy, please contact us:
- Privacy inquiries: Submit a support ticket
- General inquiries: Submit a support ticket
Data Controller:
Jag Journey, LLC
Texas, USA
Ready to Simplify Everything?
Join the organizations, entrepreneurs, and creators who've replaced their patchwork of tools with one integrated platform. Get started today.
Have questions? Talk to our team · We're real humans.