INSPECTION REQUESTS
Request privacy notice.
A practical explanation of the information used to manage your inspection request. Sending a request is not a marketing signup or an appointment confirmation.
What you provide
The request form requires your full name, phone and email. Property city or address, service interest and notes are optional. You can leave the optional fields blank or select “Not sure yet” for the service.
Please include only information useful for the inspection conversation. Do not send payment card details, passwords or sensitive health information through the form.
How your request is used
Kerwin uses your contact details and any optional information to respond to your inquiry, discuss the inspection scope and quote, and arrange scheduling separately. The form does not add you to a marketing list and does not automatically send you a confirmation email.
When the server confirms receipt, the request is stored as a lead record with a reference and submission time. The private owner inbox supports follow-up statuses and internal notes. A status such as “scheduled” is an internal tracking label, not an automatic booking or a notice sent to you.
Server records and owner access
Request records are stored in the website’s server-side database on Manus-managed infrastructure. The owner inbox and CSV export require separate sign-in and server authorization. Knowing the inbox URL does not grant access to request records.
Authorized owner access can include downloading a private CSV of lead records for operational follow-up. Your request details are not included in the public page HTML.
Operational owner alerts
After a request is saved, the website uses Manus’s native notification service to alert the project owner, with a request reference and a compact contact and service summary. The owner’s Manus notification preferences control email and in-app channels.
Service acceptance does not establish that an email or in-app alert arrived or was read. A notification failure does not erase the saved request; its state is tracked for owner review and retry. These operational alerts are not messages sent to the visitor.
Browser handling and duplicate prevention
The form scripts do not place your contact details, property information or notes in page URLs, browser local storage or browser session storage. They do not send form values to conversion analytics.
An anonymous request identifier may be kept in session storage so a retry can be recognized without saving the form’s personal information there. A hidden spam-prevention field and server request limits help protect the intake. The private inbox uses an authenticated session to authorize its API requests.
If a network problem prevents confirmation, the page will explain that receipt could not be verified and ask you to retry. Only a successful server response confirms that your request was saved.
Questions about your information?
Contact Kerwin to ask about a request record, request a correction or discuss an access or deletion request. Include your private reference if you have it; please do not send unnecessary personal information.