Prototype scope and data practices

This site is presented as a static editorial prototype. By default it does not perform behavioural advertising or active analytics. If cookies or analytics are introduced later, the site will describe their function and provide opt-out information. The prototype’s contact forms are non-transmitting examples; any functional contact mechanism will be accompanied by a clear explanation of data practices before it collects personal information.

A View In, Lower Antelope Canyon.jpg
A View In, Lower Antelope Canyon.jpg · Tatiana12 · CC BY 2.0

Cookies and local storage

As a static prototype, the site does not set third‑party tracking cookies by default. If cookies are introduced in a later iteration, they will be used sparingly to support essential functionality—such as preserving a user’s language preference—and their presence will be disclosed. Visitors should manage cookies through their browser settings and consult the site’s notices for any future changes.

20030820-antelope-canyon.jpg
20030820-antelope-canyon.jpg · Gerd Müller (talk · contribs), www.twam.info · CC BY-SA 3.0

Analytics and third‑party services

There is no active analytics tracking on this prototype by default. If an analytics service is enabled in future, the site will identify the provider and describe the data collected, the retention policy and how to opt out where feasible. Third‑party services that require data transmission will be disclosed at the point the service is introduced.

1993 lake powell (cropped).jpg
1993 lake powell (cropped).jpg · R-E-AL (talk | contribs | Gallery)  (German Wikipedia) · CC BY-SA 3.0

Contact-form prototype and email handling

The contact form visible on the prototype does not transmit data. Email correspondence to the site’s editorial address ([email protected]) is handled by the editorial team. Emails are used to respond to enquiries, process correction requests and manage rights or attribution queries. Editorial email handling minimises retained personal information: messages are used to address the enquiry and stored only as necessary to complete that task, subject to the retention principles described below.

Horseshoe Bend overlook at Seedskadee National Wildlife Refuge (49960930493).jpg
Horseshoe Bend overlook at Seedskadee National Wildlife Refuge (49960930493).jpg · USFWS Mountain Prairie · Public domain

Newsletter and mailing lists

The prototype may describe a conceptual newsletter but does not collect subscription information on this site. If a mailing list is activated in the future, the site will clearly explain the sign-up mechanism, the data retained, unsubscribe procedures and whether third parties are involved in distribution. Any such service will be governed by the privacy principles described here.

Glen Canyon Conservancy-- Page, Arizona (53197835269).png
Glen Canyon Conservancy-- Page, Arizona (53197835269).png · BLMUtah · Public domain

Data retention and minimisation

The site’s guiding principle is minimisation: collect the least information necessary to respond to enquiries and retain it only as long as required. For email correspondence, the editorial team retains messages long enough to address the inquiry and to maintain a record of substantive corrections or rights agreements. If a service requiring longer retention is introduced, the retention period will be disclosed along with user control options where feasible.

- panoramio (1751).jpg
- panoramio (1751).jpg · thewayofthings.org · CC BY-SA 3.0

Access, correction and deletion requests

Users may request access to personal information held by the editorial team, request corrections, or ask for deletion of personal data submitted in correspondence. Send such requests to [email protected] with clear identification of the data and the requested action. The editorial team will respond in a reasonable time and will explain any practical limits to fulfilling requests, especially where data retention is necessary for legal or operational reasons.

06082013 - Antelope Canyon (9638595084).jpg
06082013 - Antelope Canyon (9638595084).jpg · WiLPrZ from Rabat, Maroc · CC BY-SA 2.0

GDPR and U.S. privacy considerations

For readers in the European Economic Area, this site recognises GDPR‑aligned requests for access, rectification and erasure. Submit GDPR-related requests to the editorial email with the relevant details. For U.S.-based readers, privacy rights may vary by state; the editorial team will make reasonable efforts to respond to local access and deletion requests consistent with applicable law. The site does not claim certification under any privacy standard and does not offer guaranteed legal compliance; it seeks to operate transparently and to address individual requests in good faith.

A337, Lower Antelope Canyon, Page, Arizona, USA, 2011.JPG
A337, Lower Antelope Canyon, Page, Arizona, USA, 2011.JPG · Brian W. Schaller · FAL

Security and practical limits

The editorial operation implements common-sense measures to protect stored email and contact information. However, no online system is immune to risk. The site does not guarantee absolute security or legal compliance; instead it aims to limit collection, be transparent about practices and to respond promptly to concerns. Users should avoid sending sensitive personal data through insecure email and should use official channels for any exchange that requires high security.

A View In, Lower Antelope Canyon.jpg
A View In, Lower Antelope Canyon.jpg · Tatiana12 · CC BY 2.0

Changes to this policy

Any material changes to privacy practices will be recorded on this page. Substantive changes that affect data collection or sharing will be signalled in the site’s editorial notices. If the site evolves from prototype to a functional service that collects personal information, clear consent mechanisms and opt-out processes will be implemented and described at that time.

20030820-antelope-canyon.jpg
20030820-antelope-canyon.jpg · Gerd Müller (talk · contribs), www.twam.info · CC BY-SA 3.0