Privacy Policy

Version: 2026-10-19-v3

This privacy policy informs you, pursuant to Art. 13 and Art. 14 GDPR, about the processing of personal data when you visit the website zensu.dev (https://zensu.dev) and when you use the Zensu platform at app.zensu.dev (https://app.zensu.dev) and the desktop software Zensu Session Hub.

§ 1. Controller

The controller within the meaning of the GDPR is:

MK IT Consulting Owner: Marcel Karras Enderstr. 94 01277 Dresden Germany Email: [email protected]

§ 2. Hosting and data location

The Zensu platform is hosted on the Open Telekom Cloud (OTC) in data centres within the European Union (region eu-de, Frankfurt); your account and platform data are stored at rest within the EEA. Limited transfers to processors in third countries (USA) occur only for optional features such as the AI features (see sections 3.5 and 5) and are covered by appropriate safeguards under Art. 46 GDPR.

§ 3. Data collected and processing purposes

3.1 Server log files: When the website is accessed, technical data is stored in server logs (IP address, date/time, requested resource, referrer, user agent). Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in operation and security). Storage period: a maximum of 14 days.

3.2 Registration: When you register, we process your email address to administer your account. Legal basis: Art. 6 (1) (b) GDPR (performance of a contract).

3.3 Platform use: When you actively use the Zensu platform, the content you enter (features, tests, documents, configurations) is stored. Legal basis: Art. 6 (1) (b) GDPR (performance of a contract).

3.4 Contacting us: If you contact us by email, your details are processed to handle the enquiry. Legal basis: Art. 6 (1) (b) or (f) GDPR.

3.5 AI assistant and documentation generation: When you use the AI assistant or have documentation generated for a feature, Zensu transmits the data listed below to OpenRouter (OpenRouter Inc., USA). OpenRouter forwards the request to the provider of the language model in use and returns its response. Data is transmitted only when you actively use one of these features. Legal basis: Art. 6 (1) (b) GDPR (performance of a contract).

For the AI assistant, this means your messages and the conversation so far; a system instruction that, in a product-focused conversation, contains the product's name, description and type; and the results of the queries the assistant runs in Zensu on its own to answer you and of changes you have confirmed. These queries can concern in particular features, products, user journeys, roadmaps, sprints, tasks, releases, teams, wiki pages and knowledge-base content, as well as the names, email addresses and roles of your organisation's members, for example when you ask the assistant to assign a feature to someone. The first message of a conversation is also used to generate a title for the conversation. Apart from the values described in the next two paragraphs, the assistant does not receive input that you have not yet saved in forms or editors of the application.

If you use the assistant in the side panel that can be opened on most pages of the application, each message you send there also carries a description of the page you are viewing: the type of page, the IDs in its address, the type, ID and name of the items shown (for example the open product or feature), the open tab and, on some pages, the search text and filters you have set there, even if you have not saved them. Email addresses in this description are replaced with a placeholder. On account and settings pages, on the overview, members, invitations and billing pages of your organisation and on a product's settings page, only the type of page and the IDs in its address are sent; the same applies to Pulse pages, feedback boards and the review page of a single scan unless you share the page or attach an entry as described in the next paragraph. Before sending, you can see exactly what will be transmitted and remove individual items. Zensu stores this description together with the conversation. Administrators of your organisation can switch the assistant off for the whole organisation; while it is off, nobody in the organisation can start or continue a conversation and no data is transmitted for the assistant. Existing conversations are kept.

Where the assistant may also act on the open page, the description additionally lists the forms, editors, filters, boards and lists of that page that it can fill with suggestions, together with their current content, including input you have not saved yet; the content of fields marked as secret is never included. You can remove these entries, or only their content, before sending. Suggestions from the assistant appear on the page as proposals and change nothing until you keep them. On Pulse pages, the session you have open, its product and features and your filters are sent only after you choose “Share this page” in the side panel, and only until you leave that page. A feedback post or a scan candidate is sent only if you attach it to the conversation: for a feedback post its type, status, number of votes, title and description, and for a scan candidate its review status, component, title, description and the listed file paths are then transmitted once to the AI provider to create a short summary; email addresses in it are replaced with a placeholder. The assistant then works with this summary, not with the original text. Zensu stores the summary with your conversation, and only you can read it.

For documentation generation, this means the information stored in Zensu about the feature: title, description, status and scope; the product's name and documentation URL; the component's name and description; sub-features; linked source files with path, programming language and technical summary, plus the names, signatures and documentation comments of the code symbols they contain; tests; security classification and OWASP and compliance tags; tier availability; related user-journey steps; the type, title and publication status of existing documentation; and the requested document type, audience and language. This contains personal data only where it appears in this content.

For every request to the language model, Zensu instructs OpenRouter to route it only to providers that do not collect inputs for training and that offer zero data retention. For the AI assistant, the model provider may briefly cache the unchanged beginning of a request (instructions, descriptions of the query functions and the conversation so far) so that it does not have to process it again on the next request (prompt caching, 5 minutes by default). Processing by OpenRouter and the model providers is not limited to the EU.

Zensu stores conversations with the assistant (messages, replies and query results) in its database (see section 2) so that you can continue them; other members of your organisation cannot view them. There is currently no automatic deletion period: conversations remain stored until you delete them in the assistant or your account or organisation is deleted.

To execute and bill assistant requests reliably, Zensu also stores internal execution logs containing messages, replies, query results and proposed changes. Their content becomes due for deletion 30 days after the execution completes; if it does not complete, the period runs from the start of the execution. This also covers abandoned executions. If the associated conversation, your account or your organisation is deleted earlier, the log content is deleted during the next cleanup run. After cleanup, expired executions cannot be recovered and their pending proposed changes can no longer be executed. Deletion markers prevent these logs from being filled with content again. This log cleanup does not delete your conversation if you have kept it.

Automatic cleanup runs when the service starts and every 5 minutes. It processes a limited amount of data in each run and retries failures; backlogs and service outages can delay actual deletion. Operators of self-hosted installations can configure the periods; the default for log content is 30 days.

Temporary events used to resume response delivery become due for deletion 1 hour after an execution ends, and associated execution metadata after 30 days. Abandoned running executions are also cleaned up after 30 days without a heartbeat. Cleanup intervals, backlogs and service outages can delay these deletions in the same way.

Reduced usage and billing evidence and identifiers needed to prevent repeated processing remain separate from the deleted log content. Log cleanup does not alter existing acceptance evidence or the associated legal documents; sections 6 and 3.6 continue to govern deletion of account data and Session Hub acceptance evidence.

For documentation generation, Zensu does not keep the request to the language model or the generated text; the result is only transferred to your browser and is stored only if you save it in Zensu yourself. Zensu logs for which feature a document of which type was generated.

3.6 Zensu Session Hub: For the desktop software Zensu Session Hub, we process the data needed to check your entitlement: your Zensu account, your entitlement (a trial with its start and end, a subscription or a seat of an organisation), for each activated device a device ID, a device name, the public device key with its fingerprint and the times of activation and blocking, events of your Hub account (such as the start of the trial or the activation or blocking of a device), the record of your acceptance of the license terms (document, version, checksum, language, occasion and time) and technical connection data such as the IP address that arise with every connection to our servers. Legal basis: Art. 6 (1) (b) GDPR (performance of a contract); for the events and the acceptance record also Art. 6 (1) (f) GDPR (legitimate interest in preventing abuse and in proving the conclusion of the contract). We delete this data together with your Zensu account (see section 6). The content of your Claude sessions and the sign-in emails the software reads for the automatic sign-in are processed only on your device; we do not receive them.

3.7 Payments through Paddle: Paid subscriptions are sold by Paddle as reseller (merchant of record), outside the USA and Canada by Paddle.com Market Limited. Paddle processes the data you enter during checkout, such as name, email address, address, payment details and, where applicable, VAT ID, as an independent controller under its privacy notice (www.paddle.com/legal/privacy (https://www.paddle.com/legal/privacy)). When you start the checkout, we transmit your email address and internal identifiers to Paddle so that we can assign the payment to your account. From Paddle we receive the customer, subscription and transaction identifiers, the status, amounts and periods of your subscriptions and payments, and the event data Paddle sends us; these can contain your name, email address and country. We do not receive complete payment details such as card numbers. Legal basis: Art. 6 (1) (b) GDPR (performance of a contract) and Art. 6 (1) (c) GDPR (tax obligations). Section 6 applies to retention.

§ 4. Cookies and tracking

On the marketing website zensu.dev (https://zensu.dev) we use no tracking or analytics cookies. No data is transmitted to third-party providers such as Google Analytics or Facebook Pixel. On the platform at app.zensu.dev (https://app.zensu.dev) we store only technically necessary data: an HttpOnly cookie (zensu_refresh) for session renewal, plus technically necessary entries in the browser's local storage for the access token and your display preferences (theme, language). No tracking or analytics technologies are used.

§ 5. Disclosure to third parties

Your personal data is disclosed to processors within the meaning of Art. 28 GDPR: hosting (Deutsche Telekom AG / Open Telekom Cloud, data centres in the EU), email delivery (SendGrid Inc., USA — only where activated), and AI-assisted features such as the Product Studio, the AI assistant and documentation generation (OpenRouter Inc., USA — only when you use these features, see section 3.5). A data processing agreement under Art. 28 GDPR is in place with the hosting provider. Where personal data is transferred to providers in a third country (USA), this is done on the basis of appropriate safeguards pursuant to Art. 46 GDPR (EU Standard Contractual Clauses). For payments, we also transmit data to Paddle, which processes it as an independent controller (see section 3.7).

§ 6. Storage period

Personal data is stored only for as long as necessary for the respective processing purposes or as required by statutory retention obligations (e.g. section 257 HGB, section 147 AO). When an account is deleted, its account data is deleted from the active system, except for the separately retained data described here and evidence required by law. Section 3.5 applies to conversations, execution logs and documentation generation; section 3.6 applies to Session Hub. Cleanup of the active database does not rewrite existing backups. Backups are subject to the operator's separate retention and deletion policy; the stated periods for the active database do not promise simultaneous deletion from backups. After a restoration, cleanup must run again before access is enabled.

§ 7. Data-subject 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 objection (Art. 21). To exercise these rights, please contact [email protected].

§ 8. Right to lodge a complaint with a supervisory authority

You have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for the provider is the Saxon Data Protection and Transparency Officer (Sächsischer Datenschutz- und Transparenzbeauftragter, www.saechsdsb.de (https://www.saechsdsb.de)).

§ 9. Changes to this privacy policy

We reserve the right to adapt this privacy policy in order to keep it aligned with current legal requirements or to implement changes to our services. The version in force at the time then applies to your next visit.