Before you decide.
Frequently asked questions about security, data processing and enterprise use.
22 answers
Which security certifications does oNabu hold?
oNabu’s information security program is supported by independent assurance and an additional GDPR compliance assessment:
SOC 2 Type 2 — Audited by Atom Assurances LLC for the May–November 2025 observation period. More than 60 controls covering security, access control, change management and other areas were tested, with no exceptions reported.
ISO 27001:2022 — Certified by TNV in March 2026. The risk-based information security management system includes a commitment to continuous improvement.
GDPR compliance assessment — The GDPR control framework and processes were reviewed, and the assessment findings documented.
Certification documents are available at trust.onabu.ai.
How often are audits performed?
oNabu maintains a four-layer audit model.
| Layer | Mechanism | Frequency |
|---|---|---|
| Layer 1 | Independent SOC 2 Type 2 audit | Annually |
| Layer 2 | ISO 27001 surveillance audit | Annually |
| Layer 3 | Continuous automated control monitoring with Sprinto | Real time |
| Layer 4 | trust.onabu.ai — public transparency center | Continuous |
Do you perform penetration testing?
oNabu’s published plan provides for annual external penetration testing by an independent accredited security firm from Q2 2026. Continuous static code analysis (CodeQL), dependency scanning (Dependabot), and SOC 2 Type 2 / ISO 27001 audits are also part of the process. Contact the Trust Center for the latest completed report and its availability.
How is data encrypted?
In transit: all data transfers are encrypted using TLS 1.2+. Legacy protocols are not permitted.
At rest: stored data is encrypted using AES-256. Encryption keys are rotated through managed key services and maintained within a separate trust boundary.
Application layer: user authentication tokens are protected by additional encryption layers.
Where is my data hosted?
oNabu runs on Google Cloud Platform (GCP). GCP is covered by oNabu’s DPA. Please contact our sales team for specific data residency requirements.
How is access control managed?
All internal access is managed through role-based access control (RBAC) based on least privilege. Multifactor authentication (MFA) is required for production access. Separate credentials are used for privileged access and reviewed annually. Access logs are retained for auditing.
How long are meeting recordings and transcripts retained?
Raw meeting transcripts are held in temporary storage and automatically deleted within 3 days. oNabu does not retain raw MP3 audio permanently; it is used only for speech-to-text conversion and then destroyed.
Only analysis outputs, such as Discovery Framework reports and meeting summaries, are retained for the active service period. On contract termination, customer data is destroyed through cryptographic erasure; a deletion confirmation report is available on request.
Which subprocessors handle personal data?
Subprocessors are third-party providers that may process customer data on oNabu’s behalf to deliver the service.
| Subprocessor | Purpose |
|---|---|
| Google Cloud Platform (GCP) | Infrastructure hosting and database |
| Microsoft Foundry | LLM analysis and report generation |
| Recall AI | Meeting recording and transcription |
For the current complete list, visit trust.onabu.ai.
Is my data used to train AI models?
No. oNabu contractually requires that customer data is not used for model training, fine-tuning or product improvement by its AI services. This commitment is implemented through the DPA, service terms and enterprise data processing terms with Microsoft Foundry and other relevant AI subprocessors.
How are international data transfers protected?
Transfers outside the EU/EEA are safeguarded through Standard Contractual Clauses (SCCs) under GDPR Article 46. Transfer impact assessments (TIAs) are conducted, and subprocessors are bound by DPAs.
For customers in Türkiye, oNabu signs contractual annexes for data transfers under the KVKK and related regulations, including a DPA and equivalent transfer safeguards.
What personal data does oNabu process?
oNabu follows the principle of data minimization. The personal data processed includes:
Names and corporate email addresses for authentication and meeting matching; Jira/Azure DevOps ticket content for project analysis; meeting transcripts processed temporarily and deleted within 3 days; and messaging-channel content where integrated.
oNabu is not intended to receive special-category personal data and asks customers not to upload it.
Does oNabu evaluate individual employee performance?
No. oNabu is an enterprise management assistant that provides team- and process-level insights, not individual performance evaluations.
oNabu is not designed for automated decision-making or employee performance scoring.
How can data subjects exercise their rights?
oNabu maintains procedures for requests for access, correction, deletion, portability and objection to processing. Requests can be sent to [email protected].
How are customers notified of a data breach?
oNabu’s documented Personal Data Breach Notification Procedure distinguishes between these roles:
As a processor, oNabu notifies the customer without delay after identifying a personal data breach and provides technical information about its scope, affected data categories, measures taken and root-cause analysis.
In the limited cases where oNabu acts as a controller, the relevant supervisory authorities are notified within the applicable statutory deadlines.
What are your SLA commitments?
The SLA commitment for core services is 99.5% monthly uptime.
| Priority | Initial response | Resolution target |
|---|---|---|
| P1 — Critical | 1 hour | 4 hours |
| P2 — High | 4 hours | 24 hours |
| P3 — Medium | 1 business day | 3 business days |
| P4 — Low | 2 business days | 5 business days |
Under the KVKK, is oNabu a controller or a processor?
For enterprise customers, oNabu acts as a data processor. The customer organization is the controller, and oNabu processes personal data only on its instructions.
oNabu signs a Data Processing Agreement (DPA) with each customer.
Can we sign a Data Processing Agreement with oNabu?
Yes. oNabu offers a standard DPA to enterprise customers. For Turkish organizations, the DPA is structured in accordance with Articles 8 and 9 of the KVKK. Contact [email protected] to request it.
Is data transferred abroad, and how is KVKK Article 9 addressed?
oNabu runs on GCP. Some subprocessors, such as Recall.ai, may be based in the United States, so limited categories of data may be transferred abroad.
Cross-border transfers under KVKK Article 9 are assessed under applicable mechanisms, such as adequacy decisions, appropriate safeguards, standard contracts or undertakings approved by the Board.
oNabu determines the applicable transfer mechanism with Turkish customers during contracting. Contact [email protected] for details.
How are VERBİS registration requirements managed?
Where oNabu processes enterprise customer data solely on the customer’s instructions, VERBİS registration obligations belong to the customer organization acting as controller.
oNabu maintains documentation of processing activities to support customers’ registration processes and shares it on request.
Who provides privacy notices when employee data is processed?
The customer organization, as controller, is responsible for providing employee privacy notices. Contact [email protected] for available documentation about oNabu’s processing activities.
Data flow documentation detailing the data processed
Technical documentation explaining platform features and data processing logic
Draft information sets to help customers prepare privacy notices for their own employees, available on request
Who reports a personal data breach under KVKK Article 12?
The customer organization acting as controller is responsible for notifying the Personal Data Protection Board. oNabu, as processor, informs the customer without delay and provides available information about the breach to support that process.
Informs the customer immediately and without delay upon detecting a breach
Provides a technical report on the scope of the breach, affected data and measures taken
Prepares the documents needed for the customer’s notification to the Board
What technical and organizational safeguards does oNabu use?
Technical safeguards include TLS 1.2+ in transit, AES-256 at rest, multifactor authentication, least-privilege RBAC, firewalls and network segmentation, automated security monitoring, comprehensive external penetration testing (planned annually from Q2 2026) and automatic deletion of raw transcripts within 3 days.
Organizational safeguards include SOC 2 Type 2 assurance (zero exceptions), ISO 27001:2022 certification, a personal data breach notification procedure, staff confidentiality commitments, annual security awareness training, DPAs with all subprocessors and supplier risk assessments.