Privacy
Privacy practices
How the static site and record-prep workflow keep information narrow and practical.
Minimal website data
The public website uses local fonts, local images, static pages, a map surface on the message page, and a local notice acknowledgement. It does not load advertising trackers, heat-map scripts, social profiling pixels, or behavioural analytics suites.
Ordinary hosting logs may exist at the hosting layer. They are not used by the consultancy to score visitors or build advertising audiences.
Message form handling
The form opens a draft in the visitor’s own application. The static site does not store form entries in a database. The first note should describe the record problem broadly: year, source type, rough volume, and whether files are paper or digital.
Visitors should avoid attaching sensitive source files, credentials, full identity documents, or unnecessary account details in the first note. Safer handoff details can be confirmed after the scope is understood.
Record materials
A consultancy packet may involve payer forms, receipts, platform exports, mileage notes, owner annotations, calendars, invoices, and envelopes. Those materials are used to build an evidence map, question ledger, exhibit labels, and handoff note.
The use of those materials is limited to the agreed source-record scope. Materials unrelated to that scope should be removed, marked out of scope, or returned when identified.
Access and retention
Access to packet materials is limited to the practical work needed to inventory, sort, label, compare, and prepare the handoff. Copies should not be kept longer than needed for ordinary follow-up, scope confirmation, or correction of organization errors.
If the owner asks about an incorrect label or misplaced source group, the consultancy may need to review the relevant packet portion. That review is about organization accuracy, not tax judgement.
Security habits
Static pages reduce many tracking surfaces, but a visitor’s own device, browser, network, and storage choices still matter. Visitors should keep originals under their control and avoid sending more information than the first review requires.
The consultancy encourages cautious sequencing: broad description first, confirmed handoff method second, source files only when needed for the record-prep scope.
Corrections
A visitor may ask that unnecessary materials be disregarded for the packet when they were sent by mistake. The consultancy may still preserve a limited note that a correction request was made or that a scope was revised.
If a visible website value is wrong, such as address formatting or service language, the public page can be updated separately from any professional decision made outside this work.
No sale of visitor data
The consultancy does not sell visitor information and does not use page views to build advertising profiles. Packet materials are source records for an organization workflow, not marketing assets.
Any service providers involved in ordinary hosting, mapping, or application handling may process data under their own systems. The public site remains narrow to reduce those surfaces.
Packet notes and owner explanations
Owner explanations may be written into a packet note when they clarify what a source record appears to be. The note should identify the source group and the owner’s explanation without turning that explanation into a professional conclusion.
If an owner explanation includes unnecessary sensitive details, the consultancy may summarize only the part needed for record organization. The goal is to make the source trail understandable, not to collect every private fact surrounding the record.
Third-party services
The public site uses a map surface on the message page. The map provider may receive ordinary map-related request data under its own terms and settings. Visitors who prefer not to load the map can rely on the written address shown on that page.
The consultancy does not add advertising pixels or behavioural analytics to compensate for that narrow map use. The public site remains static and local-first so most pages load without third-party tracking surfaces.
Practical safeguards
The strongest privacy habit is minimization. The owner should gather only the records needed for the current scope, keep unrelated files out of the packet, and avoid sending credentials or full identity documents unless a qualified professional separately requires them.
The consultancy supports that habit by separating unknown items from finished records and by keeping the first website message broad. More detailed source handling belongs in the confirmed record-prep workflow, not in casual website browsing.
Record sensitivity
Freelancer records can contain more than accounting details.
Receipts, invoices, travel notes, platform exports, calendars, and bank files can reveal clients, locations, work patterns, account names, and business relationships. The privacy policy treats that context as sensitive even when a record looks ordinary. Visitors should avoid sending original documents through public channels unless they have reviewed what the document contains.
The site itself is written to keep intake minimal. Public pages explain record organization and policy terms. They do not require uploads, portal access, account creation, or public comments.
Retention awareness
Records should be kept under the owner’s control until a specific workflow is agreed.
When a visitor later chooses to share materials, the appropriate handling method should be clear before files are exchanged. That includes the type of files, the purpose of review, the expected output, and how copies will be handled. This policy page does not replace that later agreement.
Because the raw public site is designed for broad visitors, it avoids collecting unnecessary details. The only persistent browser feature is the local notice acknowledgement described in the cookie policy.