HCM Integrations & Analytics Hub logo with text around a circle conating a graphic of three people in a rising bar graph split with an right upward arrow.
Tap Innovations Logo and Paycor logo side-by-side

TAP Innovations, LLC — Incident Response & Breach Notification Policy


This policy describes how TAP Innovations, LLC prepares for, detects, responds to, and communicates about security incidents affecting the FlowIQ platform, Customer Data, or related Services — consistent with GDPR, UK GDPR, CCPA/CPRA, and U.S. state breach notification laws.

13.1 Definitions


  • Security Event. An observable occurrence in our systems or network.
  • Security Incident. A security event that compromises, or is reasonably suspected to compromise, the confidentiality, integrity, or availability of the Services or Customer Data.
  • Personal Data Breach. A security incident leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data.

13.2 Incident Response Team


We maintain a designated incident response function led by security engineering and supported
by executive sponsorship. Roles, responsibilities, escalation paths, and external advisors are
documented internally and exercised through periodic tabletop and live drills.

13.3 Detection and Reporting


  • Automated detection: Monitoring, alerting, anomaly detection, and SIEM rules covering
    identity, network, application, and infrastructure layers.
  • Employee reporting: An internal channel for employees and contractors to report
    suspected incidents.
  • Customer reporting: customers can report suspected incidents at any time to
    Help@tapinnov.com.
  • External reporting:we welcome reports from independent researchers under a coordinated disclosure model.

13.4 Response Process


  • Triage. Confirm the incident, classify severity, and assemble responders.
  • Containment. Limit further impact through isolating systems, revoking credentials, or rolling configurations.
  • Investigation. Determine scope, root cause, affected systems, and affected data; preserve evidence.
  • Eradication. Remove the cause, including malicious artifacts and exploitable conditions.
  • Recovery. Restore normal operations from validated, secure configurations and confirm stability.
  • Post-Incident Review. Conduct root-cause analysis and implement corrective actions.

13.5 Severity Classification


Severity Description
Sev 1 — Critical Confirmed or likely Personal Data Breach affecting many customers, or major loss of platform availability and Customer Data integrity.
Sev 2 — High Confirmed material security incident with limited customer impact, or significant operational degradation.
Sev 3 — Moderate Contained security incident with limited or no Customer Data impact.
Sev 4 — Low Event of interest with no confirmed compromise.

13.6 Customer Notification


Where we act as a processor on behalf of customers, we will notify the customer without undue delay and generally within 48 hours of becoming aware, to allow the customer sufficient time to meet their own applicable notification obligations.

13.7 Regulatory and Individual Notifications


Where required by applicable U.S. law (including state breach notification statutes and CCPA/CPRA), we will notify relevant state attorneys general, regulators, and affected individuals as required. Where we act as a processor on behalf of customers, we will support customers in meeting their own notification obligations.

13.8 Communications and Status Updates


During significant incidents, we provide updates through email and a status page where
available. Final post-incident summaries are shared with affected customers and, where
appropriate, made available more broadly

13.9 Customer Responsibilities


  • Promptly notify us of suspected incidents affecting their accounts, users, or integrations.
  • Maintain accurate security contact information so we can reach you.
  • Secure credentials, follow least-privilege principles, and configure SSO and MFA.
  • Cooperate with our investigation and notification timelines.

13.10 Documentation


We document incidents and responses in line with applicable legal and regulatory expectations.Summary information may be made available to affected customers on request, subject toconfidentiality and security considerations

13.11 Continuous Improvement


Post-incident reviews drive concrete improvements in detection, controls, and processes. Thesecurity program tracks corrective actions through closure and reports periodically to executive leadership.

REPORT AN INCIDENT

Report a Security Incident

Contact our security team immediately if you suspect a breach or security issue.

Report Now

TAP Innovations | the App Place