Website information

Privacy, in plain language.

Understand what the new preview pages do with information you type and how to contact the team with questions.

Draft for review · Not an adopted production policy.
This page describes the public marketing pages. It is a draft: the operating service’s policy still needs confirmation before publication.

This page’s scope

This notice applies to the public marketing pages at municiply.com. It does not describe the Municiply application that municipal staff sign in to, or a municipality’s own website.

Information you enter

The demo and contact forms send what you type to Municiply when you submit them. Both ask for the same things: your name, email address, municipality, your role, what you are interested in, and your message. Which page you submitted from is recorded with it.

A submission is stored in Municiply’s own database and read by the Municiply team in an internal queue. No email notification is generated — somebody opens that queue and replies to the address you gave. Include only what your inquiry needs; these forms are not a route for resident personal data or anything confidential.

Cookies, storage and analytics

These pages set no cookies, and nothing you type is kept in your browser. Checklists reset when the page reloads. There is no advertising script, no tag manager and no cross-site tracking pixel on any page.

One measurement script does run, and it is worth describing exactly. Cloudflare hosts this site, and it adds its own Web Analytics beacon (static.cloudflareinsights.com/beacon.min.js) to each page as the page is served. It is not written into the page files themselves. The beacon measures how the page performed and reports the address of the page, the referring address if you arrived from a link, the type of navigation, Core Web Vitals (largest contentful paint, cumulative layout shift, first contentful paint, time to first byte and interaction to next paint), connection and load timings, and, on browsers that expose them, JavaScript memory figures. Each report carries an identifier for this site and an id generated fresh for that one page view. The beacon sets no cookie and writes nothing to your browser’s storage, so it carries no identifier that survives a reload or ties one visit to another, here or on any other site. Each report is posted back to municiply.com itself, at /cdn-cgi/rum, which Cloudflare answers at the edge; only the script file is fetched from static.cloudflareinsights.com.

Two things happen on the server whatever your browser runs: a form submission is stored as described above, and submissions are rate-limited by IP address, so your address is held briefly in a counter and discarded as that window passes. Fonts, photographs and screenshots are served from municiply.com. Every request also reaches Cloudflare, whose request logging applies and from which Cloudflare derives the country, browser and device figures shown in its analytics.

The site is hosted now, so the Cloudflare logging and the beacon described above are current rather than prospective. Any service added later that runs in your browser or receives information about your visit will be described here as well.

Before a public launch

The final notice must identify the operating entity and accurately explain the live service’s information collection, purposes, providers, retention, rights-request process, and contact details. These are not settled. In particular, how long a demo or contact submission is kept has not been decided, so no retention period is stated here rather than one being invented.

Privacy questions

Contact the team at hello@efferentmedia.com or (800) 313-3750.

Product screenshot