Trust Center
Employee Acceptable Use Policy
How SendTax personnel may use the company’s systems, accounts, devices, and information.
1. Purpose
This policy defines how SendTax personnel may use the company's systems, accounts, devices, and information. It exists to:
- Protect customer data and SendTax systems from harm caused by personnel behavior.
- Support SendTax's obligations under the FTC Safeguards Rule, IRC §7216, and applicable state laws.
- Give SendTax a documented, enforceable basis for action when rules are violated.
This policy supports the commitments made in the Information Security Policy and complements the Access Control Policy, Encryption Policy, Incident Response Policy, and Data Retention & Deletion Policy.
2. Scope and acknowledgment
This policy applies to all SendTax personnel — co-founders, employees, contractors, consultants, advisors, and any other person granted access to SendTax systems, code, or customer data.
All personnel must acknowledge this policy in writing before being granted access to SendTax systems, again within 14 days after each new version is approved, and at least once a year. Each acknowledgment records the person, the version, and the date, and is kept in an append-only record. Using SendTax systems does not by itself count as acknowledgment.
3. Principles
- Customer data is not yours. Personnel may access customer data only to perform a defined operational, support, or legal task — never out of curiosity, never for personal benefit, never for any purpose other than serving the customer or operating SendTax.
- Default-deny applies to people too. Personnel access only what they need for the task at hand, and stop there.
- Tax data is regulated data. Personnel handling taxpayer information are subject to IRC §7216 and FTC Safeguards Rule obligations. Violations carry civil and potentially criminal exposure beyond ordinary employment consequences.
- You are responsible for output, regardless of how it was produced. This applies to AI-assisted work, automation, and anything else: the person who shipped the work owns the result.
4. Acceptable use
Personnel may use SendTax systems, accounts, and information to:
- Perform their assigned role at SendTax.
- Communicate with customers, sub-processors, and other authorized parties on SendTax's behalf.
- Access, modify, or transmit customer data when operationally necessary and within the scope of their role.
- Develop, test, deploy, and operate the SendTax product.
- Collaborate with other personnel using approved channels (§ 7).
- Use approved AI tools subject to the restrictions in § 8.
5. Prohibited activities
Personnel must not:
- Access customer data beyond what is needed for a specific operational task.
- Disclose customer data to any unauthorized party.
- Share their own sign-in password, access tokens, or MFA codes with any other person — including other personnel. A service credential that more than one person needs (an API key, for example) is shared only through 1Password (§ 9).
- Sign in to a production system with a shared login or a generic account.
- Attempt to bypass or disable security controls (RLS, MFA, audit logging, encryption).
- Store production secrets anywhere other than 1Password, our hosting and compute providers' encrypted secret stores (Fly.io, Vercel, and Modal), GitHub Actions' encrypted secrets, or those providers' own command-line tools signed in on a person's device.
- Keep customer data on a device except as § 6 allows.
- Transmit customer documents, the tax and identity data in them, credentials, or production secrets over personal communication channels, or send them by email or chat on any channel (§ 7.1).
- Develop or experiment in production. Release checks and demos there use only SendTax's own test and demo accounts, never a customer's account or data.
- Use SendTax systems for personal profit, business activities unrelated to SendTax, or any unlawful purpose.
- Install unauthorized software on company-managed systems where company-managed systems are in use.
- Use AI tools in violation of the restrictions in § 8.
- Misrepresent themselves as another person, including other SendTax personnel, customers, or sub-processor representatives.
6. Device and endpoint security
- Customer data and production systems may be accessed only from devices
that meet SendTax's device security baseline:
- Full-disk encryption enabled (Apple FileVault, BitLocker, or equivalent).
- Screen set to lock after no more than 10 minutes idle, with a password required to unlock it.
- Automatic updates turned on, and operating-system security updates installed within 30 days of release.
- Built-in anti-malware protections enabled (on a Mac, Gatekeeper and XProtect; on Windows, Microsoft Defender), and on Windows BitLocker in place of FileVault.
- Personal devices meeting the baseline are acceptable. Personal devices that do not meet the baseline must not be used for customer data access. Public or shared devices (hotel business centers, etc.) must not be used at all.
- No device-management (MDM) tool is in place yet (Roadmap), so each person keeps their own device to this baseline, checks it once a month and records the check on our compliance dashboard.
- Customer data is never kept on a personal device. On a company-owned device, a copy is allowed only for incident response, a support request the customer authorized, or debugging the Qualified Individual approved in writing, and it is deleted within 7 days.
- The one exception is our training computer (Written Information Security Program § 4.2). It may hold approved training contributions, only as the sealed exports SendTax makes for it, for at most 30 days after each export is built. Nothing is copied off it, and no other customer data goes on it. Our staff label those pages there, from their own computers over our private network, and never save, download, copy, print or capture a page. Nobody keeps another person's documents for training: someone who wants to help shares their own, from their own account.
- Devices used to access customer data must not be left unattended in unsecured locations.
7. Communication channels
Approved channels for SendTax business communication:
- Gmail (Google Workspace) — email.
- Google Chat — internal messaging.
- Google Meet — video conferencing.
- Google Drive and Google Docs (Google Workspace) — documents.
- GitHub and Notion — work coordination.
- The CRM in our admin app, with its Gmail connection — our record of the tax professionals and firms we contact about SendTax, and the sales email we send from our own send.tax Gmail, once our Qualified Individual's written approval of it is recorded.
Using another tool for SendTax business communication or coordination needs the Qualified Individual's written approval, and the tool is added to this list at the next version of this policy.
7.1 What may be communicated where
- Customer documents and the tax and identity data in them (tax forms, identity documents, financial records, SSNs, account numbers): only inside the SendTax application. Do not send them by email or chat, or copy them into another tool, even an approved one; link to the record in the application instead. If a customer emails one to us, do not forward or copy it, and ask them to upload it in the application.
- Contact details needed to help a customer (a name, an email address): approved company channels only, and only what the task needs.
- Credentials and secrets that may be shared (§ 5): only through 1Password. Never by email, chat, SMS, a ticket, a document, or an AI tool.
- General product discussion that does not expose customer data (architecture, roadmap, internal coordination): approved and vetted company channels.
- Public information (marketing, blog posts, this policy): any channel.
Never use personal email, iMessage, SMS, social media, or any personal channel for customer data or credentials.
7.2 Data minimization
Even within approved channels, personnel apply data minimization: send only the data needed to accomplish the task. Every copy of customer data outside the application expands SendTax's blast radius in the event of an account compromise. To refer to a document, link to it in the application; a file's name often carries the client's own, so it is not written into email or chat either.
8. AI tools
Personnel may use AI tools to assist with their work, subject to the following restrictions. They cover AI assistants, AI coding agents, AI features built into other tools, and AI services that our internal scripts and tools call. The SendTax platform's own document classifier is covered in § 8.4.
8.1 What may be sent to AI tools
- Public information.
- SendTax-owned non-confidential content (e.g., this policy text, public marketing copy).
- Code that does not include production secrets, customer data, or personally identifying information, to a tool approved in § 8.4.
- Architectural and process questions about SendTax that do not reveal customer-specific details, to a tool approved in § 8.4.
8.2 What must not be sent to AI tools
- Customer documents (tax forms, identity documents, financial records).
- Customer personally identifying information (names, SSNs, addresses, account numbers).
- Production secrets (API keys, database credentials, KMS material, JWT signing keys).
- Internal credentials of any kind.
- Source code containing embedded secrets or hardcoded customer data.
- Production database rows or logs that contain customer data.
These limits apply whether or not a tool keeps what it is sent. They apply to AI coding agents too, including anything a command they run prints and any page, mailbox, or document they open. Our document-labeling tools send page images to OpenAI; they may be given public or fictional sample documents, or a SendTax operator's own documents with that person's agreement, never a customer's document or a training contribution. The labeling tool on our training computer, where training contributions are labeled, can't call OpenAI.
8.3 Responsibility for output
Personnel are responsible for the output of their work regardless of whether AI tools assisted in producing it. This includes:
- Reviewing AI output for accuracy before relying on it (AI tools can produce plausible-sounding but incorrect information).
- Verifying any factual claims, code, or recommendations against authoritative sources.
- Disclosing AI assistance in contexts where it materially affected the output, where disclosure is reasonable (e.g., AI-drafted customer communications should be reviewed and edited before sending).
8.4 Approved AI tools
Approved for SendTax code and internal work (§ 8.1): Claude and Claude Code, from Anthropic, including the AI security review a member runs in Claude Code, on their own subscription, on code changes that touch security-sensitive files before they are merged. Approved only for the use § 8.2 describes: OpenAI's API, through our document-labeling tools. Any AI tool may be used with public information and SendTax's non-confidential content. Using any other AI tool with SendTax code or internal information requires approval under the exception process in § 13, and an approved tool is added to this list at the next version of this policy.
No AI assistant, coding agent, or internal tool is approved for customer data. The SendTax platform's own document classifier runs on Modal, a sub-processor listed on our Sub-processors page. Any other AI service that would process customer data must pass the review in our Vendor Management Policy and be listed on that page before it is used.
9. Account and credential handling
- Each person uses their own individual account on every system. No shared accounts, no shared passwords.
- Passwords are stored in 1Password, not in browsers, plaintext files, sticky notes, or personal password managers.
- MFA must be enabled on every system that offers it, including each system named in the Access Control Policy § 3. SendTax's own sign-in, including for SendTax administrators, doesn't offer two-step verification yet; it switches on for pilot firms in December (Access Control Policy § 3).
- A service credential that more than one person needs (an API key, for example) is shared only through 1Password (§ 7.1).
- Compromised or suspected-compromised credentials must be reported immediately to [email protected] (§ 12) and rotated as part of incident response.
10. Tax data — IRC §7216 obligations
Personnel handling tax return information are agents of a tax return preparer for purposes of IRC §7216. This means:
- Tax return information may be used only for tax return preparation, the auxiliary services SendTax provides, and the specific purposes authorized by §7216.
- Tax return information must not be disclosed to any unauthorized party or used for any unauthorized purpose.
- Cross-border disclosure of tax return information without §7216-compliant consent is prohibited (SendTax operates U.S.-only and does not currently use cross-border consent mechanisms).
Violations of §7216 carry civil and potentially criminal penalties under federal law in addition to any consequences SendTax imposes.
11. Monitoring
SendTax may monitor use of company systems for security, compliance, and operational purposes. This includes review of system logs, audit logs, authentication events, application activity, and infrastructure logs. Personnel should not have an expectation of privacy in their use of company-issued accounts and systems.
Monitoring is conducted in service of security and operational integrity, not for surveillance of personal communications. Personnel personal device contents are not monitored even when the device is used for SendTax work — only what flows through SendTax-controlled systems and accounts.
12. Reporting
Personnel must report the following to [email protected] immediately, and no later than one business day after noticing it:
- Suspected or confirmed security incidents, including a near miss (see Incident Response Policy).
- Lost or stolen devices with SendTax access.
- Compromised or suspected-compromised credentials.
- Suspicious emails, messages, or contact attempts targeting SendTax personnel.
- Violations of this policy by any person.
- Operational concerns that may indicate a control gap.
Reports made in good faith are protected. SendTax does not retaliate against personnel who report in good faith, even where the reported activity turns out to be benign or attributable to the reporter themselves.
13. Exceptions
A deviation from this policy may be authorized only when:
- The deviation is documented in writing with a specific business need.
- The Qualified Individual approves the deviation in writing. A deviation for the Qualified Individual is approved by the other member of Howell & Gibbs LLC. No one approves their own deviation.
- A defined re-evaluation point is set.
- Compensating controls are in place where the deviation reduces an existing safeguard.
Exceptions are reviewed at each policy review and are not allowed to become permanent without explicit re-authorization.
14. Enforcement
The Qualified Individual investigates suspected violations. A suspected violation by the Qualified Individual goes to the other member of Howell & Gibbs LLC.
Violations of this policy may result in:
- Required retraining.
- Revocation of access to SendTax systems.
- Termination of employment, contract, or engagement.
- Civil or criminal referral where applicable, including for violations involving customer data, IRC §7216, or unauthorized access to taxpayer information.
The consequences applied to a violation are proportional to the severity, the intent, and any pattern of prior violations. SendTax follows a blameless approach to honest mistakes that are promptly reported and remediated, consistent with the postmortem culture described in the Incident Response Policy.
15. Related policies
- Information Security Policy — umbrella security commitments.
- Access Control Policy — what personnel access is granted, reviewed, and revoked.
- Encryption Policy — encryption standards personnel must follow.
- Incident Response Policy — how personnel respond to and report incidents.
- Data Retention & Deletion Policy — handling and disposal of customer data.
- Vendor Management Policy — personnel obligations in vendor interactions.
- Sub-processors — the vendors that may process customer data.
16. Contact
| Security disclosures | [email protected] |
| Privacy inquiries | [email protected] |
| Operating entity | Howell & Gibbs LLC (operator of SendTax) |
17. Change history
| Version | Date | Author | Approved by | Changes |
|---|---|---|---|---|
| 1.0 | 2026-06-16 | Holly Gibbs | Not recorded | Initial publication. Drafted with Claude. |
| 1.1 | 2026-10-07 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | One 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 1.0, Notion 1.0). The internal text takes this title (it was "Acceptable Use Policy") and now agrees with the public text; section numbers here are the public text's. Dates corrected: public 1.0 is dated 2026-06-16, the day its text was merged (its header and row said 2026-05-21). Review cadence: at least annually (the public copy said semi-annual). § 2: written acknowledgment before access, within 14 days after each new version is approved, and at least once a year, kept in an append-only record (the internal text counted using our systems as acknowledgment); corrected: it said acknowledgments are kept under the Data Retention and Deletion Policy, which has no rule for them. § 5: production secrets are kept only in 1Password, our hosting and compute providers' secret stores and GitHub Actions' encrypted secrets; no one shares their own sign-in credentials, and a service credential that more than one person needs is shared only through 1Password (corrected: it banned sharing any credential, including service credentials such as API keys, which are kept in 1Password and in CI); production is used for release checks and demos only through our own accounts. § 6: the device baseline sets a screen lock after at most 10 minutes and security updates within 30 days of release (the internal text said 14 days, the public text "reasonably current"); no device-management tool is in place yet; customer data is never kept on a personal device, and a copy on a company-owned device is allowed only for incident response, authorized support or approved debugging, and is deleted within 7 days. § 7: customer documents and the tax and identity data in them stay in the SendTax application and are not sent by email or chat, and credentials are shared only through 1Password; Google Drive and Google Docs are added to the list, and another tool for business communication needs the Qualified Individual's approval; corrected: GitHub and Notion are not covered by Google Workspace's certifications; Linear is removed from the list. § 8: the rules cover AI assistants, AI coding agents, AI features built into other tools and AI services our internal tools call; none of them gets customer data or secrets, whether or not it keeps them; our document-labeling tools send OpenAI no customer document; the platform's own document classifier runs on Modal, a listed sub-processor. § 8.4 now lists the approved AI tools; corrected: it said a list of approved AI tools was kept internally; none was. § 9: corrected the Access Control Policy reference (§ 3; there is no § 5.1); SendTax's own sign-in does not offer a second factor yet. § 12: reports are due immediately, and within one business day at the latest. § 13: the Qualified Individual approves exceptions, and no one approves their own. § 14: the Qualified Individual investigates violations. Internal text: § 3 adds a monthly check of each device against the baseline. In the public text, Contact is now § 16 and Change history § 17. Drafted with Claude. |
| 1.2 | 2026-10-16 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | The training computer (#564). Internal § 3 (public § 6): it is the one exception to the 7-day rule for copies of customer information on a company device: it may hold approved training contributions, only as SendTax's sealed exports opened there, for at most 30 days after each export is built, with nothing copied off it and no other customer information on it; this applies only from publication. Nobody keeps another person's documents for training: a relative or friend shares their own, from their own account. Internal § 3 adds BitLocker and Microsoft Defender for a Windows device, and the Windows check. Internal § 5 (public § 8.2): the tools that call OpenAI never get a training contribution. Drafted with Claude. |
| 1.3 | 2026-10-21 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | Training contributions are labeled on the training computer (#581). Internal § 3 (public § 6): they are labeled there, in the labeler it runs, from a member's own computer over the company's Tailscale network; that computer meets the device baseline, and nobody saves, downloads, copies, prints or captures a page shown there. Internal § 5 (public § 8.2): the training computer's labeler refuses its AI routes and the OpenAI key, so it can't send a contribution to OpenAI. Drafted with Claude. |
| 1.4 | 2026-10-22 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | Security statements, the Qualified Individual's decision of 2026-10-21. Corrected: public § 1 listed SOC 2 (CC6.1) among the compliance obligations this policy satisfies; SOC 2 is not an obligation of SendTax's, and no outside firm has assessed SendTax against it. Public § 9: SendTax's own sign-in doesn't offer two-step verification yet, and it switches on for pilot firms in December (it said the second factor was on the roadmap). Drafted with Claude. |
| 1.5 | 2026-10-26 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | The 2026-10-26 security and legal review. Corrected, internal § 5 and public § 8.4: the AI security review runs in a member's Claude Code session, on their own subscription, before a pull request leaves draft; the check in CI calls no model (both texts said it runs in CI on code changes). Public § 7.2: a document is referred to by a link in the application, not by its name, which often carries the client's own (the text allowed the name as shown in the application). Public § 6: the Windows baseline (BitLocker, Microsoft Defender) the internal text already had, and the monthly device check recorded on the compliance dashboard. Drafted with Claude. |
| 1.6 | 2026-11-11 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | The CRM (#659, #664; docs/design/crm-and-pilot-ops.md). Internal § 4 (public § 7): admin-web's CRM, SendTax's own record of the practices and people we contact about SendTax, with its Gmail connection, which sends a CRM user's sales email from their own send.tax mailbox, is a tool for business communication and coordination, so it joins the approved list once the Qualified Individual's written approval is recorded as a decision on the compliance dashboard; until then it isn't used, and sales email goes from Gmail by hand. Drafted with Claude. |