INTEGRITY FINANCIAL ASSOCIATES, INC.
WRITTEN INFORMATION SECURITY PLAN (WISP)
Taxpayer Information, ERO Operations, Website, and GoHighLevel
Public website version
Document status: Draft for owner adoption — not in force until signed
Version: 1.0
Firm: Integrity Financial Associates, Inc. ("Firm")
Website: https://integrityfainc.com
Public contact: info@integrityfainc.com | 888-651-6113
Mailing address: PO Box 252, Apison, TN 37302
Service locations: Chattanooga, Tennessee area, and Atlanta, Georgia area
Last reviewed: ____________________
Next required review: on or before January 31 of each year, and after any material change
Classification: Client-facing safeguards policy. System inventories, access lists, and the incident runbook are internal and are not published.
NOTICE
This plan describes how the Firm protects nonpublic personal information and tax return information. It is available to clients on request. Detailed network diagrams, device inventories, account lists, and step-by-step incident procedures are kept by the Data Security Coordinator and are not posted on the public website.
The short public statement below may be used in the website footer or privacy section.
SHORT PUBLIC SAFEGUARDS STATEMENT
Integrity Financial Associates, Inc. maintains physical, electronic, and procedural safeguards that comply with applicable law and federal standards to protect taxpayer and customer information. We collect only what we need, limit who can see it, and do not use tax return information for marketing. Website and GoHighLevel forms are for scheduling and general business inquiries only. Do not send Social Security numbers, bank account numbers, or tax documents through the website chat, a web form, text message, or ordinary email.
1. OBJECTIVE
The Firm's objective is to create and maintain administrative, technical, and physical safeguards that are appropriate to the Firm's size, complexity, and the sensitivity of the information it holds, in order to:
A. Ensure the security and confidentiality of customer information and tax return information.
B. Protect that information against anticipated threats or hazards to its security or integrity.
C. Protect against unauthorized access or use that could result in substantial harm or inconvenience, including identity theft and refund fraud.
D. Comply with the Gramm-Leach-Bliley Act, the Federal Trade Commission Safeguards Rule (16 C.F.R. Part 314), the FTC Disposal Rule (16 C.F.R. Part 682), the FTC Privacy Rule (16 C.F.R. Part 313) to the extent it applies, Internal Revenue Code sections 6107, 6713, and 7216, Treasury Regulation section 301.7216, IRS Publications 4557, 5708, and 1345, and applicable Tennessee and Georgia law.
E. Meet current industry practice drawn from NIST guidance for small businesses, including unique identities, multi-factor authentication, encryption in transit and at rest, least privilege, logged access, tested backups, and written vendor oversight.
This plan is scaled to a small professional firm. The Firm adopts the full Safeguards Rule program as Firm policy, including a written risk assessment, security testing, a written incident-response plan, and an annual report to ownership, even if the Firm maintains customer information on fewer than 5,000 consumers and would otherwise qualify for the limited exemption in 16 C.F.R. § 314.6. The Qualified Individual will count covered consumers at least annually and record whether that exemption applies.
2. PURPOSE
This WISP states how the Firm evaluates and controls the collection, access, storage, use, transmission, disclosure, and disposal of personally identifiable information and tax return information, including information processed while the Firm acts as an Electronic Return Originator (ERO) or other Authorized IRS e-file Provider.
3. SCOPE
This plan covers all owners, employees, contractors, and service providers who create, receive, maintain, or transmit Firm or client information, and all paper records, devices, accounts, websites, and cloud services used for that work.
In scope:
A. Individual and business tax preparation, e-file, tax planning, bookkeeping, payroll, and related advisory work.
B. IRS e-Services, EFIN, PTIN, tax software, client portals, and secure file exchange.
C. The public website at integrityfainc.com and any page, form, chat, or scheduler that collects information from visitors or clients.
D. The Firm's GoHighLevel (HighLevel) sub-account, including funnels, forms, pipelines, calendars, email, SMS, and workflows.
E. Paper files, email, backups, mobile devices, printers, and home or remote work locations used for Firm business.
Out of scope for taxpayer data, and prohibited from receiving it:
A. Personal email, personal cloud drives, personal phones used as a storage location, and personal social media.
B. The owner's separate electrical and pressure-washing service operations, except for the owner's own business records. Those operations must not be used to store or transmit client tax return information.
C. Any website plugin, analytics tool, advertising pixel, or artificial-intelligence feature that has not been approved in writing by the Data Security Coordinator.
The plan identifies reasonably foreseeable risks, assesses harm, evaluates current safeguards, implements controls, and requires regular monitoring. It does not guarantee that every incident will be prevented. It requires prompt containment, notice, and correction when an incident occurs.
4. DEFINITIONS
Customer information. Any record containing nonpublic personal information about a customer of a financial institution, whether in paper, electronic, or other form, that is handled or maintained by or on behalf of the Firm, as used in the Safeguards Rule.
Tax return information. Any information that is furnished in, or derived from, or collected for, the preparation of a tax return, or that reflects the Firm's services to a taxpayer in connection with a return, within the meaning of IRC § 7216 and Treas. Reg. § 301.7216-1. This includes names combined with SSNs, dependents, income, deductions, credits, banking data used for a return, e-file status, and preparer workpapers.
PII. Information that identifies a person and is linked to an SSN or ITIN, date of birth, government ID number, financial account number, income or tax data, unpublished contact information, authentication data, or similar sensitive data. Public directory data alone is not PII under this plan.
Taxpayer data environment. Any system that stores, processes, or transmits tax return information or sensitive authentication data, and any system connected to those systems. The public marketing website and GoHighLevel are outside the taxpayer data environment unless the Data Security Coordinator documents a written exception before any tax return information is placed there.
Qualified Individual / Data Security Coordinator (DSC). The person designated to implement and enforce this program.
Security event. An event resulting in unauthorized access to, or disruption or misuse of, an information system or customer information held by the Firm or a service provider, as used in 16 C.F.R. § 314.2.
Online Provider. An Authorized IRS e-file Provider that owns or operates a website through which taxpayer information is collected, transmitted, processed, or stored for individual income tax returns, as described in IRS Publications 3112 and 1345. The Firm's present website is a marketing and scheduling site, not an e-file intake system. The Firm will not become an Online Provider unless Section 10 is completed first.
5. GOVERNANCE
5.1 Qualified Individual
Until a written designation names another person, the President of Integrity Financial Associates, Inc. is the Qualified Individual and Data Security Coordinator.
The DSC will:
A. Implement, supervise, and enforce this WISP, including day-to-day operational controls.
B. Identify repositories of customer information and tax return information and treat them as restricted assets.
C. Oversee the risk assessment and keep it current.
D. Approve access, remote access, new technology, and any exception to this plan. MFA exceptions, if any, must be approved in writing and must be reasonably equivalent to or more secure than MFA.
E. Verify training and acknowledgment before access is granted, and at least annually after that.
F. Evaluate service providers, require appropriate safeguards by contract, and oversee their work.
G. Review this plan at least annually, and whenever a material change in operations, systems, threats, or the law affects the security or integrity of covered information.
H. Coordinate incident response and required notices.
I. Provide a written annual report to Firm ownership describing the status of the program, risk assessment, service-provider oversight, security events, and recommended changes.
5.2 Public Information Officer
Until a separate person is appointed in writing, the President is also the Public Information Officer. If the Firm adds personnel, these roles should be separated. The PIO is the only person authorized to approve client notices, statements to law enforcement other than the DSC's required incident reports, media inquiries, and statements to business associates about a security event.
5.3 Authorized users
Access is granted only for a documented business need, only to the minimum information required, and only through a unique user ID. A current access list is maintained internally (Attachment F) and is not published. Sharing usernames, passwords, EFIN credentials, PTIN credentials, or tax-software seats is prohibited.
5.4 Accountability
Violation of this plan may result in loss of access, termination of employment or contract, and referral to law enforcement. Anyone who sees a suspected violation must report it to the DSC immediately. If the DSC is the source of the risk, the report goes to any other principal, or to outside legal counsel.
6. INFORMATION THE FIRM HANDLES
The Firm may handle:
A. Client and dependent identities, SSNs or ITINs, dates of birth, and contact information.
B. Individual and business income, expense, payroll, bank, and tax-position data.
C. Prior-year returns, workpapers, e-file acknowledgements, and direct-deposit instructions.
D. Engagement, billing, and scheduling records.
E. Employee and contractor records of the Firm.
F. EFIN, PTIN, e-Services, and software-vendor credentials. These are Firm secrets, not client files, and receive the same or stricter controls.
The Firm does not collect more information than it needs for the engagement, legal compliance, or a specifically authorized disclosure.
Website and GoHighLevel may collect only:
A. Name, business name, email, phone, preferred contact method, general service interest, and scheduling details.
B. Messages that do not include tax return information.
C. Marketing consent and SMS consent, recorded separately from any tax engagement.
Website visitors and leads must not be asked for an SSN, ITIN, bank account, routing number, driver's license number, wages, or a copy of a return through a web form, chat widget, survey, or text campaign.
7. RISK ASSESSMENT
The DSC maintains a written risk assessment covering each area of operation that handles customer information, including office storage, remote work, tax software, email, the website, GoHighLevel, payroll and bookkeeping platforms, backups, vendors, and paper files.
Foreseeable risks include:
A. Phishing and spear-phishing aimed at the Firm, the IRS, tax software, cloud storage, or GoHighLevel.
B. Stolen or reused passwords and missing MFA.
C. Malware, ransomware, and remote-access takeover, especially after hours.
D. Mis-delivery of tax return information by email, text, or a marketing automation workflow.
E. Placing tax return information into GoHighLevel, website logs, analytics, or an AI tool.
F. Use or disclosure of tax return information for marketing without a valid IRC § 7216 consent.
G. Dishonest or departed workforce access that is not removed.
H. Lost paper files, unlocked screens, or unencrypted laptops and phones.
I. Vendor breach, excess vendor access, or a subprocessors change that is not reviewed.
J. EFIN or PTIN misuse and fraudulent direct-deposit changes.
K. Fire, flood, theft, or loss of the only copy of client records.
L. Public Wi-Fi interception and insecure wireless networks.
M. Improper disposal of drives, printers, and paper.
For each risk the DSC records likelihood, impact, existing controls, gaps, the owner, and the remediation date. The assessment is reviewed at least annually and after a security event or a material system change. Effectiveness of safeguards is evaluated as part of that review, not only on paper.
8. SAFEGUARDS PROGRAM
Controls below are mandatory Firm policy. They implement 16 C.F.R. § 314.4 and IRS Publication 4557, scaled to this Firm.
8.1 Access control
A. Unique IDs for every person. No shared mailboxes for tax work except a monitored firm inbox that does not store tax return information in readable form.
B. Least privilege. Reception and marketing roles do not receive tax-software, EFIN, or payroll-file access.
C. Access is approved by the DSC, recorded on Attachment F, and removed within 24 hours of termination, role change, or end of need. Same-day removal is required during filing season and for any for-cause separation.
D. Unattended computers are locked. Paper files are not left on desks. Rooms and cabinets holding records are locked when unattended.
E. Visitors do not enter areas where tax return information is in use unless escorted.
F. Failed-login lockout is enabled where the system allows it.
G. Administrative passwords are at least 16 characters or a long passphrase. Other passwords are at least 14 characters or a passphrase of comparable strength. Passwords are unique, not based on the Firm name or a person's name, and are not reused on personal sites.
H. A reputable password manager may be used if MFA protects it and the DSC has approved the product. Passwords are not stored in browsers, spreadsheets, GoHighLevel notes, or chat.
I. The Firm follows NIST SP 800-63B practice: passwords are changed when compromised, reused, shared, or when someone with knowledge of the password leaves. Arbitrary rotation solely because a year has passed is not required. Suspected compromise requires an immediate reset.
J. MFA is required for every person accessing any information system that contains or can reach customer information. This includes email, tax software, e-Services, the website host, GoHighLevel, cloud storage, the password manager, remote access, and banking used for Firm operations. MFA must use at least two different factor types. SMS is a last resort; an authenticator app or hardware key is preferred. The DSC may not waive MFA for tax software, email, e-Services, or GoHighLevel.
8.2 Inventory
The DSC keeps an internal inventory of devices, accounts, and software that store or transmit customer information (Attachment E), including owner, location, data type, and disposal date. The inventory includes laptops, phones used for MFA or email, routers, printers, external drives, backup targets, the website host, GoHighLevel, tax software, and bookkeeping or payroll platforms. Personal devices are not approved storage locations.
8.3 Encryption and transmission
A. Customer information is encrypted in transit and at rest. Approved in-transit protection is TLS 1.2 or later. SSL 3.0, TLS 1.0, and TLS 1.1 are disabled on Firm-controlled systems.
B. Laptops and other portable devices use full-disk encryption. Removable media used for client files are encrypted.
C. Tax return information is not sent by ordinary email, SMS, voicemail, or a GoHighLevel message. If a file must move outside the approved tax portal, it is encrypted, and the password or key is sent by a different channel.
D. The preferred exchange method is the secure portal of the Firm's approved tax or document system. SFTP may be used if configured by the DSC or the IT provider.
E. Website collection, if any, uses HTTPS only. The site is not used to collect tax return information.
F. If a system cannot encrypt customer information, it may not be used for that information unless the DSC approves compensating controls in writing and documents why encryption is not feasible.
8.4 Endpoint and network protection
A. Supported operating systems and browsers only. Unsupported systems are removed from the taxpayer data environment.
B. Automatic updates for operating systems, browsers, tax software, and security tools.
C. Anti-malware with automatic updates on systems that handle customer information.
D. A host firewall, plus a network firewall between the internet and any private office network.
E. Wireless networks, if used, use WPA3 where available, otherwise WPA2-AES. WEP and open office networks are prohibited. Default router passwords are changed. The office network name does not identify the Firm as a tax office. Guest Wi-Fi, if offered, is isolated from the office network.
F. Public Wi-Fi is not used for email, tax software, e-Services, GoHighLevel administration, or client files unless a Firm-approved VPN is connected first. A VPN is required for remote access to any office network.
G. Remote-access tools must encrypt the session and the login, require MFA, and be approved by the DSC. Unattended remote access after hours is disabled unless the DSC documents a monitored exception.
H. USB autorun is disabled. Unknown USB devices are not connected to systems that hold client data.
I. New software, browser extensions, AI tools, and connected devices require DSC approval before installation or connection.
J. Printers and copiers that store jobs have default passwords changed, local disks encrypted or purged, and are wiped before disposal.
K. The Firm does not download "security" tools from pop-up ads or unknown sites.
8.5 Application and website security
The Firm does not custom-develop tax-filing software. For the website and GoHighLevel configuration, the DSC will:
A. Keep the content-management system, themes, and plugins updated and remove unused components.
B. Use MFA and least privilege on the hosting and DNS accounts.
C. Restrict administrator accounts to named persons.
D. Review forms and workflows before publication so they cannot collect tax return information.
E. Disable storage of full card numbers. The Firm does not take card payments through ad-hoc email. Any payment page must use a PCI-DSS compliant processor; card data is not stored on the website or in GoHighLevel.
F. Review logs for unexpected administrator logins and form-spam events.
8.6 Monitoring and audit
A. Logging remains enabled on tax software, email, the website host, GoHighLevel, and remote access, where the vendor provides logs.
B. The DSC or the IT provider reviews security-relevant logs at least quarterly, and weekly during filing season for e-Services EFIN activity.
C. The DSC reviews the EFIN application status and return counts weekly. Unexpected volume, odd-hour transmissions, or unknown returns are treated as a security event.
D. PTIN return counts are reviewed when the IRS account makes them available. Misuse is reported on Form 14157.
E. Centralized Authorization File or other IRS authorizations are withdrawn when the engagement ends.
F. Each return's direct-deposit information is reviewed against source documents or a client confirmation that did not arrive solely by an unexpected email, before the return is transmitted.
8.7 Secure disposal
A. Paper containing customer information is cross-cut shredded or incinerated. Locked shred consoles are acceptable if the vendor contract meets Section 11.
B. Electronic media is cleared, purged, or destroyed so the information cannot be practicably read or reconstructed, consistent with 16 C.F.R. Part 682. Deletion alone is not enough for retired drives, phones, copiers, or USB media. Devices that cannot be sanitized are physically destroyed.
C. Departing users' cloud access is revoked even if a device is not recovered. Firm data on a personal device is remotely wiped if the platform allows it, or the device is inspected before release.
D. Backups of disposed records are deleted on the same schedule, subject to any legal hold.
8.8 Change management
Material changes — new tax software, a new portal, a GoHighLevel workflow that touches client files, a new website form, a hosting move, or a new subprocessor — are reviewed against this plan before use. The DSC records the decision.
8.9 Physical security
A. Records are stored in a locked office area or locked cabinet, protected so far as practical from theft, fire, and water.
B. Mailing address PO Box 252, Apison, TN 37302 is not a storage location for client files. Client documents are not left in a vehicle.
C. A clean-desk and clear-screen practice is required at the end of each work period.
D. The Atlanta service location, when an address is finalized, will be added to the inventory before any client records are stored there. A placeholder address will not be used for receiving client documents.
8.10 Workforce security
A. People hired into roles with access to customer information are subject to reference or background checks appropriate to the role, as permitted by law.
B. Access is not granted until this plan has been read, training is complete, and Attachment D is signed.
C. The Firm may require a confidentiality agreement. Tax return information remains confidential whether or not a separate agreement is signed.
D. Terminated users return keys, tokens, and Firm devices the same day. Credentials are revoked as provided in Section 8.1.
9. ERO AND TAX-RETURN RULES
9.1 Role
When the Firm originates electronically filed returns, it does so as an ERO under IRS Publication 1345 and the Firm's IRS e-file application. EFIN and e-Services credentials are used only by authorized persons and only for authorized purposes. Unused EFINs are deactivated.
9.2 Section 7216 — use and disclosure
Tax return information may be used or disclosed only as permitted by IRC § 7216, Treasury Regulation sections 301.7216-1 through 301.7216-3, or a valid taxpayer consent that meets the regulation's timing, format, and disclosure rules.
Without a separate, compliant consent, the Firm will not:
A. Use tax return information to market accounting, payroll, insurance, financial-planning, construction, electrical, pressure-washing, or any other service beyond the service the taxpayer requested.
B. Load tax return information into GoHighLevel, an email campaign, a lookalike audience, or an advertising pixel.
C. Sell, rent, or trade client lists built from tax return information.
D. Disclose tax return information to a bookkeeper, payroll provider, financial planner, lender, or software tool except as the regulations allow for the purpose of the engagement, or with valid consent.
Disclosures required to e-file, including disclosures to the IRS, applicable state agencies, and the authorized transmitter or software provider for the purpose of electronic filing, are made only to the extent allowed by Treas. Reg. § 301.7216-2 and Publication 1345.
A request from a caller, email sender, or even a known client is authenticated before any tax return information is discussed. Identity is verified with information that is not taken solely from the inbound message. Refund status, copies of returns, and banking changes require a documented authentication step.
9.3 Other preparer duties
A. The Firm retains a completed copy of each return or claim, or a list of the taxpayer's name and TIN, for at least three years after the close of the return period, as required by IRC § 6107(b).
B. The Firm does not alter a direct-deposit account based only on an email request.
C. The Firm recommends that clients obtain an IRS Identity Protection PIN.
D. Suspicious IRS email is not opened. It is forwarded to phishing@irs.gov.
E. The Firm subscribes to IRS e-News for Tax Professionals or an equivalent IRS practitioner alert channel.
9.4 What "e-file through the website" would require
The Firm does not collect, transmit, process, or store taxpayer information for individual income tax returns on integrityfainc.com. If that ever changes, the Firm will, before go-live, comply with the six IRS security, privacy, and business standards for providers, including as applicable:
A. A current extended-validation certificate if still required, with TLS 1.2 or later. Obsolete SSL and early TLS versions will not be enabled to meet an older minimum.
B. Weekly external vulnerability scans of the taxpayer data environment by a PCI Security Standards Council Approved Scanning Vendor located in the United States, with reports kept at least one year, and remediation of findings. Any host in that environment must meet applicable PCI-DSS requirements and be located in the United States.
C. A written privacy and safeguard policy that includes the statement that the Firm maintains physical, electronic, and procedural safeguards that comply with applicable law and federal standards, plus any privacy-seal certification the IRS then requires.
D. Controls against bulk filing of fraudulent returns. Taxpayer information will not be collected except through the protected channel.
E. Domain registration with a United States ICANN-accredited registrar, with the domain locked and not privacy-masked, if that standard applies to the site.
F. Incident reporting as provided in Section 13.
The Firm will also submit any website URL the IRS requires for sites that collect taxpayer information.
Even while the site is marketing-only, the domain is kept locked at a reputable registrar, DNS and hosting use MFA, and WHOIS or registration contacts are accurate. The Firm will not rely on a free website builder as a tax-document portal.
10. WEBSITE AND GOHIGHLEVEL
10.1 Role of the website
integrityfainc.com is used to describe services, publish this safeguards statement, and invite visitors to book a financial evaluation or contact the Firm. It is not a repository for returns, workpapers, or e-file credentials. Form submissions are delivered only to a Firm-controlled mailbox or to the GoHighLevel sub-account, not to a personal inbox.
10.2 Role of GoHighLevel
GoHighLevel (HighLevel) is an approved service provider for customer-relationship management, scheduling, and non-tax marketing communications. It is not approved for tax preparation, payroll processing, or storage of tax return information.
Permitted data in GoHighLevel:
A. Lead and client contact records needed to schedule and communicate: name, business name, phone, email, city or service area, service interest, appointment history, and general notes that contain no tax return information.
B. Consent records for email and SMS.
C. Pipeline stage, such as "evaluation booked" or "engagement letter sent," without income, SSN, or refund amounts.
Prohibited in GoHighLevel custom fields, notes, tasks, forms, surveys, chat, SMS, email templates, workflows, AI training fields, and attachments:
A. Social Security numbers, ITINs, EINs of clients, dates of birth, driver's license or state ID numbers, and bank or card numbers.
B. Tax returns, wage statements, profit-and-loss detail, payroll registers, or workpapers.
C. EFIN, PTIN, e-Services, or tax-software credentials.
D. Direct-deposit routing or account numbers.
E. Any data element that would make the record tax return information, unless the DSC has issued a written exception after a Section 7216 review, a security review, and a contract review. No exception is granted by this plan.
10.3 Configuration standard
Before client or lead data is used in GoHighLevel, and at least annually after that, the DSC confirms:
A. A dedicated Firm sub-account is used. It is not shared with unrelated businesses.
B. Every user has a unique login and MFA. Former users are disabled within 24 hours.
C. Roles are least privilege. Marketing contractors do not receive export rights unless the DSC approves a time-limited export of non-tax contact data.
D. Public forms and funnels collect only the fields in Section 6. Hidden fields are reviewed so tracking data does not include form contents that could become sensitive.
E. Conversation AI, review requests, and workflow actions are disabled or restricted so they cannot ingest or send tax documents.
F. Exports, API keys, and third-party integrations are inventoried. Unused integrations are removed. API keys are rotated if exposed and at least annually.
G. Audit logs, if available in the Firm's plan, are reviewed quarterly for new users, exports, and failed logins.
H. Retention in GoHighLevel is limited to what marketing and client-service records require. Leads who do not become clients are deleted or anonymized within 24 months unless a shorter period is adopted. Clients' non-tax contact records may be kept for the engagement plus the retention period in Section 12, then deleted.
I. A tested method exists to export or delete Firm data if the vendor relationship ends.
10.4 Vendor assurance relied upon
The Firm's vendor file will include the current HighLevel terms, privacy policy, data-processing terms, and the most recent security summary the vendor will provide. As of the Firm's last public-source review, HighLevel represents that it undergoes an annual SOC 2 Type II assessment covering security, availability, and confidentiality; hosts on Google Cloud Platform; encrypts with TLS 1.2 or later in transit and AES-256 at rest; offers multi-factor authentication, granular permissions, and audit logs; and maintains a vulnerability-reporting program. Those are vendor representations, not a substitute for the Firm's own configuration or for a review of the SOC report.
The DSC will request the SOC 2 report or a SIG Lite packet at onboarding and at each annual vendor review. If the vendor cannot provide reasonable assurance, or if a report shows an unremediated control failure affecting confidentiality, GoHighLevel will not be used for any information beyond public business-card data until the gap is accepted in writing or closed.
10.5 Marketing law, separate from tax law
Email and SMS sent through GoHighLevel must comply with CAN-SPAM, the Telephone Consumer Protection Act, and applicable state telemarketing rules. Consent to receive marketing is not consent to disclose tax return information. Tax return information is not used to build marketing segments.
10.6 Analytics and embedded tools
Advertising pixels, session-replay tools, and chat widgets are disabled on any page that could receive client documents or identifiers. If a scheduler is embedded from GoHighLevel, the embed is limited to scheduling fields. The website will not pass form contents to an analytics platform.
11. SERVICE PROVIDERS
The DSC selects service providers that are capable of maintaining appropriate safeguards, requires those safeguards by contract, and periodically oversees them, as required by 16 C.F.R. § 314.4(f).
Covered providers include, as applicable, the tax-software and transmitter vendor, cloud email, website host, domain registrar, GoHighLevel, bookkeeping and payroll platforms, IT support, shredding, off-site storage, and the landlord's cleaning personnel to the extent they can see records.
Contracts or terms, to the extent the Firm can negotiate them, must require the provider to:
A. Protect confidentiality, integrity, and availability of Firm and client information.
B. Use the information only to perform the contracted services.
C. Encrypt information in transit and at rest, or apply approved equivalent controls.
D. Restrict and authenticate access, including MFA for administrative access.
E. Notify the Firm without undue delay, and in any event soon enough for the Firm to meet IRS, FTC, and state deadlines, after discovering a security event.
F. Return or delete information at the end of the service, subject to law.
G. Flow down equivalent duties to subcontractors who will handle the information.
H. Allow the Firm to review security summaries, SOC reports, or equivalent evidence on request.
Oversight is risk-based. Tax software, email, and GoHighLevel are reviewed at least annually. A provider that only shreds paper under supervision may be reviewed at engagement and on renewal. Results are recorded in the vendor file.
Providers that already operate under stricter federal tax-administration rules, including the IRS and state tax agencies, and authorized e-file transmitters acting within Publication 1345, are noted as such. That status does not allow the Firm to send them information they do not need.
12. COLLECTION, RETENTION, AND DISCLOSURE
12.1 Minimum necessary
Information is collected only for the engagement, for required filings, for billing, or for a communication the person requested. Staff will not copy an entire client file to a laptop when a single workpaper is enough.
12.2 Retention
Records are kept only as long as law or a documented business need requires, then destroyed under Section 8.7.
A. Return copies or the IRC § 6107 client list: at least 3 years after the close of the return period.
B. Engagement files and workpapers: 7 years from the end of the engagement year, unless a longer hold applies. This covers the ordinary 3-year assessment period and the 6-year substantial-omission period, plus a short administrative margin.
C. Employment-tax and payroll records: at least 4 years after the due date of the related return or the date the tax was paid, whichever is later, or longer if a specific rule requires it.
D. Firm personnel and contractor records: as required by employment and tax law.
E. GoHighLevel non-client leads: not longer than 24 months.
F. Security logs and vendor-review records: at least 3 years, or longer if needed to document an incident.
G. Legal hold: destruction stops when litigation, an IRS examination of the Firm, or a breach investigation requires the records. The DSC documents the hold and the release.
Keeping records "just in case" beyond these periods is not allowed for tax return information.
12.3 Disclosure inventory
The Firm may disclose customer information, limited to what is needed, to:
A. The IRS, state tax authorities, and authorized e-file transmitters, for filing and administration.
B. A tax-software vendor, as required to prepare or transmit a return.
C. A successor preparer, bookkeeper, payroll processor, or professional advisor only as Section 7216 and the engagement allow, or with valid consent.
D. The Firm's legal counsel, insurer, or forensic provider, when necessary to protect the Firm or respond to an incident, and subject to confidentiality.
E. Law enforcement or a regulator, when required by law, subpoena, or a mandatory breach notice.
F. An IT provider, only to the extent access is required to maintain a system, under Section 11.
Any other disclosure requires DSC approval and, where tax return information is involved, a Section 7216 analysis before the disclosure.
13. TESTING, TRAINING, AND PROGRAM REVIEW
13.1 Testing
A. The DSC confirms at least annually that MFA is on, encryption is on, backups restore, and terminated-user removal works. A restore test uses a non-production copy and is recorded.
B. Vulnerability remediation follows vendor severity guidance. Critical patches on internet-facing Firm systems are applied within 14 days, or the system is isolated.
C. If the Firm later maintains a taxpayer data environment that it controls, it will add continuous monitoring or, at minimum, an annual penetration test and vulnerability assessments at least every six months, as provided in the Safeguards Rule. While a qualified hosting or tax-software vendor controls that environment, the Firm reviews the vendor's testing evidence instead of scanning the vendor's platform without authorization.
D. Phishing awareness is discussed at least annually. The DSC may send a benign internal test. Results are used for coaching, not for public shaming.
13.2 Training
All personnel with access to customer information complete security training before access, and at least annually. Topics include this plan, Section 7216, phishing, public Wi-Fi, clean desk, direct-deposit fraud, GoHighLevel prohibitions, and how to report an incident. Attendance is certified on Attachment D.
13.3 Annual report and plan update
On or before January 31, the DSC reports to ownership in writing on:
A. The status of this plan and material changes.
B. The current risk assessment and open gaps.
C. Service-provider reviews, including GoHighLevel.
D. Security events, even if notice to clients was not required.
E. Training completion and access-list review.
F. Recommendations for budget or control changes.
The plan is also updated when the Firm adds a service, changes tax software, opens a new office, or suffers a security event.
14. INCIDENT RESPONSE
This section is the Firm's incident-response plan. A non-public runbook with phone numbers and account-recovery steps is kept with the DSC and offline.
14.1 What must be reported internally
Any lost device, lost file, ransomware screen, unexpected e-file rejection because a return was already filed, client notice of a transcript or refund the client did not request, unusual EFIN volume, credential prompt the user did not initiate, or discovery of tax return information in GoHighLevel, email, or the website, is reported to the DSC immediately. Staff must not pay a ransom, wipe a machine, or message clients before the DSC directs them to do so, unless disconnecting an infected machine from the network is needed to stop ongoing loss.
14.2 Response steps
The DSC will:
A. Contain. Disconnect affected systems from the internet, disable compromised accounts, revoke exposed keys, and preserve logs and images before rebuilding.
B. Assess. Determine what information was affected, whose it was, whether tax return information was involved, the likely cause, and whether the website or GoHighLevel was involved.
C. Eradicate and recover. Remove the cause, reset credentials, confirm MFA, and restore from a clean backup. E-file operations resume only after the DSC concludes the channel is safe. If the IRS requires a new EFIN before transmission resumes, the Firm will follow that instruction.
D. Notify. Make the notices in Section 14.3. The PIO approves client wording.
E. Learn. Within 30 days after containment, record what failed and update this plan, access, or vendors.
14.3 External notices
After a confirmed security event involving taxpayer or customer information, the Firm will notify, as applicable and as soon as the facts allow:
A. The IRS Stakeholder Liaison for the Firm's area, as soon as possible. For a confirmed incident involving individual income tax return information, the Firm's standard is no later than the next business day after confirmation, consistent with IRS e-file security-incident reporting. ERO-only incidents are reported through the Stakeholder Liaison path published by the IRS. The Firm will not rely on a general IRS phone assister to accept a third-party identity-theft report.
B. State tax agencies in each state for which the Firm prepares returns for affected taxpayers, using the Federation of Tax Administrators breach contacts or the state's current instructions.
C. The Federal Trade Commission, through the Safeguards Rule security-event reporting form, as soon as possible and no later than 30 days after discovery, if the event notifies, or is reasonably likely to notify, at least 500 consumers.
D. The FBI Internet Crime Complaint Center, and local law enforcement, when the event may be a crime. A police report is filed when needed for clients, insurers, or regulators.
E. The Firm's tax-software vendor, cyber insurer, and legal counsel.
F. Affected individuals when required by Tenn. Code Ann. § 47-18-2107, O.C.G.A. § 10-1-910 and following, any other state law that applies to a resident whose information was affected, or when notice is the right step to prevent identity theft even if a statute's trigger is unclear. Notice will not be delayed for an internal investigation beyond what the statute allows. Law-enforcement delay requests will be honored only when legally permitted and documented.
G. State attorneys general when the applicable statute requires it. Thresholds will be confirmed with counsel at the time of the event rather than guessed.
If the website is the proximate cause of an incident involving taxpayer information, collection of taxpayer information through the website stops immediately and does not restart until the cause is fixed.
Client notices will describe, in plain language, what happened, what information was involved, what the Firm is doing, what the person can do, and how to reach the Firm. The FTC's data-breach guidance may be used as a model. The Firm will not include unnecessary sensitive details in a public post.
Identity-theft affidavits are filed by the affected taxpayer. The Firm will help clients understand IRS identity-theft resources and the IP PIN program, and will not file Form 14039 as if the Firm were the taxpayer.
14.4 Ransomware
The Firm does not pay ransom as a matter of policy. Any exception requires ownership and legal counsel, and still requires notice to the IRS and, as directed, to CISA and the FBI. Payment does not replace containment or client notice.
14.5 Continuity
Encrypted backups are made at least weekly, and daily during filing season, to a location that is not continuously writable by the production workstations. At least one backup is offline or immutable. Backups are encrypted before they are placed in a cloud store. A monthly backup checklist is initialed by the DSC during filing season.
15. IMPLEMENTATION
This WISP is adopted to comply with the Gramm-Leach-Bliley Act, the FTC Safeguards Rule and Disposal Rule, IRC §§ 6107, 6713, and 7216, and IRS e-file safeguard requirements. It also serves as the Firm's written commitment that it maintains physical, electronic, and procedural safeguards that comply with applicable law and federal standards.
This plan is effective on the date of the last signature below. It replaces any earlier undocumented practice. Employees and contractors with access to customer information will sign Attachment D within 15 days after adoption, and before access if hired later.
A public copy of Sections 1 through 15, excluding internal attachments, may be posted at integrityfainc.com. Posting does not waive confidentiality of client information or of the internal attachments.
The DSC will keep a signed PDF offsite or in an approved cloud location so a physical loss does not destroy the only copy.
LIMITATION
This document is an operational policy. It is not a legal opinion, an IRS ruling, or a warranty that a particular system is certified. Federal and state requirements change. The DSC will verify notice deadlines and Online Provider standards at the time of an incident or before any website begins to collect taxpayer information.
SIGNATURES
Qualified Individual and Data Security Coordinator
Signature: ________________________________ Date: ________________
Name: ____________________________________
Title: President, Integrity Financial Associates, Inc.
Ownership adoption
Signature: ________________________________ Date: ________________
Name: ____________________________________
Title: President, Integrity Financial Associates, Inc.
ATTACHMENT A — RECORD RETENTION SCHEDULE
(Internal. Do not publish.)
Record class | Minimum | Firm period | Destruction method
Return copy or IRC 6107 list | 3 years after return period | 7 years | Portal deletion plus backup expiry, or shred
Workpapers | Business need | 7 years after engagement year | Shred or crypto-erase
Payroll / employment tax | 4 years | 7 years unless longer rule applies | Shred or crypto-erase
Engagement letters and consents | Life of engagement plus limitation period | 7 years | Shred or crypto-erase
GoHighLevel non-client leads | None | 24 months | Vendor deletion
Security logs | Program evidence | 3 years | Log rotation
Vendor SOC reports | Oversight evidence | 3 years | Access-controlled archive
Legal holds are recorded here:
Matter | Start | Records frozen | Released by | Release date
______ | _____ | ______________ | ___________ | ____________
ATTACHMENT B — RULES OF BEHAVIOR
(Give to every user. May be posted inside the office. Do not post network details.)
1. I will not put SSNs, bank numbers, returns, or wage data into GoHighLevel, a website form, chat, text, or ordinary email.
2. I will not click unexpected links or open unexpected attachments. I will call the sender using a number I look up myself.
3. I will not use personal email or personal cloud storage for client work.
4. I will not connect unknown USB drives or use public Wi-Fi for client work unless the Firm VPN is on.
5. I will lock my screen and clear my desk before I step away.
6. I will not share passwords, MFA codes, or EFIN access. No vendor, client, or "IRS agent" is entitled to my password.
7. I will verify direct-deposit changes and caller identity before I discuss a return.
8. I will use only Firm-approved software. I will not install free remote-access or "PC cleaner" tools.
9. I will report a lost device, strange login, or suspected phishing the same day to the Data Security Coordinator.
10. I understand that tax return information cannot be used to market other services unless the Firm has a valid IRC § 7216 consent.
ATTACHMENT C — INCIDENT CONTACT RUNBOOK
(Internal. Keep a paper copy offline. Do not publish.)
Role | Name | Phone | After-hours
Data Security Coordinator | __________________ | ________________ | ________________
Public Information Officer | __________________ | ________________ | ________________
IT provider | __________________ | ________________ | ________________
Cyber insurer / policy no. | __________________ | ________________ | ________________
Legal counsel | __________________ | ________________ | ________________
Tax software vendor | __________________ | ________________ | ________________
IRS Stakeholder Liaison | Confirm current local contact at IRS.gov before filing season | |
IRS phishing | phishing@irs.gov | |
FTC Safeguards event report | Report through the FTC online form if 500 or more consumers | |
FBI IC3 | https://www.ic3.gov | |
State tax agencies | Federation of Tax Administrators breach contacts | |
First 60 minutes:
[ ] Isolate affected devices. Do not power them off if a forensic image may be needed, unless encryption or ongoing theft requires disconnecting the network immediately.
[ ] Disable compromised accounts and rotate exposed keys.
[ ] Record who discovered the event, when, and what systems are involved.
[ ] Do not post about the event on social media or in a client blast.
ATTACHMENT D — ACKNOWLEDGMENT
(Internal personnel file.)
I, ________________________, acknowledge that I have received and understand the Written Information Security Plan of Integrity Financial Associates, Inc., including the rules on tax return information, GoHighLevel, passwords, multi-factor authentication, and incident reporting. I have had a chance to ask questions. I understand that violations may result in loss of access and termination, and may be reported to authorities. I understand that I must complete refresher training when the plan changes and at least annually.
Signature: ______________________________ Date: ________________
Role: __________________________________
Training provided by: _____________________
ATTACHMENT E — SYSTEM AND DATA INVENTORY
(Internal. Do not publish.)
Item | Location / vendor | User or admin | Data types | In service | Last review
Example: tax software | Vendor cloud | President | Tax return information | ____ | ____
Example: GoHighLevel sub-account | HighLevel | President | Contact and scheduling data only | ____ | ____
Website integrityfainc.com | ________________ | ________________ | Marketing inquiries only | ____ | ____
Email | ________________ | ________________ | | ____ | ____
Laptops / phones | ________________ | ________________ | | ____ | ____
Backups | ________________ | ________________ | | ____ | ____
Router / office network | ________________ | ________________ | | ____ | ____
ATTACHMENT F — ACCESS LIST
(Internal. Do not publish.)
Name | Role | Systems | Level | Granted | Revoked
President / DSC | Owner | All approved systems | Full | ________ |
________________ | ________ | ________ | ________ | ________ | ________
ATTACHMENT G — ANNUAL REVIEW CHECKLIST
(Internal.)
Review year: ________ Completed by: ________________ Date: ________
[ ] Consumer count recorded. Under 5,000 consumers? Yes / No
[ ] Risk assessment updated
[ ] MFA confirmed on email, tax software, e-Services, website, GoHighLevel, backups
[ ] Access list matches current personnel
[ ] Departed-user test passed
[ ] Backup restore test passed
[ ] EFIN weekly-review habit confirmed
[ ] GoHighLevel forms rechecked for prohibited fields
[ ] GoHighLevel users, API keys, and integrations reviewed
[ ] Vendor list reviewed; HighLevel security packet requested
[ ] Training and Attachment D current
[ ] Retention destruction completed for records past schedule
[ ] Domain lock and hosting MFA confirmed
[ ] Annual report given to ownership
[ ] This public plan updated if controls changed
Open gaps and due dates:
________________________________________________________________
________________________________________________________________
END OF PLAN
Integrity Financial Associates, Inc. — WISP version 1.0 — integrityfainc.com
