Privacy Policy

Privacy Policy

How Protocol15 handles facilitator accounts, hosted sessions, participants, analytics, and product operations.

Analytics notice updated November 9, 2026: usage analytics is enabled by default. The cookie notification has an Accept button to save acknowledgment. You can turn analytics off in Cookie preferences. Existing saved opt-outs are respected. IP addresses are discarded before analytics events are stored.

PostHog provides public-page usage analytics and pseudonymous host journeys. Acknowledging the notice is separate from giving opt-in consent.

This Privacy Policy explains how Protocol15 collects, uses, shares, protects, and retains information when facilitators, hosts, participants, visitors, and account contacts use the website, hosted game sessions, account features, and related services.

Protocol15 is built for hosted group activities. Hosts create sessions and participants usually join by link or code without creating accounts. Please do not enter sensitive personal information into nicknames, team names, support messages, or session content.

01

Who controls your information

Protocol15 is operated by Ilya Vaiman, a sole proprietor trading as Protocol15 (“Protocol15,” “we,” “us”). Ilya Vaiman is the data controller for personal information processed to operate the Protocol15 website, host accounts, hosted sessions, participant access, and related service operations.

For privacy requests or questions, contact support@protocol15.com.

02

Information we collect

  • Host account information, including email address, authentication provider details, profile fields, login metadata, and session-credit or usage status.
  • Participant information, including nickname, team assignment, join time, connection state, participant session token, and session participation records.
  • Gameplay information, including scenario selection, team rankings, locks, scores, result views, completion PDFs, and facilitator-owned session data.
  • Legal acceptance records, including subject category, Terms and Privacy document versions, acceptance source, and server-recorded acceptance time. Participant evidence uses internal participant and session identifiers rather than copied nicknames.
  • Support, billing, purchase, and contact information you choose to send, including email address and message content.
  • Device, usage, log, and analytics information, including browser type, approximate location derived from IP address, timestamps, referral data, diagnostics, security events, anonymous aggregate public-page counts, and public-page analytics while enabled.
  • Payment and billing information when you purchase session packs or other paid services. Card details are handled by the payment provider; Protocol15 does not store full card numbers.

03

How we use information

  • Provide, secure, and operate hosted sessions, participant join flows, host dashboards, scoring, results, completion PDFs, and account features.
  • Authenticate hosts, preserve intended redirects, enforce session-credit and room limits, prevent abuse, and troubleshoot live-session reliability issues.
  • Respond to support requests, billing or purchase questions, security reports, account questions, and legal requests.
  • Measure product usage and improve usability and performance using the analytics preferences described below. Essential diagnostics and security monitoring remain separate from optional analytics.
  • Maintain records needed for billing, tax, compliance, dispute handling, fraud prevention, and enforcement of the Terms of Service.

04

Legal bases for processing

Protocol15 processes information to perform a contract with hosts, operate and improve the service, manage requested communications, and comply with legal obligations. Usage analytics in this deployment is enabled by default, with an opt-out as described below; it is not gated on prior opt-in consent.

05

Cookies, local storage, and analytics

Protocol15 uses essential cookies, local storage, session storage, and similar technologies to operate the service, including authentication, security, redirect recovery, language preferences, participant session continuity, and live-session functionality.

PostHog usage analytics is on by default and can send individual analytics events before you press Accept. Accept acknowledges the notification. You can turn analytics off in Cookie preferences. It uses random browser and session identifiers, cookies, and browser storage. If you sign in as a host while analytics is enabled, we link your visits and confirmed host milestones with a random pseudonymous analytics ID. The account-to-analytics mapping stays in our database; your account ID is not sent to PostHog. Participant identities and content are excluded.

PostHog uses its EU region. Automatic click capture, session recording, heatmaps, advertising tracking, full referrer URLs, raw URL query strings, and fragments are disabled. Pseudonymous host profiles contain no names or emails.

While usage analytics is enabled, we collect the referring website domain, public campaign labels (utm_source, utm_medium, utm_campaign, utm_content and utm_term), browser language, and clicks on Start Free Demo buttons. Only validated campaign labels are retained, not the full query string. Validated referral and campaign context is kept in session storage across sign-in redirects and cleared when analytics is turned off. We also measure page exits, time on public pages and numeric Web Vitals performance measurements, without element text, DOM selectors or content. Confirmed host milestones include new signup after analytics was enabled, session creation, actual live start, first results publication, closure, another live start after closure, verified purchases and purchased-credit use.

For public-page visits with usage analytics enabled, PostHog uses your IP address to estimate location, such as country, region, and city. This is approximate network location, not GPS location. The IP address is discarded before the analytics event is stored.

Usage reporting clarification (September 10, 2026): we also count public pageviews using our own service. Basic counting is on by default to improve the site. The counter stores only a fixed page category and daily total for 90 days; it does not store visitor identifiers, IP addresses, or referrers. Only completed daily page-category totals are sent from our server to PostHog (EU), where they may be retained for up to one year. No individual visit time, visitor identifier, IP address, browser details, referral data, or campaign tags are included in this export. Basic counts do not measure unique visitors or sessions. You can turn off Basic page counts and Optional analytics independently in Cookie preferences. Counts already aggregated cannot be associated with a visitor or removed individually. Hosting providers may separately retain request logs. We retain daily sign-in counts by host for 90 days. Authorized operators can view aggregate account, sign-in, exercise, participation, and order counts from service records.

You can reopen Cookie preferences in the public-page footer to change your choice. Turning analytics off stops new optional browser captures and removes its stored analytics identity. For signed-in hosts we also save the opt-out to stop server exports and delete pending analytics events. Preferences expire after 90 days. After expiry, the default-on notification is shown again. Accessible legacy Google Analytics cookies are removed during the transition. Blocking essential browser storage can break host login, participant join, or live session behavior.

We do not send pageviews or page-exit/performance data from authentication, account, host, participant-join, live-game, presentation or Operations routes. Confirmed host milestones are captured from service records only while host analytics is enabled. Analytics excludes room codes, account and participant identifiers, user-provided names, emails, rankings, discussion and participant content. Pending and delivered first-party analytics envelopes are retained for at most 90 days; the pseudonym mapping is held while the host account exists and is used to locate analytics data for access or deletion requests. Turning analytics off does not automatically delete events already sent to PostHog; contact support to request deletion. A request already in transit may finish when preferences change.

Tools currently used or wired for use include:

  • Supabase, for authentication, session management, database, and realtime product functionality.
  • PostHog (EU), for daily aggregate page counts by default with an opt-out, and optional public-page analytics and pseudonymous host journeys enabled by default with an opt-out. Analytics cookies expire after 90 days; the free PostHog plan retains event data for up to one year.

06

How information is shared

  • With service providers that help run the product, such as hosting, database, authentication, analytics, email, error monitoring, and payment providers.
  • Within a live session, where hosts and participants may see nicknames, team names, team progress, submitted rankings, scores, and published results.
  • With professional advisers, authorities, or other parties when needed for legal compliance, safety, fraud prevention, security, or enforcement.
  • In connection with a merger, financing, acquisition, reorganization, or sale of assets, subject to appropriate protections for personal information.

07

No sale of personal information

Protocol15 does not sell personal information. Protocol15 also does not use participant gameplay data to create formal psychological, employment, credit, health, or educational assessments.

08

Retention

  • Host account records are kept while the account is active and for a reasonable period afterward for security, billing, legal, and backup purposes.
  • Session, participant, result, and completion PDF records may be kept so hosts can run, review, and support sessions, unless deleted under applicable policy or law.
  • Trajectory retention clarification (September 22, 2026): Solution Trajectory data consists of sampled team score points stored on the server. Free Demo trajectories are available for seven days from live start; paid session-credit trajectories are available for 90 days. Expired points are unavailable in the product and removed by scheduled cleanup. These windows do not apply to other session or result records.
  • Analytics, security logs, backups, and payment-related records may be retained for different periods where needed for operations, compliance, or fraud prevention.

09

Children, students, and classroom use

Protocol15 is not directed to children under 13 and should not be used by children under 13 without legally valid school, parent, or guardian authorization. Hosts using Protocol15 with students or minors are responsible for obtaining required permissions, following school or organization policies, and avoiding unnecessary personal information. Participants should use non-identifying nicknames where appropriate.

10

Your privacy choices and rights

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, objection, withdrawal of consent, or opt-out of certain processing. To make a privacy request, contact support@protocol15.com. For account access or authentication issues, contact auth@protocol15.com. Protocol15 may need to verify the request and may keep information where allowed or required by law.

11

Security

Protocol15 uses technical and organizational safeguards designed to protect information, including authentication, row-level access controls, participant-scoped access tokens, and provider-managed infrastructure. No internet service is completely secure, so hosts and participants should avoid entering sensitive or confidential information into the product.

12

International use

Protocol15 may process and store information in countries other than where you live. Those countries may have data protection rules different from your local rules. Where required, Protocol15 relies on appropriate transfer mechanisms or provider safeguards.

13

Changes to this policy

Protocol15 may update this Privacy Policy as the product, providers, legal requirements, or business model change. The updated version will be posted on this page with a new effective date.

14

Contact

For privacy requests or questions, contact support@protocol15.com. For account access or authentication issues, contact auth@protocol15.com.