This policy explains what the public Kendr website collects, how early-access submissions are stored, and how analytics are used on kendr.org.
Effective date: April 17, 2026
This policy applies to the public Kendr website at kendr.org, including the homepage, feature pages, use-case pages, community page, privacy page, terms page, and the early-access form that appears on the site.
When you submit the early-access form, Kendr stores the information you enter and the related submission metadata sent by the site.
Information you provide
Email address, team or role selection, and primary product interest such as deep research, agentic workflows, or knowledge base usage.
Submission metadata
Source page, form context, referrer, browser user agent, client-side timestamp, and server-side created and updated timestamps.
Early-access data is used to manage the launch list, understand what kinds of teams want Kendr first, and review demand across product motions such as deep research, agentic work, and reusable knowledge bases.
The data is also used to avoid duplicate records when the same email updates its interest later.
Kendr does not present this public website as a consumer ad-tech product, and the launch-list data is not collected for resale.
Early-access submissions are stored in a PostgreSQL database operated for the Kendr website. Access to the admin leads endpoint is protected behind admin authentication. The public site does not expose the leads database directly.
Kendr uses Google Analytics through the Google tag with measurement ID G-R8PWS5SE55. This helps measure traffic and page usage across the public marketing site.
Google Analytics may collect device, browser, and usage information according to Google's own policies and may use cookies or similar technologies to support reporting.
The site links to external services such as Discord and GitHub. Once you leave kendr.org, the privacy practices of those external services apply instead of this policy.
Early-access entries may be retained as long as they remain useful for launch planning, product follow-up, or launch-list management. If the same email is submitted again, the record may be updated instead of duplicated.
This policy may be updated as the public site and launch process evolve. Material updates will be reflected on this page with a revised effective date.
For questions about this policy or the public Kendr launch site, use the official Kendr community channels on the community page, Discord, or GitHub.