These Production Standards (“Standards”) apply to Event Providers (Talent, Venues, Promoters) and Production Vendors and are incorporated into the Show Streamz Terms & Conditions. These Standards exist to protect stream quality, security, rights compliance, and the Fan experience. Where the Platform displays technical specifications or operational requirements for a particular Event, those event-specific requirements control.

Operational support: support@showstreamz.com
Legal/compliance: legal@showstreamz.com

1. Scope, Roles, and Responsibility Allocation

1.1 Who Must Comply

These Standards apply to:

• Event Providers who create/list/operate Events, including any co-producers; and

• Production Vendors who capture, produce, encode, monitor, or otherwise support the stream.

1.2 Show Streamz Role

Show Streamz provides the Platform and may provide tools for testing, delivery, and monitoring. Except for Show Streamz Produced Events, Show Streamz does not act as production manager, venue operator, or employer of any crew. Event Providers remain responsible for end-to-end event readiness and execution.

1.3 Event Provider Is the “Single Point of Accountability”

Even if a Production Vendor is contracted, the Event Provider is responsible for:

• selecting a reputable production partner;

• ensuring all requirements are met by all parties;

• providing accurate event information; and

• completing all readiness gates by required deadlines.

2. Go-Live Readiness Gate (Mandatory)

Show Streamz may require all or some of the following before an Event is approved for scheduling and/or go-live. Requirements may scale with the Event’s risk profile, audience size, and feature set (e.g., VIP Rooms enabled, paid VOD enabled).

2.1 Approved Production Partner Requirement

Show Streamz may require confirmation that the Event has an Approved Production Partner (Production Vendor) and may:

• request a vendor profile, portfolio, and references;

• require proof of insurance and business registration (see Section 8);

• require vendor acceptance of event-specific obligations (e.g., monitoring, secure key handling); and

• deny go-live if a vendor is unqualified or unverified.

2.2 Readiness Checklist Completion

Event Providers must complete a readiness checklist that may include:

• finalized show schedule (start time, doors, runtime, segments);

• confirmed camera/audio plan;

• confirmed network plan;

• confirmed encoder configuration;

• confirmation of moderation staffing (if chat/Watch Rooms/VIP Rooms enabled);

• confirmation of rights clearances status (music, video, likeness releases); and

• emergency contacts and escalation path.

2.3 Test Stream Requirement

Show Streamz may require one or more successful test streams prior to the Event, including:

• a pre-flight test (at least 24–72 hours prior, depending on scale); and/or

• a day-of-show final check.

A test stream may be required to verify:

• stable ingest and sustained bitrate;

• audio intelligibility and sync;

• switching/camera feeds;

• latency expectations;

• DRM/content protection measures;

• VOD capture settings (if enabled).

2.4 Security Checks (Stream Keys and Access Controls)

Before go-live, Show Streamz may require:

• confirmation that stream keys are stored securely and shared only with required personnel;

• confirmation that credentials are not shared broadly (no “team-wide” passwords);

• verification of role-based access and least-privilege (Section 5);

• confirmation of geo restrictions and tier gates (if enabled); and

• confirmation of anti-piracy controls (watermarking/session limits where enabled).

2.5 Free Promo Shows: Deposit Confirmation

For Free Promo Shows:

• Delivery Fees apply to all tiers;

• a deposit may be required in advance to cover estimated Delivery Fees and pass-through costs;

• the deposit amount is quoted and agreed prior to scheduling and/or go-live; and

• go-live may be withheld until deposit confirmation is received.

2.6 Right to Delay, Disable Features, or Decline Go-Live

If requirements are not met, Show Streamz may:

• delay the event,

• disable interactive features (chat/Watch Rooms/VIP Rooms),

• restrict resolution/bitrate,

• require additional testing,

• require additional moderators, or

• decline go-live to protect the Platform and Fan experience.

3. Technical Minimums (Baseline)

These are baseline expectations. The Platform may publish event-specific specifications that override or supplement these baselines.

3.1 Network/Uplink Stability

Event Providers/Vendors must provide:

• sufficient upload bandwidth with reasonable headroom above target bitrate;

• stable connectivity (avoid congested public Wi-Fi);

• redundancy planning appropriate to event scale (e.g., bonded cellular, secondary ISP, backup hotspot), especially for paid events or large audiences.

3.2 Encoder and Ingest Configuration

Event Providers/Vendors must comply with Platform requirements for:

• supported encoder types and protocols;

• supported video/audio codecs;

• bitrate ladders (if applicable), keyframe intervals, and frame rate;

• resolution and aspect ratio standards;

• audio channels, sampling, and loudness management;

• closed captioning workflow (if required by law/event setting).

If the Platform publishes updated specs, those specs control.

3.3 Audio Intelligibility and Mix Standards

Audio must be:

• intelligible for speech and balanced for music;

• free of clipping/distortion;

• reasonably consistent in level;

• monitored continuously, with a plan to address dropouts, interference, or feedback.

3.4 Monitoring Requirements

At minimum, the production team must monitor:

• ingest health, dropped frames, and sustained bitrate;

• audio levels and sync;

• stream output quality from at least one external viewer perspective;

• chat/moderation feeds if enabled;

• time-to-start and outage response readiness.

3.5 VOD Processing (If Enabled)

If VOD is enabled, Event Providers/Vendors must:

• confirm recording/capture settings before go-live;

• comply with post-event packaging and publishing steps;

• complete any required title/thumbnail/metadata steps; and

• meet any deadlines for making VOD available, where disclosed.

4. Operational Standards (Show Readiness and Execution)

4.1 Defined Roles and Responsibilities

Event Providers/Vendors should define roles, such as:

• producer/director, technical director, audio engineer, camera ops;

• encoder/stream operator;

• moderation lead (if chat/Watch Rooms/VIP Rooms enabled);

• incident escalation contact.

4.2 Call Time, Pre-Show Checks, and Run of Show

Event Providers/Vendors should perform pre-show checks appropriate to scale:

• camera white balance/exposure checks;

• audio line checks;

• lighting consistency check;

• graphics/lower thirds verification (if used);

• stream start/stop procedure;

• run-of-show alignment and timekeeping.

4.3 Contingency Planning

Event Providers/Vendors must plan for foreseeable issues including:

• network degradation;

• encoder failure;

• audio failure;

• camera feed loss;

• venue power interruptions;

• talent delays or lineup changes.

Contingency measures may include backup encoder, backup internet, and fallback scenes.

4.4 Live Incident Response

During an Event, teams must:

• monitor and respond promptly to issues;

• follow escalation procedures;

• communicate materially impacting issues to Show Streamz support where appropriate (support@showstreamz.com), especially for paid events.

4.5 Post-Event Wrap and Reconciliation

After the Event:

• confirm stream end state and recording completion (if VOD enabled);

• document incidents and root causes;

• provide requested logs if needed to resolve disputes or refunds;

• complete reconciliation steps for deposits and Delivery Fees where applicable.

5. Security Standards (Credential Handling, Access Controls, Anti-Piracy)

5.1 Least-Privilege Access

Access to show tools, dashboards, stream keys, and settings must be limited to personnel who need it. Use role-based access where available.

5.2 No Shared Credentials

Do not share logins across multiple people. Each team member should have their own access where supported. Avoid storing keys in unsecured notes, public docs, or group chats.

5.3 Stream Key Handling

Stream keys must be:

• transmitted securely;

• rotated/reset if compromise is suspected;

• disabled after use if the Platform supports it.

5.4 Incident Reporting

If compromised credentials, stream key leaks, suspected piracy, or unusual access patterns occur:

• notify Show Streamz immediately at support@showstreamz.com;

• preserve relevant logs and evidence;

• cooperate with containment actions (key rotation, session resets, geo restrictions).

5.5 Compliance with Content Protection

Event Providers/Vendors must not disable or bypass security measures implemented by the Platform and must support watermarking/session controls where enabled.

6. Audience Experience Standards (Premium + Reliable)

6.1 Quality Expectations

Events should meet reasonable professional standards for:

• steady framing, acceptable lighting, and clear audio;

• minimal downtime or dead air;

• clear communication of start times and delays.

6.2 Interactive Features Readiness (If Enabled)

If chat, Watch Rooms, or VIP Rooms are enabled:

• provide adequate moderation staffing (see Community Guidelines moderation section);

• use slow mode, link restrictions, and keyword filtering as needed;

• implement a VIP room host/moderator per room.

6.3 Accessibility and Disclosures

Where applicable or required, Event Providers should provide:

• accurate content ratings/age gates;

• content warnings for mature themes;

• captioning workflows where required by law or contract.

7. Event Provider Responsibility for Labor and Vendor Payment

7.1 Sole Responsibility for Compensation

Event Providers are solely responsible for contracting and paying all amounts owed in connection with their Events, including:

• performers, talent, comedians, musicians, DJs;

• employees, contractors, crew;

• Production Vendors and sub-vendors;

• venue staff (if applicable);

• any licensors/rights holders; and

• any other personnel or vendors engaged for the Event.

7.2 No Employment Relationship with Show Streamz

Show Streamz does not employ, manage, direct, supervise, or pay Event Provider or Vendor personnel and is not responsible for wages, payroll, benefits, workers’ compensation, unemployment insurance, or contractor classification.

7.3 Taxes, Withholding, and Labor Compliance

Event Providers are solely responsible for payroll taxes, withholdings, reporting obligations, labor law compliance, and contractor classification compliance.

7.4 Union/Guild and CBA Compliance

Event Providers are solely responsible for union/guild obligations and collective bargaining compliance, including required payments, reporting, residual/reuse obligations, and clearances where applicable.

7.5 Disputes and Non-Payment

Show Streamz is not responsible for non-payment disputes between Event Providers and any performers, employees, contractors, Production Vendors, or other third parties.

8. Vendor Qualification and Approval

Show Streamz may require Production Vendors to provide:

• portfolio, references, and relevant experience;

• business registration details;

• proof of insurance (general liability; professional liability/E&O where applicable; workers’ compensation where applicable);

• equipment capability confirmation (cameras, audio chain, encoder, monitoring);

• security practices acknowledgement (key handling, access control);

• agreement to comply with these Standards.

Approval may be revoked for repeated quality failures, security incidents, inaccurate representations, or serious complaints.

9. Enforcement, Remedies, and Platform Controls

If these Standards are not met, Show Streamz may:

• delay scheduling or go-live;

• require additional testing or documentation;

• restrict stream parameters (resolution/bitrate);

• disable interactive features;

• require additional moderators or security controls;

• suspend or remove the Event; and/or

• apply payout holds/reserves consistent with the Terms.

10. Updates and Event-Specific Requirements

We may update these Standards over time. The most current version posted on the Platform applies. Event-specific requirements displayed in the Platform control for that Event.

Last Updated: February 23, 2026