Policies
Privacy and Website Data
This is the privacy description for the fictional information-only website in this package. It describes what these supplied pages do, and deliberately separates that from any future hosting or chatbot service. No external analytics, advertising scripts or booking integrations are included. If an operator uploads the pages or attaches a chatbot, the operator must accurately document that service's actual practices. A website scraper must not turn this static site's limited behaviour into claims about an unrelated chatbot's retention or training settings.
Visitor information
- Data collection
- The supplied pages contain no enquiry forms, accounts, payment fields or file-upload controls. They do not collect booking details themselves. Hosting-provider logs, if any, are controlled by the chosen host and are not specified here.
- Cookies and tracking
- The supplied website sets no cookies and contains no analytics, advertising pixels, local-storage code or third-party embedded content. A hosting platform may add its own behaviour, which requires separate verification.
- Chatbot data
- No. No chatbot is bundled with this website. Conversation retention, model-training use, processor identities and access permissions for any attached chatbot are unspecified and must be obtained from that chatbot's operator.
- Retention
- No chatbot retention period is published because no chatbot is included. Do not substitute a guessed number of days or the phrase "as long as necessary" as if it were a confirmed chatbot-specific policy.
- Sensitive details
- No payment-card numbers, security codes, passwords or medical records should be submitted through an attached general enquiry chat. This demonstration site has no secure payment or clinical intake workflow.
- Privacy contact
- The demonstration privacy address is privacy@alderwick.example. It is a reserved, non-operational address used for testing and cannot action a real access or deletion request.
- Deletion capability
- No. These static pages have no chat database or deletion function. Any request to erase information held by a separately connected service must be handled by that service's actual operator; an answer must not falsely confirm deletion.