If you are the one using it
You do not have to know what to call it yet.
HABLA™ is for the moment before you are ready to explain anything. There is no account to make and no app to install. You choose from plain-language statements until one sounds like what you are carrying, and HABLA offers words you might use to begin a conversation — with someone you choose, if and when you decide to.
Three steps
- SPEAK — Recognize what you are carrying in plain language.
- SAY — Get words you can actually use to begin the conversation.
- CONNECT — Choose a human or resource when you are ready.
You can stop at any of them.
Three steps, and you can stop at any of them.
Each step is short, and none of them asks you to explain yourself. What the whole thing is built to do is give you words — not a finding about you, not a score, and not a place your name has to go before you have decided you want it there.
Leaving is offered as plainly as continuing. Stopping is not a failed session — there is no session. Nothing identifies a return visit as the same person, and what a tap leaves behind is a topic, a placement and an hour, never anything about you.
SPEAK
Recognize what you are carrying in plain language.
SAY
Get words you can actually use to begin the conversation.
CONNECT
Choose a human or resource when you are ready.
In your own terms
Finding it. You read short, ordinary statements — the kind a person actually says — and pick the ones that fit. You can type a few words to narrow the list; that search runs on your device, and what you type never leaves it. You are never asked to write your situation out, because anonymous free text is not a thing HABLA has.
Saying how much something sounds like you. If you want to, HABLA asks how much a statement fits you — a little, quite a bit, very much. That is how much it sounds like you, not how bad you are. HABLA has no severity scale, no screening instrument, and no clinical threshold anywhere in it, and it never averages your answer into a number about you. What it becomes is one of three shares of the reportable activity for that statement — and if any of the three falls below the floor, that breakdown is not shown at all.
Getting words. What comes back is language you could use — an opening sentence for a conversation you have been putting off — and the points of help your organization has listed, alongside crisis resources that are always present.
Deciding, or not deciding. Reaching out is a separate, deliberate step that you take or skip. Skipping it is a complete and ordinary way to use HABLA.
What the anonymous experience never stores
- Name
- Phone
- IP address
- Device identifier
- Fingerprint
- Session identifier
- Cookie identifier
- GPS or location
- Free text
- Diagnosis
- Risk score
How the separation is built, and what each domain holds.
What it does keep: which deployment, which placement, which audience pack, which topic, which date, which hour, which language, how many, and how much the statement fit — nine fields on one row, with two more records kept beside that row rather than on it, both of them counters: how many topics an interaction involved, and how often a topic was named the most important. Those are real records, and HABLA does not pretend otherwise. Not one of them is a fact about you.
Nothing is ever reported from a group small enough for a name to be guessed from it: never below ten taps, and never for a group of fewer than fifty people.
Counts like these are also combined with other organizations' counts — at a size where no organization can be picked out — into sector and national figures. Nothing about you travels with them, because nothing about you was there.
If you choose to ask someone to contact you, you give a name and a way to reach you. That is a separate system, with no key back to anything anonymous — and the two limits above are what stop a small group from being reported at all, so a name you give here does not lead back to a topic you tapped.
Two systems, drawn below this paragraph: one holds what was tapped, the other holds what you chose to send. No key was ever created between them — and where very few interactions share an organization, a placement and an hour, the two floors on the reporting side are what keep that handful from being published at a size where it could start to point somewhere.
Two paths that never meet
Anonymous activity and voluntary contact are separate paths. HABLA created no key that would join them, and no role can read across the two.
-
HABLA records nine fields on one row: which deployment, which placement, which audience pack, which topic, which date, which hour, which language, how many, and how much the statement fit. Two records sit beside that row rather than on it, both of them counters: how many topics an interaction involved, and how often a topic was named the most important. It does not record a person.
-
The event joins an aggregate. Nothing recorded identifies who tapped, so there is nobody to look up later.
-
Reports show which topics keep reaching the surface, where the count clears the privacy floor.
-
The two sides of this drawing are different shapes because they are different systems. Nothing on the anonymous side was declared to match a row on the contact side, and no role can read across the two. What the database engine stamps on its own rows is named on the privacy page rather than argued away here.
-
A separate, deliberate choice. Nothing about the anonymous experience requires it.
-
This is the only place HABLA holds identifying information, and the person typed it knowingly.
-
A person the organization designated. HABLA never contacts anyone on the individual’s behalf.
If you decide to ask someone to contact you
This is the one point where your name can enter HABLA, and it only happens because you chose it. Before you send anything, the screen is required to show you three things: who will receive it, how long a reply usually takes, and that this is not an emergency channel. If a reminder or a second recipient is part of the route, they are named on that same screen, before you decide — so the choice you make is the whole of it, not the part you were shown.
Nothing leaves HABLA that you did not send. What you tapped anonymously is not attached to your message, is not shown to the person receiving it, and cannot be looked up from it.
What HABLA will not do, including for your own good.
A system that quietly did any of these would be more useful to an organization and worse for the person using it. Each one is refused in the architecture, not left to good intentions.
- HABLA is not monitored in real time. Nobody is watching this as you use it, and nothing you tap raises an alert.
- HABLA never contacts anyone you did not choose, and never acts on your behalf — it does not refer you, book anything, notify a clinician, or escalate. If a reminder or a second recipient is part of what you are sending, you are told so on the screen before you send it.
- HABLA is not a route into clinical care. It offers language, resources, and — if you choose it — a way to reach a person you named yourself.
- Nothing you do here produces a score, a level, or an assessment about you. There is no such field to write one into.
- The topic search runs on your own device: what you type to find a topic never leaves it.
Crisis resources are permanent.
Your organization can add its own points of help. The crisis resources HABLA ships, including 911 and 988, are always there and cannot be removed — not by a customer, not by a contract, not by an administrator.
Reaching one produces no organizational record of any kind: no count, no trend, no row in any report, and no notification to anyone. HABLA is not monitored in real time, and it will not tell your organization that you looked.
The fair way to read this page is next to the other one.
Everything an organization receives is described in the same detail, on its own page. If the two pages did not fit together, one of them would be marketing.