Privacy

What is the site’s privacy approach?

The site sets no cookies, has no forms or accounts, and uses anonymous cookieless statistics. Page views are counted without cookies or personal identifiers. Hosting logs are kept by the hosting provider.

These statements describe the guide's own setup. They should not be read as a description of every external site linked from a page or of the email services involved when someone sends a message. Keep those separate when deciding what information to share.

You can read the guide without creating a site account or submitting information through a site form. There is no account profile to complete as part of using these pages. The contact method is email, and a message may contain whatever personal information the sender chooses to include.

What do anonymous cookieless statistics mean here?

Here, anonymous cookieless statistics mean that page views are counted without cookies or personal identifiers. This describes the counting approach rather than a personal reader history or an account-based activity record.

Do not interpret that statement as a promise about every technical record involved in delivering a web page. The hosting provider keeps hosting logs, which are separate from the anonymous page-view count. This notice does not state a retention period or list particular hosting-log fields that have not been supplied for the guide.

In plain English: the guide counts views without attaching a personal identifier to the count. That statement is about the statistics described here. It does not describe a message you send by email, a linked site's own practices, or every record the host provider may maintain.

Does the guide have forms or accounts?

No, the site has no forms or accounts. Reading a town page, landmark page, or owner guide does not require creating a profile in this site.

The contact page provides an email address instead of a form. If someone asks you to supply an account password or booking payment in order to read the guide, that request does not match the service described here. Check the actual destination before sending information.

• Read the page without completing a site profile.
• Use the published email only when an editorial message is needed.
• Do not send booking payment information to the guide.
• Keep property access instructions out of correction requests.

The guide sells nothing and takes no bookings. A request about an existing reservation should go to the party responsible for that reservation, rather than being added to an editorial email.

What happens when a reader sends an email?

An email to the guide contains the information the sender includes, so write only what is needed for the editorial question. Contact the guide at info@1000friends-ct.org for a privacy question related to this notice or for the editorial subjects described on the contact page.

For a correction, a page name, a short passage, and an official source link can explain the issue without guest identities or financial details. If the concern involves a property, describe the editorial error rather than sending a complete booking file. The editor does not need entry codes to understand a broken source link.

Before forwarding a message, read the quoted thread and any attachments. Remove details unrelated to the issue you want to raise. This is suggested care for a sender, not a claim that an email service strips information or that the guide can control the sender's mail system.

How should private information be kept out of a correction?

Use the public statement and the official source to explain the correction whenever that is enough. Avoid including a person's booking history, medical situation, payment record, or access details merely to make the report feel complete.

Consider an unnamed owner who notices a rule summary needs review. The owner can identify the town page, quote the disputed sentence, and provide the current official provision. The report can be useful without a guest's name or the owner's private correspondence with a service provider.

• Check the visible text of the message before sending it.
• Review attachments for unrelated personal details.
• Describe a practical issue without identifying a guest when identity is unnecessary.
• Ask how to explain the issue if a private document seems essential.

This example illustrates a restrained correction request. It does not describe a submission process beyond email or promise a particular response time.

What should readers know about external links?

An external link leads to a separate destination whose privacy practices are outside this notice. Check the destination before entering information there, particularly if the page asks for contact, account, or payment details.

Official source links help a reader inspect the evidence for a local fact. A link does not make the source site part of this guide. The same separation applies when a reader follows a management service link provided on a relevant page.

Think of the distinction as a notice in a guest room pointing to another venue. The notice can identify where to find more information, while the destination is responsible for its own arrangements. Here, the privacy statement concerns the guide's own cookies, accounts, forms, statistics, and contact method. It does not make a privacy promise on another operator's behalf.

What can be asked about this privacy notice?

Ask about a statement in this notice that is unclear or appears inconsistent with the guide. Use info@1000friends-ct.org and identify the page and behavior you are asking about without including unnecessary personal information.

If the concern is about another destination, check that destination's own contact information. The guide cannot provide an account response for a service it does not operate. If the concern is about a booking, contact the party handling the booking rather than treating the guide as a reservation service.

The contact page explains the editorial contact subjects. The terms page explains the information-only purpose of the guide, and the about page describes its scope. Read those statements together while keeping each question specific to the service or page actually involved.

Questions