Terms of use
Terms of use, in plain language.
These terms cover this website, the enquiry form on it, and HABLA™ AI, the chat that sits on every page. They are written so that a reader in a hurry can take them in once, and so that a public entity can strike a clause without unravelling the rest. They begin with what HABLA is not, because that is the part that matters most.
Last updated:
Draft pending review by counsel.
Nobody who wrote these terms is a lawyer. They were drafted by the team that builds HABLA and have not yet been reviewed by a licensed attorney. Until they have, read them as a plain statement of what HABLA is and of how this website is meant to be used, not as a finished contract. A signed agreement with a customer takes precedence over everything on this page.
What these terms cover
One website, one form, one chat, and the company behind all three.
This website, its enquiry form and its chat
These terms apply to www.habla.care, to the enquiry form on its contact page, and to HABLA AI, the chat that can be opened from any page of this site. By reading the site, sending an enquiry or typing into the chat you accept them. If you do not accept them, the remedy is simple: do not use the site.
They do not govern a HABLA deployment. An organization that deploys HABLA does so under a signed agreement, and that agreement governs the deployment. A person using the anonymous experience inside a deployment meets its own boundary on its own screens, before anything is sent, and those screens govern that use.
Who we are
HABLA is developed and maintained by Pragmatic Business Solutions, LLC, of Rio Grande City, Texas. "We" and "HABLA" in these terms mean that company. You can write to us at info@pragmaticsolutions.app.
What HABLA is not
Stated first and stated plainly, because a boundary buried in a waiver protects nobody.
Not an emergency service, and not monitored in real time
HABLA is not watched while somebody uses it. Nobody at HABLA reads what arrives as it arrives, no alarm goes off anywhere, and nothing reaches anyone faster because of what it says. If you or someone else could be hurt today, this website and this product are not the way to get help. In the United States, call 911 in an emergency, or call or text 988 to reach the Suicide and Crisis Lifeline at any hour.
The crisis resources HABLA ships, including 911 and 988, are in every plan and cannot be removed by a customer.
Not clinical care
HABLA does not diagnose anyone, treat anyone, or create a relationship with a healthcare provider. It offers plain language for what a person is carrying and, if they choose, a way to reach a human they selected. It does not refer, book an appointment, notify a clinician, escalate, or follow up. HABLA never acts on a person’s behalf: if something leaves HABLA, the person pressed the thing that sent it, and knew what they were pressing.
Not an investigation, compliance or monitoring tool
HABLA is organizational listening: it shows an organization which topics keep reaching the surface, counted as activity rather than as people. It is not designed to find out who selected something, to screen anyone, to assess conduct or policy compliance, or to watch an employee or a student. An organization that needs any of those needs a different product, and we would rather say so here than let a buyer discover it later.
Who does what
HABLA is a conduit. The customer is the responder. These clauses say which party owes what.
No duty to monitor, review or act on content
HABLA does not review the anonymous experience for content, and it cannot: the anonymous experience stores no free text and no identifier, so there is no text to read. What it counts is which topic was named, how often, and in which deployment.
When a person chooses to leave anonymous mode and ask to be reached, their request is held for the one recipient they picked, at their own organization. HABLA’s systems do not read that request, assess it, or forward it to anyone the person did not choose. HABLA takes on no duty to monitor, review, moderate or act on what a person writes there.
The customer responds
The organization that deploys HABLA decides who its named recipients are, what response window they state, and how they answer. A recipient replies through that organization’s own means, not through HABLA. The response window shown to a person is what the organization said it usually takes, and it is the organization’s to keep.
Mandatory reporting is the customer’s obligation
A recipient who learns something through a contact request that the law requires them to report — for example, a school employee who learns of possible abuse — has that duty under the law that applies to them and to their employer. The duty belongs to the recipient and to the customer. HABLA’s systems do not read, assess or forward the request, and HABLA takes on no reporting duty of its own.
The customer is responsible for telling its recipients what their duties are before naming them as recipients. Whether and how the existence of such a duty should be disclosed to the people a deployment serves is a question for the customer and its counsel, not one these terms answer.
Placements are the customer’s, and a placement is not a location
The customer decides where its posters, QR codes and links are placed and keeps them accurate. HABLA records which placement was used, never where anybody was: a placement is a property of the material, not of the person, and it does not establish that anyone was physically anywhere. HABLA does not verify a physical location and never claims one.
What you may not use it for
These are the refusals HABLA is built around. They protect the people who use it and they protect HABLA, in the same clause.
Four answers that are fixed, whatever is offered for them
A customer may not use HABLA, or anything it produces, to do any of the following. HABLA will not build a way to do them at any price, and an attempt to do them is a breach of these terms and of the customer’s agreement.
- Attempt to identify an individual who used the anonymous experience.
- Combine HABLA output with HR, student-information or any other data to re-identify a person.
- Use HABLA as a disciplinary, performance-management, investigation or compliance instrument.
- Ask for raw activity data, for a suppressed value, or for a lower privacy floor.
Using this website
You may not attempt to defeat the rate limit or the spam controls on the enquiry form or on HABLA AI, send anything through either of them that is unlawful, abusive or not a genuine enquiry, press HABLA AI to act outside what this page says it does, probe or attack the site or the systems behind it, or copy the site at scale by automated means. The site sets no cookie and carries no analytics script, session replay, fingerprinting or ad pixel, and you may not add tracking to it by any route.
This website and your enquiry
Operational terms: what the site does, what the chat does, and what happens to a message you send us.
The enquiry form
The form on the contact page is the business enquiry channel. It composes what you type into one email and delivers it to the shared inbox at Pragmatic Business Solutions, where a person reads it and replies; we aim to reply within two working days. HABLA’s own systems keep no copy, and the form is a different system from the person-side contact handoff inside a deployment. What holds your message afterwards is a mailbox, and we delete it if you ask.
What happens to an enquiry, and to a chat conversation, in full
HABLA AI, the chat on this site
HABLA AI answers questions about the product, how it works, what it costs and the company behind it, and it answers them from HABLA’s own published documents. It is not a support channel, not advice, and not a route to any service: a personal, health or workplace matter is answered with one fixed sentence naming 988 and 911, and no message is sent and nobody is contacted. It asks for no personal details, and if you choose to ask to be contacted it takes a name, a work email, an organization and what you want to discuss, shows you what will be sent and to whom, and sends it only after you confirm — to the same mailbox the enquiry form reaches.
To write each reply, the conversation and HABLA’s product documentation are sent to Anthropic, the company that runs the Claude model. The chat lives on this website and not inside a deployment: it does not touch the anonymous experience or the person-side contact handoff. HABLA keeps no copy of a conversation once the reply is written, sets no cookie and stores no identifier. Please do not type personal, health or workplace details into it. The acceptable-use rules above are the enquiry form’s and they apply to the chat in the same words.
Information, not advice
Everything on this site describes HABLA and the reasoning behind it. It is not legal, clinical, security or procurement advice for your organization, and it is not a substitute for reading the agreement you would sign. Where a page states something you can check against the architecture, check it — the privacy page says which claims are verified and which are not yet.
Availability
We make no promise about the uptime, performance or availability of this website. Nothing is measured yet that would let us make one honestly, and we say so rather than imply it.
People under eighteen
Students are a named audience. This section describes exactly what happens and stops there, because the rest is a question for counsel.
The anonymous experience
The anonymous experience asks for no account, no name, no email address and no free text, and stores none of them. What it stores is nine values about an interaction — which deployment, placement, audience pack, topic, date, hour and language, how often, and how much the statement fit — with two records beside that row. None of it is about a person. That is an architectural fact rather than a promise, and it is the position we would defend.
The contact step is different
A person who chooses to leave anonymous mode gives a way to be reached — an email address or a phone number — and, if they want, a name, and writes a message to one named adult at their own organization. That request is stored in the customer’s contact record, separate from the anonymous side with no key between the two, usually for 90 days, with the recipient, the response window they were shown and their acknowledgement that this is not an emergency channel. The person is told all of this on screen before they send.
A student giving a name and an email to reach a named adult at their school is a different act from using the anonymous experience, with different obligations, and it lands in the customer’s own record. Whether and under what consent students may use that step is for the customer, its privacy officer and its counsel to decide, in the agreement, before a deployment reaches students. These terms do not decide it.
Commercial terms
The clauses a public entity most often has to strike or replace. Each stands on its own; striking one leaves the rest intact, and a signed agreement takes precedence over all of them.
Intellectual property
The site, the HABLA name and mark, the software, the drawings and the writing on this site belong to Pragmatic Business Solutions, LLC. You may read, print and quote the site for the purpose of evaluating HABLA. The topics, resources and configuration a customer writes into its own deployment stay the customer’s.
For a public entity. Public records law may require a public entity to disclose what it received from us. Nothing here is intended to prevent that.
No warranty
This website is offered as it is. We make no promise that it is error-free or that it will be available at any moment, and we make no promise about the results of using HABLA beyond what the agreement with a customer states.
For a public entity. A public entity may be unable to waive a warranty implied by its own state’s law. Where that is so, the implied warranty stands and this clause yields to it.
Limitation of liability
To the extent the law allows, we are not liable for indirect, incidental or consequential loss arising from the use of this website, and our total liability arising from it is limited to $100. Liability for a deployment is set in the customer’s agreement, not here. Nothing in this clause limits liability that the law does not allow to be limited.
For a public entity. A public entity may be barred by statute from agreeing to a cap below a stated minimum. Where that is so, the statutory minimum applies and this clause is read to that minimum rather than struck.
Indemnity
If you use this website or the enquiry form in a way these terms prohibit and a third party makes a claim against us because of it, you will cover the cost of that claim.
For a public entity. A public entity is often barred by its constitution or statute from agreeing to indemnify a vendor. Where that is so, this clause does not apply to it and the rest of these terms stand.
Termination and what happens to data
We may withdraw access to this website from anyone who breaches these terms. For a deployment, termination and its notice periods are set in the customer’s agreement. What HABLA holds for a customer has a documented retention rule for each store — a contact request usually 90 days, an administrator account 90 days after it is deactivated, an action record the contracted history, the sealed figures of a closed reporting period seventy-two months, and the register of which report versions were sealed one hundred and forty-four months — and anonymous activity is held as counters that are never handed over as raw records. The sealed figures run for six years because that is the longest life this system gives a record that could cite them: a figure lasts exactly as long as the longest-lived decision able to point at it, and not one month more. They are totals a report already published, above the reporting thresholds, and the anonymous counters they were drawn from are deleted on their own separate and shorter clock. That last pair is deliberate: the register outlives the figures by six years and holds none of them, so a decision record citing a sealed version can be answered with when those figures went rather than with nothing at all. Six years is also the furthest out such a decision record can itself be dated, because the database refuses a longer date rather than relying on the program that sets it. What happens at the end of a period today depends on which row it is, and saying which is the only accurate version. A contact request past its date is hidden by the database itself from every part of HABLA that could reach it — unreadable, and still there. The other rows on that list have no such boundary: an administrator account past its ninety days, an action record past its contracted history, and a sealed figure past its seventy-two months all stay reachable until something deletes them. Deleting is a separate program that has to be run by hand, and nothing schedules it. The narrow accounts those programs connect as have been set up, so a missing credential is no longer what stops them; what stops them is that nothing schedules them. We would rather say that than describe a schedule that does not exist.
The retention rule for every store
For a public entity. A public entity’s records-retention schedule may require it to keep what it received from HABLA for longer than HABLA keeps it. That obligation is the entity’s and is met from its own copies, not from HABLA’s stores.
Changes to these terms
When these terms change, the new version is published here with a new date at the top, and a change that matters is named there rather than left for you to find. Continuing to use the site after a change means you accept the changed terms. A customer’s signed agreement does not change when this page does.
For a public entity. A public entity usually cannot be bound by a change it did not sign. For a customer, the agreement controls and this page does not amend it.
Governing law and venue
These terms are governed by the laws of the State of Texas, and a dispute about this website is heard in the courts located in Starr County, Texas.
For a public entity. A public entity outside Texas is often barred from agreeing to another state’s law or venue, and a Texas public entity may have a venue rule of its own. Where that is so, the entity’s own law and venue apply and this clause is replaced in the agreement.
Assignment
You may not transfer your rights under these terms to anyone else. We may transfer ours to a successor that takes on HABLA and the obligations in these terms with it, and we will publish the change here.
Events beyond our control
We are not responsible for a failure to provide this website that is caused by something outside our reasonable control, such as a network outage, a natural disaster or an act of a public authority.
If a clause cannot stand
If a clause of these terms is found unenforceable, or is struck by a public entity that cannot agree to it, that clause alone is removed and the rest of these terms stand. The clauses were written separately so that this is possible.
What takes precedence
A signed agreement between a customer and Pragmatic Business Solutions, LLC takes precedence over these terms wherever the two differ. These terms take precedence over anything else on this site that reads like a term.
Trademarks
HABLA™, P²HI™, Privacy-Preserving Human Intelligence™ and the promise “Know what. Never who.™” are trademarks of Pragmatic Business Solutions, LLC. They are marks in use rather than registered marks: no registration has issued for any of them, and we do not write them as though one had. The notice at the foot of every page is that claim and nothing more — we make it ourselves, no office has examined or approved anything, and it is not a finding by anyone. You may use these names to write about HABLA™. You may not use them as your own, or in a way that suggests we endorse you or are connected with you.
Questions about these terms
They reach a person, not a queue.
Write to us
Questions about these terms, a clause your organization needs struck or replaced, or a request for the agreement a deployment is governed by: write to info@pragmaticsolutions.app or use the contact page. A person reads it and replies.
The terms are the last line of defence, not the first.
What protects the people who use HABLA is the architecture: no account, no free text and no identifier in the anonymous experience, and floors under every published figure. A terms page that describes that accurately is worth more than one that disclaims broadly, because it can be checked.