TaxpaceEspañol

Draft for legal review. This is not the version in force yet.

Taxpace and Pacekeeping Data Processing Agreement

Version: 2026-10-12 · Status: draft for attorney review

This Data Processing Agreement (the "DPA") is part of the Taxpace and Pacekeeping Terms of Service between Twenty Techworks LLC (the "Service Provider") and the Subscriber that uses the Service with its clients' data: a tax firm, an accounting practice or a preparer (the "Firm"). Capitalized terms not defined here have the meaning given in the Terms.

It is written so the Firm, when it is a financial institution, can meet its obligation, under the FTC Safeguards Rule (16 CFR §314.4(f)), to oversee service providers through a contract that requires them to maintain appropriate safeguards. It also helps the Firm meet IRS Publication 4557 and IRC §7216.

1. Roles and scope

2. Instructions

3. Confidentiality of personnel

Everyone at the Service Provider who can access Client Data:

How access to Client Data works:

4. Information security program

The Service Provider maintains a written information security program that matches the elements of 16 CFR §314.4. It includes at least the measures in Annex A. The Service Provider:

5. Subprocessors

6. Security incidents

7. Assistance

The Service Provider will give reasonable help so the Firm can:

8. Data location

Client Data is stored and processed in the United States.

9. Return and deletion

10. Audits and information

11. Term

This DPA lasts as long as the Service Provider processes Client Data for the Firm.

12. Precedence

If this DPA and the Terms conflict on the protection of Client Data, this DPA governs.


Annex A. Security measures

AreaMeasure
Encryption in transitHTTPS (TLS 1.2 or higher) for every connection, including the client upload links
Encryption at restDatabase and file storage encrypted by the hosting provider. In addition, Social Security and ITIN numbers are encrypted at the field level, and each document file is encrypted with AES-256 before it is stored
Access controlSign-in with Google (with its two-step verification) or a password with a strict minimum length; roles and permissions per user; a user who cannot see a client sees nothing of that client
Client linksPersonal, expiring links. The client confirms identity with a known date before seeing anything. The link locks after repeated failed attempts
LoggingActivity history of who created, changed, viewed or deleted client records and documents; security logs kept [12] months
Data minimizationFull Social Security numbers are never shown in lists, URLs or logs; spouses' and dependents' numbers keep only the last 4 digits
SeparationEach firm's data is isolated from other firms' data [one database per firm — CONFIRM WITH #187]
InfrastructureDigitalOcean (United States): App Platform with managed HTTPS certificates and denial-of-service protection; managed PostgreSQL reachable only from the application; private Spaces storage; DigitalOcean account protected with two-step verification
BackupsDaily automated backups of the managed database with point-in-time recovery, kept [7] days; restore tested [quarterly]
Secure developmentEvery change goes through a reviewed pull request with automated tests; dependencies are kept up to date
PersonnelLeast-privilege access to production; access removed promptly when no longer needed
Incident responseWritten plan with roles, steps, and notice timelines (Section 6)
Vendor oversightSubprocessors are reviewed before use and listed publicly