PRIVACY

Your information, plainly explained.

What this site stores and what becomes public when you contribute.

Browsing and local tools

The public library can be browsed without a contributor account when the site is public. Saved favorites and your selected AI tool use browser local storage. Unfinished contribution forms also save automatically on the current device, separately for each signed-in account. These local drafts are removed after a successful save or submission; use Save draft to keep a copy in your account. Clearing your browser’s site data removes local drafts, favorites, and tool preferences. The project-tracker example also saves tasks in the current browser. Neither feature synchronizes that data to our submission database.

Prompt customization happens in your browser. This site does not send your customized prompt to an AI provider or execute terminal commands. Copying or running the output in another tool is a separate action.

Aggregate page-view counts

When the site is public, the server counts successful loads of public HTML pages, including when you decline optional analytics or send a privacy signal. The stored counters contain only the UTC date, public page path or referring website domain, and a total. These counters do not set cookies or browser storage, store IP addresses, browser identifiers, account identities, or user-agent strings, or connect visits to the same person. Query strings and full referrer URLs are not stored. The counters are separate from optional browser tracking.

We filter known automated requests and prefetches without storing their user-agent strings. A signed-in editor’s existing authentication is checked solely to exclude their visits. Failed pages, private pages, and internal referrers are excluded. Reloading a page counts again; cached pages or client-only transitions may not reach the server. These totals measure page loads, not unique people. Only the editor can view reports. Daily aggregate totals are retained for historical comparisons.

Optional unique-visitor analytics

When the site is public and you accept optional analytics, we count visits using a random browser identifier stored on this device for up to one year. It is specific to this website and is not your account ID. Our server stores a hashed version with the UTC date, public page path, referring website domain, approximate country when provided by hosting, and broad browser/device type. We do not store IP addresses, full referrer URLs, query strings, or prompt contents in analytics.

Analytics are off until you choose to allow them. Use Privacy choices in the footer to accept or decline, or withdraw your choice later. The choice is saved on this device for up to six months. Declining removes the local analytics identifier and stops future browser-based collection; it does not disable the identifier-free server counters or automatically remove historical counts. Only the site editor can view traffic reports. Repeated visits to the same page by a browser count once per day. Aggregated reports and pseudonymous daily counts are retained to provide historical comparisons. We exclude signed-in editor visits and private account pages, and honor Do Not Track and Global Privacy Control signals. Clearing this website’s local storage removes its browser identifier; enabling either privacy signal stops future browser-based collection by this tracker. Analytics are first-party and are not sent to advertising or AI providers.

Contributor accounts

This hosted version uses ChatGPT sign-in. The hosting platform supplies a site-specific user identifier and account identity to the server. We use the identifier to authorize access to your submissions. Your account email is not included in public contribution pages.

Information you submit

We store your submission, public display name, optional project name and URL, status, timestamps, review feedback, and ownership identifier in a hosted database. Approved content and attribution become publicly accessible. Drafts and pending content are available to their author; submitted content is available to the editor for review.

Community votes

When you vote, we store your site-specific account identifier, the contribution you voted on, your upvote or downvote, and the latest vote timestamp. Public pages show totals and scores, not the identities of voters. Each account has one vote per contribution. You can change your vote or select it again to remove it. Deleting a contribution also removes its votes.

Managing your information

You can download and delete your own submissions from your account. Deleting a submission removes its public page if one exists. Operational audit records can retain a submission ID, actor ID, action, version, and timestamp after deletion. Hosting backups and access logs follow the platform’s retention controls.

Advertising and Google

No advertising scripts are active in this version. If Google AdSense is enabled later, Google and other third-party vendors may use cookies to serve ads based on visits to this and other websites. Google advertising cookies can enable Google and its partners to show personalized ads. You can manage Google personalization at My Ad Center and learn about participating vendors’ choices at AboutAds. See how Google uses information. Applicable consent choices will be provided before advertising storage or processing that requires consent. The analytics choice on this site is not advertising consent.

Contact and privacy requests

Email jack@wilbankswebdesign.com for access, correction, deletion, or other privacy questions. Describe the relevant information without sending secrets. We may verify your ownership before processing account-related requests.

Hosting and external links

The hosting and authentication providers process requests needed to operate the site. Contributor project links and documentation links lead to other websites with their own policies. No third-party advertising or analytics scripts have been added to this version.

Last updated October 16, 2026. If the site’s data handling changes, this page should be updated before those changes go live.