Privacy Policy

This policy covers the website, benchmark estimator, outreach, fit calls, client portal and audit work.

Anchorfield Consulting Group is operated by SwiftMart, LLC, a New York limited liability company. In this policy, "Anchorfield", "we" and "us" mean SwiftMart, LLC. Anchorfield provides business-to-business audit and implementation services for home-services companies. This policy applies to information we collect through anchorfieldgroupconsulting.com, related marketing pages, booking flows, email communications, client access surfaces, and the Revenue Audit engagement.

If you sign a separate written agreement with us, that agreement may include additional confidentiality, data-handling, security, benchmarking or deletion terms. Where those written terms give you stronger protection for client data, those written terms control that engagement.

We collect contact details, business context, usage data and the files needed for the work.

We may collect information you provide directly, such as your name, work email, phone number, company name, role, service line, revenue band, region, call notes, messages, booking details, and information you choose to share during a fit call.

If you use the benchmark estimator, we collect the inputs needed to return ranges, such as service line, revenue band, region and operating figures. The estimator is designed without an email gate and without a company or contact field on the submission record.

If you become a client, we may collect dispatch exports, CRM records, job-costing data, invoices, accounting exports, QuickBooks or Xero exports, interviews, implementation notes, audit artifacts, model-call records, and related business files you or your team provide.

We do not ask for bank logins, dispatch-system credentials, accounting-system credentials or personal employee information unrelated to the audit.

We may also collect technical data such as pages viewed, device and browser type, approximate location from IP address, referral source, session identifiers, logs, errors and performance data.

If you allow it, your browser shares your device's location with the page. We use it on your device to find the nearest town we cover. Your coordinates never leave your device, and we don't store them. A cookie remembers the town, or that you said no, so we don't ask again.

We use the information to answer the audit question and operate the business around it.

We use information to operate the website, respond to inquiries, schedule calls, evaluate fit, deliver the Revenue Audit, reconcile operational and accounting records, produce findings and roadmaps, support implementation work, maintain client access, improve our benchmark model, secure the platform, debug errors, measure demand, and comply with legal obligations.

We may also use business contact information for business-to-business outreach, follow-up and relationship management. If you ask us not to contact you, we will use your information to honor that request.

Your company record and the benchmark pool are separate by design.

The benchmark pool is intended to hold segment-level aggregates: metrics for a trade, revenue band and region, with basis and sample size. It is not intended to hold company names, contacts, invoices, addresses, engagement records or a number that belongs to one operator.

If a delivered audit contributes to the benchmark pool, only de-identified aggregates may enter it, and only under the benchmark participation rules. A band that could only have come from one business is not a band. The benchmark participation page explains those rules in more detail.

We share information with service providers that help us operate the site, the platform and the audit.

We may share information with vendors that provide hosting, database, authentication, email, analytics, error monitoring, model processing, outbound workflow, data enrichment, email verification, security, professional services and other business operations.

The current platform design names providers including Supabase, Vercel, Render, Clerk, Resend, PostHog, Sentry, Anthropic, Google, OpenAI, Apollo, LinkedIn, Clay, MillionVerifiers and Instantly. Not every provider sees every category of data. For example, model providers are used for selected audit or workflow steps, and only the input needed for that step should be sent.

Two limits from our data page apply to that list. There is no analytics or session-recording tool running on the surfaces that hold client audit material, and model providers are the only third parties that audit material is sent to. Outreach, enrichment and verification vendors handle business contact information, not client audit files.

We may also disclose information if required by law, to protect rights or safety, in connection with a business transfer, or with your direction or consent. We do not sell client audit files or identified client financial records.

Some work may be assisted by language models, but findings remain our responsibility.

Parts of the audit or acquisition workflow may use language models to summarize, classify, draft, compare or help locate bottlenecks. A model does not own the finding and does not invent the numbers in an audit. We remain responsible for the work product we deliver.

The platform records model-call context and output so there is an audit trail of what was sent, which model responded and what came back. Those records sit inside the same tenant boundary as the related client work.

The exact retention and training terms of each model provider depend on the account plan and provider terms in force. Those terms should be confirmed before any stronger public claim is made about provider-side retention or training.

Client work is tenant-scoped, access-controlled and retained for the period needed to support the engagement.

Client data is stored in a Supabase Postgres database in the US East region, Northern Virginia. Access to client work is scoped by organisation and role. The system is designed so a client sees their own company and not another client, public visitors cannot reach audit artifacts, and recorded audit artifacts are append-only.

For audit data, the operational retention commitment is one year from the close of the engagement unless your written agreement says otherwise or you ask us to remove it sooner. De-identified benchmark aggregates may be kept after that because they are not intended to identify your business.

No internet service can be guaranteed perfectly secure. If we learn of a security incident affecting your information, we will evaluate it and notify affected parties as required by law and by our agreements.

You can ask for access, correction, deletion or a limit on use.

You may contact us to ask what information we hold about you or your company, correct it, delete it, opt out of business outreach, or limit how we use data in a particular engagement. Some requests may be limited by legal, security, accounting, dispute-resolution or contractual obligations.

For client audit files, we would rather receive less than more. If you are unsure whether a file contains information we do not need, ask us before sending it.

We will update this policy when the product or providers change.

We may update this Privacy Policy as our site, platform, vendors, legal obligations or services change. The updated date above tells you when the current version was posted. This version is published for review and may be revised as that review completes.

For privacy questions, data requests, or concerns about what to send, contact hello@anchorfieldgroupconsulting.com.