Terms of Use (draft for review)

This is a draft for review, not an approved policy. It has no effective date and it is not legal advice.

It is written from what the product actually does, and the sections below name where each statement can be checked. 8 points in it are decisions the owner has not made yet, and each one is marked where it belongs rather than filled in with a plausible guess.

Questions about it, or about the beta, go to support@navelyra.com — see Contact.

1. The agreement

These terms are between you and OcularIT Solutions, Inc., a Virginia corporation, which operates Navelyra.

By using the beta you accept these terms. If you are using Navelyra for an organisation, you confirm you may accept them for that organisation.

Awaiting the owner’s approval — this section cannot be published until these are decided:

The registered address and company number of OcularIT Solutions, Inc.

2. The beta basis

Navelyra is in an invitation-only beta. Access is by invitation and may be withdrawn.

The beta is provided at no charge. Because no fee is paid, no refund is owed and none is offered for any period of the beta.

The beta carries no service-level commitment. The service may be unavailable, may change without notice, and may lose data if something goes wrong. Keep your own copy of anything you cannot afford to lose — the export screen exists partly for that reason.

Awaiting the owner’s approval — this section cannot be published until these are decided:

Whether the owner wishes to state an expected level of availability in place of the explicit no-commitment wording above

Where this section comes from

docs/04-product-cards.md records the beta posture
apps/web/app/(practitioner)/app/privacy/page.tsx provides the export the third paragraph points at

3. What Navelyra does, and what it does not do

Navelyra calculates chart facts with a deterministic engine, stores them as evidence, and asks a language model to draft text grounded in those facts. The model is not permitted to calculate a chart, and every draft carries the evidence identifiers it was built from.

Nothing reaches your client without you. A summary can only be delivered once you have approved the exact version that will be sent, and the API enforces that rather than relying on the screen to.

Navelyra produces reflective guidance. It is not medical, legal, financial or psychological advice, it is not a diagnosis, and it does not replace your professional judgement.

Where this section comes from

packages/db/src/portal.ts refuses to serve a version that is not approved
packages/db/src/artifacts.ts records approval against one named practitioner
apps/web/components/site-footer.tsx carries the reflective-guidance disclaimer

4. Your responsibilities

You are responsible for what you put in. Before you record a client’s data you need a lawful basis for doing so, and for any client whose data you enter you must have the consent or other authority your jurisdiction and your professional body require.

You are responsible for what you send out. Read what you are about to deliver and approve it deliberately; approval binds your name to that content.

You are responsible for your account. Keep your sign-in credentials secure, and tell us if you believe someone else has access to your practice.

Where this section comes from

docs/08-trust-safety-and-privacy.md records the consent posture
packages/db/src/artifacts.ts records the practitioner’s name against an approved version

5. Acceptable use

Do not use Navelyra to enter data you have no right to hold, to attempt to reach another practice’s data, to probe or defeat the access controls, or to resell the service.

Do not use it to produce content that is unlawful, or to present its output as a clinical, legal or financial determination.

Where this section comes from

packages/db/src/runtime-role.ts and the forced row-level security policies are the access controls this clause refers to

6. Your clients’ data

You keep whatever rights you and your clients have in the records you enter. Navelyra holds them to produce the work you ask for, and does not sell them.

This draft does not yet state the full allocation of responsibility between us for a client’s data, because that is a decision rather than a description.

Awaiting the owner’s approval — this section cannot be published until these are decided:

The controller/processor allocation to be published, and whether a data processing agreement accompanies it
The registered address and company number of OcularIT Solutions, Inc.

Where this section comes from

packages/db/src/privacy.ts describes exactly which records exist and how they are exported

7. Who owns the drafts

You own the summaries you approve and deliver to your clients, and the client records you entered.

This draft does not yet state the position on the generated text before you approve it, or on the methodology templates the product supplies.

Awaiting the owner’s approval — this section cannot be published until these are decided:

Whether the owner assigns copyright in generated drafts to the practitioner, and on what terms
The licence the practitioner grants Navelyra to store, process and transmit their content in order to run the service

Where this section comes from

packages/db/migrations/0020_authoring_templates.sql defines the supplied templates

8. Availability, changes and suspension

Features may be added, changed or removed during the beta. Access may be suspended if these terms are broken.

9. Disclaimers and liability

The beta is provided as it is, without warranties beyond those the law does not allow to be excluded.

The limits of liability are not yet decided, so this draft does not state a cap, an exclusion or a carve-out.

Awaiting the owner’s approval — this section cannot be published until these are decided:

The liability cap and the exclusions the owner wishes to publish
Whether any consumer-law carve-out is required for practitioners who act outside a business

10. Ending the agreement

You may stop using Navelyra at any time. You can export your practice’s data and ask for its deletion from the data screen.

If these terms change, the version you are reading will be replaced and the effective date stated.

Where this section comes from

packages/db/src/deletion.ts executes the deletion the second sentence refers to

11. Governing law

These terms are governed by the laws of the Commonwealth of Virginia, United States, and the courts of that Commonwealth have jurisdiction over any dispute.

12. Contact

Questions about these terms can be sent to the contact address published on the contact page.

Where this section comes from

apps/web/lib/site.ts holds the single confirmed contact address

No effective date is stated, because there is not one yet. This page will carry a date on the day an approved version replaces it.