Frequently asked questions

You do. Your company data stays yours: you can export it at any time, and after the contract ends it is exported on request and then deleted. This is set out in the terms (AGB) and the data processing agreement (AVV) — both in German.

In the EU. The database runs in a European region, encrypted in transit and at rest, and every company is strictly separated from others at the database level (row-level security).

OBELISK runs in the browser and as an installable app (PWA), built to work offline — data entry works even with poor signal. Synchronisation and office features need an internet connection.

About two minutes: create your company, invite the team by e-mail, start. No installation, no server, no training days — the field app is deliberately kept simple.

The field app works with big tiles and clear paths. The interface is available in German, Romanian and English — switchable per user.

Yes, in two ways: payroll data is exported in the real import formats for DATEV Lohn & Gehalt and DATEV LODAS (plus Quick-Lohn and Lexware). For the tax office, OBELISK also generates DATEV posting batches (EXTF) from outgoing invoices.

Yes. Tenders are read as GAEB (X83/P83/X81) and priced bids are returned in GAEB format; measurements come in via DA11. E-invoices are generated as XRechnung and ZUGFeRD and validated against the official tools (KoSIT validator, veraPDF).

During the pilot phase: nothing. Anyone starting now uses OBELISK free of charge and keeps preferential terms when regular pricing begins. The planned packages are published transparently on the pricing page (in German).

Yes — as soon as you keep employee data in OBELISK, the GDPR requires a data processing agreement with us. The template is available at /avv, ready to print (in German); you receive the final version when regular contracts begin.

Then you leave. During the pilot phase you can cancel at any time; export your data beforehand or receive an export on request — after that, the data is deleted.