Loading...
Loading...
Encryption
Traffic to Lexel Translate uses TLS 1.2 or higher. Stored account data, translation history, and document artifacts are encrypted at rest.
Loading...
We use essential storage to operate Lexel Translate. With your permission, we also use analytics, advertising, and marketing technologies. Read our Cookie Policy.
Loading...
Security
Explore the diverse security controls offered by Lexel Translate including scoped access, tenant isolation, configurable retention, and request tracing.
Lexel Translate does not currently hold any third-party security certifications. This page describes controls that exist in the product.
Traffic to Lexel Translate uses TLS 1.2 or higher. Stored account data, translation history, and document artifacts are encrypted at rest.
Your data is never used for training without your permission.
Organizations, teams, API keys, jobs, glossaries, usage, and other product records are scoped to the owning account.
History, deletion behavior, and document flows run on customer-visible retention controls.
Requests, jobs, usage events, support debugging, and status workflows can be traced through request IDs and related platform records.
What Lexel protects
Concrete controls that map to customer questions, not abstract architecture labels.
API keys
Raw API keys are shown once and stored as hashed values.
Customer text
Product text moves through scoped request paths and is kept out of general analytics processing.
Glossaries
Glossaries are tenant-owned resources with automatic versioning.
Documents
Large document workflows run inside worker-owned execution and storage boundaries.
Webhooks
Customer callbacks are configured through explicit webhook profiles with signed delivery.
Admin and support access
Support and internal access is permissioned, minimized, and tied to operational review.
Data Lifecycle
Review the five-stage process through which all translation requests are processed in Lexel Translate.
Lexel validates the request, authenticates the session or API key, and resolves tenant scope before translation work begins.
Rate limits, quotas, glossary ownership, request context, and retention-related behavior are applied.
Requests are dispatched to the specified route and executed either in realtime or queued for worker-owned execution with scoped storage.
The platform records usage metadata for billing, debugging, quota enforcement, and abuse handling.
History, artifacts, and related records follow customer-visible retention and deletion behavior, subject to platform limits.
Operational security
Rate limits and abuse controls
Browser quotas, API-key rate limiting, invalid-key throttling, and anti-abuse controls help reduce noisy traffic and basic misuse.
Request tracing
Request IDs and related usage records support debugging, escalation, and customer-facing incident investigation.
Public incident visibility
Customers can check status and incident information on the public status page.
Security reporting
Share the facts needed to investigate a vulnerability, sensitive data exposure, or other security issue quickly and safely.
1. Provide your information
Let us know your contact information so we can follow up as needed.
2. Estimate the issue severity
Mark the report as low, medium, high, or critical based on the potential impact to customer data, access control, or service integrity.
3. Provide a clear summary
Explain what you found in one sentence. A short summary helps our team triage the issue before deeper review begins.
4. Share details
Describe what could be exposed or abused as well as the steps needed to reproduce the issue safely. Be sure to include any other information that may help confirm the issue, such as logs, request IDs, or timestamps.
Submit a security report
Include the affected route, request IDs, severity, reproduction details, and any evidence that helps triage the issue safely.