Data export and switching

Head offices and franchise partners can export all data they are allowed to see in Symiko at any time – also during the contract and free of charge. The export is in the application under Export data (head office: settings, partners: profile). It is built in the background; when it is ready you receive an email and can download it for seven days with your second factor. It contains structured files (JSON and CSV) and the stored original files.

Everyone can also download their own data under “My data”, optionally with their documents.

• You can request a switch to another provider or to your own infrastructure with a notice period of at most two months.
• A transition period of 30 days follows. During it we keep operating Symiko unchanged, support the export, inform you about known risks to business continuity and maintain the level of security.
• If 30 days are technically not feasible, we tell you within 14 working days, with reasons; the period is then at most seven months.
• After the switch or the end of the contract you can keep exporting for at least 30 days. We then delete all data of your system completely and confirm the deletion.
• We charge no fees for export and switching.
• For questions about switching and your exit planning contact hello@symiko.de.

• Everyone exports what they are allowed to see: head office does not receive the personnel files of its partners’ employees – each partner exports these itself as employer. Whistleblowing reports are only available to the handlers of the reporting channel.
• Passwords, sessions, second factors: Credentials are not portable and would endanger access.
• Invitation, unsubscribe, confirmation and device codes, API keys and webhook secrets: Secrets that grant actions (e.g. accept an invitation, pair a device, fetch data).
• Push subscriptions and app device tokens: Technical delivery identifiers without use outside Symiko.
• Time clock pairings, PIN hashes, device receipts: Device security data; the recorded times themselves are included.
• Mail queues (including webhook deliveries), rate counters, idempotency receipts: Internal operating state without business content.
• Search indexes and text extracted from PDFs: Derived; the originals (chapter text, PDF) are included.
• Content of generated hygiene reports: Derived from the included raw data; period and checksum are included.
• Data outside one's own permissions: The scope follows the database access rules: partners see their locations, head office its system but no other employers' personnel files; anonymous answers stay anonymous; whistleblowing cases only for designated handlers.
• Data of other franchise systems and operator data: Tenant separation.

• JSON: UTF-8, one JSON array of objects per file; keys = field names below; missing values as null.
• CSV: UTF-8 with BOM, semicolon separated, header row with field names, CRLF line endings. Text quoted (inner quotes doubled); text starting with =, +, -, @, tab or carriage return gets a leading apostrophe (protection against spreadsheet formulas). Numbers and true/false unquoted, empty values empty, lists and JSON as JSON text. The JSON file is authoritative.
• Files: dateien/<storage area>/<path> – original files (documents, images, videos, photos) as far as the exporting person may open them; paths match the fields in the data.
• Overview: manifest.json – time, system, role, list of all files with row count, fields and description; LIESMICH.txt/README.txt explain the structure.

All export files with fields and formats (Art. 26(b) Data Act). Machine-readable as register.json.