Privacy outline · Needs counsel and provider review
Capture evidence deserves precise privacy language.
This launch-ready outline identifies the subjects the final policy must cover. Legal company details, providers, retention periods, and jurisdiction must be confirmed before publication as a binding policy.
Public inquiry data
Early conversations should collect only what is needed.
- name, work email, company or project, and application URL;
- application type, intended use case, preservation goal, and notes;
- server and analytics data if analytics are enabled;
- communications and follow-up records related to the inquiry.
Do not submit through the public form
Credentials, private tokens, source archives, authenticated session data, HAR files with secrets, private URLs, user data, or confidential capture artifacts.
Capture and evaluation data
A real engagement needs a separate data-handling boundary.
Any early-access engagement involving an application capture should define the authorization basis, approved environments, allowed data, storage location, access controls, retention, deletion, processors, confidentiality, and incident handling before sensitive evidence is collected.
KodeCapture does not treat application evidence as ordinary marketing data. The final privacy policy and any design-partner agreement must distinguish public inquiry information from technical capture data.
Complete before publication
Operational facts still required.
- legal company name and jurisdiction;
- privacy contact email and mailing address;
- form, hosting, analytics, and infrastructure providers;
- legal bases, retention periods, deletion process, and user rights;
- cross-border processing and policy-change procedure.