When you request the free toolkit
We store the email address you submit, the date of your toolkit request and public source labels. Your email is required to unlock a short-lived download link on this page. It is not an email verification process, and no email is sent automatically.
Requesting the workbook does not subscribe you to a newsletter or request a workflow review. We do not use this request to contact you about a workflow review; you can request one separately. Staff can review requests in the protected growth dashboard. We retain toolkit requests for up to 12 months; you can request deletion using the privacy contact process below.
Download links expire after 15 minutes. You can submit the form again to get a fresh link. Email addresses and download tokens are not sent to analytics.
When you contact us about a workflow
The general workflow inquiry stores your work email, company, optional role, industry, selected workflow, a short description, permission to respond and public attribution labels. We use this to review and respond to your inquiry. It is separate from an accounting audit and does not subscribe you to ongoing marketing. Do not include private client information.
For accounting audit requests, ParseMill stores your work email, firm, optional role, location, services, selected workflow and software stack, along with calculator inputs, the model version, calculated results and your permission choices. Source and campaign labels are attached to the request to understand what brought you here. We use these details to review your workflow and respond about the audit. The request does not subscribe you to a newsletter or authorize unrelated marketing.
Do not include taxpayer records, client identifiers, passwords or financial documents. Any later workflow sample requires a separately agreed secure process.
Optional analytics on public pages
If you select “Allow analytics”, ParseMill records public page views, calculator starts and completions, selected content, audit-link clicks and toolkit download clicks on our own server and through Google Analytics. Google also receives an event after our server accepts an accounting audit request, provided analytics consent was active when you submitted and remains active when it succeeds. Failed requests, calculator results and form entries are not leads.
Google Analytics uses browser-session analytics cookies and processes technical connection and browser information, including your IP address when connecting to Google, device/browser information and a pseudonymous browser identifier. Our implementation sends canonical public page paths, a public workflow category where relevant, and a limited referring page or search-engine origin. It removes query strings and fragments, and does not send work email, firm name, form answers, calculator values, filenames, uploaded files, contact identifiers or private workspace activity. Advertising storage, Google signals and ad personalization are disabled. Automatic form, search, download, outbound-link and history measurement are disabled; resource events come from our explicit controls.
Google is a separate analytics provider and may process data internationally under its terms and privacy policy. Read Google’s Privacy Policy and how Google uses information from sites that use its services. Public-page analytics is separate from any private Google inbox connection; mailbox data is never sent to Analytics.
The analytics choice and our anonymous attribution are stored in browser session storage for that tab. The Google cookies are configured to expire at the end of the browser session. Our own optional events may include bounded public campaign labels and a random tab-session identifier; if you request an audit while analytics is enabled, this identifier can link the request to our first-party events. Google does not receive our lead ID, audit submission ID or first-party session ID. Exact organic search queries are researched separately in aggregate through Search Console.
Previous permission for first-party measurement alone does not enable Google Analytics: we ask for a new choice. Before that choice, no Google analytics script or collection request loads. Declining does not affect the calculator, forms or downloads. Do Not Track and Global Privacy Control disable optional analytics. Select “Measurement settings” in the footer to withdraw consent for future activity; this disables the Google tag, drops queued events and removes this site’s analytics cookies. Already transmitted data cannot be recalled by the browser control. We do not replay actions taken before consent. Visits without permission are absent from the analytics sample, so these counts are not total site traffic.
Temporary calculator context and operational records
Selecting “Continue to a workflow audit” stores your calculator inputs in this tab so the audit can use the estimate you requested. This contains no contact details and is cleared after a successful request. Closing the tab clears its session storage. We use an essential CSRF cookie when submitting forms. The service also keeps bounded, hashed request-rate counters to prevent abuse. Existing infrastructure may keep operational logs; optional measurement does not replace these security controls.
Retention, access and deletion
Unconverted audit and prospect contact records are retained for up to 12 months after the latest recorded activity. Our first-party anonymous measurement events are retained for 90 days. Google Analytics data retention is controlled separately in the ParseMill property settings; browser-session cookie expiry does not delete previously collected analytics data. The operator retention command removes expired records; the deployment runbook schedules it daily. Converted customer records follow the relevant engagement requirements and are not deleted by this acquisition cleanup. Access to the dashboard and inquiry records is restricted to authorized operators.
Minimal suppression records are kept to honor opt-out requests. They contain a hash of the normalized email address and the opt-out record; they are not used for marketing. To request access, correction, deletion, or withdrawal of benchmark permission, submit a workflow audit request using the same email and put “Privacy request” in the optional role field. We will confirm the scope with you before acting.
When you connect an inbox or accounting account
Connecting an account is a separate, explicit authorization. Gmail and Microsoft connections read a bounded sample of inbox messages and supported text attachments when you request an import. QuickBooks and Xero connections read a bounded contact sample from the organization you select. ParseMill uses this information for your private review queue and exact sender-to-contact matching. These connections do not send messages, move mail or change accounting records.
Access and refresh credentials, imported message text, attachment text and contact payloads are encrypted in the database with a separate connection key. Account labels, provider identifiers, timestamps and review states are stored as operational metadata. Your workspace owner can view the imported data. It is not added to acquisition analytics, used for advertising, sold, or used to train general-purpose AI models. We do not share it with model providers. Hosting and encrypted backups use our existing infrastructure.
Imports are retained until you disconnect or request deletion. The sample workspace limit is 500 messages and 2,000 contacts; new imports stop at that limit. Disconnecting deletes that connection’s credentials and imported records from the live database. Encrypted backups expire on the backup schedule. If provider-side revocation is unavailable, remove ParseMill from the provider’s authorized applications as well. Staff access to message content requires your specific permission except where necessary for security or legal obligations.
ParseMill’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Accounting administration research
Benchmark permission is separate and optional. If you allow it, your submitted estimates may contribute to an aggregated benchmark. Estimates remain labeled self-reported model inputs, separate from directly timed measurements and verified pilot outcomes. Your firm and email will not be published. We review aggregated results before publication to prevent individual firms or people being identified.
The published intake benchmark uses synthetic fixtures only. Connected mailbox and accounting data are not used in that benchmark.
Email preferences
Marketing emails identify the sender and include a working opt-out method. Unsubscribing suppresses future outreach to that address, including queued follow-ups and later campaigns. A reply or objection is reviewed before any next touch.