GV Cricket data and safety policy for match data, date and time, location, photos, weather, livestream links, audio, browser permissions, security controls, and public sharing.
GV Cricket policy
Lists match data, date, time, timezone, location, photos, weather, livestream, and overlay risks.
Explains browser permissions, public links, third-party providers, and operator responsibilities.
Clarifies that weather, timestamps, scores, and results need official review for high-stakes use.
Documents security controls, retention, deletion, and request routing.
This policy works with the Terms, Privacy Policy, Copyright Policy, and Image Upload Policy. It is a practical checklist for app features that can expose data or create safety, privacy, rights, or reliability risk.
01
What this policy covers
This policy lists the main data and safety areas in GV Cricket so match operators can understand what may be collected, displayed, shared, restricted, or deleted when using the app.
Match setup, score events, ball history, innings, rosters, toss details, results, live status, and operator actions.
Date, time, timezone, live-relative timestamps, start times, update times, server logs, audit records, and cleanup timing.
Optional location, GPS coordinates, country or region, venue text, weather lookup, and location-based match display.
Photos, match covers, result images, logos, audio choices, microphone or walkie-talkie use, and livestream or overlay links.
Browser permissions, local device storage, public links, PINs, edit tokens, director tools, overlays, and third-party providers.
02
Match data and scoring records
GV Cricket stores or processes match data needed to run scoring, live scoreboards, result pages, overlays, announcer tools, image tools, and director controls.
Authorized operators may edit, correct, replace, delete, or publish match records depending on the feature and access controls available.
Scores, results, player stats, weather, and generated summaries should be reviewed by the scorer or organizer before being treated as official.
GV Cricket is not a guaranteed archive, official scorebook, tournament authority, evidence system, or backup service.
03
Date, time, and timezone
GV Cricket may use device time, server time, browser time, timezone, match start time, update time, and relative live timing to display and organize matches.
Date and time values can be inaccurate if a device clock, browser timezone, network request, hosting region, or saved match setting is wrong.
Timezone may be inferred from browser settings, selected location, GPS-backed location, or match setup choices where the feature needs it.
Do not rely on GV Cricket timestamps for legal deadlines, emergency response, official attendance, disciplinary decisions, betting, payroll, or other high-stakes records.
04
Location, GPS, and venues
Location is optional unless a match operator chooses to add it or use a feature that depends on it.
If browser GPS is used, the browser asks for permission first. Approved GPS may include exact latitude, longitude, accuracy, and timezone details.
Manual venue text, GPS-backed labels, country, region, and approximate network-derived location may be inaccurate or incomplete.
Do not add private homes, restricted venues, school grounds, youth-event locations, or sensitive addresses unless you have permission and understand the public sharing risk.
Public match pages and overlays may display human-readable location details depending on match settings and app features.
05
Weather and field conditions
Weather features may use match location, approved GPS, timezone, date, or venue information to request weather or pitch-related display data.
Weather data can be delayed, approximate, unavailable, or wrong because it comes from third-party services and changing conditions.
Do not use GV Cricket weather for lightning, heat, air quality, severe weather, evacuation, medical, travel, venue safety, or official match-abandonment decisions.
Use official weather services, venue officials, league rules, and qualified safety guidance for decisions that affect player or spectator safety.
06
Photos, media, and livestream content
Photos, match covers, team images, logos, stream links, overlays, result images, and generated previews may be visible to anyone with a public or shared link.
Upload only photos, logos, audio, videos, stream links, and other media that you own, created, licensed, or have permission to use.
Remove sensitive EXIF, GPS, timestamp, camera, filename, background, voice, school, child-safety, or private-location details before uploading or streaming when those details should not be public.
GV Cricket may compress, resize, cache, hide, remove, disable, restrict, or delete media when needed for safety, rights, abuse prevention, legal compliance, storage limits, or service integrity.
07
Livestreams, overlays, and third-party platforms
GV Cricket may help display score overlays, browser sources, live links, YouTube or streaming fields, director settings, and OBS-compatible views.
GV Cricket does not provide broadcast rights, music rights, venue rights, league permission, platform permission, or rights to use third-party logos, clips, commentary, or sponsor assets.
YouTube, OBS, PRISM Live, Streamlabs, social platforms, browsers, venues, leagues, clubs, schools, and rights holders may apply separate rules, claims, mutes, takedowns, or restrictions.
Stream keys, private broadcast controls, secret links, admin links, and platform credentials should never be placed in public match fields.
08
Camera, microphone, files, and browser permissions
Browser permissions such as location, microphone, camera, file picker, clipboard, notifications, and storage are controlled by your browser and device settings.
GV Cricket features that use microphone, walkie-talkie, live audio, file upload, image upload, or location can require browser permission or operator action.
Do not use microphone, walkie-talkie, live audio, overlays, or contact forms for emergency, medical, legal, confidential, safeguarding, or safety-critical communications.
You can deny or revoke browser permissions, but the related app features may stop working or may need manual setup instead.
09
Public links and sharing risk
Live score links, result pages, overlays, images, rosters, announcements, stream links, location labels, and score history may be visible to anyone who receives or discovers the link.
People who receive public links may screenshot, download, cache, embed, record, repost, or share the content outside GV Cricket's control.
Search engines, social platforms, messaging apps, browsers, and streaming tools may create previews or cached copies after a link is shared.
Use initials, nicknames, generic team labels, manual location, and restricted sharing when privacy matters, especially for children or private events.
10
Security and abuse prevention
GV Cricket may use PIN checks, edit tokens, private links, browser storage, validation, rate limits, request-size limits, timeouts, same-origin checks, audit logs, moderation, and abuse detection.
Protect edit links, admin links, director controls, operator devices, match PINs, and browser sessions. Anyone with access may be able to change a match.
GV Cricket may block traffic, revoke tokens, rotate access, remove content, disable links, preserve logs, or restrict features to protect users, rights holders, and the service.
Do not scrape, probe, overload, bypass limits, guess tokens, automate abuse, upload harmful files, or try to access matches, media, overlays, or controls without permission.
11
Retention, deletion, and limits
Match records, images, score data, logs, settings, public links, and support messages may be kept as long as needed to provide the service, protect security, resolve disputes, comply with law, or improve reliability.
Deleted or changed data may remain for a time in backups, logs, browser caches, search previews, social previews, screenshots, recordings, or third-party systems.
GV Cricket may delete, restrict, hide, or make unavailable stale matches, media, stream links, result pages, overlays, or records because of user action, policy enforcement, technical limits, abuse prevention, or product changes.
For access, correction, deletion, safety, or legal requests, use Legal Contact and include exact URLs, match IDs, screenshots if helpful, and the action requested.