Legal
The controller within the meaning of the General Data Protection Regulation (GDPR) and the German Federal Data Protection Act (BDSG) is:
Booklera UG (haftungsbeschränkt)
represented by die Geschäftsführerin Nadine Glamngiw
Landsberger Straße 155, Haus 1, 80687 München
Germany
Email: n.glamngiw@booklera.de
Booklera is a SaaS platform for commercial providers from the following industries: Tradesperson, Online shop, Fitness studio, Haulage, Office, Booklera Todos. Personal data is processed either as an independent controller (registration, contract processing, technical logs) or as a processor on behalf of the registered tenants (end-customer and employee data of the tenants).
When you register on booklera.de, we collect the following data: name, email address, password (stored bcrypt-hashed with rounds = 12, never in plain text), company name, chosen subdomain slug and the chosen industry (see section 1). This data is required to provide our SaaS service and to perform the contract. The legal basis is Art. 6(1)(b) GDPR (performance of a contract). Your user account and the associated data are stored for as long as the contract exists. After termination, the data is deleted within 30 days unless statutory retention obligations prevent this (see section 10).
To prevent abusive registrations (e.g. spam accounts or sign-ups with third-party email addresses), we additionally store the IP address and browser identifier (user agent) of the registering device during registration. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in the security of the service and the prevention of misuse). This information is not merged with other data sources, is not used for advertising or profiling and is deleted together with the user account. For early misuse detection, the platform operator is informed internally by email about every new registration. The tenant email mailbox created during registration is only enabled for sending after the email address has been confirmed (double opt-in).
As a SaaS platform, Booklera processes data on behalf of the registered tenants. The tenants' end customers book appointments or classes or request work services via the respective tenant website. In doing so, personal data of the end customers (name, email address, telephone, address, booking details, payment data where applicable) and — for trade tenants — employee data (see Section 2.4) is collected and processed.
In this relationship, the respective tenant is the controller within the meaning of the GDPR, and Booklera acts as a processor pursuant to Art. 28 GDPR. Processing takes place exclusively on the instructions of the tenant and within the framework of a data processing agreement (DPA). The legal basis is Art. 6 (1) (b) GDPR (performance of the contract between end customer and tenant) in conjunction with Art. 28 GDPR.
When you visit our website, technical access data is automatically stored in server log files. This includes: IP address, date and time of access, page accessed, browser and operating system used, referrer URL. This data is not merged with other data sources and serves exclusively to technically secure operations and detect misuse. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in the security of the service). The log files are automatically deleted after 14 days at the latest.
On our public pages (booklera.de, booklera.com) we count page views to learn which pages are visited and where visitors come from. Only daily counters are stored: date, page visited, referring website, campaign parameters of the address, the country derived from the IP address, device type and browser language. The IP address itself is not stored; to count unique visitors, a hash of the IP address and browser identifier with a random value that changes daily is created for the current day and deleted at the end of the day. No cookies are set and no external analytics services are used. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in measuring the reach of our website).
For trade tenants, Booklera processes the following employee data as a processor — the tenant is and remains the controller for this data and must ensure lawful processing (e.g. informing employees, works agreement where applicable):
This data is stored tenant-isolated (see Section 7) and is only visible to the respective tenant. Retention follows statutory obligations (generally 6 years under Section 257 HGB for payroll-relevant data, longer periods for tax-relevant or GoBD-relevant data — see Section 10).
If a tenant operates an online shop, Booklera processes the data of that shop's end customers as a processor. The controller within the meaning of the GDPR is and remains the shop operator; they must inform their customers and provide their own privacy policy for their shop. The following is processed:
Transmission to customs authorities for deliveries outside the EU: If a shop operator ships goods to a country outside the European Union, the platform generates a commercial invoice and a customs declaration (form CN23). These documents contain the name and address of the recipient, the contents of the shipment, its value and, where applicable, the customs tariff number and country of origin. They are attached to the parcel and presented to the customs authorities of the dispatch and destination countries. This transmission is legally required to comply with customs and export regulations (Art. 6 (1) (c) GDPR) and cannot be avoided for an international delivery.
For trade tenants, the system can process special categories of personal data pursuant to Section 193 SGB VII (statutory accident insurance reporting obligation), in particular:
The legal basis for this processing is Art. 9 (2) (b) GDPR in conjunction with Section 193 SGB VII (fulfilment of the employer's social-law reporting obligations). The official accident report is generated as a PDF and can be sent by the tenant to the responsible employers' liability insurance association — the sending itself is carried out by the tenant on their own responsibility. The accident file is retained for 10 years (GoBD Sections 146, 147 AO as well as internal retention obligations of the insurance association) — see Section 10.
Booklera uses a granular cookie consent system. On the first visit to the website (both booklera.de and every tenant subdomain), a modal is displayed in which the user can decide per cookie category. Consent is logged in an audit trail (browser ID, IP, user agent, page, timestamp) and can be changed or revoked at any time via the footer link “Cookie settings”.
bl_session — Login session (HttpOnly, Secure, SameSite=Lax). Lifetime: 8 hours.bl_csrf — CSRF protection token. Lifetime: 8 hours.bl_platform_session — Platform admin session (internal only). Lifetime: 8 hours.bl_flask_session — Short-term storage for notices after an action, for form entries after an error and for security identifiers of forms (registration, shop customer account). Lifetime: until the browser is closed.site_lang — The selected language of the website, once a language has been chosen. Lifetime: 1 year.bl_cookie_consent — Storage of the cookie consents themselves. Lifetime: 1 year.bl_trial_dismiss, bl_firmendaten_dismiss, bl_2fa_dismiss — Marker in the admin area that a notice (end of the trial period, missing company details, recommendation of two-factor sign-in) stays hidden. Lifetime: 7 days.sf_kunde — Sign-in to the customer account of an online shop. Lifetime: 30 days.sf_cart — Shopping cart of an online shop. Lifetime: 30 days.fb_portal — Login session for the customer portal of a business, only on its own web address. Lifetime: 8 hours.__stripe_mid, __stripe_sid — Stripe cookies for online payments and fraud prevention. Provider: Stripe Payments Europe Ltd., Dublin. Used only if the user makes an online payment and has previously consented to “Stripe cookies”. Without consent, online payment is not possible; alternatively, on-site payment can be offered.We do not use tracking cookies, analytics cookies or marketing cookies. There is no user tracking by third parties. The audit trail of consents is stored for a maximum of 3 years pursuant to GDPR Art. 7 (1) (accountability); upon revocation, the old entry is marked with the time of revocation and a new entry with the current values is created so that the history remains fully traceable.
Security- and compliance-relevant actions (login, logout, password change, 2FA activation/deactivation, finalization of construction diary and safety documents, cancellations, backdating attempts) are logged in an audit log with the following data: tenant ID, user ID, action, old value, new value, reason, IP address, user agent, timestamp.
The audit log is immutable pursuant to GoBD Section 146 AO — the database triggers block UPDATE and DELETE on the audit table. Retention: 10 years pursuant to Section 147 AO (see Section 10). Legal basis: Art. 6 (1) (c) GDPR (legal obligation — tax and compliance duties) and Art. 6 (1) (f) GDPR (legitimate interest in security and misuse detection).
Booklera offers AI-supported functions. They run exclusively on locally operated language models of the Qwen 2.5 series (for texts, for the chat and for image recognition of receipts), which run entirely on our own server in Germany (Hetzner Online GmbH). No data whatsoever is transferred to external AI providers such as OpenAI, Google, Anthropic, Microsoft or other third parties. Following an internal review procedure, the models are regularly checked against the state of the art and updated when a significantly better model becomes available.
In the admin panel, all AI functions are marked with an AI badge in accordance with the EU AI Act (Art. 50), contain result disclaimers and are explained in the tool info entries (what the AI does, where it runs, which model is used).
For voice input (e.g. for measurements, in time tracking and in construction documentation), Booklera uses the browser’s speech recognition (Web Speech API). By default, the browser sends the recording to an online speech recognition service for this purpose; Booklera only receives the recognised text.
If a filter blocks an obvious manipulation attempt, Booklera records the time, the function and an excerpt of the input (at most 100 characters) in the server log, and for the AI customer chat also the IP address; the retention period of the server log files applies (section 10).
Which of these functions an industry includes, from which plan and with which monthly quota, is set out in our General Terms and Conditions (§ 3 and § 4.3).
Operating-help chatbot for tenant owners in the admin panel. For each request, the time, tenant, user, function, model and usage are stored, not the text of the request. If the assistant proposes a change, the proposal and, after confirmation, the executed change with its values are stored so that it can be traced and undone. A prompt injection filter with 22 patterns (DE+EN) blocks obvious manipulation attempts.
Answers end-customer questions on the tenant’s website about services, prices, bookings or enquiries. The question is passed to the local AI model only to answer it and is not used for training. For each answered question, the time, tenant, model and duration are stored, but not the text of the question. To protect against misuse, the IP address is stored for rate limiting and deleted after two hours at the latest.
Processes photos or PDF files of incoming invoices. Text recognition is performed using Tesseract OCR (open source, local). The local language model then extracts relevant fields (supplier, amount, date, category). The uploaded receipts are stored permanently in a tenant-isolated folder on our server (retention obligation pursuant to Sections 147 AO, 257 HGB). Invoice data is not transmitted to third parties — all processing takes place locally.
OCR function for receipts, invoices, delivery notes. Same tech stack as the invoice scanner, more broadly applicable.
During goods receipt, delivery notes can be read in as a photo or PDF. The image content and the recognized text are processed to record items and quantities. If such a document contains personal details of the supplier (such as the name of a contact person), these are processed as well; processing takes place locally on the provider's server. All AI suggestions are presented to the user for review and only adopted after their confirmation.
Converts a free-text description of a trade project into a complete bill of quantities (items, quantities, descriptions). The description is sent to the local AI model.
Measurement values can be dictated via the microphone; the AI extracts dimensions and calculates areas. The AI processing takes place locally on the server.
Employees can summarize their working day verbally; the AI extracts structured time entries (job, date, hours, description) with fuzzy matching against existing jobs. Up to 10 entries per batch.
Structures voice and photo notes into construction progress reports.
Creates suggestions for product descriptions and short search-engine texts, for assigning products to categories and for customs tariff numbers and countries of origin. This function also runs exclusively on the provider’s local language model and only processes the tenant’s product data — no customer or order data.
The legal basis for all AI features is Art. 6 (1) (b) GDPR (performance of a contract) and Art. 6 (1) (f) GDPR (legitimate interest in preventing misuse and in efficient task completion).
For processing payments (SaaS subscriptions as well as end-customer payments via Stripe Connect, including on-site card payments via Stripe Terminal), we use the Stripe service.
Videos from YouTube can be embedded on tenant websites. We use the extended privacy mode (youtube-nocookie.com), in which YouTube only sets cookies when the user actively plays the video.
Alternatively, videos from Vimeo can be embedded. We use the dnt=1 parameter (Do Not Track).
From the Business plan, tenants can upload their own videos (MP4, WebM, up to 100 MB per file) directly to the platform. These videos are stored exclusively on our server in Germany (Hetzner) and are not passed on to third parties.
This website and the SaaS platform are hosted on a dedicated server of Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany). The server is located in Germany. All data (database, files, emails, AI model, backups) is stored and processed exclusively in Germany. Hetzner is contractually bound as a processor pursuant to Art. 28 GDPR. hetzner.com/de/legal/privacy-policy
For the optional own domain (from the Pro plan), the tenant enters the DNS records with their own domain provider; an automatic job checks them every 30 minutes via public DNS resolvers until they are correct. SSL certificates are issued via Let's Encrypt and renewed automatically.
Backup concept: 4 independent layers (Restic every 15 min to offsite storage, PostgreSQL WAL archive every minute, daily offsite dump, offline copy twice a day). All backups are encrypted (Restic AES-256, separate master key).
Booklera is a multi-tenant platform. Technical measures for tenant separation:
Every tenant automatically receives a data processing agreement (DPA) pursuant to Art. 28 GDPR by email immediately after registration. The DPA is also available at any time in the admin panel under Settings → DPA / Privacy and can be re-sent from there. If you have any questions about data protection, please contact info@booklera.de.
This website and all tenant subdomains use SSL/TLS encryption (HTTPS, at least TLS 1.2, HTTP/2 supported). You can recognize an encrypted connection by the browser address bar changing from “http://” to “https://”. All data you transmit to us cannot be read by third parties. In addition, HSTS (HTTP Strict Transport Security) is active for one year.
Two-factor authentication (2FA, TOTP per RFC 6238) is available for access to the admin panel — mandatory for platform admins (Booklera-internal access), opt-in for tenant owners with a gentle reminder. During setup, ten single-use recovery codes are generated; the TOTP secrets are stored encrypted in the database.
For trade tenants, Booklera provides a cross-tenant network (trades pool and transport marketplace, reading from the Pro plan, posting from the Business plan). If a tenant actively uses these features, certain data becomes visible to other users of the platform:
The visibility of the data is limited to your own network (accepted connections) or to the recipients of a posting. There is no automatic data sharing between tenants — all data transfers only take place after an active action by the user (sending/accepting an invitation, posting a signal, expressing interest, submitting a transport offer).
Legal basis: Art. 6 (1) (b) GDPR (performance of a contract — the cross-tenant network is part of the booked plan features) and Art. 6 (1) (a) GDPR (consent of the user through active use of the feature). The user can disconnect a connection at any time, delete their own signal or revoke an expression of interest — the associated data is then removed from the network.
Personal data is only stored for as long as is necessary for the respective processing purpose or as long as statutory retention obligations exist. In detail:
| Data category | Retention period | Legal basis |
|---|---|---|
| Active user account | for the duration of the contract | Art. 6 Abs. 1 lit. b DSGVO |
| After termination — tenant data | 30 days soft delete for data export, then hard delete | Art. 17 DSGVO |
| Server log files | 14 days | Art. 6 Abs. 1 lit. f DSGVO |
| Rate limiting and login protection (IP address, for logins also the e-mail address) | up to 2 hours | Art. 6 Abs. 1 lit. f DSGVO |
| Cookie consent audit | 3 years | GDPR Art. 7 (1) (accountability) |
| Tax-relevant data (invoices, payment records) | 10 years | §§ 147 AO, 257 HGB |
| Construction diary, site meeting minutes, acceptance protocol, safety documents, safety accidents | 10 years after finalization | Sections 146, 147 AO (GoBD) |
| Audit log (immutable) | 10 years, UPDATE/DELETE blocked | § 146 AO |
| Payroll and salary data | 6 years | § 257 HGB, § 147 AO |
| Accident file (special categories Art. 9) | 10 years | Section 147 AO + internal retention obligations of the insurance association |
| Internal error tracking (resolved errors) | 30 days | Art. 6 Abs. 1 lit. f DSGVO |
| Webhook failures (resolved) | 30 days | Art. 6 Abs. 1 lit. f DSGVO |
| Sessions (expired) | 7 days after expiry | Art. 6 Abs. 1 lit. f DSGVO |
| Domain health log (resolved) | 30 days | Art. 6 Abs. 1 lit. f DSGVO |
Under the GDPR, you have the following rights vis-à-vis us regarding your personal data:
To exercise your rights, please contact us by email at n.glamngiw@booklera.de. We will respond to your request without delay, at the latest within one month.
You have the right to complain to a data protection supervisory authority if you believe that the processing of your personal data violates the GDPR. The supervisory authority responsible for us is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18
91522 Ansbach
www.lda.bayern.de
As of: November 2026