Epic Experience Advisors, LLC

Privacy Policy

This draft explains how Epic Experience Advisors, LLC handles business, contact, consulting, and SignalOps-related information across its public website and operating platform.

V1 draft for qualified legal counsel review. This page is not attorney-reviewed, final, or legal advice.

1. Who we are and what this policy covers

Epic Experience Advisors, LLC (EEA) is a legal management consultancy and the operating company behind SignalOps. SignalOps is EEA’s operational-intelligence SaaS product and operating brand; SignalOps is not a separate corporation or LLC.

This V1 policy covers the public EEA and SignalOps website, EEA business and contact activity, consulting and advisory engagements, procurement and support interactions, and information processed through SignalOps workspaces. A signed consulting agreement, order form, procurement document, or other customer agreement may add terms for a particular engagement.

2. EEA business, contact, and engagement information

When someone contacts EEA, discusses a consulting or advisory engagement, evaluates SignalOps, or works through procurement or support, EEA may handle the information needed to respond and administer that relationship.

  • Business contact details and the organization, venue, or role connected to the inquiry.
  • Information shared about a consulting, advisory, assessment, procurement, implementation, or support request.
  • Purchase-order, invoice, billing, and commercial administration records.
  • Support, account-administration, and other correspondence with EEA.
  • Outbound email delivery and reply information associated with those communications.

3. SignalOps account and operational data

SignalOps is designed for organizations and venue teams. Customer operational data is different from EEA’s general business-contact data: it is information a customer or authorized user chooses to place in a SignalOps workspace or provides to EEA for an Operational Intelligence Scan.

  • Account details and authorized-user information used to access a workspace.
  • Organizations and venues represented in a customer workspace.
  • Incidents, corrective actions, and shift logs entered by customer teams.
  • Operational Intelligence Scans, reports, findings, and related source records.
  • CSV and XLSX scan uploads, together with the file metadata and quarantine status used to process them.
  • Billing, procurement, purchase-order, and invoice records associated with a SignalOps relationship.
  • Support and account-administration interactions connected to a workspace.

4. How information is used

EEA uses information to communicate with a contact or customer, provide consulting or advisory work, operate and support SignalOps, administer accounts and workspace access, process scans and reports, manage procurement and billing, investigate service or security issues, and maintain the public website and its documented features.

Customer operational data is used in the context of the customer’s SignalOps workspace or requested scan. EEA does not treat a public marketing page as permission to publish a customer’s operational records.

5. Cookies, local storage, and analytics

The deployed application may use browser local storage to keep a deploy-controlled visitor identifier for the Polsia analytics beacon when analytics is enabled for that deployment. The beacon records a page-view signal using the deploy-injected analytics destination and the visitor identifier. This policy does not claim that advertising cookies, cross-site behavioral profiles, or analytics are enabled in every deployment.

SignalOps also uses the browser and session mechanisms required for signed-in account access. The exact browser storage behavior for an authenticated session is governed by the deployed authentication implementation rather than by a separate advertising-cookie program.

6. Access, disclosures, and customer direction

EEA may make information available to people who need it to provide the requested consulting, advisory, product, support, account, billing, or administrative service. A customer controls which authorized users and operational records it places in its workspace and should avoid uploading information it is not permitted to share.

This V1 draft intentionally does not state a subprocessor list, transfer mechanism, legal-basis schedule, or fixed retention period. Those details require confirmation against the relevant EEA engagement, deployment, and counsel guidance before publication as a final policy.

7. Questions and privacy requests

For a privacy question or request connected to EEA or SignalOps, use the existing EEA engagement, account, or support channel. A direct company contact route is signalops-ai-7@polsia.app. Please do not send credentials, secrets, or sensitive operational records in an initial email.

This draft does not promise a specific response period or outcome for a request. EEA will review requests in light of the applicable relationship, records, and law, with qualified counsel completing the final process language.

8. V1 draft status

This is a working V1 document for qualified legal counsel review. It is not attorney-reviewed, final, or legal advice. Do not rely on it as a substitute for a signed agreement, a customer-specific data-processing document, or professional advice about a particular privacy obligation.