FLOOR 0
Your data stays on your own server
- 08
KVKK tooling
delete history, user deletion chain, data export, retention cleanup.
- 09
A licence that needs no internet connection
if it cannot be verified, the system does not run.
Security and KVKK
Security is the design itself.
Your data stays in-house; the AI sees a summary, not your table; every answer shows its source. Design evidence below.
One gate
One door for what leaves
The result of your question reaches the AI as a summary; individual records are shared only with administrator consent, and only approved content leaves. If you want zero external traffic, you need an on-premises model, closed external channels, closed cloud connections and network exit measurement.
What leaves
What leaves, channel by channel?
Everything that goes out is written out channel by channel, and you switch each one on yourself.
| Channel | What leaves |
|---|---|
| 01Text chat | Your question, business context and summary go to the cloud AI; rows are shared only with administrator consent and with personal data hidden. With an in-house model this flow drops to zero. |
| 02Real-time voice | Your microphone audio goes directly to the voice provider; what the assistant uses is hidden, and the session is verified with a signed assurance. |
| 03Telegram and email | Only the final answer text leaves, and you are the one who switches this channel on. |
| 04Answers to external systems | The answer returned to an outside assistant leaves; an access key is mandatory, personal data is scanned and only read permission is granted. |
| 05Connecting to in-house systems | Connects only to targets on your corporate network; it opens no new cloud connection. |
| 06Fabric and Power BI | The Power BI query runs in your own environment; it connects only to two approved addresses. |
For nothing to leave at all, language, document and voice work must run in-house, external channels and cloud connections must be closed, and outbound network traffic must be measured. This is verified separately for each deployment.
Principles
Six fixed principles
These principles are not negotiable in product decisions.
- 01
Authority narrows; it never widens
no component can widen another's authority.
- 02
Approval is not a tool
every write intent goes through the same draft route and waits for human approval.
- 03
Rules cannot be overridden
you decide what is allowed on each channel, and those rules cannot be changed from above.
- 04
When unsure, it stops
the action runs once the required context is verified, and a request missing what it needs is rejected.
- 05
If a channel or model changes, it appears on screen with its reason.
- 06
Transitions break nothing
architecture changes are made without breaking these principles.
Layers
Nine layers of defense
Each layer works with the others, not alone.
FLOOR 0Your data
FLOOR 1–2Identity and access
FLOOR 3Masking
FLOOR 4–5Approval and records
FLOOR 6One gate
FLOOR 1–2
Everyone sees only the data their role allows
- 01
Identity and session
passwords are stored with strong hashing, and a disabled user's sessions end instantly.
- 02
Authorization
a category-based permission catalogue, group-based access, menu and screen gates, report rights delegation.
FLOOR 3
Personal data is hidden automatically
- 04
Personal data hiding
consistent hiding for the whole turn, reversed in the answer; log records count as outgoing too.
FLOOR 4–5
Every action asks you first, and is recorded
- 05
Audit trail
questions, reports, actions, digital-assistant runs, external-software calls and Power BI queries are recorded with data hidden.
- 06
Approval chain
draft, permission check, second approval, execution and record.
FLOOR 6
You decide what leaves
- 03
One gate leads out
the AI sees a summary, not your table, and every result travels within the scope the turn approved; your whole database is never copied out.
- 07
Outbound network
leaving to external addresses passes through a single checkpoint; outbound calls cannot be pointed at internal network addresses, connections to your internal systems are defined separately, and external notification addresses are limited to the approved list.
KVKK and license
KVKK tooling is inside the product
Delete my history, the user deletion chain, data export, retention cleanup and backup verification are built into the product. Example questions that contain personal data are not added to what is sent to the AI.
- Delete my history
- User deletion chain
- Data export
- Retention clean-up
- Backup verification
A licence that needs no internet connection
The licence is verified without an internet connection and is time-limited. The system runs only with a valid licence; if the licence cannot be verified, it stops.
A half-day pilot and a live demo on your own data
Discovery typically takes half a day, deployment half a day to a day, and the pilot two to four weeks. Fill in the form for a quote, or write to [email protected] directly.