Transparency by design
Data practices.
What the public site processes, how application programming interfaces may support the Archive Guide, and where a visitor remains in control.
Effective date: September 10, 2026
The public site is designed to minimize collection. Secret API credentials are never intentionally placed in downloadable page code.
Public website data
The site can be viewed without creating an account. The pages do not directly request a visitor’s name, address, payment details, government identifier, or precise location. Basic hosting records—such as IP address, browser type, requested page, approximate time, and security events—may be processed by the hosting provider as part of delivering and protecting the site.
Archive Guide
The Archive Guide provides short answers about published works, purchase routes, official archive links, submission procedure, and general support. Its built-in knowledge responses operate in the visitor’s browser. When a secure remote assistant endpoint is enabled, the visitor’s question, the current page path, and limited technical metadata needed to process the request may be sent through an encrypted HTTPS connection to the configured service.
The Guide is instructed to avoid requesting sensitive personal information. Complex historical interpretation, contractual questions, rights matters, manuscript decisions, and questions involving unpublished evidence are escalated to the publishing desk.
How APIs are used
An application programming interface may connect the public interface to a protected server-side service. The server-side service can classify a question, retrieve approved catalog information, produce a concise response, and mark a complex request for human review. API keys and service credentials must remain on the protected server; they must not be copied into config.js, HTML, or other public files.
Email inquiries
When a visitor chooses the email link, the visitor’s own email application handles the message. The public website does not receive the message first. The publishing desk may retain the correspondence as needed to answer the inquiry, maintain an editorial or business record, prevent abuse, or satisfy legal obligations.
Retail and archive links
Links to retailers, libraries, social channels, and archival catalogs take the visitor to independent services. Those services apply their own terms and data practices. The Registers of Hérédom™ does not control their checkout, account, tracking, retention, or security procedures.
Retention and deletion
Browser-based Guide questions are not intentionally stored by this static website. If a remote assistant or email workflow is enabled, operational logs and correspondence should be kept only as long as reasonably necessary for support, security, recordkeeping, and legal compliance. A deletion or access request may be sent to theregistersofheredom@gmail.com. A request may require verification before records are disclosed or changed.
Security controls
The site uses local assets, a restrictive content policy, encrypted transport when served over HTTPS, limited connection destinations, protection against framing, and browser-level deterrents against casual copying and dragging. These controls reduce common risks but cannot guarantee that visible public information will never be captured, copied, or reproduced.
Children
The site is directed toward historical readers, researchers, purchasers, and prospective authors. It is not designed to knowingly collect personal information from children.
Changes
This page may be updated as the assistant, hosting arrangement, support workflow, or publishing services change. The effective date will be revised when a material change is published.