Privacy Policy

2.1 Account and Identity Information

• Login credentials and associated identifiers
• Contact details, including email addresses
• Information relating to account preferences, marketing opt-in status, referral relationships, and verification processes
• Technical metadata such as IP addresses and user agents
• Timestamps relating to account creation, updates, and verification events

Purpose: Account creation and authentication, communication, fraud prevention, service administration, and compliance.

2.2 Payment and Payout Information

For streamers eligible for revenue share:

• PayPal payout details
• Transaction records, including payout amounts, dates, and processing status
• Logs relating to changes to payout information, including metadata such as originating IP address and user agent

Purpose: Processing of payments, financial reconciliation, fraud prevention, accounting, and compliance with statutory record-keeping obligations.

2.3 Integration and Platform Data (Twitch, Kick, YouTube)

Where you connect a third-party streaming account to our platform, we process:

• Platform profile and channel information
• Stream performance metrics (e.g., follower counts, average viewers, viewer numbers, minutes streamed)
• Content classification labels and broadcaster status (e.g., affiliate/partner)
• Information required to confirm branded content compliance
• OAuth tokens necessary to maintain authentication with third-party services
• Chat-related data received through webhooks or APIs, including messages, message metadata, participant identifiers or usernames, timestamps, and spam/quality classifications
• Moderator status of our automated bot

Purpose: Campaign eligibility checks, viewer-hour measurement, impression verification, analytics, fraud detection, and fulfillment of contractual obligations between advertisers and streamers.

2.4 OBS Browser Source Data and Visibility Verification

When using our advertising overlay via OBS or similar broadcasting software, we receive periodic technical data, including:

• Source visibility state and rendering behavior
• Overlay dimensions, resolution data, and related metadata
• Information regarding which advertising asset is displayed at a given time
• Error logs, transmission timestamps, and diagnostic data necessary to detect manipulation, visibility issues, or technical failures

Purpose: Verification of advertising impressions, campaign compliance, fraud detection, and overlay performance diagnostics.

2.5 Stream Screenshot and Banner Verification Data

To ensure contractual compliance with advertisers, we automatically retrieve publicly available stream thumbnail images and, where necessary, capture additional screenshots during the live broadcast from supported platforms. These images are stored and analyzed for the purpose of:

• Verifying whether the advertising banner was visible
• Detecting placement, size, clarity, and any obstruction
• Generating internal visibility scores
• Maintaining evidence supporting campaign delivery

Purpose: Fulfilling contractual obligations towards advertisers, fraud prevention, and quality assurance.

2.6 Audience Verification Submissions

For certain advertising campaigns, verification of a streamer's audience demographics is mandatory to determine campaign eligibility. To participate in such campaigns, streamers are required to submit audience analytics documentation through the methods provided within the platform.

Accordingly, we process the following information:

• Audience analytics screenshots or supporting documentation submitted by the streamer
• Extracted demographic data, including country-of-origin percentages, obtained through automated systems and/or vetted third-party data processors
• Verification metadata, such as review status, internal notes, reasons for rejection, resubmission attempts, and compliance flags
• Automated or manual assessment outputs required to validate accuracy and detect potential manipulation

Purpose: This processing is necessary to (i) assess eligibility for campaigns with demographic or regional requirements, (ii) comply with advertiser specifications, and (iii) conduct fraud prevention, risk assessment, and quality assurance to ensure that campaigns are delivered only to audiences meeting the required criteria.

2.7 Partnership and Link Tracking

When visitors interact with referral links, QR codes, promotional banners, or campaign-specific URLs, we process:

• Technical request data (IP address, user agent, timestamps)
• Information regarding the originating campaign, banner, or placement
• Visitor interaction metadata, including click counts and deduplication identifiers
• Conversion and attribution information

Purpose: Campaign analytics, attribution modeling, fraud prevention, and reporting to advertisers and streamers.

2.8 Earnings, Performance, and Reporting Data

We maintain detailed earnings records for:

• Cost-per-view (CPV) impressions
• Cost-per-viewer-hour (CPVH) calculations
• Referral-based earnings
• Associated performance logs and verification data

Purpose: Revenue calculation, payout processing, advertiser billing accuracy, fraud detection, and historical auditing.

2.9 Business & Support Communication Data

When you contact us or submit a business inquiry, we process:

• Identification and company information
• Contact details and communication content
• Budget or campaign-related information (where voluntarily provided)
• Technical metadata such as IP address and user agent
• Internal notes, follow-up actions, and inquiry status

Purpose: Responding to inquiries, sales communication, internal documentation, and customer support.

2.10 Email Communication & Tracking Data

For system, onboarding, or permitted marketing communications, we may process:

• Recipient contact information
• Email type, delivery status, and interaction history
• Open-tracking metadata (open counts, first-open timestamp, associated IP and user agent)
• Unsubscribe tokens and preferences

Purpose: Communication analytics, service optimization, compliance with email regulations, and respecting user preferences.

2.11 Error, Diagnostic & Security Logging

We may process error and diagnostic information including:

• Technical error messages, stack traces, status codes
• Timestamp and URL where the issue occurred
• Associated device and browser information

Purpose: Debugging, service security, ensuring platform integrity, and detecting malicious behavior.