What we store
Last updated 25 September 2026
HooqBi keeps eight tables. This page lists all eight and what is in each one, because a product that tells you your network is yours should be checkable rather than trusted.
Signing in
Your email address is held by our authentication provider so we can sign you in, along with the times you signed in. There is no password, because there is no password field. You sign in with a code sent to your email. Supabase generates and checks the code; Resend delivers the email.
Your profile
What you type. Shown to anyone you connect with.
One line about what you do.
Optional.
The city you type. Nothing is read from your device.
Optional, free text.
The tags you add. These are what the matching reads.
Nothing, one of ours, or one you upload. An uploaded photo is re-encoded on our server before it is stored, which removes the camera data written into it, including the GPS coordinates most phones record. It is kept as a 512-pixel square and served from a public address, so anyone holding the link can open it, in the same way as the profile it sits on.
Your website, LinkedIn, Instagram, Facebook and YouTube, if you add them. They appear on your profile to anyone who opens it.
If you add one. It never appears on your profile and is never put in an email. Where you have one, your profile says a number exists without showing it. It is shown in exactly one place: after somebody accepts an introduction to you, the two of you see each other’s numbers on the handoff screen, so you can start the conversation somewhere that is not HooqBi. Nobody else ever sees it.
The code behind your QR. It is treated as a credential, not as profile data: read access is revoked from every account including other members, and even you read your own through a function rather than by selecting it.
A switch for turning your profile off. The column exists and is currently always on; there is no screen for it yet.
Who invited you, if somebody did.
When the profile was created and last changed.
Connections: the people you have met
One row per connection, holding both people, who initiated it, how it formed and the date it formed. It formed one of three ways: a code scanned in person, a signup through your profile, or an introduction HooqBi routed. There is also a column for where you met, which nothing writes to; no screen asks for it yet.
Both of you see the same row. Neither of you can see the other person’s other connections, and there is no screen anywhere that would show them.
Notes: what you wrote about them
A private note and a relationship strength from one to five. Only the person who wrote it can read it. The other person never sees it. Nobody else does either.
Objectives: what you are trying to do
The title and description you type, how urgent it is, its status, when it expires, the reason you give if you abandon it, and the dates it was stated and closed.
Four more fields sit on the same row: what you are looking for, an industry, a location and the tags to search for. You do not type those. A model reads what you wrote and fills them in, and they are shown back to you on your objective card so you can see what was understood. See what a model sees.
Activations: the requests that went out
Which objective it came from, who the bridge was, who it reached, the relevance score, the reason shown to the recipient, whether they accepted or declined, the reason they gave if they gave one, and the timestamps, including when the email actually went out.
The row also records who decided the request was worth sending: the matching, or a person in the middle naming somebody they know. It holds that person’s answer, whether they helped, said not now, or took their name off. It holds what they typed when they named somebody, which no screen shows to anyone. Last, a count of how many times checking the match was attempted, so a request that keeps failing stops being retried.
Briefs: the sentence written about a candidate
One sentence per request, written by the model, saying why the request is worth reading. One per request, replaced if the request is checked again.
This is the only place in HooqBi where a description of a person is stored rather than assembled when someone opens a screen. The person in the middle and the person it describes may read it; the person who asked may not, until that person has accepted. No screen displays it yet. It is written and, for now, read by nobody.
Invites: somebody not on HooqBi
If a person in the middle thinks of someone who has no account, they can write down that person’s name, and HooqBi produces a message and a link for them to send.
This is the only place HooqBi holds anything about somebody who has not signed up, and it holds a name. No phone number, no email address. The person inviting them already has those, and the message goes from their own phone. Only the person who typed the name can read it, not the person who asked, not anyone else, enforced in the database. The invite expires after thirty days, and can be used once, by the one person it names.
Outcomes: whether it worked
Whether the conversation actually happened, how useful it was from one to five, and what happened if you wrote it down.
What a model sees
HooqBi sends text to a model twice. It is Claude Haiku, run by Anthropic, in the United States. Anthropic says it does not train models on what is sent through its API.
When you state an objective. Sent: the title and description you typed, and a list of the tags people on HooqBi have added to their profiles: the hundred most common, lowercased, most common first, with nobody’s name attached to any of them. Returned: what you are looking for, an industry, a location and the tags to search for. Those four are the line on your objective card.
When a route is found to somebody. Sent: your objective, and up to twenty-five descriptions of people it might fit. Each description is a headline, company, location, bio and tags, under a number. Not sent: names, account ids, email addresses, photos, phone numbers, or anything about who is connected to whom. The model is given a number and can only answer with that number, so it is not able to name anyone. Returned: one sentence per person, which is the brief above.
Nothing else is ever sent. Your connections are not sent, your notes are not sent, and no message you write anywhere is sent, because HooqBi does not carry messages.
What we do not store
- No contact list. There is no import, no sync, and no permission request for your address book.
- No contact details for anyone who is not a member. When somebody invites a person who has no account, HooqBi keeps the name they typed and nothing else. The message goes from their own phone, using the number they already had.
- No message content. Conversations happen wherever you have them; HooqBi does not carry them.
- No location beyond the city you type. Nothing is read from your device or your network, and the camera data inside an uploaded photo, GPS included, is removed before the file is stored.
- No behavioural tracking. This site runs no analytics, no advertising and no third-party scripts.
- No payment details. Nothing is charged during early access.
- No passwords.
Where it lives
The database, the authentication records and the uploaded photos sit with Supabase in Frankfurt. Photos are kept as files rather than in any of the eight tables. The application runs on Microsoft Azure in Germany West Central.
Two things leave the EU. Every email HooqBi sends, your sign-in code and the two introduction emails, is delivered by Resend, which processes in the United States, so Resend handles your email address. The two model calls above go to Anthropic, in the United States. Neither receives anything beyond what is described above.
Getting it out, or getting rid of it
Email team@hooqbi.com and we will send you everything above as a file, or delete it. Both are done by hand at the moment. Self-serve export and deletion are not built yet, and we would rather say so than imply a button exists.