Privacy before monetization.

Information used by the calculators

Calculator values, permit-check answers and project-brief inputs are used in the browser to produce the requested result. Building, copying, downloading and printing a project brief does not require contact details or submit the brief. These values are not treated as a verified survey, permit application or professional record.

Moving tools and federal lookups

Moving inputs are processed in your browser and by our server to produce the requested result. Form fields can appear in the resulting URL, browser history and routine hosting request logs. The moving tools retain a local, limited history of tool steps and recent checks in browser storage; that history is not sent to an analytics service or synchronized. Mover Check sends the submitted company name, USDOT or docket through our server to the U.S. Department of Transportation public FMCSA data service to retrieve the requested federal record. It does not send quote inputs or contact details to FMCSA. Cached federal records are explicitly labeled when the live service is unavailable. Automatic Cloudflare Web Analytics injection is disabled for moving pages so company identifiers in their paths are not counted.

Optional technical lead handoff

The final Project Brief layer asks for a name, email, phone number, preferred contact method and project ZIP code, and sends those fields with the scope and draft-consent record to the lead-capture endpoint only after the visitor submits the form. In the current mock configuration, the endpoint validates the payload, creates a non-personal delivery receipt and does not persist the lead or send it to a contractor. Real contractor delivery, final consent language, recipient disclosure and retention terms remain launch gates.

Technical delivery data

Hosting and security providers may process ordinary request data such as IP address, user agent, requested URL, timestamps and error diagnostics to deliver and protect the site. The current interface uses system fonts and does not make a third-party web-font request.

Local browser state

The current project brief and calculator inputs live in page memory for the active browser session. The site sets no analytics or advertising cookies. The application may retain non-sensitive interface preferences in local browser storage when a feature explicitly says so. Nothing is synchronized across devices without a future, separately disclosed account feature.

How visits are counted

YardPermit is hosted on Cloudflare, and page views are counted with Cloudflare Web Analytics. Cloudflare says its Web Analytics uses no client-side state such as cookies or local storage, does not fingerprint visitors by their IP address, user agent or other data, and does not log query strings, so no calculator or brief input leaves the page with a view. It records the country, the site, the page path, the referring page, the device type, browser and operating system, and page-load timing, and Cloudflare describes it on its Web Analytics page and in its documentation of what it records.

The site also has a restricted vocabulary of events for calculator, project-brief and lead-funnel steps. It is not sent anywhere today. Contact fields, free-form scope text and ZIP codes are never valid event properties. If a destination that needs consent is added, such as Google Analytics, the site will ask before any event reaches it, and this notice will change first.

Advertising and Google AdSense

YardPermit has applied to show ads through Google AdSense. Two things on the site identify the publisher account today: a verification tag in the head of each page and an ads.txt file that lists Google as an authorized seller. Neither causes your browser to contact Google, and neither sets a cookie. No advertising code loads until the application is approved and this notice changes its Advertising status above.

Once advertising is switched on, third-party vendors, including Google, use cookies to serve ads based on a visitor's prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads based on visits to this site and other sites on the internet. You can opt out of personalized advertising from Google in Google Ads Settings, and from other participating vendors at aboutads.info. Google explains how it uses information from sites that show its ads in How Google uses information from sites or apps that use its services. Visitors in the European Economic Area, the United Kingdom and Switzerland will be asked for consent through a Google-certified consent management platform before personalized ads are served.

The advertising/CMP gate

Before personalized advertising, measurement cookies or similar nonessential technology is enabled, YardPermit must update this notice, document every vendor and purpose, install a Google-certified consent management platform where required, honor consent choices before tags fire, and provide a persistent way to change those choices. A decorative cookie banner is not considered consent management.

Retention and requests

The application does not create profiles or store mock lead payloads in a database. A short-lived in-memory idempotency receipt contains a lead identifier and delivery status, not the submitted contact fields. Infrastructure logs may be retained by hosting and security providers under their operational policies. Privacy questions can be sent to privacy@yardpermit.com. A final retention schedule, and the recipient disclosure that goes with real contractor delivery, must still be published before lead delivery or production monetization is switched on.