Trust center
How we protect your clients' documents
What happens to a document from upload to delivery, who can see it, and the controls your organization can turn on. Written for partners, IT teams and procurement reviewers.
- Never emailed
- Encrypted in transit and at rest
- Every download logged
- Two-factor sign-in, SSO and SCIM
JukeLingo for Business keeps client documents out of email: staff upload them to a private workspace, the assigned translator works in our translator portal, and certified translations are downloaded from the workspace. Files are encrypted in transit and at rest, access is limited by role, every download is logged, and organizations can require two-factor sign-in, single sign-on, IP allowlists and automatic deletion schedules.
At a glance
Never emailed
Documents and finished translations move only through the portal. Notification emails carry a link, never a file.
Encrypted
Every connection uses TLS. Files and the database are encrypted at rest, and contact details are also encrypted field by field with AES-256-GCM.
Access by role
Six roles and workspace scopes decide who sees which orders. Billing admins see bills, not translations.
Everything logged
Downloads, policy changes, member changes, API keys and support sessions are recorded in an audit log your owners and admins can export.
Your security policy
Require two-factor sign-in by role, sign in through your identity provider, restrict access to your networks and cap session length.
Deleted on schedule
Set a retention period and the files of finished orders are deleted automatically.
How a document moves
- 1UploadA member of your team uploads in the workspace. The file goes straight to encrypted storage through an upload link that expires after 15 minutes.
- 2Safety checkOur own systems confirm the file really is a PDF or image and look for embedded scripts, attached files and other active content. Files are never sent to outside scanning services. A flagged file is held, and nothing from it is delivered until our team has reviewed it.
- 3First draftOur AI translation providers produce a first draft. Under our paid agreements they do not train their models on your documents. The names and dates you add for double-checking are never sent to them.
- 4Translation and signatureThe translator assigned to the document checks the draft against the original in our translator portal, confirms your names and dates, corrects it and signs the certification. Questions come back to your team inside the order.
- 5DeliveryThe certified translation is published to your workspace, and the people who need to know get a notification with a link.
- 6DownloadDownloads require a signed-in member with access to that order, follow your organization's security policy, and are logged with who and when.
- 7RetentionIf your organization has a retention schedule, the files of finished orders are deleted when the period ends. The order record and audit trail remain.
Who can see a document
- People in your organization whose role and workspace give them access to the order. Members see their own orders; managers, admins and owners see the team's.
- The translator assigned to that document. Translators receive documents only through our translator portal, never by email.
- A small JukeLingo operations team, when an order needs support: a question, a correction or a flagged file.
- The service providers that store and process documents to deliver your order, listed on our subprocessors page.
Support sessions are on your record
To help with setup or support, a JukeLingo administrator can view the portal as one of your members for up to 30 minutes. The session is recorded in your audit log with its reason, follows your IP allowlist, and cannot place orders, sign, or change billing or security settings.
Controls your organization can turn on
| Control | What it does | Who sets it |
|---|---|---|
| Two-factor sign-in | Requires an authenticator app for the roles you choose. | Your owners and admins |
| Single sign-on (SAML or OIDC) | Members on your organization's email domain sign in through your identity provider. It can be made mandatory. | Your owners and admins, with our team |
| Automated provisioning (SCIM 2.0) | Your identity provider adds members and deactivates them when they leave. | Your owners and admins |
| IP allowlist | Portal and API access only from the networks you list. | Your owners and admins |
| Session length | Signs members out after the number of hours you set. | Your owners and admins |
| Manager approval | Orders a member submits above an amount you set wait for a manager's approval before work starts. | Your owners and admins |
| Retention schedule | Deletes the files of finished orders after the period you choose. | Our team, at your request |
| Dedicated translators | Only translators agreed with your organization work on your documents. | Our team, at your request |
| API keys | Scoped, rate-limited, shown once and stored hashed. They stop working when the member who created them is deactivated. | Your owners and admins |
- Two-factor sign-in
- What it does
- Requires an authenticator app for the roles you choose.
- Who sets it
- Your owners and admins
- Single sign-on (SAML or OIDC)
- What it does
- Members on your organization's email domain sign in through your identity provider. It can be made mandatory.
- Who sets it
- Your owners and admins, with our team
- Automated provisioning (SCIM 2.0)
- What it does
- Your identity provider adds members and deactivates them when they leave.
- Who sets it
- Your owners and admins
- IP allowlist
- What it does
- Portal and API access only from the networks you list.
- Who sets it
- Your owners and admins
- Session length
- What it does
- Signs members out after the number of hours you set.
- Who sets it
- Your owners and admins
- Manager approval
- What it does
- Orders a member submits above an amount you set wait for a manager's approval before work starts.
- Who sets it
- Your owners and admins
- Retention schedule
- What it does
- Deletes the files of finished orders after the period you choose.
- Who sets it
- Our team, at your request
- Dedicated translators
- What it does
- Only translators agreed with your organization work on your documents.
- Who sets it
- Our team, at your request
- API keys
- What it does
- Scoped, rate-limited, shown once and stored hashed. They stop working when the member who created them is deactivated.
- Who sets it
- Your owners and admins
Encryption and storage
Every connection to the portal, the API and our storage uses TLS. Documents and translations are kept in Cloudflare R2 object storage, encrypted at rest, and the location of each file is itself stored encrypted. Order records and account data are kept in our database provider's AWS US-East region, encrypted at rest.
Contact details, such as an end customer's email address or phone number, are additionally encrypted field by field with AES-256-GCM, each with its own random initialization vector. API keys and provisioning tokens are stored only as hashes.
Logging and monitoring
Your owners and admins can read and export the audit log for your organization. It records downloads, member and role changes, security policy changes, API key and provisioning token changes, retention deletions, payment events and support sessions. Audit entries never contain document text, names or dates you entered, addresses or phone numbers.
Our operations team is alerted to failed translation jobs, payment problems and other system faults, so issues are found before they reach your queue.
AI and your documents
We use AI for the first draft only. Google and Anthropic process document content under our paid agreements, under which they do not train their models on your documents, and neither do we. A translator reviews every draft against the original, corrects it and signs the certification. The names and dates your team asks us to double-check are shown to the translator and never sent to the AI providers.
Audits and certifications
We have not completed a SOC 2 audit or ISO 27001 certification. Our controls are documented against the SOC 2 criteria, and an external audit and penetration test are on our roadmap. If your procurement process includes a security questionnaire, send it to [email protected] and we will answer it.
Report a security issue
Email [email protected]. If an incident affects your organization's data, we notify your organization's owners.
Security questionnaire answers
Do you have a SOC 2 report?
Not yet. We have not completed a SOC 2 audit or ISO 27001 certification. Our controls are documented against the SOC 2 criteria, and an external audit is on our roadmap. We will answer your security questionnaire directly.
Where is our data stored?
Order records and account data are kept in our database provider's AWS US-East region. Documents and translations are kept in Cloudflare R2 object storage. Every provider and its location is listed on our subprocessors page.
Is our data encrypted?
Yes. Every connection uses TLS, files and the database are encrypted at rest, and contact details are also encrypted field by field with AES-256-GCM. API keys and provisioning tokens are stored only as hashes.
Are our documents used to train AI?
No. Our AI translation providers, Google and Anthropic, process documents under paid agreements under which they do not train their models on your documents, and we do not train models on them either.
Are documents ever sent by email?
No. Documents and certified translations move only through the portal. Notification emails contain a link to the order, never a file.
How do you check uploaded files?
Our own systems confirm each file really is a PDF or image and look for embedded scripts, attached files and other active content. Files are never sent to outside scanning services. A flagged file is held, and nothing from it is delivered until our team has reviewed it.
Who are the translators?
Translators under contract with JukeLingo, trained to International Board of Certified Official Translators (IBCOT) standards. They receive documents only through our translator portal, and each certification names the translator who signed it.
How is access removed when someone leaves?
An owner or admin deactivates the member, or your identity provider does it through SCIM. Portal access ends at once and any API keys that member created stop working. Members are deactivated rather than deleted, because their names stay on the certifications and records they were part of.
What happens to our files after the work is done?
Without a retention schedule, files stay in your workspace so your team can download them again. With one, the files of finished orders are deleted automatically when the period you choose ends, while the order record and audit trail remain.
Can JukeLingo staff see our account?
Our operations team sees orders that need support. For setup help, an administrator can view the portal as one of your members for up to 30 minutes. Each session is recorded in your audit log with its reason and cannot place orders, sign, or change billing or security settings.
Related
Last reviewed 2026-10-27 by the JukeLingo for Business operations team.
Open a JukeLingo for Business account
We confirm your per-page rate and open your workspace. No subscription, no minimum.