How Lokbox protects and isolates your client data and browser tasks.
Lokbox prepares read-only results from defined sources. You decide what happens next.
Swiss company. Hosting in Switzerland (Zurich).
Your client data and documents are stored in data centers in Zurich (Supabase). The compute power for executing tasks is provided in Switzerland (Infomaniak). Web and database are operated from Zurich; a copy remains in Frankfurt (DE) until 22 August 2026.
For current Claude processing, Lokbox uses AWS Bedrock's EU geographic inference profile with Frankfurt as the primary source Region. AWS may process requests in the European destination Regions documented for that profile. For the current Claude processing path through Amazon Bedrock, AWS states that model providers do not have access to customer prompts or completions. Any retention by AWS depends on the configured Bedrock data-retention mode and AWS's documented exceptions.
Workspace access is enforced server-side and monitored by CI checks; additional database policies are in progress.
Nothing is sent without your approval. You make any final submission yourself. Lokbox does not initiate payments.
For ePortal services of the FTA that require a login, AGOV is gradually replacing CH-Login. Lokbox tracks the AGOV cutover date of 31 October 2026 as a deadline object per company and mandate. AGOV does not use traditional passwords, but hardware-bound login factors. Logins and 2FA remain with you. You sign in yourself and retain approval of every step (human-in-the-loop); the AI never sees your input.
Logins and 2FA remain with you. You enter them yourself in the live browser; the AI never sees your input.