Livote

Privacy Policy

This is a translation for convenience. The Japanese version is authoritative, and Japanese law governs.

VirtualCross ("we") complies with the Act on the Protection of Personal Information and other applicable laws, and sets out this Privacy Policy (this "Policy") on how we handle users’ information in Livote (the "Service").

In this Policy, "Broadcaster" means a user who registers an account and creates or runs events, "Viewer" means a user who joins a vote through a participation URL or QR code distributed by a Broadcaster, and "Organisation" means the unit to which events, plan subscriptions, tickets and the like belong, created when a Broadcaster creates an account.

1. Operator

The business that provides the Service and handles users’ personal information is VirtualCross. Our address and the name of our representative are published on the Business Information page of the Service.

2. Information we collect

We collect the following information in providing the Service.

InformationWhoseCollected byPurpose
The identifier, display name, email address and profile image URL received from your Google account, and the information Google issues to link the sign-inBroadcastersUs (received from Google)Creating accounts and signing in, verifying identity, sending notices, showing to other Broadcasters in the same Organisation
Sign-in records (IP address, browser type and similar information)BroadcastersUsManaging signed-in sessions, preventing unauthorised sign-in
Content registered by Broadcasters (event names, questions, options, images, input to AI features and so on)BroadcastersUsProviding the Service (including display on Viewers’ screens and the stream overlay), producing AI output
Email addresses of people invited as membersInvitees (entered by a Broadcaster)UsSending invitation emails, matching invitations, showing to Broadcasters in the same Organisation
Current plan, purchase records and payment identifiersBroadcasters using Paid FeaturesUs (received from Stripe)Billing and managing plans, tickets and credits
Email address, name and similar details entered at payment (excluding card numbers)Broadcasters using Paid FeaturesStripe (we can also see them in the Stripe dashboard)Payment, responding to billing enquiries
Credit card numbers and other payment detailsBroadcasters using Paid FeaturesNot collected (handled by Stripe)—
An anonymous identifier issued automatically per device, voting records, and how you joined (QR code or direct link)ViewersUsTallying votes and showing them on the stream overlay, discouraging repeat voting by the same viewer
Email address, nameViewersNot collected—
IP addressEveryoneUs (via Cloudflare)Bot protection (Cloudflare Turnstile) and limiting bursts of requests (rate limiting)
Records of the Service’s server operation (time of access, URL requested, error details and so on; may include IP addresses and browser information)EveryoneUs (stored in Cloudflare’s logging feature)Investigating faults, preventing abuse
Information stored in cookies and the browser’s local storageEveryoneUsKeeping you signed in, identifying a viewer’s device, showing which option you already chose (kept only on your device and not sent to us), remembering settings such as display language
Name, email address, company name and message entered in the contact formPeople who contact usUsResponding to enquiries
Location, camera imagesEveryoneNot collected—

We do not store passwords. We do not collect email addresses or names of Viewers. A Viewer’s IP address is used only for the checks above and is not stored with voting records.

The Service does not use location data or your camera.

3. Purposes

We use the information we collect for the following purposes.

  1. providing the Service (including managing accounts, creating and streaming events, and tallying votes and showing them on the stream overlay)
  2. discouraging repeat voting by the same viewer, preventing abuse, investigating faults and keeping the Service secure
  3. billing and managing plans, tickets and credits
  4. sending member invitation emails
  5. showing members of the same Organisation each other’s display names, email addresses and roles, and the email addresses of pending invitees
  6. producing output from the AI features
  7. responding to enquiries and sending important notices about the Service
  8. dealing with conduct that breaches the Terms of Service
  9. producing statistics to improve the Service, in a form that cannot identify an individual

4. Processors

We entrust the handling of information to the following businesses to the extent necessary for the purposes above. We select processors carefully, secure security measures by contract, and supervise them as necessary and appropriate.

ProcessorCountryWhat we entrustWhere data is stored
Cloudflare, Inc.United StatesServers, database and file storage, storing records of server operation (logs), sending email (Cloudflare Email Sending, for invitation emails and forwarding enquiries; the body of each email sent is kept for about 7 days to confirm delivery)Data centres in the Asia-Pacific region (the country cannot be identified because Cloudflare does not publish it). Where access logs are stored also cannot be identified, because Cloudflare does not publish it
Stripe Japan, Inc.JapanProcessing payments for Paid Features (personal data is processed by Stripe Payments Europe, Limited in Ireland and transferred to Stripe, LLC in the United States; service providers in India and other countries may handle it)Ireland, the United States (service providers in India and other countries may handle it)
Google Cloud Japan G.K. (Gemini API)JapanProducing output for the AI features. We send what the Broadcaster enters. Under our paid contract, this input is not used to train Google’s modelsCountries where Google’s group has facilities (cannot be identified)
Zoho Japan CorporationJapanReceiving, storing and replying to enquiries and other email (Zoho Mail)Japan (Tokyo and Osaka). Group companies outside Japan may access it

5. Handling by processors in foreign countries

  1. Of the processors above, Cloudflare, Inc. is a US business and handles personal data outside Japan. Based on its Global CBPR certification, we have confirmed that it has a system in place to continuously take measures in line with Chapter IV, Section 2 of Japan’s Act on the Protection of Personal Information (security, no use beyond the entrusted purpose, control of sub-processors, breach reporting and so on) (Article 28(1) of the Act and Article 16(ii) of its Enforcement Rules).
  2. We review these measures, and any foreign laws that may affect them, at least once a year. Information on each country’s data protection system is published by the Personal Information Protection Commission of Japan (https://www.ppc.go.jp/personalinfo/legal/kaiseihogohou/#gaikoku ).
  3. Of the processors in Japan, personal data received by Stripe Japan, Inc. is processed by Stripe Payments Europe, Limited (Ireland) and transferred to Stripe, LLC in the United States. Service providers in India and other countries may handle it. Stripe, LLC holds Global CBPR certification. The countries of the European Economic Area (EEA), including Ireland, and the United Kingdom are recognised by the Personal Information Protection Commission of Japan as having an equivalent level of protection. What we send to Google Cloud Japan G.K. (Gemini API) is processed in countries where Google’s group has facilities (cannot be identified). Group companies of Zoho Japan Corporation outside Japan may access email.
  4. On request, we will provide information about these measures as required by law at "14. Contact" (Article 28(3) of the Act).

6. Disclosure to third parties

  1. We do not provide personal information to third parties without the person’s consent, except as required by law.
  2. Provision under "4. Processors", and provision that accompanies the succession of our business by merger, business transfer or otherwise, is not provision to a third party.
  3. Member invitation emails include the display name of the Broadcaster who sent the invitation.
  4. In an Organisation where several Broadcasters run events together, each member’s display name, email address and role, and the email addresses of pending invitees, are shown to the other Broadcasters in that Organisation.

7. Information sent from your device to external parties

When you use the Service, information is sent directly from your device to the following businesses. They handle it under their own privacy policies and on their own responsibility (this is not a provision of personal data by us). We receive from them only what is listed under "What we receive".

RecipientInformation sentPurposeWhat we receive
Cloudflare, Inc. (Turnstile, on the participation screen and the contact form)IP address, browser and device information, interaction on the pageDetecting bots (preventing fraudulent votes and submissions). Cloudflare also uses it to improve its detectionThe result of the check
Google LLC (Google’s sign-in screen, when a Broadcaster signs in)Google account information, IP address, browser informationSigning in (verifying identity)Identifier, display name, email address and profile image URL (see "2. Information we collect")
Stripe (Stripe’s payment and billing management screens, when buying or managing Paid Features)Payment details you enter, IP address, browser and device informationProcessing payments. Stripe also uses it as an independent business to prevent fraud, comply with law and improve its servicesThe result of the payment (we do not receive card numbers)
The host of an option image, where a Broadcaster has set an external URL as the image (when the participation screen or the event editing screen shows the option image)IP address, browser informationShowing the option imageNothing

In addition, our servers send what you enter into the AI features to Google Cloud Japan G.K. (Gemini API) and the information needed for payment to Stripe Japan, Inc., and send invitation and enquiry emails through Cloudflare, Inc. (see "4. Processors").

8. Advertising

The Service does not show advertising. We do not use users’ information for advertising or provide it to advertising businesses.

9. Security measures

We take the following measures to prevent leakage, loss or damage of personal information and otherwise keep it secure.

  1. Rules: we set out how information is handled at each stage of collection, use, storage, provision and deletion.
  2. Organisational and human measures: we limit who handles personal information and handle it with attention to confidentiality.
  3. Physical measures: we take steps to prevent theft and loss of devices used to handle personal information.
  4. Technical measures: we use encryption in transit (TLS), access control scoped to each organisation, signed participation tokens with expiry, secured administrative credentials and similar measures.
  5. Understanding the external environment: we entrust the handling of personal data to a business in the United States (Cloudflare, Inc.). Data is stored in data centres in the Asia-Pacific region (the country cannot be identified). Payment data is processed in Ireland and the United States (service providers in India and other countries may handle it), and input to the AI features in countries where Google’s group has facilities (cannot be identified). We take security measures with an understanding of these countries’ systems for protecting personal information.

10. Retention and deletion

  1. Once the retention period set by your plan has passed, finished events are no longer shown, and 30 days later we delete the events and their aggregated data (until then, they are still included in exports). Retention periods are shown on the pricing page. If a Broadcaster deletes a finished event, we delete it 30 days after it is deleted.
  2. Raw tap logs (who pressed which option and when) are kept only while an event is live and are deleted when it ends.
  3. Member invitation records (including invitees’ email addresses) are deleted when the inviting Organisation or the inviting Broadcaster’s account is deleted. If an invitee deletes their account, the invitation record kept on the inviting Organisation’s side remains until one of those happens. To ask for it to be deleted, please use "11. Requests for disclosure and other actions".
  4. Enquiries are sent to our contact email address (Zoho Mail; see "4. Processors") and kept for as long as needed to respond. They are not stored in the Service’s database.
  5. Sign-in records are deleted when you sign out on that device or delete your account. Records of sessions that were not signed out are deleted after the sign-in expires (30 days after last use), in a daily clean-up.
  6. Records of the Service’s server operation are stored in the logging feature of Cloudflare, Inc. and are deleted automatically 7 days after they are stored, for investigating faults and preventing abuse.
  7. When an account is deleted, we delete the account’s information (including sign-in records). Any Organisation that has no other Broadcaster is deleted together with its events and aggregated data. However, purchase records (date and time, quantity, amount and payment identifiers) are retained by us and by Stripe as accounting records, as is any other information we are required by law to retain.
  8. Broadcasters can export the events, questions and aggregated results of the Organisation they have open as JSON from the account settings. The export does not include account information; requests for disclosure of personal data are handled under "11. Requests for disclosure and other actions".

11. Requests for disclosure and other actions

  1. If the person concerned or their representative asks us to notify the purpose of use of, disclose, correct, add to or delete, stop using or erase, or stop providing to third parties their retained personal data, or to disclose records of provision to third parties (together, "Disclosure Requests"), we will verify their identity and respond without delay in accordance with the law.
  2. Disclosure Requests are accepted by email to "14. Contact". We verify identity by matching the email address registered with the Service or by other means we consider appropriate. There is no fee.
  3. Because Viewers’ information is managed only by anonymous identifiers, we may be unable to respond to a request if we cannot confirm that the requested information belongs to the person making it.

12. Information of minors

From November 1, 2026, only persons aged 18 or older may create an account and use the Service as a Broadcaster (Terms of Service, Article 4 (Use by minors), which applies from that date). Viewers who are minors must obtain the consent of a parent or other legal guardian before using the Service and providing information.

The AI features (Gemini API) are part of the management screens used by Broadcasters. Viewers do not use the AI features, and we do not send viewers’ information to them.

13. Revisions

We may revise this Policy in response to changes in the law or in the Service, and will post the revised Policy on this page. We will announce in advance on the Service any material change, such as a change to the purposes of use.

14. Contact

For enquiries about this Policy and the handling of personal information (including complaints and consultations), please contact:

VirtualCross Email: info@virtual-cross.com

Our address and representative are published on the Business Information page of the Service.

Established: September 18, 2026

Last revised: October 9, 2026

← Back to top