Production checklist
For widget integrations
- Set the exact allowed hostname, including the subdomain used in production.
- Submit a test response and confirm it appears in the intended project.
- Decide whether to show a consent checkbox with
hide-privacy-policyand link your policy withprivacy-policy-text. See Text. - If you use reCAPTCHA, test it on the production domain.
- If submissions require a key, embed only a project-restricted
feedback_createkey. Browser keys are visible.
For API integrations
- Store private keys outside source control and browser code.
- Send keys in the HTTPS
Authorizationheader. - Grant only the required scopes and restrict the project where possible.
- Test missing-scope and invalid-key responses before relying on the integration.
- Revoke unused keys. Rotate a key by verifying its replacement before revoking the old one.