Information Processed
The interview may process donor identity, donor address, SSN, donee names and addresses, gift dates, gift descriptions, values, basis, valuation methods, and generated packet PDFs.
What Stays Local
The current app does not require an account and does not store return data on an application server. The project file and final PDF are downloaded to the user's device when requested.
- Return data lives in browser memory while the interview is open.
- Plain JSON export is available for local testing and should be treated as sensitive.
- Encrypted project export uses browser WebCrypto before download.
Address Autofill
Address entry uses browser-native autofill and local state dropdowns by default. The app does not call a third-party address autocomplete API in the current workflow.
Account And Payment Metadata
When account and payment providers are connected, the account may process email sign-in, payment, order, entitlement, and audit metadata. That account layer is not for storing Form 709 return payloads, generated PDFs, project files, SSNs, addresses, or gift facts.
Analytics
Return-entry pages should not use session replay, ad pixels, or analytics that capture taxpayer data. Public marketing pages may use aggregate, non-PII analytics after review.
Service Providers
A paid production version may use hosted checkout and email receipt providers. Those providers should receive only the minimum data needed for payment and receipt workflows, not Form 709 return payloads.
User Choices
Users can avoid cloud storage by downloading their own project file and packet. Once a file is downloaded, securing that local file is the user's responsibility.