Trust & how it works

How an answer is allowed to exist.

BeforeMe answers only from what a person published and approved. Everything else — who may see what, whether something can proceed, whether it is still current — is decided by rules you can read, not by a model’s confidence.

What never changes

Be callable.
Not exposed.

01Only explicitly published information becomes callable.
02The owner approves every line of published state.
03The model never decides who is allowed to see what.
04Ambiguity goes to the owner instead of being guessed.
05Minimum necessary disclosure — never more than the question needs.
06Capability before raw state: “you can proceed”, not the threshold.

Every answer shows its work

Outcome: One of five: Answered, Proceed, Use this, Needs the person, Not known.
Answer: Only sentences the person published — or BeforeMe saying plainly that it cannot answer.
Freshness: When the person last confirmed it and when it is due for review. Past that date the answer is marked stale, so old information never looks current. Nothing without a review date counts as fresh for more than 90 days.
Source: Which published state it came from — the subject and the kind of state — or a pre-approval rule whose limit never leaves the private side.
Scope: Who that state was published for (public, verified contacts, project members) and who the page takes you to be — from your personal link, never from anything you type.

What you get back

Not a chat reply. A result you can act on.

Every answer says what kind of result it is, how fresh it is, whose published state it came from, and who that state was published for.

Answered
From what the person published and approved.
Proceed
Yes, you can go ahead — by a published approval or a pre-approval rule. The limit itself stays private.
Use this
The approved document, page or form to use.
Needs the person
Only they can decide. Your question goes to them, with the context attached.
Not known
Nothing published covers it, so nothing is guessed.

Private state · what you said

“I'll fly to Lisbon tomorrow morning, stay at X hotel, meet the supplier at 2pm. The supplier proposal is approved but the price still needs confirmation...”

BeforeMe safety compiler

Travel→ availability only
Locationstays private
Private schedulestays private
Status→ callable
Pricing · pending→ callable, unconfirmed

Safe callable state

Availability Contacts

Unavailable until 6 PM.

Supplier proposal Project members

Approved to proceed.

Pricing Project members

Pending confirmation.

State in. Capability out.

The people you work with never need to see the flight, the hotel, or the meeting.

Minimum necessary disclosure

Noah · project member

“Can we move forward at $18,000?”

Private state

never leaves this side

answered in 40 ms

This request can proceed without additional approval.

The threshold never leaves the private side. Not in the answer, not in the prompt, not even in the database credentials that answered — the service that replies cannot read it. It can only ask a yes-or-no question.

What is the minimum this person needs to move forward?

Deterministic authorization

Who may see what is decided in code and in the database before any model is involved. Rows you may not see are never loaded, so no prompt can reveal them.
The service that answers you connects to the database with credentials that cannot read private state at all. It can only ask narrow yes-or-no questions, such as whether an amount is within a pre-approval.
A model, if one is configured, may only phrase an answer from the rows already selected — and its wording must pass an output guard, or the published sentence is used as-is. It can make an answer more cautious, never less.
A pre-approval that is unconfirmed or past its review date grants nothing: the question goes to the owner.
Every question and answer is written to an append-only audit log the owner can review and correct.

Safety is not a page in the footer

Three layers, and none of them is a promise.

Human safety

Better habits, not more anxiety.

While you review

“Others need to know you’re unavailable — not where you are.”

BeforeMe shows what it detected and what the other person actually needs. You decide.

Product safety

Safe by default — the defaults are the product.

No live location
No full calendar
No internal thresholds
No searching everything you know
No inbox or chat ingestion
Capability before raw state

Technical security

The model never decides who is allowed to see what.

Identity→Relationship→Object→Scope→Permission→Allowed state→Model

item this caller may seereaches the model

item this caller may not seestopped at Permission

identity · permission · scope · expiry · audit · rate limits · tenant isolation · deterministic authorization

Give AI access to your entire life.

GmailWhatsAppDriveCalendarSlack

BeforeMe doesn’t read your inbox or crawl your chats. Nothing enters unless you publish it.

You decide what AI knows.
You decide what others can call.

Confidence, not confidence tricks

Confirmed

Supplier proposal: approved to proceed.

verified · fresh

Not yet confirmed

My latest verified information is from Sep 16.

answered, with the caveat

Comes to you

Pricing needs a personal decision. I’ve passed this on.

escalated in 1 second

Escalate ambiguity rather than guess.

Most questions end at BeforeMe. The ones that genuinely need a person — a price, a commitment, something nobody published — arrive with the context already attached. You step out of the loop; exceptions bring you back.

Privacy & data handling →