2. Information We Collect
2.1 Account Information
When you create an account, we collect your name, email address, and organisation name. Authentication credentials are managed securely using an enterprise-grade identity provider.

2.2 Meeting and Call Data
The core function of Cybenta involves joining your sales calls as a bot participant. When you enable this feature, we collect:
- Audio recordings of meetings you explicitly authorise the bot to join
- Real-time and post-call transcripts of those meetings
- Participant names and identifiers as provided by the conferencing platform
- Meeting metadata (title, duration, date, platform)
You are responsible for obtaining any legally required consent from all meeting participants before enabling this feature. Cybenta provides tools to help you notify participants, but compliance with applicable recording consent and privacy laws remains your responsibility.

2.3 Calendar Data
If you connect a Google Calendar or Microsoft Outlook calendar, we access:
- Event titles, times, locations, and attendee lists for events on your calendar
- Meeting links to enable automated bot joining
- Acceptance status of calendar invitations
We access only the minimum calendar data necessary to provide scheduling and auto-join features. We do not read, store, or analyse calendar events unrelated to meetings you have authorised.

2.4 Knowledge Base Content
If you upload documents or connect cloud storage or productivity integrations, we store and process the content of those files to power the AI knowledge search features. This may include proprietary business documents, sales materials, and competitive intelligence.

2.5 Usage Data
We collect information about how you use the Service, including:
- Features accessed and actions taken
- Session duration and frequency
- Error logs and diagnostic information

2.6 Billing Information
Payment processing is handled by a PCI-DSS compliant payment processor. We do not store full payment card numbers. We retain billing metadata such as subscription status, plan tier, and customer identifiers.

2.7 Desktop Application Data
If you use the Cybenta desktop application, it connects to our service over an encrypted connection. The application processes data locally and transmits only the data necessary for the AI features. We do not capture screen content outside of active, authorised meeting sessions.

2.8 Zoom Integration Data
When you connect Zoom through the Cybenta Zoom App, we collect your Zoom user ID, display name, and meeting identifier via the Zoom Apps SDK. We use this solely to authenticate your session and correlate real-time coaching data with the correct meeting. We do not store Zoom access tokens beyond the duration of the active session. Zoom OAuth refresh tokens are stored encrypted and used only to maintain your connected integration.