Skip to main content
Security overview · 日本語版 VoicePing verifies who is making a request (authentication) and whether they have permission to access the data or perform the action (authorization). These checks are enforced on the server as well as in the application interface. Updated October 22, 2026. This guide describes authentication, permissions and input validation. Internal API specifications, detection rules and limits are not published.

Accounts, sign-in and recovery

Accounts are managed per user. Standard password registration includes email verification. Verification codes have expiry, attempt and resend limits to prevent reuse and repeated guessing. Users can change passwords in account settings, or use password recovery when they cannot sign in. Reset links expire, serve a single purpose and can only be used once. Completing a reset invalidates existing sessions. Any outstanding identity checks or additional authentication are still required.
Identity and membership checks before sign-in, and expiry and prior-use checks before resetting a password and revoking existing sessions

Representative authentication and account-recovery flows.

For SSO and Google or Apple sign-in, the server validates the received authentication information. Additional email verification or multifactor authentication depends on the sign-in method and organization settings. See SSO configuration. When a member leaves or changes roles, administrators update membership and roles and remove unnecessary access. They also review user-bound API keys, connected integrations and shared organization keys.

Authorization by endpoint type

An endpoint is an API or connection that receives requests from an application or external system. Authentication and permission checks depend on its purpose.
Requests pass authentication and authorization checks before the permitted operation; requests that fail either check are rejected

Identity and data permissions are checked according to the endpoint's purpose.

Organization and data separation

Data is logically separated by workspace. Checks consider membership, role, ownership and visibility. Meetings, transcripts, summaries, invoices and time-tracking records each have their own access conditions. Administrators must also have permission to access private data. Download links for recordings and attachments are issued only after checking access to the underlying resource.
Membership, role and visibility checks allow access to authorized organization data and reject unauthorized access across organizations

Organizations and resources have separate permission checks within the same service.

Invitations, guests and meeting access

Invitations use hard-to-guess tokens. New invitation tokens are stored as hashes, have an expiry and are replaced when resent. Enterprise manual invitations also check the operator’s permissions, email/domain and plan conditions. Guests can join only the workspaces or meetings they are allowed to access. Media tokens are issued after checking participation rights, with publishing and receiving permissions set for the intended use.
Validate the invitation and entry conditions, issue a media token with required permissions, then join the meeting

Invitation and meeting permissions are checked before issuing the required media permissions.

Rotating an invitation link and removing a guest who has already connected are separate actions. Revocation must consider both links and existing connections.

APIs, AI tools and processing workers

The secret portion of an external API key is stored as a hash. Scopes define allowed operations, and configured source-IP conditions can restrict use. User-bound keys are distinguished from shared organization keys. MCP integrations for AI tools use OAuth authorization and PKCE to protect authorization-code exchange. Operations check current membership and data permissions as well as scopes.
API and MCP access checks scopes and data permissions; processing workers check caller identity and job assignment before updating results

Integrations and internal processing check the relationship between credentials and the requested operation.

Workers check their assigned job before updating a result. If workers share credentials, a credential leak may affect more than one worker.

Defenses against web application attacks

We check input, permissions, processing and output. The table summarizes the main controls and review areas.
Validate input, check permissions, process safely and limit display, response and log output

Input validation and authorization are combined with controlled processing and output.

Command-injection defenses

Command injection occurs when input runs as an operating-system command. To prevent it, we keep executable instructions separate from user-supplied data.
Check input types, ranges and permissions, separate executable instructions from data, and pass validated input to restricted processing

Examples of checks between external input and execution. Implementation and isolation coverage vary by feature.

File names, paths, URLs and settings are also restricted to what the operation allows. Even with separate arguments, values must not introduce unsafe options, arbitrary destinations or external-file references. Tests check that invalid values are rejected before execution while legitimate inputs, including Japanese file names, work. Request limits and suspicious-request detection add another layer of protection.

File validation and parser boundaries

File validation checks the actual contents as well as the name and declared type. Media and document processing also restrict storage references and parsing methods.
Validate file format, size and storage references, then restrict parser selection, external references and processing resources

Media/document validation and isolated SAML/collaborative-data parsing apply to different processing paths.

Some additional upload controls are still in testing, and coverage varies by service as of October 21, 2026. Path, URL and configuration checks are also being expanded. Format validation is not an antivirus scan, and upload paths do not all use the same checks or isolation. See software supply-chain review for controls addressing malicious code within packages or models themselves.

Request limits and records

Request and volume limits depend on the IP address, user or feature. Sign-in, verification-code resends and guest access have specific controls. Reaching a limit does not by itself indicate abuse. See the infrastructure guide for detection and blocking. Deletion checks ownership and storage locations so retries cannot delete another user’s data. Logs retain what is needed for investigation while minimizing content and credentials. Hashed identifiers are still treated as potentially identifying information.

Configuration guides for administrators

For setup instructions, see member roles, member management, IP restrictions, event logs and SSO.

Infrastructure security

Encrypted connections, server access, detection, backups and recovery.

Security operations

Monitoring, incident response, software reviews and update records.
For questions about these controls or your security review, contact support.