DryHome Ventilation — Website and Business Engine Terms
Effective date: 28 September 2026.
1. About these terms
These terms cover use of the DryHome Ventilation website and the private DryHome Business Engine, including authorized Google integrations and the DryHome Jeffrey assistant. The website provides ventilation information, a suitability checker and enquiry/contact facilities. The Business Engine supports DryHome’s internal customer, booking, installation, receipt and reporting work.
DryHome Ventilation is operated as a sole-trader business. Contact info@dryhomeventilation.co.uk for questions about these terms.
2. Enquiries, suitability and installation agreements
The website’s suitability output uses the answers supplied and supports an initial assessment; it is not a completed site survey or a guarantee that a particular installation is suitable. Submit accurate information and tell DryHome about relevant corrections. A successful form submission records an enquiry; the website does not provide an online checkout that itself completes an installation purchase.
Installation scope, price and contractual terms are agreed separately. These website terms do not replace your installation agreement or statutory rights. They do not impose additional fees, cancellation charges or warranty exclusions.
Nothing in these website terms is intended to remove mandatory consumer rights. Customer-specific quotations, agreed work and applicable legal rights must be considered separately from the internal app’s recorded status.
3. Appropriate use and private access
Use the website lawfully, provide information you are entitled to provide and do not attempt unauthorized access, impersonation, interference or access to another person’s private records. Access to the Business Engine and Jeffrey is restricted to authorized users. Keep account access secure and report suspected misuse to DryHome. Do not submit unnecessary sensitive information through enquiry forms or operational notes.
4. Google connections and diary synchronization
An authorized account owner decides whether to connect Google services and grants the permissions shown by Google. Public website enquiries do not require this connection. The Calendar integration uses event permissions for the configured diary; other Google business-reporting connections have separate authorizations.
The CRM is the booking source of truth. When enabled, Calendar sync creates or updates linked diary events from CRM records and handles cancellations under the implemented workflow. Users should correct bookings in the Business Engine; a manual Google diary change is not a supported replacement for updating the CRM. Linked identifiers reduce duplicates, but an unrelated manually created event may require reconciliation. A connected status alone does not mean that sync is enabled or that every booking has synchronized successfully.
The owner must review the destination calendar and its sharing permissions. Revoking Google access or disabling sync can stop future synchronization without deleting existing diary entries or CRM records. Google’s service availability and account permissions can affect synchronization.
Approval of these terms does not itself activate Calendar sync, authorize historical backfill or create test events.
5. Jeffrey and business reports
DryHome Jeffrey retrieves information and performs permitted actions through controlled Business Engine tools. Users must review the exact record and proposed action before approving changes. Assistant text is not proof of a completed write; persisted records and audit history provide the operational evidence. Do not use the assistant to send customer communications without a deliberate authorized sharing action.
Reports reflect recorded information, dates, classifications and import coverage. Missing historical values are not necessarily zero. Recorded job revenue, cash received and gross profit describe different measures; gross profit is not a representation of net business profit. These reports do not replace professional accounting advice or source-record review.
6. Receipts, sharing and review requests
Receipt PDFs use recorded customer/job/payment details and should be checked before issue. Issued copies are archived; corrections preserve the earlier document and issue a replacement under the implemented workflow. A generated receipt or a recorded payment status is not, by itself, independent evidence that funds cleared.
The owner chooses whether and how to share a receipt through an available service or device. The optional review request is separate from the receipt. A prepared sharing link is not proof of delivery, and a recorded request is not proof that a review was received. Users should confirm sharing in the Business Engine only after it actually occurred.
7. Privacy and third-party services
The Privacy Policy explains the processing associated with the website, Business Engine, Google connections and Jeffrey. It is available at our Privacy Policy. Google, Hostinger, Auth0, OpenAI and chosen communication services provide parts of the operational environment and have their own applicable terms. DryHome must still meet its own obligations; reference to a supplier does not transfer all responsibility to the customer.
These terms do not grant new Google permissions or consent to unrelated processing.
8. Availability, responsibility and disputes
The website and integrations can be interrupted or unavailable. The system includes error/retry controls, but it does not establish a contractual uptime guarantee or support response period.
Nothing in these terms excludes liability that cannot lawfully be excluded or limits mandatory consumer rights. No additional liability cap or contractual service-level guarantee is imposed by these website terms.
These website terms do not impose an exclusive jurisdiction or override applicable legal rights and remedies.
Questions about these terms can be directed to info@dryhomeventilation.co.uk. Changes will be dated when published. Material contract changes must not be treated as accepted merely because a webpage was silently updated.