BackGerman version (binding)
Only the German version is legally binding. This English text is a convenience translation. German version (binding)

Privacy Policy – Bobits Flow (flow.bobits.at)

Version: 18 November 2026

1. Controller

bobits GmbH
Wiener Bundesstraße 57a/24, 5300 Hallwang, Austria
Email: office@bobits.at
Contact for privacy requests: datenschutz@bobits.at

No data protection officer has been appointed because there is no obligation under Art. 37 GDPR.

2. Scope and roles

This policy applies to the web application "Bobits Flow" at flow.bobits.at, including the installable app version (PWA). It does not apply to other websites of the Provider (e.g. bobits.at); those have their own privacy notices.

Bobits Flow is accounting and administration software for businesses ("customers"). We process personal data in two roles:

  • As controller (Art. 4(7) GDPR) for the data we need for registration, customer account, sign-in, billing, operation, security and support. This policy describes these processing activities.
  • As processor (Art. 28 GDPR) for all content that customers store in Bobits Flow: invoices, documents, customer and supplier data, bank transactions, employee and scheduling data, emails and documents in the inbox. The controller for that content is the respective customer. The basis is the data processing agreement (AVV), which is part of our terms. If you are affected as a business partner or employee of a customer, please contact that customer.

We process the login data of all users as controller (security, sign-in). We process the other data of users inside a customer account on behalf of the customer.

3. Processing in detail

3.1 Accessing the application (server and security logs)

When you open flow.bobits.at, our web server technically needs to process your IP address, date and time, requested address, HTTP status code, browser identifier (user agent) and referrer.

  • Our application logs every request in structured form (time, path, status code, duration, request ID and, for signed-in users, customer and user ID). These log lines do not contain the IP address.
  • For requests inside a customer account the application also stores a request log (per customer account). It contains method, path, status code, duration and selected request headers, without IP address and without user agent. Cookie and authorization headers are masked. We store request bodies only for JSON write requests, with credentials redacted. We store response bodies only for error responses (status code 400 and above). For sign-in, email and IMAP settings, integrations, dictation, private accounts and reports of security-policy violations (see 3.6) we store no bodies at all.
  • To prevent abuse we count sign-in, registration and other requests per IP address (rate limiting). These counters exist only in memory and are deleted shortly after their time window ends (the window is at most one hour).

Purpose: provision, stability and security of the application, error analysis.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and functional operation); where needed for performance of the contract, Art. 6(1)(b) GDPR.

Retention: operational logs 30 days in the central log store (Grafana/Loki, operated by us on the same Hetzner server); container logs are capped at 250 MB. Web server access logs 14 days. Request log in the customer account 30 days, at most the newest 1,000 entries per customer account; a daily job removes older entries.

3.2 Registration and customer account

At registration we process: company name, requested account identifier, country (Austria or Germany), optionally the VAT ID (we only check the format), name of the managing person, email address and password. We store the password only as a bcrypt hash. The user name of the first account is always "admin". Your browser language (Accept-Language) determines the language of the emails we send you. A hidden form field helps us block automated registrations. To confirm your email address we send a link; it is valid for 24 hours and we store only a hash of it. The hash is deleted at the latest one day after use or expiry. Without confirmation no sign-in is possible. We are informed internally of new registrations by email (company name, identifier, email address).

At registration you confirm that you act as a business for an existing business and you accept the terms including the AVV. We store records of acceptance: document (terms, AVV, privacy notice), version, time, source (registration or renewed acceptance) and the business confirmation. We do not store an IP address with them.

During operation we store for user accounts: user name, display name, email address, role, active status, time of the last sign-in and of the email confirmation, and an activity log of important actions (e.g. "user created"). For the customer account we store plan, status and administrative events (e.g. a block with reason, upgrade requests) and plan changes with their time. We also count, per user and day, sign-ins, failed sign-ins and session renewals (counters only, no IP address) and, per month, AI requests and tokens used per function and model. We record actions of operators in the operator area in an operator log. The operator area shows a customer's usage and sign-in activity only as counters and under pseudonyms ("User 1"); the operator reveals a user's name and email address only for a stated reason with a reference number, and every such retrieval is first recorded in the operator log.

Purpose: contract initiation and performance, account administration, abuse prevention, proof of acceptance of the contract terms.
Legal basis: Art. 6(1)(b) GDPR; for the internal notification, the activity and operator logs and the records of acceptance Art. 6(1)(f) GDPR.

Providing this data is necessary to conclude the contract. Without it we cannot set up an account.

3.3 Sign-in and session

After sign-in we set two technically necessary cookies: bobits_token (15 minutes) and bobits_refresh (7 days), both HttpOnly, Secure and SameSite=Lax (see section 6). We store the refresh token only as a SHA-256 hash with an expiry date. It can be used only once and is replaced at every renewal. It is revoked at sign-out and when the password changes; we delete expired tokens at sign-in. We record successful sign-ins with the user name in the activity log. We log failed sign-in attempts with user ID (if known) and reason, not with user name or password.

In addition to the password there is a second sign-in step:

  • Code by email: If a user has an email address on file, we send a six-digit code to it after the password. The code is valid for 10 minutes; we store only a hash of it. The number of entries per code and per day is limited. Between the two steps we set the cookie bobits_login_pending (10 minutes, see section 6). Users without an email address sign in with the password only.
  • Trusted computer (optional): If the user chooses to trust this computer for 30 days, the code is skipped in this browser (never the password). For this we store a hash of a random token, a coarse device label (e.g. "Chrome on macOS", without IP address and without version numbers) and the creation, last-use and expiry times. The token is kept in a cookie (see section 6). We delete expired entries daily; the user can revoke all trusted computers.
  • Passkey (on all plans): Users can set up a passkey (e.g. Face ID, fingerprint, Windows Hello) and sign in with it without password and without code. Per passkey we store: identifier, public key, counter, transports, device type, whether it is backed up or synced, a name (by default a coarse device label, changeable by the user) and the creation and last-use times. Biometric data never leaves the device. For sign-in and set-up we store short-lived one-time challenges (5 minutes); used or expired ones are deleted after one day. Setting up a passkey requires a sign-in within the last 5 minutes (cookie bobits_recent_auth, see section 6); we then send the user an email about it. A passkey stays stored until the user removes it, an administrator resets the user's sign-in factors or the account is deleted.

Adding and removing a passkey, revoking trusted computers and a reset of the sign-in factors by an administrator are recorded in the activity log.

Legal basis: Art. 6(1)(b) GDPR (providing the account) and (f) (security).

3.4 Billing of paid plans (Stripe)

We bill paid plans through the payment provider Stripe, monthly in advance. For billing we send Stripe the company name, the email address of the customer account and internal identifiers (customer ID, account identifier, chosen plan). You enter payment data (e.g. card data) directly on Stripe's checkout page; we do not receive or store it. We store the Stripe customer and subscription ID and the subscription status. Invoices and payments are managed in Stripe's customer portal.

Stripe Payments Europe, Ltd. (Dublin, Ireland) processes payment data as an independent controller for payment processing, fraud prevention and compliance with legal duties. Data may be transferred to Stripe, Inc. (USA) on the basis of the EU-US Data Privacy Framework or standard contractual clauses.

Legal basis: Art. 6(1)(b) GDPR; retention of accounting records: Art. 6(1)(c) GDPR in conjunction with § 132 BAO and § 212 UGB.

3.5 System emails

We send emails to confirm email addresses, sign-in codes (see 3.3), notices about newly set-up passkeys and internal registration notices through our own mail server at Hetzner Online GmbH (Germany).
Legal basis: Art. 6(1)(b) GDPR, for the security notices (f).

Emails that customers send from Bobits Flow to their own customers (e.g. invoices) go through the mail server the customer has configured and are part of the processing on the customer's behalf.

3.6 Error reports from the browser

If an error occurs in the application, your browser sends us an error report: type and message of the error, technical stack trace, name of the program component, the page visited and its full address including the query string and, for failed server requests, method, path, status and request ID. For signed-in users the report also contains the customer and user ID. The reports go to our central log store (30 days).
Legal basis: Art. 6(1)(f) GDPR (fixing errors).

Your browser also sends us reports of violations of our Content Security Policy. The policy is currently in report-only mode: it blocks nothing and only reports violations. From each report we store only: the violated directive, the origin (domain) of the blocked resource, the path of the page visited without the query string, the origin of the source file and a code sample of at most 100 characters. This is one line in the central log store (30 days), not a database record; we do not store the rest of the report. To prevent abuse we count reports per IP address (in memory only, see 3.1).
Legal basis: Art. 6(1)(f) GDPR (security).

3.7 AI-assisted document recognition and dictation (OpenAI)

Only on the Professional and Enterprise plans can a customer have documents read automatically: incoming and outgoing invoices, quotes and bank statements. The feature is off by default. The customer switches it on in the settings; after that, new documents in the inbox are read automatically. We then send to the OpenAI API: the document (image, PDF or extracted text), its file name, and the customer's own company name, VAT ID and IBAN (to tell "own company" from business partner), plus up to five earlier corrections by the customer as examples. For quotes we send the text and up to 20 price-catalogue entries, for bank statements the image or text. The result is a proposal that the user must check and confirm. There is no automated decision within the meaning of Art. 22 GDPR.

With the same consent, documents that are neither in German nor in English are translated automatically by machine (target language German or English, selectable by the customer in the settings). For this we send the pages of the document as images (at most two pages per request) to the OpenAI API (model gpt-6-luna). We store the translation as a PDF in the customer's document storage; it belongs to the customer's content, is deleted together with the document and can be appended to the PDF of the booked incoming invoice. We do not log the text of the pages or the translation.

With the same consent (the "AI processing" switch in the settings), dictation is available in the invoice editor. The user records speech in the browser; the recording is sent to our server and forwarded from there to the OpenAI API for transcription (model gpt-transcribe). We then send the dictated text together with the current content of the invoice draft (line items, recipient, date and text fields such as greeting, introduction and payment terms, prices from the customer's price catalogue and matching customers) to OpenAI so that changes can be proposed. A recording may contain personal data of third parties, for example the names of the customer's customers. We hold the recording in memory only for the duration of that request and do not store or log it. We also neither store nor log the dictated text or the proposals; only metadata such as size, duration and counts is logged. Nothing on the invoice changes until the user confirms each individual change; the AI never issues an invoice itself.

This processing concerns the customer's content and takes place on its behalf (AVV). The customer can switch the feature off in the settings at any time; dictation then no longer works either.

Recipient: OpenAI Ireland Ltd., Dublin, Ireland (contracting party); the processing is done by OpenAI OpCo, LLC and other OpenAI sub-processors in the USA (see sections 4 and 5). OpenAI may keep inputs for up to 30 days for abuse monitoring.

3.8 Telegram (optional)

Customers can link a Telegram chat with our bot (@bobitsbot) and send photos, PDFs, documents, voice messages, text and locations to it. Telegram first processes these messages as an independent controller; we download the files through the Telegram Bot API and store them in the customer's inbox. The customer's administrator creates link codes for this. We store the chat ID, the Telegram user ID of the sender and the time of linking, per message the chat and message ID, for voice messages the duration, and for locations the location. We store voice messages as audio; we do not transcribe them.
Legal basis: Art. 6(1)(b) GDPR (function chosen by the user).
Use is voluntary. Telegram has its seat outside the EEA (see sections 4 and 5).

3.9 Own email address for the inbox

Every customer on the Starter plan or higher can get its own address under bobitsflow.at. Emails to this address land in our mailbox at Hetzner and are fetched every minute. We store: sender address and name, subject, sent and received time, the results of the sender checks (DKIM, DMARC, SPF; domains only), the content and the attachments. If the text of an email is itself the invoice (no PDF file, enough text), we convert it into a PDF document on receipt and place it in the inbox. For the sender checks we make DNS lookups. Sender rules decide how a mail is handled: allowed senders are processed, unknown senders are held for approval, blocked senders and spam are rejected.

Retention: copies in the mailbox 30 days. Held emails expire after 14 days (content and files are deleted). We delete rejected or expired entries after 90 days. Emails to unknown or revoked addresses stay for 30 days in our mailbox folder "Unzugeordnet" (unassigned) and belong to no customer. This is our own processing (Art. 6(1)(f) GDPR, abuse prevention). All other emails are customer content and are processed on the customer's behalf (AVV).

3.10 Other integrations (optional, enabled by the customer)

  • Own mail server (IMAP/SMTP): If a customer configures a mailbox, we fetch unread emails from it, mark them as read and take attachments into the inbox; we send outgoing emails through the configured SMTP server.
  • Invoice export via FTP, FTPS or SFTP: A customer can specify its own server to which incoming and outgoing invoices are transferred.

These integrations process customer content on the customer's behalf; the named services are endpoints chosen by the customer.

3.11 Exchange rates

To convert foreign currencies we fetch reference rates from the European Central Bank, the Swiss BAZG/ESTV, the National Bank of Serbia (via kurs.resenje.org) and the Central Bank of Bosnia and Herzegovina (cbbh.ba). No personal data of yours is sent (our server makes the request).

3.12 Support and other enquiries

If you contact us by email we process your details to handle the enquiry.
Legal basis: Art. 6(1)(b) GDPR (contract-related) or (f) (other enquiries).

4. Recipients and processors

RecipientPurposeDataLocation / safeguards
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany Server, managed PostgreSQL database, file storage (Storage Box) for documents and backups, mail server (system emails and mailbox for the inbox address), log store all data stored in the applicationGermany; data processing agreement under Art. 28 GDPR
OpenAI Ireland Ltd., Dublin, Ireland (contracting party); processing by OpenAI OpCo, LLC and other OpenAI sub-processors in the USA AI document recognition, machine translation of foreign-language documents and dictation in the invoice editor (only if the customer switches on AI processing) document images, PDFs or texts (also for translation), the customer's company data, earlier corrections; voice recordings, dictated texts and the content of the invoice draft USA; EU Commission adequacy decision (Art. 45 GDPR) or Standard Contractual Clauses (Art. 46(2)(c) GDPR), as agreed in OpenAI's data processing addendum
Stripe Payments Europe, Ltd., Dublin, IrelandBilling of paid plans (independent controller)company name, email, plan, internal IDs; payment data directly at Stripe EU; transfer to Stripe, Inc. (USA) possible, on the basis of the EU-US Data Privacy Framework or standard contractual clauses
Telegram Messenger Inc., Road Town, Tortola, British Virgin Islands; EU representative under Art. 27 GDPR: European Data Protection Office (EDPO), Brussels optional document intake via Telegram bot (independent controller, only if the customer uses it) messages, files, chat ID third country; according to Telegram, data of users from the EEA is stored in data centres in the Netherlands

We operate the central log store (Grafana/Loki), the web server and the PDF renderer (creates PDF documents, without a connection to the internet) ourselves on the same Hetzner server; no further service providers are used for this. We do not embed analytics or tracking services, advertising networks, social media plugins or external fonts in the application.

Beyond that we pass on data only if we are legally obliged to (e.g. to authorities or courts).

5. Transfers to third countries

  • OpenAI (USA): EU Commission adequacy decision (Art. 45 GDPR) or Standard Contractual Clauses (Art. 46(2)(c) GDPR), as agreed in OpenAI's data processing addendum.
  • Stripe (USA): EU-US Data Privacy Framework or standard contractual clauses.
  • Telegram: Telegram is an independent controller with its seat outside the EEA. According to Telegram, it stores data of users from the EEA in the Netherlands. Messages you send via Telegram are governed by Telegram's privacy policy.

You can get a copy of the safeguards on request at datenschutz@bobits.at.

6. Cookies and local storage in the browser

We use only cookies and storage techniques that are necessary for the function you requested or that store a setting you chose (§ 165(3) TKG 2021). We set no analytics, marketing or third-party cookies. Consent is therefore not required.

NameTypePurposeDuration
bobits_tokenCookie, HttpOnly, Secure, SameSite=LaxSign-in (access token)15 minutes
bobits_refreshCookie, HttpOnly, Secure, SameSite=Lax, only for /api/authExtend the session7 days
bobits_login_pendingCookie, HttpOnly, Secure, SameSite=Lax, only for /api/authIntermediate step between password and email code10 minutes
bobits_recent_authCookie, HttpOnly, Secure, SameSite=Lax, only for /api/auth/passkeyProof of a recent sign-in for setting up a passkey5 minutes
bobits_td_<customer ID>_<user ID>Cookie, HttpOnly, Secure, SameSite=Lax, only for /api/auth"Trust this computer" (skips the code); only if the user chooses it30 days
i18n_redirectedCookie, SameSite=LaxChosen language1 year
incoming-invoices-rowsCookie, SameSite=LaxChosen number of table rows1 year
darkMode, privacyModeCookie, SameSite=LaxDisplay (dark theme, hide amounts)1 year
nuxt:reloadSession StorageNavigation after sign-in and sign-outuntil the tab is closed
invoiceProofHintSeenSession StorageOne-time hint in the invoice view on the phoneuntil the tab is closed
bobits:passkey-on-device, bobits:passkey-offer-dismissedLocal StorageFlag that a passkey is used on this device or that the offer was declineduntil you delete them
invoiceZoom:<user ID>Local StorageChosen zoom level of the invoice previewuntil you delete it
bobits.sammelaufstellung.dismissedLocal Storage Flags for dismissed hints about the collective listing (contains account ID, supplier key, month and currency) until you delete it
bobits-upload-queueIndexedDB Queue for document photos and files not yet uploaded, including their content; customer ID and user ID of the current session; time of the last session refresh uploaded entries are removed about five minutes after upload; everything is removed at sign-out
Service worker cacheCache Storage Program files, icons and fonts for faster loading; no page contents and no data from your account until the next app version
Browser HTTP cacheBrowser cache Documents (PDF files, attachments) may sit in your browser's private cache; the browser revalidates them with the server before every use. At sign-out we instruct the browser to clear the cache (Safari and iOS do not follow this). until sign-out or until the browser removes them

7. Retention

  • Account data: for the term of the contract; afterwards under clause 10 of the terms (export, 30-day retrieval period, erasure), unless a statutory retention duty applies.
  • Activity log, notifications, AI corrections and metadata of inbound emails are customer content: they are kept for the term of the contract and deleted with the account (clause 10 of the terms).
  • Records of acceptance: for the term of the contract, deleted with the account.
  • Plan history: for the term of the contract, deleted with the account.
  • Sign-in counters (per user and day): 90 days.
  • AI usage counters (per month): 24 months.
  • Billing records: 7 years from the end of the calendar year (§ 132 BAO, § 212 UGB), longer if relevant to pending tax or court proceedings.
  • Operator log: 3 years.
  • Request log in the customer account: 30 days (see 3.1).
  • Operational logs and error reports: 30 days.
  • Web server access logs: 14 days.
  • Rate-limit counters: shortly after their time window ends (at most one hour).
  • Email confirmation links: valid 24 hours, deleted at the latest one day after use or expiry.
  • Inbound emails: see 3.9; unassigned emails 30 days.
  • Sign-in codes and passkey challenges: valid for 10 and 5 minutes, deleted one day after use or expiry. Trusted computers: 30 days. Passkeys: until removed by the user or with the account.
  • Backups: 30 days rolling.
  • Customer content (processing on behalf): per the customer's instructions and the AVV.

8. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on Art. 6(1)(f) GDPR (Art. 21). Contact datenschutz@bobits.at for this.

If your data is part of content that a customer stored in Bobits Flow, please contact that customer. We forward requests that reach us to the customer.

9. Right to lodge a complaint

You can complain to the Austrian Data Protection Authority: Österreichische Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb@dsb.gv.at, www.dsb.gv.at.

10. Changes

We update this policy when the application or the law changes. The version published at https://flow.bobits.at/datenschutz applies.

ImprintPrivacy policyTerms