Privacy policy

This policy describes how Jubal, Inc. (“we”) handles information in Jubal med. Where you use Jubal med through an organization — your employer, typically — that organization controls the account, decides who may access it, and can see the work done in it. Questions about your organization’s own policies go to your administrator.

Account information. Your name, email address, and the organization you belong to, together with the sign-in events needed to keep a session secure. Authentication is handled by WorkOS; we never see or store a password.

What you give the assistant. The questions you ask, the conversations they belong to, any documents you upload, the text extracted from those documents, and the memos the assistant produces. This is the substance of the product and is retained so your work is there when you come back.

A record of what the assistant did. For each research run we keep which model answered, how many tokens and tool steps it took, how it ended, and any feedback you left on the answer. We also log when the assistant could not answer from the corpus, together with the question it could not answer — that record is what tells us which regulations to add next.

Technical records. Ordinary server and delivery logs (IP address, browser, timestamps) and, when something breaks, an error report. See section 3 for what those reports deliberately exclude.

These are configuration choices in the product, not promises about future intentions:

• No product analytics and no advertising trackers. There is no analytics SDK in Jubal med. We do not track you across sites, and there is nothing to opt out of.
• Error reports carry no request contents. When something fails, our error reporting is configured to exclude request and response bodies and to skip user identity entirely. A crash report tells us what broke and where; it does not carry the question you asked or the document you uploaded.
• We do not sell personal information, share it for cross-context behavioral advertising, or hand it to data brokers.
• Your content is not used to train models. The model providers we use serve Jubal med under zero-data- retention terms, meaning your questions and documents are not retained by them after a response and are not used to train their models. We do not train models on your content either.

Jubal med answers regulatory questions. By design it does not need to know who a patient is in order to do that: a question can describe a clinical situation in general terms and get a fully cited answer about what the regulation requires. Our tier contract explains where that line sits and why.

Do not upload or type protected health information into Jubal med unless your organization has a written business associate agreement with us that covers it. Absent that agreement, the service is not offered for PHI, and sending it is a breach of the terms of service.

Where such an agreement is in place, its terms govern that information and take precedence over this policy to the extent they conflict. That includes restricting processing to model providers covered by an appropriate agreement.

We use the following providers to run the service. Each receives only what its function requires.

Data is stored and processed in the United States. Uploaded documents are held in encrypted object storage under a key scoped to Jubal med; everything moves over TLS in transit.

Access inside the product follows your organization: a project is the sharing boundary, so people who can see a project can see its conversations, documents and memos, and people who cannot, cannot. Personal research conversations stay with the person who ran them.

A small number of our staff can access customer data where necessary to operate the service or to help you with a problem. That access is role-restricted and logged.

Your content is kept while your account is active, because the point of it is to still be there. Deleted projects are recoverable for 30 days and then removed. Operational records — usage counts, error reports — are kept on shorter schedules appropriate to their purpose.

When an organization’s agreement ends, we delete or return its content on request, and delete what remains within a reasonable period afterwards except where law requires us to keep it.

We keep encrypted backups so that an outage or a mistake cannot lose your work. Content you delete persists in those backups for up to 35 days, and in a monthly copy for up to 12 months, and is then gone; backups are encrypted under keys we control, cannot be altered during their retention period, and are used only to restore service.

You can see and edit your account details in the product, and delete your own conversations, memos and documents. For a copy of your information, or its deletion, contact your organization’s administrator or write to us at privacy@jubal.law. Where your organization controls the account, we will generally direct the request to them.

Depending on where you live you may have rights to access, correct, delete, or port your personal information, and to complain to a regulator. We honor those rights without charging you or degrading the service for asking.

If we change this policy in a way that materially affects how we handle your information, we will say so — a new date at the top is not notice on its own. Questions go to privacy@jubal.law, or by post to Jubal, Inc., c/o Kenneth J. Ronan, Esq., Lavalle, Brown & Ronan, P.A., 750 South Dixie Highway, Boca Raton, FL 33432.