Privacy
Privacy and AI Website Integrations
A future site collects less. A prompt is not a junk drawer for customer data.
Build-time prompts are still data flows
Pasting a client export into a personal chat account can move customer information, unpublished prices, or credentials into a third party. That is a project decision, not a shortcut.
We use approved accounts, strip data that the task does not need, and keep secrets out of prompts entirely.
Live features get a written boundary
If a form is summarized by a model, the visitor should know, and the payload should be the message they typed — not their whole history.
Logs are kept only as long as needed to operate and debug the feature. They are not a training set by default.
Document the subprocessors
GPT, Gemini, Grok, and Claude providers are subprocessors when a live feature calls them. They belong in the privacy notes before the feature is turned on.
Until that is true, the feature stays off. A demo key on a production form is not a launch plan.
Continue
When a Website Should Call an AI API
A decision test for live calls to GPT, Gemini, Grok, or Claude versus keeping the model in the build and shipping static HTML.
Read →Editorial Control Over Model Drafts
How to keep GPT, Gemini, Grok, and Claude drafts inside a review process so the published site stays accurate and on-voice.
Read →Accessibility Still Comes First
Why GPT, Gemini, Grok, and Claude features must meet the same WCAG 2.2 AA bar as the rest of an Alaska website.
Read →