Privacy notice

Your information.
Explained plainly.

What the current public preview handles, why it is handled, and how to contact the operator about your information.

Product previewLast updated
Updated 15 October 2026 · Preview scope

Use synthetic examples in this preview. Customer onboarding, regulated data, and live business integrations are outside its current scope.

01

Operator and privacy contact.

PraxisForge AI is the project name for this public preview. Privacy questions and requests go to [email protected]. This notice covers this hosted preview; an independently self-hosted deployment has its own operator and must provide notices for its own processing.

02

Information by context.

Visiting the website

The hosting and Cloudflare edge services receive connection and request information, such as IP address, browser information, requested URL, time, and security events, to deliver and protect the website. This is separate from anything you type into the demonstration.

Exploring the public workspace

The interface starts with illustrative records. Demo decisions and edits are held in the current page state; the application does not implement localStorage or sessionStorage persistence for them. URL parameters may identify the current view. Do not include private information in URLs.

Contacting the operator

An email provides your address, message, and any attachments you choose to send. It is handled through the operator’s email service to answer and manage the conversation. Please exclude passwords, API keys, and unnecessary sensitive information.

Restricted operations

Authorized access uses account identifiers, a password hash, and server-side session records. Tasks, supplied knowledge, execution events, approvals, results, and evidence can be stored as durable business records. This area is reserved for controlled testing; it is not open customer registration.

03

Why information is used.

The preview uses information to deliver pages, authenticate authorized access, protect the service, investigate failures, maintain test records, and respond to requests. The current operations configuration runs model inference on the self-hosted environment; it has no configured fallback to an external model API. That does not mean the public website is disconnected from hosting, edge, or email providers.

Where a law requires a lawful basis, that basis depends on the purpose: service or pre-contract requests, legitimate operational and security interests subject to the required balancing, legal obligations, or consent for a genuinely optional use where required. Browsing this notice is not blanket consent.

04

Services and disclosures.

The operator and relevant infrastructure or email providers may process information needed for their role. Cloudflare handles edge delivery and security; email you send is processed by the email providers involved. Information may also be disclosed where legally required or necessary to address abuse, protect rights, or investigate a security incident.

The application has no implemented advertising network, data-broker sale, or cross-site advertising feature. No claim is made that every edge diagnostic is disabled. Optional analytics or new integrations require a review of the notice, provider arrangements, and any necessary user choices before use.

05

Retention and deletion.

Authentication cookies expire after eight hours unless removed sooner. Other data does not have one universal automatic deletion period in this preview. Retention of correspondence, request logs, test records, and backups depends on the relevant system and operational need; a finalized customer retention schedule is not yet available.

Removing a knowledge document from retrieval clears its active content from that retrieval path. It does not automatically erase earlier task snapshots, results, audit records, or backup copies. There is no complete self-service account erasure or export workflow. Ask the operator for a review of specific information; the response will explain what can be removed, what must be retained, and any technical limits.

06

Location and transfers.

The hosted preview, edge network, and email services may process information in more than one country. This notice does not promise EU-only or US-only residency. Before a customer deployment that requires regional restrictions or international-transfer safeguards, the actual providers, locations, contractual measures, and applicable requirements must be agreed.

07

EU and EEA requests.

Where GDPR applies, you may have rights to access, correct, erase, restrict, object to processing, or receive portable data, depending on the processing and legal conditions. Consent can be withdrawn for future consent-based processing. You can also raise a concern with a competent data protection authority. The demonstration is not offered for decisions that produce legal or similarly significant effects about people.

08

US and California requests.

Privacy rights vary across US states and depend on whether the relevant law covers the activity. Where California law applies, rights can include knowing, deleting, correcting, and opting out of covered sale or sharing, limiting certain sensitive-information uses, and receiving non-discriminatory treatment for exercising rights. Applicable opt-out signals, including Global Privacy Control, must be respected where legally required. The current application does not implement advertising sale or sharing.

The application does not alter its behavior in response to the browser’s legacy Do Not Track header. That disclosure does not limit any obligation to honor a legally recognized privacy signal.

09

Make a request.

Email [email protected] with the nature of your request and enough context to locate the relevant information. Avoid sending identity documents unless a proportionate verification method is agreed. The operator may need to confirm your identity or authority without revealing another person’s data. Requests will be handled within the deadlines applicable to the circumstances; reasons and available options will be explained if a request cannot be fulfilled.

10

Children and sensitive information.

This is a business-operations demonstration, not a service directed to children. Do not submit children’s information, health records, payment credentials, identity documents, or other regulated or highly sensitive data. Contact the operator if such information may have been submitted. Security controls reduce risk; they do not eliminate it.

A direct conversation

A privacy question is welcome.

Describe the data or interaction you are concerned about. You do not need an account to contact the operator.