Know what runs in your browser, what leaves it, and what SHVL keeps.

The paid pack is generated after checkout from the CSV you provide.

SHVL does one practical job: aged-debtors CSV in, reviewable chase-pack ZIP out. The ZIP contains editable Word letters, openable email drafts, an Excel statutory-interest log, and a README.

• You preview the CSV count and totals before paying.
• Paid chase-pack checkout is handled by Stripe before generation.
• SHVL uses the checkout session status to confirm payment before processing the uploaded CSV.
• Nothing is sent to debtors automatically. You download the files, review them, and decide what to send.

ChatGPT can use a supplied CSV or your signed-in SHVL workspace.

When you connect SHVL in ChatGPT and ask it to analyse an aged-debtors CSV, ChatGPT sends the CSV text, sender name and the Bank Rate you supply to SHVL's MCP endpoint. SHVL processes that request in memory to return draft wording and indicative UK B2B statutory-interest calculations.

After SHVL sign-in, protected read-only tools can instead answer questions from the latest CSV import or completed accounting sync already stored in that SHVL workspace. Results can include customer names, invoice references, balances, aggregate invoice and receivables-payment totals, case and readiness state, and limited reminder evidence. The receivables view does not include bank balance, expenses, cash out, profit or runway. Results exclude email addresses, message content, provider IDs and individual payment records. Requests are scoped to the signed-in workspace. These tools do not call an accounting provider live, write to it, queue a reminder or send a message.

• SHVL does not store the submitted CSV in its database or use it to train a general model.
• The tool result repeats the debtor name, invoice number, due date and outstanding amount from the supplied CSV. It adds days overdue, statutory interest, fixed compensation, total claim, a subject line and a draft body. It does not return debtor email addresses.
• The endpoint does not send messages, create a workspace or start a payment.
• You must review every draft, check payment and dispute status, and confirm the applicable Bank Rate before sending anything.

Your workspace keeps the records needed to track each chase.

A signed-in credit-control workspace stores customers, invoices, payments, chase status, notes, reminder schedules, connected-account identifiers and relevant communication history in SHVL's Cloudflare service. OAuth tokens are encrypted at rest. Xero, QuickBooks or FreeAgent and your mailbox remain the source of truth.

• Xero, QuickBooks or FreeAgent access is used to sync overdue invoices and payments. Microsoft 365, Outlook.com or Hotmail access is used to send reminders and approved invoice-blocker requests, and record matched replies or delivery failures. Gmail uses send-only access. SHVL cannot read Gmail Inbox messages, replies or delivery failures.
• An explicitly approved blocker request may send one selected clean, reviewed document through the connected mailbox. The member confirms that it belongs to the customer. SHVL retains the message, invoice links, document reference, approval and follow-up date. Provider acceptance is not confirmation of inbox delivery. Draft downloads do not send anything or establish delivery.
• Disconnecting a provider removes SHVL's stored connection and token, pauses reminders, and keeps previously synced records and communication history for review.
• Workspace owners can permanently delete the workspace from Data controls. SHVL cancels an active subscription before deleting the workspace and its local credit-control records.
• Stripe may retain payment records under its own legal obligations. You can also revoke SHVL from the connected provider's account settings.

We track product signals, not the body of your work.

Public marketing pages load js/analytics.js for selected SHVL funnel events and a small Ahrefs Web Analytics tag for page-level measurement. Together they cover page views plus selected conversion events such as checkout clicks, sample downloads, demo views, and CSV preview actions.

• The current public-site analytics posture is product telemetry, with no retargeting ad-pixel stack.
• Analytics events describe funnel actions. They do not include the contents of your aged-debtors CSV.
• Signed-in product events may include the page path and account id, but not uploaded CSV or PDF contents. Free tools do not require an account.
• Theme preference is stored in local browser storage.
• Paid checkout status is used before chase-pack generation starts.

The practical boundary.

This page is a plain-English guide to the current product boundary. Privacy, terms, and any supplier review should handle formal checks.

• Signed-in free tools marked browser-side keep the chosen file on the page.
• Paid chase-pack generation processes the uploaded CSV after checkout so the ZIP can be created.
• The one-off chase pack creates reviewable files and does not post letters, send emails or call debtors. The signed-in recurring workspace can connect to Xero, QuickBooks or FreeAgent and a mailbox when you choose.