Question 1

How do you handle strings that reference unreleased IP?

Accepted Answer

We sign MSAs and NDAs before any ingestion. Your footage and strings sit behind per-project access controls, and your IP is never shared, sold, or used to train external systems.

Question 2

What if we don't have gameplay footage yet?

Accepted Answer

Ship us a build, screenshots, or static UI mockups. The more context we have, the better the translation lands. We never block a project on footage availability.

Question 3

How do you handle patch cycles and live-ops string drops?

Accepted Answer

Default turnaround is 14 days from string ingestion to an approved pull request. Incremental string drops from patches and content updates flow through the same pipeline, mapped against the style guide we already built for your game. Rush turnaround is available when a trailer or launch window demands it.

Question 4

What languages do you support?

Accepted Answer

30+ languages including Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish (LatAm and EU), Brazilian Portuguese, French, German, Italian, Polish, Russian, and Arabic. Full list on request.

Question 5

Who are your linguists?

Accepted Answer

Native speakers who play games in the genres they review. RPGs go to RPG players. Tactics games go to tactics players.

Question 6

What engines and workflows do you work with?

Accepted Answer

Native support for Unity, Unreal, and Godot. We sync directly with GitHub, Perforce, and UVC. If your setup is custom, we integrate with anything that has a file format and a pull-request concept.

Question 7

How is this different from a traditional localization agency?

Accepted Answer

Agencies hand your producer a spreadsheet and quote in opaque tiers with setup fees and per-language minimums. We work directly from your repo and your gameplay footage at a flat $0.10 per word. Agencies take four to six weeks and need a coordinator on your side. We take fourteen days and we are the coordinator.

Question 8

Can you work around our milestone calendar?

Accepted Answer

Yes. Most of our studios plan ingestion around content locks and patch cadences. Tell us when strings freeze and when the pull request has to land, and we schedule the linguist review around your milestone, not ours.