On-premise or cloud
Install Akollo in your own data centre or use our cloud. The product is the same; the location of your data is your decision.
Security & trust
Your data, your rules, with evidence they are kept
Akollo is built for teams that need to know where their data lives. You choose where it runs, who sees what, and where its AI runs. Sensitive changes need a second person, and the record of who did what is kept for you.
Foundations
Controls built into the product, not added on
The same rules apply on every screen, in every export and through the API.
Tenant isolation
Every page, list, export and API response contains only the data of the organisation you work in. Another organisation's record looks exactly like one that does not exist.
Permissions down to the field
Roles and permission sets decide who can do what. Field policies hide, mask or lock sensitive fields. When several apply, the strictest one wins, for administrators too.
A second administrator for sensitive changes
Granting administrative rights, loosening a field policy or activating a connection waits for another administrator. Nobody approves their own request.
Audit records
Changes to privileges and configuration are written to the audit log, which administrators read under Administration › Audit records.
Read-only support sessions
When Akollo support opens a session, a banner says so. The session can read what it is allowed to see, but cannot create, change, approve or delete anything, and sensitive fields stay hidden.
Access that follows people, not spreadsheets
Who joins, moves and leaves is handled as a process with approvals, and reviewed on a schedule.
Sign-in and identity
Strong sign-in, your directory as the source
People sign in with two-step verification and, where enabled, passkeys. When you connect your directory, for example through SCIM, each joiner, mover and leaver becomes a lifecycle case. The directory alone never grants access or disables an account, and mass changes wait for an approver.
- Two-step verification with backup codes, passkeys and trusted devices
- Joiner, mover and leaver cases with approval for risky changes
- Contractor access with a sponsor and a mandatory end date
Access reviews
Ask every manager: should this access stay?
An access review records every piece of access in scope and sends each item to one reviewer, never the person themselves. Removals run through the same approval rules, and the results download as CSV or Excel with a checksum, so the file you give the auditor is the file that was recorded.
- Campaigns by unit, role, administrators, contractors or service accounts
- Reminders before the due date; unanswered access can be removed
- Every download is written to the audit log
Connections and data
Nothing leaves unless you allowed it
Connectors reach only the external hosts your administrators have allowed; with no list, they reach nothing. Credentials and API keys are stored encrypted and shown once, never again. Retention is set per kind of data, and an administrator can erase one employee's data when the law requires it.
- Outbound allowlist per installation and per connector
- Keys with scopes, expiry and optional IP ranges
- Retention periods and recorded, irreversible erasure
Akollo AI
AI that respects the same boundaries
The assistant works with each person's own permissions and never changes anything on its own.
Restricted data stays inside
Data classified as restricted is answered only by a model inside your organisation. If there is none, the request is refused rather than sent elsewhere.
Personal data masked
E-mail addresses, phone numbers, IBANs, card numbers and national ID numbers are masked before a model sees them.
Logs without content
Each AI request is logged with who asked, which feature, when and the outcome, not the question or the answer.
No guesses about people
AI never infers anyone's health, personality, mood or intent, and pay is never used in staffing suggestions.
A person confirms
Every change and assignment AI suggests waits for someone to review and confirm it.
An emergency stop
Administrators decide who may use AI, and one switch stops every AI request in the organisation at once.
Transparency
Employees can see what is recorded about them
AI and you
Every employee can open a page that explains what AI can see about them, where it runs and what is recorded.
My data
People can see and ask to correct the data held about them. Time corrections never overwrite the measured record; both figures stay side by side.
Honest status
What is in place, and what is still planned
We would rather tell you what is not finished than let you assume it is.
SIEM forwarding — planned
Sending security events to your SIEM over an encrypted connection, with alerts and incident pages for the security team, is planned.
Control mapping — planned
A control register mapping Akollo to ISO/IEC 27001:2022 Annex A and KVKK is planned. It is a mapping, not a certification.
Certifications — none claimed
Akollo does not hold a security certification today. Independent audits are planned, and we will publish the result here when there is one.
Read more about security
- Security statementOur security measures and how to report a vulnerability
- Privacy noticeHow we handle personal data on akollo.com
- KVKK noticeInformation under Turkey's data protection law
- On-premise & data residencyRun Akollo inside your own network
- Security in the docsAccount security, roles, audit records and support sessions
Questions about security
Can Akollo run entirely inside our network?
Yes. Akollo can be installed on-premise on your own infrastructure. Connectors then reach only the external hosts your administrators allow, and restricted data is answered only by models inside your organisation.
Can Akollo support see our data?
Only when a support session is opened in your organisation, and a banner shows it. A support session is read-only: it cannot create, change, approve or delete anything, sensitive fields stay hidden and the assistant accepts no new messages.
Is Akollo certified to ISO/IEC 27001?
Not today. We do not claim any certification. A control mapping to ISO/IEC 27001:2022 Annex A and KVKK requirements is planned, and independent audits are planned too.
Does the AI send our records to an outside provider?
Only to the models your administrators approve, and never data classified as restricted. That is answered inside your organisation or refused. Personal identifiers are masked before a model sees them, and AI can be switched off entirely.
How do we prove to an auditor who had access?
Run an access review. Its results download as CSV or Excel with a checksum recorded when the campaign closed, and changes to privileges and configuration are in the audit log.
Bring your security team to the demo
We walk through deployment, permissions, audit records and AI controls with the people who have to approve them.