1. Scope of this policy
This policy concerns the public website at datlore.com, its informational content, and its contact, expert-interest, and access-request interactions. References to “Datlore,” “we,” or “our” concern the provider of that website. The policy describes the website code and interactions offered here, rather than assuming that every possible platform service uses the same process.
Expert-data programs, reinforcement-learning episodes, and other separately agreed services may involve different information and contractual requirements. Their handling arrangements must be established in the relevant service agreement or notice. This website policy does not grant permission to use confidential project data or override a separate agreement.
2. Information you choose to provide
Website inquiry fields ask for information such as a name, email address, organization, inquiry topic, and message. The expert-interest form also asks for an area of expertise and relevant experience. The access-request form asks for an organization and allows a short description of intended use. Required and optional fields are identified in the interface.
Provide only what is necessary for the question you want to raise. Do not enter passwords, security codes, identity documents, client records, sensitive personal information, confidential datasets, or material you are not authorized to share. A brief description of a program or area of expertise is sufficient for an initial introduction.
3. How the inquiry forms behave
In the current website, form validation and confirmation take place in your browser. The website code does not connect these forms to a delivery endpoint, transmit the entered values to Datlore, or save a submission in a database. An on-page confirmation is an interface response and does not, by itself, establish that information has been received or reviewed.
Entries remain in the current page while you interact with it. The website does not intentionally copy them into local storage, session storage, URL parameters, analytics events, or console logs. Reloading or leaving the page may clear the entries, although your browser’s own autofill, history, or page-restoration settings can behave differently.
The access-support page does not authenticate an account, create a session, or collect a password. The access-request interaction does not provision an account. If form delivery or account services are introduced, the relevant information handling and this policy should be updated before that new processing begins.
4. Information involved in loading the website
When you view a hosted website, your browser sends requests for pages, images, styles, and scripts. Those requests ordinarily involve technical information such as a network address, requested path, and browser-provided headers. The infrastructure delivering a website necessarily receives the request information needed to return its files.
The website’s authored code does not add analytics, advertising pixels, fingerprinting, session replay, or a visitor-profiling service. This policy does not claim a particular hosting log configuration, provider, or storage period. Infrastructure-level processing depends on the actual hosting arrangement and is distinct from the browser-only form behavior described above.
5. Purposes of information use
The website uses browser interactions to validate required entries, display field errors, select an inquiry topic, and show confirmation states. Navigation and FAQ interactions use temporary page state to open or close content. These activities do not require a visitor profile or an authenticated account.
If you provide information through a separate communication channel that actually delivers it to Datlore, relevant purposes may include understanding your inquiry, discussing program requirements, addressing an access question, or considering an expression of expert interest. Such handling should be limited to the context of the communication and any applicable agreement. The unconnected website forms do not currently perform those delivery functions.
6. Cookies and browser storage
The website code does not set cookies or use localStorage, sessionStorage, or an application database for visitor information. Menu, disclosure, validation, and confirmation states are held only in the current page. No advertising preference system or analytics consent banner is included because those tracking functions are not included in the authored site.
Your browser may independently cache website files or offer to autofill fields according to your settings. Those browser functions are not a Datlore account system. You can manage caching, autofill, and browsing data through the browser. Infrastructure features added during hosting may need separate assessment; this policy does not imply that a banner can control processing it has not been built to manage.
7. Service-provider processing
No third-party form processor, email-delivery provider, authentication provider, analytics service, or remotely loaded font service is integrated into the authored website. Images, styles, and scripts are referenced as local site assets. The code does not send form entries to a third-party API.
A hosting provider, if used to serve the website, processes requests as part of delivery. Other providers may become relevant only if additional services are actually introduced. Their roles, access, and applicable terms should be assessed for the specific arrangement. This policy does not name vendors that have not been established or represent that a particular certification or processing contract exists.
9. Retention principles
The current website does not create a retained server-side record of form entries. Temporary page state ends with the page’s lifecycle, subject to independent browser features such as restoration and autofill. Clearing a page does not necessarily remove information your browser itself has chosen to retain.
For information received through other established channels, retention should be related to the purpose of the interaction, operational necessity, and applicable legal obligations. No fixed retention period is asserted here without a verified operational policy. A request about a particular communication should identify its context so the relevant record and any obligations affecting it can be considered.
10. Reasonable safeguards and your role
Limiting the information requested and avoiding unnecessary transmission or storage reduces the information handled by this website. The forms do not collect account passwords, and the code does not place personal form values in a URL. These design choices do not amount to a guarantee that every browser, device, network, or hosting environment is free of risk.
Use a device and connection appropriate for your work. Do not submit confidential materials through an initial inquiry or assume that a public website creates a secure project-transfer arrangement. For a separately agreed program, discuss access controls, approved transfer channels, and other safeguards appropriate to the information involved.
11. Your choices and privacy requests
You can browse informational pages without completing an inquiry form. You can leave optional fields empty and avoid entering information that is not needed. The website does not require a tracking preference or an account to read public content. Browser settings can control autofill and local browsing records independently.
If you have a question about information actually provided to Datlore, use the Contact page as the inquiry starting point and choose Privacy. Describe the relevant interaction without adding sensitive material. The browser-only behavior in Section 3 also applies to that form; do not assume that an on-page confirmation establishes delivery.
Depending on applicable law and the circumstances of processing, you may have rights concerning access, correction, deletion, objection, or other handling of personal information. This policy does not promise a right or response period that has not been established. Verification may be necessary before acting on a request involving records or another person’s information.
12. Children’s information
The website is directed toward professional AI research, organizations, and domain-expert interests. It is not designed to solicit personal information from children. Do not use an inquiry field to provide a child’s personal information, including records, examples, or identifying details embedded in project descriptions.
If a concern involves a child’s information that may have been received through a separate channel, identify the nature of the concern through the contact guidance and avoid repeating unnecessary personal details. Any assessment should consider the actual information, the circumstances in which it was provided, and applicable legal requirements.
13. External websites and links
A link to another website takes you to a service that may have its own privacy practices, terms, and technical processing. Datlore’s public-site code does not control an independent operator’s collection, cookies, or account requirements. Review the destination’s information before entering personal or confidential material.
The website does not include embedded social feeds or third-party media players in its authored pages. If future content introduces an external embed or service, its information implications should be considered separately. A normal link does not establish a partnership or an assurance that another site follows this policy.
14. Separately agreed platform services
A research engagement may involve task materials, expert contributions, episode records, or other information beyond a public-site inquiry. The relevant parties should establish the purposes, permitted uses, responsibilities, confidentiality, retention, and access arrangements for that work separately.
This policy does not claim that inquiry information is used to train models, that every platform workflow has identical data practices, or that a particular legal role applies to all services. Do not infer program-level permissions from a general website description. Refer to the actual service agreement and applicable notices for the handling of materials within a contracted program.
15. Changes to this policy
Changes in website functionality, hosting arrangements, or actual processing may require revisions to this policy. The effective date identifies this version. Material additions such as form delivery, authentication, analytics, or persistent storage should be reflected in the policy when introduced, rather than assumed to be covered by a general statement.
Review the current policy before providing information through a changed interaction. A later revision does not by itself authorize an unrelated use of information already received where further permission or another legal basis is required. Mandatory privacy protections remain subject to applicable law.
16. Contact and related information
Use the Contact page for website and privacy inquiry guidance, selecting the Privacy topic where appropriate. Identify the relevant page, interaction, and concern. Keep the description proportionate and avoid including credentials or sensitive records. No unverified support mailbox, office address, or corporate registration is stated in this policy.
For the conditions governing use of the public website, read the Terms of Use. For existing account access, the access-support page provides the appropriate route. These pages concern the public website; separately agreed services may require additional information and their own handling arrangements.