Client PII is the whole risk
A single engagement letter is low-risk. A folder of 8879s full of Social Security numbers is not. Uploading those to a free web tool is precisely the kind of exposure a practice should avoid on principle.
For accountants, bookkeepers and advisors
Accounting practices handle some of the most sensitive material there is: tax returns, Social Security numbers, bank details, payroll records. That raises a question most signature tools never address — what happens to the document after you hand it over?
The honest answer for a cloud e-signature service is that it is stored on their infrastructure, usually for as long as your account exists, governed by their retention policy and their security posture. For a client's tax return, that is a decision worth making deliberately rather than by default.
Signing 8879 authorisations, engagement letters and advisory agreements in the browser means the file stays in the browser. We never receive the return, the SSN, or anything else in it — because there is no server in the path to receive it.
Where the friction is
A single engagement letter is low-risk. A folder of 8879s full of Social Security numbers is not. Uploading those to a free web tool is precisely the kind of exposure a practice should avoid on principle.
Filing season brings a surge in signatures, then it stops. Monthly per-seat pricing is a poor fit for a workload that is concentrated into a few weeks.
Custodians, lenders and investment platforms push their own signing workflows. A subscription just for your own counterpart signatures rarely pays for itself.
What you sign
Clear limits
The IRS permits electronic signatures on a number of tax forms, including Form 8879, when the electronic signature process meets its requirements. Where a particular form or filing is not covered, the agency's own instructions govern — that is a separate question from ESIGN, which covers the underlying contract law. The practical rule for a practice is that ESIGN covers your engagement letters and advisory agreements, and each agency's published rules cover its own forms.
How it works
The documents in this field are the ones people are least comfortable handing to an unfamiliar service. Our tools process them entirely in the browser.
PDF pages are rendered and written in the browser with open-source libraries that run entirely on the client. Signature strokes are captured on a canvas, and saved signatures are kept in your browser's own storage — the same mechanism any website uses to remember a preference. None of these components has a network call that transmits a file, and there is no backend for one to reach.
You do not have to take that on trust. Open your browser's developer tools, switch to the network tab, and sign a document. You will see the page's own assets load — fonts, scripts, stylesheets — and nothing else. No request carries your document, because none is made.
Where this is not the right tool. Browser-based signing is excellent for documents you sign yourself. It does not send a document to other people, collect their signatures, verify their identity, or produce an audit trail. When a counterparty or a compliance policy requires those things, use a platform built for it — the trade-off is real and worth naming rather than glossing over.
Related
FAQ
It depends entirely on whether the tool uploads the document. With a browser-based tool the return never leaves your device. With a cloud signing service it is stored on their infrastructure under their retention policy, which is a vendor relationship your practice should evaluate deliberately given what is in a tax return.
Yes. The IRS accepts electronic signatures on Form 8879 when the electronic signature process meets its requirements, and it has extended electronic signature acceptance to a range of other forms. Because the list and requirements change, confirm against the current IRS guidance for the specific form you are filing.
No, and we cannot, because we never receive them. The document is opened, signed and saved in the browser. There is no upload step, no server-side copy and no storage account holding the file.
Yes. An engagement letter is a contract, and under the ESIGN Act and the state UETA an electronic signature carries the same legal effect as a handwritten one where the signer intended to sign and the record can be retained and reproduced.
Those typically require notarisation or go through the lender's own platform. A client-side signature tool is not the right instrument for a deed or a notarised document — use the lender's process for those.
Yes. Keeping the executed document is your obligation and good practice regardless of how it was signed. This tool creates the signature; storing the signed file in your practice management system is still your record-keeping step.