- Home
- Privacy
Project policy / P01
Nothing to submit, nothing to profile
Copperline Harbor is a static reading experience without accounts, forms, analytics, advertising or a consent banner.
Version: August 2026
Information you provide
The site has no registration, account, checkout, comment field, newsletter signup, booking widget or contact form. It does not provide a way to submit your name, email address, payment information, reservation number or message. No project contact was supplied, so an address or email has not been invented.
Cookies, storage and analytics
Copperline Harbor does not set first-party cookies, use local storage, run audience analytics, load advertising pixels, perform session replay or fingerprint visitors. No consent banner is shown because no optional tracking service is present. The local JavaScript file only controls navigation, small reveal effects and the displayed calendar year.
Hosting logs
The hosting provider may process ordinary technical request information required to deliver and secure the site, such as IP address, requested path, timestamp, response status and browser user agent. Copperline Harbor does not combine these requests with an analytics profile. Retention and security depend on the hosting arrangement selected by the site owner.
External links
Links to the National Park Service, City Experiences, Wikimedia Commons and Creative Commons leave this site. Those services apply their own privacy notices and may use cookies or collect information under their own terms. Copperline Harbor does not control them and adds no affiliate identifier.
Local files and remote services
Styles, scripts, the favicon and photographs are served as local files. Pages do not embed maps, video, social feeds, remote fonts, payment tools or ticket inventory. An external request occurs only after a reader follows a third-party link.
Children’s information
The site is a general educational guide and does not knowingly collect information from children or adults. If a future version adds a submission, analytics or embedded feature, this notice should be revised before publication.
Changes
The version label should change when the implementation or notice changes. This text describes the current site rather than claiming that every possible future deployment will remain identical.