Privacy notice
This notice describes the Zoom integration Prasolov Slack Status, operated by Адвокатське бюро «Юридична компанія Прасолов та Партнери» (Law Office “Legal Company Prasolov and Partners”), Ukraine. It applies to employees who choose to connect their Zoom and Slack accounts.
Інтеграція перевіряє ваш поточний стан у Zoom і змінює лише власний статус у Slack. Вона не читає записи зустрічей чи повідомлення Zoom. Для відкликання доступу або видалення даних зверніться на privacy@legal130.com.
Data we access and store
| Data | Purpose and handling |
|---|---|
| Zoom profile identity | We request your user profile during OAuth connection and use its user ID and email to verify that the Zoom account matches your work identity in Slack. The Zoom user ID is stored with the encrypted connection credentials. The Zoom email is used for the identity check. |
| Current Zoom presence | We read your own presence approximately every 30 seconds while synchronization is enabled. We use it to decide whether to show a meeting status. We do not build a Zoom attendance or meeting-content history. |
| OAuth credentials | Access and refresh tokens, expiry, granted scopes and account identifiers are stored encrypted using AES-256-GCM so the backend can refresh your permission and read your presence. |
| Slack identity and status | Slack user ID, synchronization setting, the status values owned by the integration, and retry/timing state are stored to avoid changing a manual status and to safely recover after interruptions. |
| Operational information | Error types, retry state and service diagnostics are processed for troubleshooting. The integration does not intentionally log OAuth tokens or passwords. |
Purpose and authorization
We use these data only to provide the employee-selected status synchronization, verify account ownership, maintain the service and resolve support requests. Each user authorizes Zoom and Slack separately and may turn synchronization off or revoke access. The app does not request Zoom recordings, meeting content, participant lists, chat messages, audio or video.
Recipients and hosting
The backend calls Zoom to read the authorized user's profile and presence, and Slack to read and update that user's status. Hosting providers process the application and database on behalf of the operator. Authorized company administrators may access stored operational records for maintenance and support. We do not sell Zoom data, use it for advertising, or submit it to an AI model for training or inference.
Security
Public callbacks and external provider requests use HTTPS. OAuth tokens are encrypted in the database with AES-256-GCM. Authorization state is random, stored as a hash, expires after 15 minutes and is consumed once. The callback checks that the Zoom email matches the employee's Slack email. These measures reduce risk; no system can guarantee absolute security.
Retention, revocation and deletion
Connection credentials and synchronization records are retained while the integration is connected and until an administrator removes them following a verified deletion request. There is currently no automatic deletion timer for these records. Turning synchronization off pauses its use; it does not delete stored credentials. Removing the app in Zoom revokes provider access but does not automatically erase the local connection record.
To request deletion, email privacy@legal130.com or igorprasolov@legal130.com from your connected work email, identify the integration and request deletion of your connection and synchronization records. An administrator verifies the request and coordinates removal. Backups can retain copies until the applicable backup retention cycle ends; they are used for recovery, not active synchronization.
Your rights
You may request access to, correction, deletion or restriction of your personal data, object to processing, and withdraw your authorization. Contact privacy@legal130.com to exercise these rights. Identity verification may be required before data are disclosed or removed. You may also contact the relevant data protection authority, including the Ukrainian Parliament Commissioner for Human Rights.
Cookies and changes
These public documentation pages do not set cookies or use analytics. The company cabinet and third-party authorization pages have their own session mechanisms. We publish changes to this integration notice on this page.