Privacy Policy

1. Information we collect

We only collect what's needed to respond to you and, if you book, to actually show up:

• Booking/contact details — first and last name, email, phone number, and (for in-person visits) street address, city, and postal code, entered into the booking form. These are stored in our CRM (provided by our site platform, systeme.io) so we can confirm and manage the appointment.
• Chat messages — anything you type into the site's chat assistant, to understand what you need and quote or route you correctly.
• Address autocomplete input — as you type a street address into the in-person booking form, what you've typed is sent to a mapping service (Geoapify) to suggest real matching addresses. Only the address itself is sent — no other form fields.

We don't collect payment card details directly — see Booking & payments below.

2. The chat assistant

The chat on this site is answered by an AI assistant, not a live person watching in real time. Your messages are sent to a small backend service we run (on Cloudflare), which forwards the conversation to Anthropic's Claude API to generate a reply, along with a short set of real business facts (services, hours, pricing) so it can answer accurately. Anthropic processes that request to generate the reply and does not use it to advertise to you.

Chat conversations aren't linked to a persistent visitor profile — each conversation exists only for that browsing session.

3. Cookies

This site uses a small number of cookies, all for making the site work — none for advertising or tracking you across other sites:

• Cookie preference (ac_cookie_consent) — remembers that you've seen and responded to the cookie notice, for 180 days.
• Platform/session cookies — set by our site platform (systeme.io) to keep the page and booking forms functioning correctly.

You can clear cookies at any time through your browser's settings — the cookie notice will simply reappear on your next visit.

4. Remote support sessions

If you and your technician agree to an online remote-support session, a temporary, one-time session is created through a dedicated remote-access service (dwService.net) so the technician can view and control your device with your permission — only for the duration of that session, only when you've explicitly started it, and never automatically.

5. Booking & payments

Appointment scheduling is handled through our site platform's built-in booking calendar. Where an appointment requires payment, that payment is processed directly by our site platform's own payment handling — we don't receive or store your full card number ourselves.

6. Who we share information with

We work with a small number of service providers to run this site and business. Each only receives what it needs to do its job:

• systeme.io — website hosting, contact/CRM storage, appointment booking and payment processing.
• Cloudflare — runs the small backend service that relays chat messages.
• Anthropic — generates chat replies from the conversation you have with the assistant.
• Geoapify — suggests real address matches as you type one into the booking form.
• dwService.net — only if you start a remote-support session, as described above.

We don't sell personal information, and we don't share it with anyone for their own marketing purposes.

7. How long we keep it

Booking/contact details are kept in our CRM for as long as needed to serve you and maintain reasonable business records, and can be deleted on request (see below). Chat conversations aren't stored beyond generating the reply in real time, aside from standard, short-lived infrastructure logs used only for keeping the service running reliably.

8. Your choices & rights

You can ask, at any time, to:

• See what contact information we have on file for you
• Correct anything that's wrong
• Have your information deleted from our CRM

Just reach out through the chat on the site, or by email, and we'll take care of it directly — there's no automated self-service portal, because this is a one-person business, not a call center.

9. Changes to this policy

If this policy changes in a meaningful way, we'll update the effective date at the top of this page. Since this is a small, actively-maintained site, check back here if you'd like the current version.