1. Service model and scope
BeKord operates a shared hosted communication service. Customer workspaces are logically separated by application authorization and scoped database queries; they are not represented as separate physical servers or separate customer databases.
This Notice covers information processed by the BeKord service, public pages, account workflows, and support and security requests.
2. Information processed
Account data includes username, email address, credential hashes, verification state, security settings, profile information, and account preferences. BeKord never stores your plaintext password.
Service data includes workspace membership and roles, channels, messages, direct messages, reactions, invitations, moderation and audit events, file metadata and uploaded files, integration settings, voice or call session metadata, and records needed for unread state and delivery.
Operational data includes session records, login history, request and security logs, health and performance metrics, provider-access audit events, support or security tickets, data-request records, and backup records. Voice and video media is transported through the BeKord-operated LiveKit service; BeKord does not advertise end-to-end encryption of customer communications.
3. Why information is used
BeKord uses information to create and secure accounts, deliver messages and media, enforce workspace permissions, prevent abuse, operate integrations, send transactional email, provide support, investigate incidents, maintain backups, and improve reliability.
BeKord does not sell customer content or account data. BeKord does not use private message bodies for advertising.
4. Customer and provider access
Workspace owners and administrators can access and manage information according to their workspace roles. Other customers are denied access unless membership, direct-message participation, or a specific permission allows it.
Routine provider support uses reason-bound, workspace-scoped, time-limited grants that expose only workspace identity and diagnostic counts. Those grants do not unlock messages, files, email addresses, or media tokens. Infrastructure and database administrators retain technical power outside the application layer; emergency use is restricted by administrative controls, change or incident records, backups, host logging, and independent review.
5. Service providers and subprocessors
BeKord uses infrastructure hosting providers for compute, network, storage, and backup capacity; Turbify for domain, DNS, and business-mail services; and SMTP2GO for transactional email relay. These providers process only the categories needed for their service. The BeKord-operated LiveKit, PostgreSQL, Redis, and object-storage components are service components rather than third-party hosted applications.
Provider identities or functions may change for security, reliability, or capacity. BeKord will update this versioned Notice before a material new processing category is introduced.
6. Retention and deletion
Active account, workspace, and message data remains while needed to provide the service or until an authorized customer action or completed deletion request removes it. Expiring sessions, verification codes, password-reset records, operator grants, and similar security records use their configured expiry controls. Security, audit, abuse, and data-request records may be retained when needed to demonstrate authorized actions or protect the service.
A verified deletion request has a seven-day recovery window. BeKord targets completion within 30 days after that window unless a documented ownership, safety, fraud, legal-preservation, or technical-integrity issue requires delay. Backup copies are retained as complete recovery sets and are not edited record by record. Deleted data may remain in a backup until that backup is retired; any restored copy remains subject to the deletion record and is not returned to ordinary active use.
7. Customer controls
Authenticated data controls let an account holder request a structured JSON export of account, profile, settings, memberships, owned-workspace structure, authored message content, and attachment metadata. They do not disclose another person's account secrets or private content merely because it was visible in a conversation.
Workspace owners can request a structured workspace export and can request workspace deletion. Attachment exports identify stored-file metadata but do not place raw binary files into the JSON response. Account and workspace deletion requests require a current password, exact confirmation text, and a recovery period; cancellation requires re-verification.
8. Security and contact
BeKord uses encrypted transport, credential hashing, role and tenant authorization, restricted administrative paths, monitoring, backup verification, and audited support access. No security measure eliminates all risk.
Privacy questions, data requests, and suspected security issues can be submitted through the Service & Security Center. Do not include passwords, access tokens, private keys, or unnecessary customer content in a report.