Privacy & browser data

Pomegranate × Lily · Updated October 13, 2026

G-CAFL-QC Builder is a browser-based tool for drafting, reviewing, sharpening and sealing production briefs. This notice describes the current public website code, not a future subscription service.

Briefs stay in browser storage

Your drafts, sealed briefs, goals, context, audience descriptions, formats, limits and quality-check notes are stored in your device's browser local storage, including the current gcaflqc.v3 record and any retained legacy gcaflqc.briefs.v1 data. This site does not currently offer user accounts or automatically upload brief text to a Pomegranate × Lily application database.

Use the app's export and copy features to keep a backup. Clearing browser data, switching browser profiles or changing website hostnames can remove access to locally stored work. Explicit copy, share, download or handoff actions may send or reveal content to applications or people you choose.

Optional seal analytics

Sitewide seal measurement is off by default. You can turn it on or off in the app's drawer. When enabled, the app creates a random device identifier and locally records sealed-brief event timestamps and elapsed times. The current code is configured to send limited, content-free event records to a Cloudflare Worker at gcaflqc-analytics.editor-hw12.workers.dev. It does not send the text of your briefs with those analytics events. Rejecting or turning measurement off does not prevent writing or sealing briefs; turning it off clears its local measurement record.

When network reporting is enabled, the Cloudflare Worker and underlying network providers may process connection metadata such as your IP address. We cannot guarantee that infrastructure operators retain no technical logs. The random device identifier may distinguish repeat visits and should be treated as pseudonymous data, not anonymous personal information.

Hosting, cookies, and sharing

GitHub Pages hosts this website and may process standard connection data. The reviewed site code does not install ad pixels or unrelated marketing trackers. Essential browser storage is used for the app. Visitors control optional seal analytics using the app toggle; no other optional advertising or analytics service has been authorized by that toggle.

Because other Pomegranate × Lily projects currently run under the same pomegranatexlily.github.io hostname, scripts on that hostname can technically access local storage regardless of URL path. Do not enter passwords, payment details or confidential third-party records in this prototype. Separate website origins are planned before account-based features.

Choices and contact

To remove local briefs, clear the app's saved records or your browser's site data after exporting anything important. To stop optional measurement, switch off its consent control in the Builder drawer. We currently have no account database from which to retrieve Builder briefs.

For public, non-sensitive questions, see the GitHub issue tracker. Issues are public: do not include private information. A verified confidential contact channel is still being set up for sensitive requests. This notice will be updated if that changes.