Terms of Service
Version: terms-2026-11-16.v2.eur-2500
Terms of Service — Feeduna
1. Who we are.
Feeduna (the service) is provided by performeon GmbH, Rodgasse 5, 97828 Marktheidenfeld, Germany ("we"). Full company details are in our seller notice.
2. Business customers only.
The service is offered only to businesses and professionals for use in their trade, business or profession. By subscribing, you confirm that you are acting for a business and that you are authorised to accept these terms on its behalf. We do not contract with consumers.
3. What the service does.
The service collects feedback about your web app, features and data records/results. A report contains the text and context submitted by its sender. You review and can edit reports, and can connect your own Linear workspace for explicitly approved issue delivery. Where enabled, scoped API keys support submission and retrieval by your own tools, including an optional local MCP connector. The service does not take screenshots, record sessions, generate content with AI, change your code, or guarantee any outcome or time saving.
4. Your plan.
Your subscription covers one app and up to 100 reports per calendar month, shared across widget and API submissions. You install our script on an app you are authorised to modify or use the supported API integration. Linear is an optional destination. You are responsible for your installation, connected services and API keys, including the scopes and access you grant to tools or AI clients. API/MCP availability and supported client requirements are described in the setup documentation.
5. Price and payment.
The price is EUR 25 per month, plus any taxes that apply. Invoices and payments are in EUR. Any displayed USD equivalent is an approximate reference only, not the amount charged. Your card provider may apply its own currency conversion and fees. Payment is collected in advance through our payment provider, Stripe, and the subscription renews monthly until cancelled. There is no free trial. If a payment is not received, new report capture and delivery to Linear pause until payment succeeds. While your account remains active you can still view, export and remove existing reports.
6. Cancellation.
You can cancel at any time in the billing portal. Cancellation takes effect at the end of your current paid billing period, and you keep access until then.
7. Refunds.
If a demonstrable fault in the service prevents the core workflow (capturing a report, reviewing it, or delivering it to Linear) and we cannot reasonably remedy it after you report it, we refund the affected period. Your mandatory statutory rights are not affected.
8. Your content and your users.
You decide where the script is installed and what happens to reports. You are responsible for informing the people who use your app about feedback collection where required. The Data Processing Agreement (DPA), version dpa-2026-11-16.v1, is incorporated into these Terms for processing customer report data. Its exact text and SHA-256 are included below; it is also available at /dpa. Issues created in your Linear workspace and copies retrieved by your connected tools are governed by your arrangements with those recipients and remain there if you remove a report from the service. Revoking an API key does not delete previously retrieved copies.
9. Acceptable use.
Do not use the service to collect special categories of personal data, payment card data or passwords. Do not install it on apps you do not control, or attempt to circumvent limits, security or other customers' separation. We may suspend accounts that violate these restrictions.
10. Support.
Support is provided by email at [email protected]. We do not offer a service-level agreement, response-time commitment or guaranteed availability. We do not promise permanent compatibility with any third-party service, including Linear.
11. Changes.
We will give at least 30 days notice by email of proposed price or material contract changes. Changes for an existing subscription require your express agreement; without it your existing terms and price remain unchanged. No price change applies to a period already paid for. You can cancel before any agreed change takes effect.
12. Liability.
Liability is governed by applicable law.
13. Law.
These terms are governed by German law, subject to any mandatory rules that apply to you.
Data Processing Agreement incorporated into these Terms
Version: dpa-2026-11-16.v1
SHA-256 (UTF-8): 2d0f3b343dbc8854ed02e2f31088787a1a93dc80150e122287ef10297d6c2810
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.