Last reviewed · November 3, 2026
Privacy and accessibility, without vague promises.
This page describes what the portfolio currently processes and how to report an accessibility barrier.
Who is responsible
This personal portfolio is maintained by Kauai Staingel. Privacy or accessibility questions can be sent to kauaistaingel@gmail.com. The link opens the visitor's own email application; the portfolio does not receive or store the message itself.
Aggregate visitor analytics
When analytics are configured in production, the portfolio records one aggregate visit when the site is opened. The visitor radar displays the public location totals.
Information used
- one aggregate visit for the current browser tab session;
- approximate country, broad region, city, and rounded coordinates supplied by Vercel from network information;
- aggregate start and last-update dates.
The portfolio does not request GPS location and does not store a raw IP address, user-agent string, advertising identifier, navigation trail, or individual visitor record. Approximate location can be wrong because of VPNs, proxies, mobile networks, or provider databases.
Browser storage
A session marker prevents a refresh in the same tab from adding another visit. It stays in the browser and is not an identifier sent to the analytics store. No advertising cookie or cross-site tracking technology is used.
Purpose, publication, and retention
The purpose is to show broad, low-volume reach without tracing people. Country and approximate-city totals are public from the first recorded visit. Aggregates remain in a private Vercel Blob while this portfolio operates and may be reset manually; there is no per-person history to retrieve or delete.
External services and links
- Vercel hosts the site and runs analytics when production is configured.
- Vercel Blob stores only the aggregate metrics described above.
- LinkedIn and the visitor's email provider apply their own terms when those external links are opened.
The analytics implementation is off until its production storage and domain configuration are explicitly activated and tested.
Accessibility approach
The portfolio targets WCAG 2.2 Level AA. Current measures include semantic landmarks and headings, a skip link, visible keyboard focus, keyboard-operable disclosures and carousels, text alternatives for meaningful images, a textual equivalent for the visitor visualization, responsive reflow, and reduced-motion support.
Automated and code-level checks do not replace testing with assistive technology. If something prevents access, use the email above and describe the page, device, browser, and barrier when possible.
Reference standards: WCAG 2.2 and the ANPD cookies guide.