No. Custom stage names you typed are never auto-translated. Only the interface labels (buttons, status messages) change when switching languages.

Yes — the time data is stored inside the file. This is useful for proving work hours to clients. If you want to remove it before sharing, delete the custom properties wtt_stages and wtt_active_stage.

No. The tracker checks a single timestamp once per second and redraws a small panel. Zero impact on viewport performance, rendering, or file size.

Yes. Open Blender's Python console and read bpy.context.scene["wtt_stages"] — it's raw JSON with stage names and seconds. You can copy it into any spreadsheet or billing tool.

Time since your last save is lost. The tracker auto-flushes data before every Ctrl+S, so save frequently. The saved data survives any crash.

No. Only actual scene changes count — moving objects, editing meshes, changing materials. Orbiting, panning, and zooming the viewport are ignored. This means the tracker measures productive work, not "Blender was open" time.