Draft — written from how Halqa actually
behaves, but not yet reviewed by a lawyer. The registered company name and address are still
to be added.
Security & data safety
What is protected — and what is not claimed.
A security page that oversells is worse than none at all, so this one says plainly where the protections end.
Last updated 14 August 2026
One telephone, one code, one person.
Getting in
A one-time code to your telephone number. There are no unverified accounts on Halqa.
Duplicates
Your first profile is asked for nothing. A second profile that looks like the same person must show a government ID before it can post, message, offer or appear anywhere — and the first profile is told.
Sessions
You can see where your account is open and end any of them.
If you lose the phone
Tell support at once and the sessions can be closed while you recover the number.
The single decision most of this rests on.
Almost every unpleasant thing that happens on a local app starts with somebody getting hold
of a number they had no business having. So Halqa carries the conversation itself. A message
goes through Halqa. A call goes through Halqa. An order shows a name and a code, never a
number.
What this buys you
A woman can order atta, hire a plumber, sell a sofa and book a school van without a single one of those people ending up with her telephone number. That is not a setting she has to find — it is the only way Halqa works.
Every share knows when it stops.
Location
Two minutes, one hour, until I arrive, or until I stop it. The person asked chooses; the asker cannot extend it.
A home address
A day pass that dies at its hour, by default. The permanent code is revocable in one tap.
A call line
Closes two hours after the order or trip that justified it.
A family's emergency grant
48 hours, and it does not renew itself.
A cart's position
30 minutes, to the one customer who asked.
The pattern is deliberate. A permission that has to be remembered and revoked is a permission
that stays on for ever, so in Halqa the ending is set at the beginning.
Said exactly, with nothing rounded up.
In transit
Everything between your telephone and Halqa travels over an encrypted connection (HTTPS/TLS).
Calls
Directly between the two telephones where the network allows it, encrypted in transit by the WebRTC protocol itself.
Messages
Not end-to-end encrypted today.They are encrypted in transit and stored on Halqa's servers so they reach your next telephone. If that changes, this line changes with it.
At rest
On managed Postgres infrastructure with row-level rules, so a row is readable only by the people it belongs to.
Photographs
In Halqa's own storage, one folder per person, readable by exactly the circles the post reached.
The alarm leaves. The picture stays.
Intrusion alarms
Ring the household's own telephones first. Nobody outside the home has been told anything yet.
Home pictures
A picture taken inside a home never leaves the home, under any circumstance the app allows.
An empty house
Halqa will never tell a stranger, or an unverified visitor, that a home is empty.
The gate register
Not shown to residents, not to moderators, and not to us.
Colony alarms
These deliberately ignore your privacy circles — a colony in danger is the one rule Halqa breaks its own privacy for, and it says so on the screen rather than doing it quietly. They end after three hours.
The honest limits.
Do not rely on Halqa for these
It cannot dial emergency services for you. An alarm reaches the people you chose. In a real emergency, telephone the emergency number yourself.
The AI photograph score is not proof that a picture is real or generated. It is an estimate, and it says so every time it appears.
Vouching is not an identity document and Halqa never pretends that it is.
Satellite position is not floor-accurate. Halqa will not claim to know which floor of a building somebody is on.
Messages are not end-to-end encrypted today.
Tell us before you tell anybody else.
If you find a way to see something you should not, or to do something as somebody else, write
to [email protected] with enough detail to reproduce it. We will confirm within 72
hours and tell you when it is fixed.
Please do not test against other people's real accounts, do not take more data than is needed
to show the problem, and give us a reasonable window before publishing. Nobody who reports in
good faith will be pursued for it.