Website information · Updated 2 November 2026
Privacy policy
How browsing, local enquiry drafts and separately sent correspondence are handled.
1. Publisher and point of contact
The map and wayfinding portfolio is maintained under the name Trent Lynn Bowman; the responsible individual is TRENT LYNN BOWMAN. The supplied address used to identify the professional is 255 Valley Loop, Heber Springs, AR 72543-8826, United States. To discuss information associated with these pages, use [email protected]. This notice covers browsing and the local enquiry tool. It does not describe a navigation application, visitor tracking service or geographic account system. A map shown as a concept is visual content, and does not collect a user’s live location or follow a journey.
2. An introduction needs only limited information
The enquiry interface contains fields for your name, reply email, project or company, selected interest and message. The project field is optional. A link from a study may preselect the interest through an item value in the page URL. No GPS permission, identity scan, payment information, file upload or precise location feed is requested. For an early map enquiry, a broad description of the place and intended audience is usually more appropriate than private access details or information about identifiable visitors.
3. What happens while preparing the form
The values you type stay in the current browser page while the form builds a preview. Its script constructs an email address, subject and body from those values. There is no authored submission endpoint storing a new record on the site. You can read the draft before choosing to open an email application. The software then used for email is a separate service. Leaving a draft on screen is not the same as transmitting it, and the preview cannot confirm receipt by the professional.
4. Handling a separately sent enquiry
If you decide to send an email and it reaches the published contact route, its information can support a discussion about map graphics, source plans, intended viewing size and scope. A conversation may need to distinguish publicly available geographical material from confidential site information. Share only what you are authorised to disclose and avoid personal visitor records in an initial message. Later project files, access arrangements or sensitive site details should have an agreed handling process rather than being treated as automatically covered by this simple portfolio form.
5. Technical requests when viewing a map
Your browser requests the page and its resources through hosting and network providers. A request can reveal its source IP, the resource path, timing and browser or protocol characteristics to infrastructure involved in delivery. Cloudflare can provide delivery, security and email protection, and may add traffic or performance measurement and network error reporting. These mechanisms are independent of the illustrated route on screen. The portfolio does not claim that a map image prevents technical logging or that the public page proves all provider retention settings.
6. Browser storage is separate from route information
The original SVG maps, font and form script load from this site’s own folders. There are no embedded map providers, external navigation widgets, social feeds or video players. The authored form does not write a cookie, local storage entry or session storage record. Browser caching, autofill and restored sessions can still keep data according to your settings. You can inspect site data and adjust those browser features directly. A fictional route displayed in an image neither starts location tracking nor grants a service permission to access your position.
7. Service providers and international handling
Hosting, security and content delivery involve providers whose systems can operate in more than one country. Choosing to send email also involves the mail software and services selected by you and by the recipient. The relevant providers’ terms and applicable requirements govern their own processing. The authored enquiry has no mechanism that posts form content to a social network or advertising list. This notice does not invent a complete list of every network operator or claim that all handling occurs solely at the professional’s identification address.
8. Keeping and identifying correspondence
A browser preview is not a separate website enquiry archive. Email copies, attachments later shared for a real project, and records necessary for an agreement may have different purposes and retention needs. No fixed universal deletion deadline is promised here. Ask about a specific exchange by identifying its subject, approximate time and relevant context through [email protected]. Where deletion is requested, an answer should consider the particular records and any continuing duty or project need, rather than assuming every provider backup can be removed instantly.
9. Requests about personal information
Depending on the applicable rules and the circumstances, you may have rights concerning access, correction, erasure, portability, objection or restriction, and a right to complain to an appropriate supervisory authority. The contact route can be used to raise a relevant request. Provide enough information to locate the conversation, but do not send an identity document unless there is a justified need discussed separately. If you supplied personal data about other people, identify the concern without repeating more of that information than is necessary.
10. Safe sharing, children and changes
Use care with plans of private sites, access codes and information about vulnerable people. None belongs in a public portfolio’s first enquiry merely because the subject is a map. The site is intended for discussion of design work and does not offer accounts or services aimed at children. Its published revision date allows you to identify the notice you read. If the tool’s actual features change, this description should be reviewed; a later paid project may require additional handling arrangements for its own materials.