What the beta does
Good Growth · Prototype helps authorised testers create temporary UX prototypes on websites. It runs as a Chrome extension with a separate local application on the user's Mac. The user chooses Codex or Claude Code and signs in through that provider's CLI.
Information handled
When you generate a prototype, the extension captures the current page's sanitised HTML, text, selectors, styles, layout information, page title, origin/path, public product-choice state and image references. The capture may include hidden responsive markup as well as visible presentation. It also handles your instruction, the selected implementation when refining it, generated code, summaries and export results.
The extension stores drafts, captures, generated versions, export files, provider choice, page/document bindings and a local companion pairing key in Chrome's local extension storage. Document bindings can include the full page URL, including its query string, although the page URL sent in the normal capture is reduced to origin and path. A pairing key authenticates the connection to the local companion; it is not a provider API key.
The companion stores local configuration and its pairing key in its .local folder. Temporary files used during generation include output schemas and generated results. Provider authentication is managed by the installed provider CLI, not by a password or API-key form in the extension.
When the beta owner configures private companion updates, that local folder also holds a read-only update access token, the approved feed URL and a public signature-verification key. Selecting Update local companion opens a separate local updater. It requests a signed version feed and, when newer, the runtime package over HTTPS from the approved download source, using the read token. It sends no page capture, prompt, generated treatment, provider credentials or workspace content to that source. The download service can see ordinary request metadata such as IP address, requested file and access token. The intended private download source is downloads.cima-studios.com, operated by Edward Jackson using Cloudflare hosting. The application does not add download analytics or application request logging. Cloudflare may process request metadata for delivery, security and its own service operations under its service terms and privacy policy; no fixed infrastructure-log retention period is promised here. Updates install only after the user approves the verified version.
The bundled application does not implement an analytics service, advertising tracking or a developer-operated telemetry endpoint. Ordinary Chrome Web Store, Google account and AI-provider services have their own data practices.
Why it is used and where it goes
The page context and instruction are used to generate the requested prototype. The selected source and relevant context are used for VEC adaptation; GGT conversion sends the selected implementation and summary rather than a fresh page capture. Those requests go to the loopback companion on the same Mac and then through the selected CLI to its AI provider: OpenAI for Codex or Anthropic for Claude Code.
This is not wholly offline processing. Provider processing locations, retention and account controls depend on your provider agreement and configuration. This policy does not promise a provider retention period, zero training use or a processing region. The business must approve the provider account and data-sharing arrangement before client material is used.
Copy and download controls put the selected code into your clipboard or a local file. Any subsequent sharing, upload or deployment is a separate action you control. The extension does not publish an Adobe Target activity or deploy an exported application.
Open Terminal and Resume last Terminal session launch an ordinary interactive provider CLI in the configured workspace. No page capture is supplied by those controls. Interactive CLI sessions can use the workspace and the CLI's normal instructions, tools, history and settings; they are separate from the restricted extension-generation request.
Filtering and limits
Capture filtering excludes typed text-field values, passwords, scripts, event handlers and many account, address and other sensitive regions. It also removes query strings from captured HTML links. Filtering is a best-effort safeguard, not a guarantee that names, confidential text, sensitive image paths or identifiers are absent. Do not generate on pages or with prompts that contain information you are not authorised to share.
Retention and removal
Chrome local extension data has no general timed-expiry rule in this version. Some stale document-bound versions are removed when the extension detects navigation or missing documents, but closing a tab or restarting Chrome is not a complete data-deletion method. New prototype keeps saved versions. Original restores the page presentation; it does not erase local records.
To remove the extension's local records, remove the extension using Chrome's controls. Removing and reinstalling it resets local extension data. The companion's .local folder, downloaded/copied exports and the provider CLI's own account/history data are separate and must be removed through their respective local or provider controls when no longer required.
The companion normally removes per-request temporary output files when a job finishes. Completed results are held in process memory for approximately an hour; abnormal termination may leave temporary files behind. No secure-erasure guarantee is made. The application uses local file permissions but does not add its own encryption layer to Chrome storage or configuration files.
The beta uses data for the requested prototype and export features. It does not implement sale of user data, advertising use, or a developer-run collection of client captures. Any future feedback service will need its own approved destination, access and retention settings before activation.
Questions and changes
Contact ed@cima-studios.com about the beta's handling of information. I publish revisions at https://downloads.cima-studios.com/privacy. Requests concerning the selected AI provider or its account records must also follow that provider's own processes.