Build-Signs.work

Privacy Policy

Last updated October 24, 2026

This policy covers Build-Signs.work and the six sign builders it links to: Road-Signs.work, Trail-Signs.work, Park-Signs.work, Airport-Signs.work, Safety-Signs.work and Railroad-Signs.work. The Terms of Service cover the same sites. There are no user accounts, and we collect as little as we can while still understanding how the sites are used. Some sites are offered in several languages; if a translation differs from this English policy, this one applies.

Build-Signs.work itself

Build-Signs.work is a static site hosted on GitHub Pages. It runs no analytics and sets no cookies, and its example signs are files served with the site. GitHub may log requests (including IP addresses) for security and operation; see GitHub’s privacy statement. Google Fonts serves its typeface.

First-party usage analytics

On the sign builders, viewing a page, building a sign or using an export button (copy link, open, download, print, products) records an event on our own server. An event may include the page path, the referring URL, your browser’s user-agent string, the type of sign involved, and that sign’s parameters, such as a speed limit of 55 or a trail name you typed. The games and practice test on Road-Signs.work also record that a game or test was started or finished, and its score.

We do not store your IP address. To count unique visitors without identifying anyone, each event carries a one-way fingerprint: a truncated SHA-256 hash of your IP address combined with your user-agent. It can’t be reversed to an IP address and is never stored next to one. This data is used only in aggregate, for example on the sites’ public statistics pages.

Google Analytics

The sign builders load Google Analytics (gtag.js), which sets its own cookies and collects standard analytics data (approximate location from IP, device and browser information, pages visited) under Google’s privacy policy. You can block it with a tracker blocker or a Global Privacy Control setting without affecting the builders.

Saved signs, games and preferences

“Saved signs”, “Recently viewed”, marks on a playable game board and similar preferences are kept in your own browser’s local storage. They never leave your device, and clearing your browser’s site data removes them.

Buying a sign on Zazzle

Builder pages can show the sign you made on products printed by Zazzle. To show those previews, your browser loads images from Zazzle’s servers (we ask it to send no referrer). If you click a product, you go to Zazzle with a link carrying the address of the sign’s image, which includes the sign’s text and settings, plus a short code identifying the sign and where you clicked. From then on Zazzle’s privacy policy applies. Zazzle reports sales to us without personal information about the buyer.

Cookies

The sign builders set no cookies of their own. The only cookies on the sites are set by Google Analytics, and by Zazzle once you go to its site. Our first-party analytics uses no cookies.

What we don’t do

Children

The road-trip games are made for families, but the sites aren’t directed at children under 13 and we don’t knowingly collect personal information from anyone. No information that identifies a player is collected.

Hosting

The sign builders and their shared sign service are hosted on Vercel, which processes requests for us and may log request metadata (including IP addresses) for normal operation and abuse prevention. See Vercel’s privacy policy.

Data retention

Aggregate analytics events are kept to track long-term usage trends. Because no event identifies a person, there is nothing to request the deletion of. If you believe otherwise, contact us and we’ll help.

Changes and contact

If this policy changes, the “last updated” date above changes with it. Questions can be raised as an issue on the Build-Signs.work GitHub repository.