Data Processing Agreement
Version: dpa-2026-11-16.v1
Data Processing Agreement — Feeduna
1. Parties, scope and duration
This agreement governs processing of customer report data by performeon GmbH, Rodgasse 5, 97828 Marktheidenfeld, Germany (processor), on behalf of the subscribing customer (controller), when incorporated into the parties' service agreement. It prevails over conflicting service terms concerning that processing. It covers collection, transmission, storage, review, editing, export and deletion of feedback and the customer's approved delivery to its connected Linear workspace.
It also covers feedback about features and data records/results, API submission and customer-authorised retrieval/export through scoped API keys, including a customer-run MCP connector. It applies from the first processing of report data until return or deletion is complete, including the period after subscription expiry in which reports remain accessible. The customer's users who submit reports, and people identified in submitted or reviewed content, are the data subjects.
2. Data and instructions
Report data includes feedback type, message, desired outcome, page path without query or fragment, release, feature identifier, structural element locator, viewport dimensions, receipt and app identifiers, timestamps, owner-edited drafts and delivery references. Network and request information is also processed to transmit and protect requests through the service and its proxy providers.
Explicit targets can also include target type, a stable record/result or feature identifier, collection reference and a short label. Data targets do not require a page or DOM element. There is no dedicated reporter-email field. The widget does not automatically collect form values, cookies, browser storage, DOM snapshots, screenshots or session recordings. People can nevertheless include personal data in text or editable context. Special-category data, passwords and card details are outside the intended use.
Documented instructions are this agreement, the customer's authorised configuration and actions, and further verified instructions sent to [email protected]. The processor acts only on those instructions, including for international transfers, unless EU or member-state law requires otherwise; it informs the controller of such a requirement unless legally prohibited. It promptly informs the controller if an instruction appears to infringe data-protection law.
3. Confidentiality and security
Authorised persons must be bound to confidentiality and access only what their duties require. Report data is not copied into internal research or AI tools; support access is limited to the particular request.
The agreed measures include HTTPS for public connections; owner-scoped application access; hashed email sign-in codes and session tokens; restricted database access; encrypted Linear credential envelopes; bounded request handling; restricted operational access; and logical retention/removal controls. Report text and other ordinary database content are not application-encrypted. Application HTTP access logs exclude request paths, queries, cookies and client IPs; sanitised worker events and maintenance counts are separate. This log limit does not describe Cloudflare, origin-proxy or mail-server processing.
Recovery copies are restricted to restoration. Restored data remains inaccessible until relevant removal instructions and account restrictions are reconciled and reapplied. Where later removals cannot be established, the affected data stays inaccessible pending resolution. These measures are reviewed as the service changes, without reducing the protection required by law.
4. Sub-processors and connected services
Cloudflare, Inc. (United States) provides DNS, traffic proxying, TLS termination and related network/security processing, including transmitted report content and request information. It is a sub-processor for report data processed on our behalf. Its DPA is incorporated into our company's self-serve agreement; the DPA and onward sub-processor list are at https://www.cloudflare.com/cloudflare-customer-dpa/ and https://www.cloudflare.com/gdpr/subprocessors/.
Our own application, origin proxy and mail infrastructure are operated by performeon GmbH. A customer can authorise its own API/MCP client to retrieve report data by supplying an appropriately scoped key. The local connector operates in the customer's chosen environment; the customer chooses any onward AI or other recipient and is responsible for its instructions and applicable arrangements with that recipient. Revocation prevents further key access; copies already retrieved must be managed at their destination. These customer-directed flows do not authorise internal research or model access by us, and do not exempt processing on our behalf from sub-processor obligations.
The customer instructs delivery to its own connected Linear workspace under its agreement with Linear. This description does not exempt any processing performed on our behalf from the applicable sub-processor requirements. Stripe does not receive report content through the billing integration. Customer support containing report data is subject to the same protections as other report processing; it must not be routed through an unapproved recipient.
The controller generally authorises the described sub-processing. The processor gives at least thirty days' email notice of a proposed addition or replacement, allowing reasonable data-protection objections. The parties seek an appropriate solution; if none is possible, the controller may terminate the affected service. This does not limit statutory rights. Each appointed sub-processor must be bound to equivalent data-protection obligations, and the processor remains responsible to the controller for its performance as required by GDPR Article 28(4).
5. Assistance, incidents and audit
Taking account of the processing and information available, the processor assists with data-subject requests, security, breach notification, impact assessments and any necessary prior consultation. It notifies the controller without undue delay after becoming aware of a personal data breach affecting report data, providing available details and subsequent material updates.
The processor provides information needed to demonstrate compliance and permits and contributes to audits, including inspections by the controller or an authorised auditor. Scheduling and confidentiality arrangements must protect other customers and avoid unnecessary disruption without preventing statutory rights or urgent justified inspection.
6. Retention, return and erasure
In ordinary operation report content becomes eligible for removal ninety days after submission, or earlier on the controller's removal action. Maintenance is bounded and batched; active delivery work and backlog may delay completion. Content removal leaves a minimal receipt record with app, timestamps, state and delivery identifiers for replay prevention; ordinary maintenance purges that record after 365 days from removal. No report content is retained in that record.
At the controller's choice, we return the report data and delete remaining service copies, or delete without returning it, subject to required legal retention and the recovery controls below. Earlier metadata-erasure instructions are handled by staff. We explain effects on replay prevention and carry out the instruction unless law requires retention; losing replay protection does not itself override erasure obligations. Closed-account receipt purging is an assisted process, not a general self-service field-erasure feature.
Removal is logical in the active database, not an immediate physical wipe of database pages or historical backups. Recovery copies are not edited individually and are used only for restoration, with access restrictions and reapplication of removals as described above. Retention is limited to necessary recovery or legal purposes, not indefinite reuse. Legally required retained data is restricted to that purpose. Copies already delivered to Linear remain within the customer's workspace and must be managed there.
7. International processing
The primary application server is in Frankfurt. The service does not commit to EU-only processing or EU-only recovery storage. International processing, including proxy services, recovery storage and Linear delivery, must follow documented instructions and the applicable GDPR Chapter V safeguards. The processor must establish the appropriate arrangements for its recipients.