Trust is enforced, not promised.
PelQi works close to inboxes, clients and production systems. These are the controls it runs under, in the product today.
Nothing consequential without a person.
Reads run, actions wait
PelQi can read and prepare freely. Anything that sends, changes or submits waits in Approvals with why, what will happen and the evidence.
The right person decides
Viewers cannot approve. Only the owner of a mailbox can send from it. On approval PelQi checks again, acts once and confirms the result.
A stop switch
An owner can stop every responsibility in a workspace at once, and approved actions stop with it.
Kept apart by design.
Sealed workspaces
Every request is checked against workspace membership. To anyone outside, a workspace does not exist, and roles decide who can see, change or approve.
Home and Work stay separate
Personal PelQi and Work have separate memory. Nothing from someone’s household reaches the business, or the other way round.
An isolated browser
PelQi’s browser runs in its own container that can reach the public internet and nothing on a private network. It reads; it never types or buys.
Not a shared AI app.
PelQi runs as its own service. Workspaces, memory, documents and sign-ins stay inside that deployment, and the AI model is reached through a business interface that does not train on what you send it.
Your data, under your control.
Sign-ins encrypted
Connected accounts are stored encrypted and never shown again. Disconnecting, or leaving a workspace, removes them.
Restricted documents
An owner can keep document text away from the AI model entirely; PelQi then points to the right document instead of quoting it.
No training on your words
Your conversations, mail and documents are never used to train anyone’s model. Work Memory refuses passwords, keys and card numbers.
A record of everything.
Activity
Everything done in a workspace, by people and by PelQi, newest first, including who approved what.
Evidence kept
Each run keeps its sources and goal checks. In Varqeni, every investigation is sealed against edits for thirty days.
Read-only on platforms
On pipelines and infrastructure every identity PelQi holds can only read, proved when it is created. The principles
Questions about security?
Join the waitlist and ask. We will walk you through how PelQi is deployed and what it can and cannot reach.