Last editorial revision: August 30, 2026.
This Privacy Policy explains the technical privacy approach of Tourism Skagway, an independent informational travel guide operated by The Travel Spark Company LLC. It is not legal advice and does not replace notices supplied by third-party services you choose to use.
Information this site may process
Ordinary web hosting can process basic request information such as IP address, browser and device data, requested URL, referring page, date and time, response status, and security signals. WordPress, hosting, caching, backup, and security systems may retain limited logs where necessary to deliver, protect, diagnose, or restore the site.
The theme itself does not create a user account, accept payment, store a booking, send a contact message, register a newsletter subscriber, or activate analytics. Contact and newsletter areas remain visibly inactive until the owner authorizes and configures a delivery service.
Cookies and local storage
The theme does not add a nonessential cookie. WordPress and active administrative, security, caching, or provider plugins may use cookies or similar storage for signed-in sessions, security, preferences, rate control, or provider functionality. Nonessential analytics, advertising, maps, chat, or embedded media should not be enabled without an appropriate owner review and, where required, consent controls.
Third-party travel surfaces
Tour and lodging regions may be supplied by TravelSpark and its connected travel providers. A provider surface can display its own images, product facts, ratings, reviews, prices, availability, tracking parameters, and external links. Opening or using an external provider page is subject to that provider’s privacy notice and technical practices. Tourism Skagway does not control a third-party website merely because it is linked or visually integrated.
Contact and newsletter status
No theme-handled contact submission or newsletter subscription is active in this release. A disabled field is a visual status indicator only and does not transmit or retain an address. If the owner later configures Brevo, another mail service, spam protection, or an inbox workflow, this policy and the interface should be updated before public collection begins.
Media, embeds, and external requests
Local theme photographs and identity files are served from this WordPress installation. The theme does not intentionally load a remote map, social feed, video, analytics script, font, or advertising tag. Active plugins and provider results may create additional requests. Those requests should be inventoried during acceptance and documented when they are essential.
Security and abuse prevention
Technical controls can include access restrictions, capability checks, secure transport, caching, backups, malware or firewall tools, rate controls, and logging. No website or storage system can promise absolute security. Do not send sensitive personal, financial, health, identity, or booking information through an inactive or unverified channel.
Retention
Retention depends on the data and the system that processes it. Hosting and security logs may be retained for operational or security needs; backup copies may persist through a documented rotation; provider systems apply their own schedules. The theme does not set or claim a universal retention period for services it does not control.
Choices and requests
Browser settings can limit cookies or other storage, although doing so may affect signed-in or provider functions. Requests concerning information controlled by this site should use an owner-authorized contact channel once published. Requests concerning a travel, payment, booking, social, or other third-party service should be directed to that service.
Children
This site provides general travel information and does not intentionally collect personal information from children through the theme. Family travel content is not an invitation for a child to submit personal data.
Changes to this policy
This policy may change when the site’s services, legal obligations, or technical stack change. A revised policy should identify its revision date and accurately reflect the services that are actually configured.