Website terms of use.

Two documents are easy to confuse and important to keep separate. One governs reading a web page. The other governs software executing administrative work on patient records. They carry completely different risk, and they should never be conflated.

If the two ever conflict

A signed agreement should take precedence over a page anyone can edit. Stating that correctly, including the order of precedence across the master agreement, order form, BAA and any data processing terms, is a drafting question.

[PLACEHOLDER — confirm with counsel: precedence and conflict language between these website terms and the signed agreement set]

Acceptance

Published terms of use normally open by saying that using the site means accepting them, and describe what happens if you do not accept. This draft does not say that, because an unreviewed page should not attempt to bind anyone.

[PLACEHOLDER — confirm with counsel: the acceptance mechanism and the operative binding language, including capacity, age and authority representations if any are required]

This is a public marketing site. Read it, quote it, send it to a colleague. The intent of this section is to describe the small number of things that are not welcome, in plain terms rather than in a wall of prohibitions.

• Do not attempt unauthorised access. No attempts to reach systems, accounts or data you have not been given access to, and no circumventing access controls.
• Do not attack the site. No denial-of-service, no attempts to interfere with availability, and no distribution of malicious code through it.
• Security testing goes through a disclosure process, not a surprise. Unsolicited scanning and exploitation of a production site is not research. If you have found something, tell us. [PLACEHOLDER — confirm with counsel and the security owner: the coordinated vulnerability disclosure route, any safe-harbour statement, and whether it lives here or on the security page]
• Do not misrepresent who you are. No impersonating Praxa, its staff, its customers or its partners.
• Do not send us protected health information. Nothing on this site is a secure channel for patient data. PHI belongs in an agreed channel under a signed agreement.
• Automated collection has limits. Ordinary crawling that respects the site's robots directives is fine. Bulk scraping that degrades the service, or that is used to rebuild the site elsewhere, is not. [PLACEHOLDER — confirm with counsel: the permitted-automation wording, and the position on scraping for AI training]
• Do not use the content to imply a relationship that does not exist. Reading this site does not make anyone a Praxa customer, partner or reseller.

Consequences

What Praxa may do in response to misuse — block access, remove content, pursue a claim — needs stating in enforceable terms rather than implied.

[PLACEHOLDER — confirm with counsel: remedies, suspension rights and any reservation of legal action]

Site content

The text, diagrams, layout, code and design of this site are intended to be owned by Praxa AI, Inc. or licensed to it. Nothing here transfers ownership to a reader.

What you may do with it

Intent: you may read, print and share pages of this site for your own evaluation, internal discussion or reporting, keeping any attribution intact. Republishing it as your own, or using it commercially, is a different matter and needs permission.

[PLACEHOLDER — confirm with counsel: the scope of the limited licence granted to visitors, and whether press and analyst use needs separate wording]

Trademarks

The Praxa name and mark, and the visual identity of this site, are the company's. Nothing on this page grants a licence to use them.

[PLACEHOLDER — confirm with counsel: registration status of the name and mark, the correct notice symbols to display, and the entity name to attribute them to. Do not display a registration symbol that is not supported by a registration.]

Third-party materials

This site uses two open-licensed typefaces, Instrument Sans and Geist Mono, served from Google's font hosts under their own licences. Those licences govern the fonts; they are not affected by this page.

Feedback

If you send us an unsolicited idea or suggestion, what happens to it needs to be stated rather than assumed.

[PLACEHOLDER — confirm with counsel: feedback and unsolicited-submission clause]

Everything published here describes what Praxa is building and how it intends to work. It is written to be accurate, and it is still marketing material about an early-stage product.

• Not an offer or a commitment. Nothing on this site is an offer to sell, a quotation, a service-level commitment, or a promise that a described capability is available to you today.
• Not an offer of securities. Nothing here is an offer or solicitation to buy or sell any security or interest in the company.
• Forward-looking by nature. Descriptions of planned capabilities, timelines and workflows are statements of current intent. They can change, and some will.
• Not professional advice. Nothing on this site is legal, regulatory, compliance, coding, billing or financial advice for your organisation.
• Not clinical advice. Praxa does not provide medical advice and does not make clinical decisions. Its operators carry out administrative steps a qualified person has already decided on. Nothing on this site should be used to make a decision about anyone's care.
• External links. Where this site links out, the linked material is not ours and is not endorsed by us.

Accuracy

We try to keep this site correct and current, and content can still go stale between a product change and a page update. The operative description of what a customer is getting is the one in their signed agreement.

[PLACEHOLDER — confirm with counsel: the no-reliance and accuracy wording, and any required forward-looking-statements disclaimer]

Intent of this section: the website itself is made available as it is. Praxa does not promise that it will be uninterrupted, error-free, or free of anything harmful, and does not warrant that the information on it is complete or current.

That intent is written here in plain English on purpose. A warranty disclaimer only works if it is drafted properly and presented conspicuously, and the required form differs by jurisdiction and by the kind of visitor. Writing it in plain prose on a draft page and hoping it holds up is exactly the mistake this page is trying not to make.

For counsel

• The operative disclaimer of implied warranties, including merchantability, fitness for a particular purpose and non-infringement, with the conspicuousness treatment required. [PLACEHOLDER — confirm with counsel]
• Any consumer-law carve-outs that cannot be disclaimed for the visitor populations this site serves. [PLACEHOLDER — confirm with counsel]
• Whether product warranties need an explicit cross-reference to the signed agreement so that a website disclaimer is not read as limiting them. [PLACEHOLDER — confirm with counsel]

Intent of this section: Praxa's exposure for something that goes wrong with this website — a page that is out of date, a link that breaks, an outage — should be limited, and should be separate from its exposure under a customer agreement.

No figure appears in this draft. A liability cap is a commercial decision with real consequences, and inventing one on a design pass would be worse than leaving it blank. The same goes for the list of excluded damages and the carve-outs that survive the cap.

For counsel

• The cap, and how it is expressed for a site with no purchase price attached to it. [PLACEHOLDER — confirm with counsel: liability cap. Intentionally left blank in this draft; no amount has been decided.]
• Excluded categories of damages. [PLACEHOLDER — confirm with counsel]
• Carve-outs that survive the limitation, for example gross negligence, wilful misconduct, fraud, or anything that cannot be limited by law. [PLACEHOLDER — confirm with counsel]
• Whether an indemnity from the visitor is appropriate for a marketing site, or over-reaching. [PLACEHOLDER — confirm with counsel]
• Express statement that this section does not affect liability allocation under a signed customer agreement. [PLACEHOLDER — confirm with counsel]

Intentionally unspecified in this draft. Choice of law, venue, and whether disputes go to a court or to arbitration are consequential decisions tied to where the entity is incorporated and where it operates. Picking a state on a design pass because it sounds plausible would be a guess dressed up as a term.

• Governing law. [PLACEHOLDER — confirm with counsel: no jurisdiction has been selected in this draft]
• Venue and exclusive jurisdiction. [PLACEHOLDER — confirm with counsel]
• Whether an arbitration clause, a class-action waiver or a jury-trial waiver is appropriate, and the disclosure required if so. [PLACEHOLDER — confirm with counsel]
• Any limitation period for bringing a claim. [PLACEHOLDER — confirm with counsel]
• Severability, no-waiver, assignment and entire-agreement clauses. [PLACEHOLDER — confirm with counsel]
• The correct legal entity name and its state of incorporation. [PLACEHOLDER — confirm with counsel: entity name and incorporation details, verified against the company's own records]

When this document is finalised it will carry a real date at the top, and a revision should be visible rather than quietly swapped in. How much notice a material change gets, and whether continued use counts as acceptance of it, is a drafting question with more teeth than it looks like.

[PLACEHOLDER — confirm with counsel: change mechanism, notice period for material changes, effective-date convention, and whether a version history is published]

Until a dedicated legal mailbox exists, the general company address is the honest route. If your question is about a live engagement, the signed agreement and your usual Praxa contact are the right place to start.

[PLACEHOLDER — confirm with counsel: the legal contact mailbox to publish, the legal entity name, and the postal address for formal notices]