Privacy policy — LedgerCopy

Last updated 11 August 2026

1. Who is responsible, and what this policy covers

The controller of the records described here is LedgerCopy, 30 North Gould Street, Sheridan, Wyoming 82801, United States. Write to mail at ledgercopy.com about anything on this page.

This policy covers the ledgercopy.com website and the trial request form on it. The form is the only place this site collects anything, and the sections below describe it field by field.

Ledger data copied under a trial or a subscription is a separate matter and is not governed by this page. What a run reads, where the copy is held, and how access is revoked at the source platform are set in the agreement for that engagement and summarised on data handling and run operations.

2. What the website collects

Submitting the trial form writes one record. The fields below are all of it: what you enter, what your browser sends with the submission, and what the record carries so it can be filed and worked through. There are no others.

Email address: The work email you type. It is stored in lower case, and it is the only field the form requires.
Source platform: The optional radio you select: QuickBooks Online, Xero, or Not sure yet. Select nothing and nothing is stored for this field.
Form source label: A fixed label naming which form on the site you submitted. The form at the foot of this page submits privacy-trial-form.
Referring URL: The Referer header your browser sent with the submission, if it sent one.
Campaign parameters: gclid, utm_source, utm_medium, utm_campaign, utm_term and utm_content, when they are present in the link you arrived from.
User-agent string: The browser and operating system string your browser sends with every request it makes to any site.
Record fields: A fixed intent of Trial request, the dates the record was created and last updated, a count of how many times the address has been submitted, and a status we set while handling the request, taken from a fixed list.

Two more fields are submitted and are never stored. One is a hidden field that a person leaves empty and an automated submission usually fills in. The other is the time at which the form loaded in your browser. Both are checked to reject automated submissions, then discarded.

Cloudflare, which serves this site, receives your IP address on every request, as any web host does. LedgerCopy does not write it into the record.

This list mirrors the code that handles the form. If the form changes, this list changes in the same release.

3. What the website does not collect

No cookies.This site sets none.
Cookieless aggregate analytics.Fathom Analytics counts page visits without analytics cookies, session recording, or advertising profiles.
No advertising or tracking pixels.Nothing on this site reports your visit to an advertising network.
No session recording.Your scrolling, clicks, and keystrokes are not recorded or replayed.
No remote fonts or images.Those assets are served from ledgercopy.com; the Fathom analytics script is loaded from Fathom.

You can check each of these yourself. Open your browser's network and storage panels on this page and compare what you see against the list above. That is why the list is worth stating rather than summarising.

4. Why it is collected

The email address exists so we can reply to your trial request and run the scoping conversation: your source platform, the ledger objects that matter to you, the cadence you need, and the review or continuity workflow the copy has to fit.

The source platform, referring URL, campaign parameters, and user-agent string tell us which route a request arrived by and which platform to prepare for. They are context for the reply, not a profile, and they are not matched against any other data set.

Your address is not added to a mailing list. It is not sold. It is not shared for advertising. We send you nothing you did not ask for.

5. Where it is stored

The record is written to a Cloudflare D1 database. The site itself runs on Cloudflare Workers. Cloudflare is the processor for both: it operates the infrastructure the record sits on and the network the request travels over.

The database is not reachable from the public internet. It is bound to the LedgerCopy Worker and to the people who operate LedgerCopy.

LedgerCopy makes no claim about which region your record is stored in. If a storage region matters to you, raise it during scoping and we will tell you what is and is not settled.

6. How long it is kept, and how to remove it

Two retention periods apply to this website, and one deadline applies to removal. Each is a stated period, not an intention.

Trial request records: Kept for 24 months from the last contact with you, then deleted. Each reply or new submission restarts that period; silence runs it down.
Email correspondence: Messages to and from the LedgerCopy address are kept for 24 months, then deleted.
Deletion on request: Actioned within 30 days of a verified request. Email mail at ledgercopy.com from the address you submitted and ask for the record to be removed. The record is deleted, and the confirmation goes back to the same address.

Copied ledger data is not website data and is not covered by the periods above. It is the product, not a record of your enquiry, and its retention is agreed per engagement during scoping and recorded in writing. No period for it is published here, because no single period fits every copy scope. The mechanism is set out under retention and deletion.

7. Access, correction, and deletion

Three requests, one route. Email mail at ledgercopy.com from the address you submitted and say which you want. Each is actioned within 30 days of the request being verified.

AccessWe send you the contents of the record.
CorrectionWe change a field that is wrong.
DeletionWe delete the record.

Sending from the submitted address is how we check that the request is yours. If you cannot send from it, say so in the message and we will agree another way to confirm it before acting.

This section describes what LedgerCopy does. It is not a statement about which statutory framework applies to you, and it is not a claim of compliance with any of them.

8. Changes to this policy

Changes are published on this page and the date at the top changes with them. Earlier versions are not archived here. A change to what the form collects, or to why it is collected, is made on this page in the same release as the change to the form.

Questions about this policy go to mail at ledgercopy.com.

LedgerCopy trial

Request a trial and scope the copy.

A trial conversation establishes four things: the source platform you use, the ledger objects that matter to you, the cadence you need, and the review or continuity workflow the copy has to fit.

What to have ready

Which organisation or company file the copy would cover.
Who can authorise a read-only connection at the source platform.
Which object groups you check at close.