Trust Center

Incident Response Policy

How SendTax detects, contains, communicates about, and learns from security incidents.

Version: 1.2Effective: 2026-10-26Owner: Howell & Gibbs LLCDownload PDF

This policy describes how SendTax detects, contains, communicates about, and learns from security incidents. It is a companion to our Information Security, Access Control, and Encryption policies.

Items marked Roadmap are not yet in production.


1. Scope

This policy covers any event that:

  • Compromises (or is reasonably suspected to compromise) the confidentiality, integrity, or availability of customer data.
  • Compromises (or is reasonably suspected to compromise) the authentication or authorization controls protecting that data.
  • Causes a sustained outage of SendTax services that affects customers' ability to access or file their data.
  • Is reported to us by a customer, researcher, employee, or sub-processor and meets any of the above descriptions.

Lower-severity operational issues (an individual user's bug, a transient deploy hiccup) follow our internal operations runbooks and are not the subject of this policy.


2. Definitions

TermMeaning
EventAny observable occurrence in a SendTax system. Most events are routine.
IncidentAn event, or a chain of events, that meets the scope criteria above.
Declared incidentAn incident that has been formally opened in our internal Security Incident system with an assigned severity, owner, and tracking ID.
BreachAn incident in which personal data was, or is reasonably believed to have been, accessed or acquired by an unauthorized party. A breach triggers the notices in §§ 8–9 that apply to it.
PostmortemWritten analysis published after resolution of an incident, covering what happened, why, what we did, and what we are changing.

3. Severity classification

Every declared incident is assigned one of four severity levels. The severity controls response urgency, notification timing, and who must be engaged.

SeverityDefinitionExamples
CriticalConfirmed unauthorized access to customer data, confirmed data exfiltration, complete outage of authentication, an outage of the whole platform lasting more than 1 hour, or any incident requiring same-day regulatory notification.Database compromise; a flaw that shows one customer's documents to another; KMS key exposure; total auth-provider outage; ransomware against production.
HighStrong evidence of attempted compromise affecting multiple customers, or sustained partial outage of a core service.Credential-stuffing wave breaching rate limits; widespread document-decryption failures; outage of document upload for >30 minutes.
MediumIsolated compromise of a single non-admin account; security-relevant misconfiguration discovered in production; vulnerability disclosure requiring an urgent patch.One filer's account taken over via reused password; an internal-only endpoint accidentally made public; a high-severity dependency CVE.
LowSecurity-relevant event that warrants tracking but does not threaten customer data.Anomalous error spike traced to a benign cause; reconnaissance traffic blocked by rate limiting; non-exploitable misconfiguration.

Severity is initially assessed by the incident commander on declaration and may be raised or lowered as the picture clarifies. Severity changes are themselves logged as updates on the incident timeline.

Whatever the severity, the breach notices in § 8 and the notices in § 9 apply whenever their conditions are met. A Medium account takeover can still require them.


4. Incident lifecycle

SendTax tracks declared incidents through four explicit statuses, enforced as a database constraint in our Security Incident system:

  1. investigating — incident declared; cause and scope are being established.
  2. identified — root cause and affected scope are understood; remediation work is underway.
  3. monitoring — fix has been applied; we are watching for recurrence or downstream effects before declaring resolution.
  4. resolved — incident is closed. A timestamp is recorded and postmortem work (if required) begins.

Movement between statuses is recorded as an append-only update on the incident's timeline.


5. Roles and responsibilities

SendTax is a small organization. Our Qualified Individual (see our Written Information Security Program) is the Incident Commander for every incident. If the Qualified Individual hands the role over in writing, including to the delegate they name for an absence, or cannot be reached when the incident needs a decision, the other operator takes it and records that on the incident timeline. The other roles are assigned per incident, and a single person may hold several roles during a small incident.

RoleResponsibilities
Incident CommanderSingle decision-maker for the incident. Declares the incident, assigns severity, drives the response timeline, decides when to resolve.
Technical LeadOwns containment and remediation work. May or may not be the same person as the Commander.
Communications LeadDrafts customer notifications and external statements. Must approve any communication that leaves the company.
ScribeMaintains the incident timeline by posting updates as the situation evolves. Often the Incident Commander on a small team.

For Critical-severity incidents, the Incident Commander and Communications Lead must be different people whenever there are at least two operators available. (Operational guideline)


6. Detection

SendTax detects incidents through a combination of automated monitoring and human reports.

Automated detection

  • Application errors and anomalies are captured by Sentry across the backend, the worker and our web apps.
  • Authentication anomalies (failed login spikes, suspicious sign-in patterns) are surfaced by Clerk and supplemented by our own application logs.
  • Infrastructure health is monitored via Fly.io's platform metrics; health checks on the API, the workers and the filer and tax-professional web apps, which also stop a failing deploy; and heartbeat monitors that alert when a background worker stops running.
  • Audit-log anomalies can be queried against our hardened audit_logs table for forensic investigation.
  • What alerts a person: Sentry's production alert rule emails our security address, and a missed worker heartbeat does the same. Nothing pages a phone for a security event yet. (Roadmap)

Human reports

  • External security researchers may report vulnerabilities to [email protected]. We acknowledge reports within 2 business days and commit to good-faith engagement with responsible disclosure.
  • Customers may report security concerns through any support channel; reports are escalated to the Incident Commander (§ 5).
  • Employees are expected to report any security-relevant observation to [email protected] immediately, and no later than one business day after noticing it, with no penalty for reporting events that turn out to be benign.

7. Response process

Once an incident is declared, response follows six phases. Phases may overlap; a complex incident may revisit earlier phases as new information emerges.

7.1 Declare

The Incident Commander triages a suspected incident within 24 hours of its report or alert reaching [email protected] or the Incident Commander. If it is an incident, they declare it by creating a record in the Security Incident system with:

  • A unique slug and human-readable title.
  • An initial severity assessment.
  • An internal summary of what is known and unknown.
  • A start time (when the underlying issue began, to the best of current knowledge — not when it was detected).

The record opens in investigating status.

7.2 Contain

Containment work is prioritized over root-cause analysis. Standard containment actions, applied as appropriate to the incident:

  • Revoke compromised credentials (Clerk, KMS, Fly.io, GitHub).
  • Rotate any potentially exposed secrets (JWT signing keys, API tokens, database credentials). The runbook for rotating SendTax secrets is documented internally.
  • Suspend affected accounts or tenant-filer links.
  • Block known-bad IPs or user-agent patterns at the application or edge layer.
  • If necessary, take a service offline rather than continue serving compromised data.

7.3 Eradicate

Eradication identifies and removes the underlying cause:

  • Patch the vulnerability in code, configuration, or infrastructure.
  • Remove any persistence mechanisms (unauthorized accounts, schedules, cron entries, OAuth grants).
  • Verify that the exploit path no longer functions.

7.4 Recover

  • Restore affected services to normal operation.
  • Restore any deleted or corrupted data from backups where applicable (see Information Security § 5).
  • Re-enable any features or accounts that were suspended for containment.
  • Move the incident to monitoring status and watch for recurrence.

7.5 Communicate

Communications are issued in parallel with — not after — the technical response, beginning as soon as we have a defensible factual picture. See § 8 below for customer-notification policy.

7.6 Close and learn

When the Incident Commander is satisfied the incident is fully resolved, they:

  • Set the status to resolved and record a resolution timestamp.
  • Schedule a postmortem, or record a closing note (see § 11).
  • Capture corrective actions in the team backlog with named owners and target dates.

8. Customer notification

SendTax has a built-in mechanism for communicating with customers during incidents. Notifications are issued from the Security Incident system itself, which guarantees that:

  • Each communication is tied to a specific incident record.
  • Each recipient is mailed at most once per notification: the fan-out sends only recipient rows still in the queued state (so a retried run skips rows already marked sent), and a unique constraint on (notification, recipient) prevents duplicate recipient rows.
  • The notification fan-out is auditable: every queued, sent, failed, and skipped delivery is recorded.

Audiences

Notifications can be targeted at:

  • All customers (filers + tax professionals) — used when the incident affects everyone or when audience scoping is not yet certain.
  • Filers only — used when the incident affects only individual taxpayer accounts.
  • Pros only — used when the incident affects only firms and their staff.

Templates and timing

TemplateSent whenContents
InitialWithin 24 hours of declaring a Critical or High incident, or of raising an incident to Critical or High; promptly after declaration for Medium; at the Commander's discretion for Low.What we observed, what we don't yet know, what customers should do (if anything), where to get updates.
UpdateWhenever a material development occurs (containment achieved, scope clarified, fix deployed).New information; corrections to previously-stated facts; revised expected timeline.
ResolvedOnce the incident is resolved and a public summary is ready.What happened, what we did, what we are changing, link to postmortem when published.

Notice of a breach

When we discover, or reasonably believe, that information in SendTax was accessed or acquired without authorization:

  • Tax professionals' firms. We tell each affected firm as soon as we can, and no later than the next business day, which of its clients and what information were involved, as far as we know then, so the firm can meet its own reporting duties. We send more as we learn it.
  • Affected people. We notify each affected person without unreasonable delay and no later than 30 days after we discover the breach, or sooner where a law or contract requires. The notice says what happened, what information was involved, what we have done, what they can do, and how to reach us.

Firms are told by email. People are notified by email where the law allows it, and otherwise by mail or another method the law requires. These notices are in addition to the notices above, and each one is recorded on the incident timeline.

Delays

A law-enforcement agency may tell us in writing that a breach notice to affected people or firms would impede a criminal investigation. We then delay that notice only as long as the agency needs and the law allows, and only with the written approval of a member of Howell & Gibbs LLC other than the Incident Commander. The request, the reason and a date to re-check are recorded on the incident timeline. No other notice is delayed this way: the initial notice above and the notices in § 9 go out on time.

Tone and accuracy

  • Initial communications do not speculate about cause or scope. They state what we observed and acknowledge what we do not yet know.
  • We do not minimize. If we are unsure whether data was accessed, we say so plainly rather than implying it was not.
  • We correct ourselves in writing when later facts contradict earlier statements, via a follow-up notification rather than by editing prior ones. The incident timeline is append-only by design.

9. Regulatory and contractual obligations

For incidents involving personal data, SendTax notifies regulators, tax agencies and affected individuals on the timelines below, and on any shorter timeline that applicable law requires:

  • FTC Safeguards Rule (16 CFR 314.4(j)): notification to the FTC, through its online form, as soon as possible and no later than 30 days after discovery when unencrypted information of 500 or more consumers was acquired without authorization. Unauthorized access counts as acquisition unless we have reliable evidence that the information was not acquired, and encrypted information counts as unencrypted if its key was accessed.
  • IRS and state tax agencies: for an incident involving taxpayer data, a report to the IRS and to the affected states' tax agencies, through the channels they publish for reporting tax data theft, no later than the next business day after we confirm the incident. This is the standard IRS Publication 1345 sets for Authorized IRS e-file Providers; SendTax is not one, so this is a voluntary commitment, kept because our customers' firms are held to it. Affected tax professionals make their own reports as well; § 8 says what we give them.
  • U.S. state breach notification laws: notification of affected individuals, and of state attorneys general and other agencies where required, on the most stringent timeline applicable to affected individuals' states of residence. Several states, including Colorado, Florida, Washington and New York, require notice to individuals within 30 days of discovery; California requires it "in the most expedient time possible and without unreasonable delay". New York also requires notice to its Attorney General, Department of State and State Police, and to the consumer reporting agencies when more than 5,000 of its residents are notified.
  • Other countries' laws: SendTax operates only in the United States. If an incident ever involved personal data that another country's law protects, such as the EU or UK GDPR, we would also meet that law's notice rules. Under the GDPR (Articles 33–34), that means the supervisory authority within 72 hours of becoming aware of the breach, and affected individuals directly when it is likely to result in a high risk to them.
  • Contractual commitments to customers: any shorter-than-statutory notification timeline agreed in a Data Processing Agreement or master services agreement takes precedence over the timelines in this policy.

The Communications Lead is responsible for confirming which notification obligations apply to a given incident and for ensuring each one is met.


10. Internal record-keeping

Every declared incident produces a durable internal record:

  • The incident row — title, severity, status, start, resolution, internal summary, public summary.
  • The append-only timeline — every status change, every update, every notification. Updates are not edited or deleted in normal flow; to correct a mistake we post a follow-up update.
  • Notification audit — every email blast and every per-recipient delivery, retained for compliance review.

This record is the source of truth for any later investigation, audit, or regulatory inquiry. We keep it as our Data Retention and Deletion Policy sets out.


11. Postmortems

Postmortems are mandatory for Critical and High incidents, and for any incident in which a notice was delayed under § 8. They are recommended for Medium. The Incident Commander completes them within 10 business days of resolution. For a Medium or Low incident without a postmortem, the Incident Commander records on the incident timeline, when closing it, the cause, the fix, and any corrective actions with named owners and target dates.

Each postmortem covers:

  • Summary — one paragraph anyone in the company can understand.
  • Timeline — derived from the incident's append-only updates plus any additional reconstruction from logs.
  • Root cause — including any contributing factors (process, staffing, tooling).
  • Detection — how we found out, how long the gap was between start and detection.
  • Response — what we did, what worked, what did not.
  • Impact — concrete numbers (customers affected, data records touched, downtime duration, financial impact if known).
  • Corrective actions — concrete items with named owners and target dates. These flow into the team backlog and are tracked to completion.

Postmortems are blameless: they describe how the system failed, not who failed. A postmortem also reviews any notice delayed under § 8, and the delay is reviewed again at the next policy review (§ 15).

Public postmortems

For incidents that materially affected customers, a customer-facing postmortem summary is published as the final notification on the incident record. Public postmortems describe what happened, what we did, and what we are changing — without disclosing details that would help future attackers (e.g., the specific exploit path of a fixed vulnerability).


12. Coordination with sub-processors

When an incident originates with or is exacerbated by a sub-processor (listed on our Sub-processors page), we:

  • Engage the provider's published incident-response or support channel immediately.
  • Track their communications on our own incident timeline so customer notifications reflect the full picture, not just SendTax's actions.
  • Reference the provider's published incident postmortem (where available) in our own postmortem.

We are responsible for notifying our customers regardless of whether the underlying issue was within SendTax-operated infrastructure or a sub-processor's.


13. Testing

  • We review this policy and the underlying response infrastructure at least annually (§ 15).
  • Tabletop exercises — walkthrough simulations of representative incidents to validate the response process and team familiarity — are run by the Qualified Individual at least once a year. None has been run yet; the first is due by 2026-11-21. (Roadmap)
  • Components of the response system — incident status transitions, audit-log writes, and notification email rendering and recipient resolution — are covered by automated tests in our CI pipeline. End-to-end coverage of the notification fan-out task itself is not yet in place (current tests stub the dispatch). (Roadmap.)

14. Reporting a security concern

We welcome reports of security vulnerabilities, suspected breaches, or concerning observations.

ChannelUse for
[email protected]Vulnerability disclosures, suspected breaches, anything time-sensitive.
[email protected]Privacy-specific concerns and data subject requests.
[email protected]General questions.

We commit to:

  • Acknowledging reports sent to [email protected] within 2 business days.
  • Working in good faith with researchers who follow responsible disclosure practices.
  • Not pursuing legal action against researchers acting in good faith under recognized safe-harbor norms (CFAA carve-outs for authorized testing, EU NIS2 / national equivalents, etc.).

15. Policy review

This policy is reviewed at least annually, and additionally whenever:

  • A material change to our incident-response tooling or process ships.
  • A regulatory notification obligation we are subject to changes.
  • A real incident reveals a gap in this policy.

Each version is recorded in § 17, Change history.


16. Contact

Security disclosures[email protected]
Privacy inquiries[email protected]
General[email protected]
Operating entityHowell & Gibbs LLC

17. Change history

VersionDateAuthorApproved byChanges
1.02026-05-30Holly GibbsNot recordedFirst published text. Drafted with Claude.
1.12026-10-07Liam HowellLiam Howell (QI), for Howell & Gibbs LLCOne version number and one change history for this policy's internal and public texts and its Notion page (WISP § 7.4; public WISP § 14); earlier versions were numbered separately (internal 1.0, public v1, Notion draft 1.0). The two texts now make the same commitments (section numbers are the public text's): a breach covers information reasonably believed, not only confirmed, to have been accessed or acquired (§ 2); one severity scale, Critical, High, Medium and Low, with an outage of the whole platform over 1 hour as Critical, and the breach and regulatory notices apply whatever the severity (§ 3); the Qualified Individual is the Incident Commander unless they hand the role over in writing or cannot be reached (§ 5); suspected incidents are reported within one business day, and triaged within 24 hours of the report (§§ 6, 7.1); the 24-hour initial notice also covers an incident raised to Critical or High, and a Medium incident's initial notice goes out promptly and a Low one's at the Incident Commander's discretion (§ 8); when information is, or is reasonably believed to have been, accessed or acquired without authorization, affected firms hear by the next business day and affected people within 30 days of discovery, and only those two notices may be delayed, at a law-enforcement agency's written request (§ 8); the IRS and state tax agencies hear by the next business day after we confirm an incident, and the FTC within 30 days when 500 or more consumers are affected (§ 9); GDPR notice applies only where the GDPR does, since SendTax operates only in the United States (§ 9 implied we serve people in the EU and UK); postmortems within 10 business days for Critical and High incidents and for any incident with a delayed notice, and for any other incident a closing note with its corrective actions (§ 11); a tabletop exercise at least once a year, the first by 2026-11-21 (§ 13). Corrected: Sentry covers the backend, the worker and our web apps; the audit table is audit_logs; which services have health checks; sub-processors are those on the Sub-processors page (§§ 6, 12). Corrected in the internal text: some detection sources, alert channels and records it named were not in place. Review cadence: at least annually, as before (the Notion draft said semi-annual). Also records a change made without a row: #155 (2026-06-08) corrected § 6 (Sentry), § 8 (how duplicate emails are prevented) and § 13 (test coverage). Dates corrected: public 1.0 is dated 2026-05-30, the day its text was merged (its header said 2026-05-21). Drafted with Claude.
1.22026-10-26Liam HowellLiam Howell (QI), for Howell & Gibbs LLCThe 2026-10-26 security and legal review. Internal § 5.5 and public § 9: SendTax is not an Authorized IRS e-file Provider, so the next-business-day report to the IRS and the states is a voluntary commitment, kept because our customers' firms are held to it (the text presented Publication 1345 as the standard that applies). Public § 9 corrected: California sets no day count for notice to individuals ("the most expedient time possible"); Colorado, Florida, Washington and New York set 30 days; New York also requires notice to its Attorney General, Department of State and State Police, and to the consumer reporting agencies past 5,000 residents. Internal § 5.5 adds those New York notices, that a dependent's disability or death answers count as medical information under New York's law since March 2025, and that email notice to a person needs their prior consent, which the Terms record. Public § 6: Sentry's alert rule emails us, and nothing pages a phone for a security event. Internal § 5.1: the clamd and admin-web apps have health checks. Drafted with Claude.