Privacy

Our West Valley AZ is designed around a simple privacy principle: residents should be able to access civic information without being tracked, profiled, or required to identify themselves to OWVAZ.

Last updated: September 23, 2026.

What OWVAZ does not use

The OWVAZ website is designed without:

• resident accounts
• advertising networks
• behavioral analytics
• tracking pixels
• browser or device fingerprinting
• third-party social trackers
• third-party analytics scripts
• third-party advertising scripts
• persistent browser storage for tracking or profiling

OWVAZ does not sell resident information or use the website to build advertising, behavioral, or personal profiles of visitors.

Cookies and browser storage

The current OWVAZ site code does not set cookies and does not use localStorage, sessionStorage, or IndexedDB to identify, track, or profile residents.

If a future feature requires cookies or persistent browser storage, its privacy impact must be evaluated before that feature is added and this page must be updated when appropriate.

Search privacy

OWVAZ search is designed to operate in the resident’s browser.

When a resident searches OWVAZ, the site loads static OWVAZ search-index data from the same website and performs the search locally in the browser. The search form does not submit the resident’s search terms to OWVAZ, a search engine, an analytics provider, or another third-party search service.

Loading a search index is a normal request for a static website file. The resident’s typed search term is not included in that request.

Contact form and information residents submit

Residents can browse OWVAZ without creating an account or identifying themselves to OWVAZ. Using the contact form is optional.

The contact form asks visitors to select a topic and enter a message. Depending on the topic, it may also ask for a city or an OWVAZ page address. Visitors submitting a general question can request a response; an email address is required only when they select that option. The form does not require a name. Please avoid including sensitive personal information in a message.

When a visitor selects Send message, the form sends the submitted information to Web3Forms, a third-party form-processing service, for delivery to OWVAZ. Web3Forms may also receive technical information associated with the request, such as an IP address. Not providing a name or email address does not make a contact-form submission anonymous.

OWVAZ receives messages in its contact mailbox and uses them to review questions, reported website issues, proposed corrections, and other suggestions. Messages and related correspondence may be retained while an inquiry is addressed or a correction is reviewed. OWVAZ does not currently publish a fixed deletion schedule for contact messages.

If a submission leads to a website correction, OWVAZ may independently verify and cite a relevant public source. OWVAZ does not ordinarily publish the sender’s message, email address, or other contact details as part of that update.

OWVAZ does not sell contact-form submissions or use them to build advertising or behavioral profiles. Web3Forms processes submissions under its own privacy practices, including any applicable technical logging and retention. OWVAZ cannot guarantee deletion of information already processed or retained by that provider. Review Web3Forms’ privacy information before submitting a message: https://web3forms.com/privacy

To ask about information you previously submitted, or to request deletion of a message from OWVAZ’s contact mailbox, use the contact form and select a general question. Provide enough information for OWVAZ to locate the message, but do not include sensitive personal information. OWVAZ may need to verify that a request relates to your own submission and cannot promise removal of copies held by third-party services or already included in correspondence outside its control.

External links

OWVAZ links to official government agencies, public meeting systems, utilities, public documents, and other external sources.

Following one of those links takes the resident to a website that OWVAZ does not operate or control. That external site may have its own cookies, analytics, logging, privacy practices, or terms.

OWVAZ does not treat a link to an external website as permission for that site to track residents through OWVAZ. External resources are linked rather than automatically embedded whenever practical so residents can choose whether to visit them.

Website requests and infrastructure

Like any website, OWVAZ must receive a network request in order to send a requested page or file to a visitor’s browser. That request can inherently include technical information needed for normal Internet communication, such as an IP address and basic request information.

OWVAZ does not intend to use website infrastructure to track or profile residents.

OWVAZ’s production website is delivered through Cloudflare Pages and related network infrastructure. Cloudflare and other infrastructure providers may process technical request information as needed to deliver the website, maintain security, and operate their services. OWVAZ does not claim that infrastructure-level logs do not exist or that every provider follows the same retention practices.

The contact form involves an additional service, Web3Forms, as described above. Merely browsing OWVAZ does not submit a contact-form message to Web3Forms.

Privacy by design

Privacy is treated as a design constraint rather than an optional feature. New analytics, tracking, advertising, profiling, third-party embeds, or similar technologies are not assumed to be acceptable merely because they are common on other websites.

If OWVAZ considers adding a feature that changes how resident information is handled, its purpose and privacy impact should be evaluated first.

Changes to this privacy information

OWVAZ’s privacy practices and this page should be reviewed when a material change affects how resident or visitor information is handled.

If OWVAZ adds a feature, service, or production technology that materially changes the privacy practices described here, this page should be updated to reflect that change.