Privacy and data use

Privacy Policy

This page explains what Vote My Clip collects, why it is needed, and how users can control their account and contest information.

Vote My Clip admin privacy and operations overview

Information We Collect

Only the information required to run accounts, contests, voting, judging, payments, and certificates.

Account detailsName, email, account type, login status, and verification records.
Contest contentParticipant video details, thumbnails, contest entries, status, and ranking data.
Voting, judging, and Community SupportOfficial votes, judge scores, scoring comments, timestamps, calculated leaderboard scores, and separate anonymous Community Support activity.
Payment recordsPayment purpose, amount, status, gateway reference, and transaction history.

How We Use Information

Vote My Clip uses data to provide the workflows users choose to perform.

  • Create and secure user accounts for Admin, Organizer, Judge, Participant, and Public Voter roles.
  • Let Participants join contests, upload videos, track approvals, receive votes, and view results.
  • Let Organizers create contests and manage the competition schedule.
  • Let Judges review approved videos and submit official scores.
  • Let visitors watch participant-authorized approved videos and leave one Community Support reaction while an approved contest is Live, Voting, or Judging. Playback and new supports close at Completed or archive.
  • Let Admin users review platform activity, payment records, video approvals, and reports.
  • Generate public leaderboards and participant certificates after contest results are available.

Access, Visibility, and Role Compliance

Each account type has a separate purpose and receives only the workflow meant for that role.

ParticipantsCan upload contest videos and manage their own entries.
OrganizersCan manage contests but cannot upload participant videos.
JudgesCan score approved videos assigned to judging workflows.
AdminsCan approve, reject, archive, and monitor platform records.

User Choices and Support

Users can request help with account, contest, payment, or certificate records.

For help, contact the Vote My Clip support/admin team using the support email configured for this installation. Do not share passwords, payment secrets, or private account verification codes in public contest comments.

Vote My Clip privacy overview

Quick Privacy Summary

Public pages may show contest names, video titles, scores, and leaderboard positions; final scores can also be reviewed in the Judge Panel after judging.
Account dashboards are restricted by role and login state.
Payment information is stored as transaction records, not card details.
Certificates may be verified by certificate number.

Consent and participant videos

Required account consents are recorded with the policy version, time, source, IP address, and browser information for audit and security. Optional marketing consent is separate and is not required to use the service.

Participants separately confirm publication permission and ownership or authorization for each uploaded video. Public no-signup playback is enabled only when the Participant accepts the specific Community playback policy. It is limited to approved videos in approved, non-archived contests from Live through Judging.

Anonymous Community Support privacy

To keep one-click support useful without requiring an account, Vote My Clip stores a protected VMCCommunity browser cookie and a one-way browser identifier. It also uses short-lived one-way network-day identifiers for abuse prevention and limited, one-way playback audit identifiers for security monitoring. These records do not contain an official voter identity and are not added to official votes.

Community Support totals are public popularity signals that stop accepting new reactions when the contest is Completed. The frozen total may remain visible, but it does not affect official vote totals, judge scores, rankings, prizes, or finalized results. Clearing browser data may remove the browser's remembered “Supported” state, but server-side abuse controls and previously recorded aggregate activity may remain according to the installation's security and retention policy.