Privacy Notice

Version: privacy-2026-11-16.v1

Privacy Notice — Feeduna

1. Responsibility and contact
Feeduna is provided by performeon GmbH, Rodgasse 5, 97828 Marktheidenfeld, Germany, represented by managing director German Hoeffner; Amtsgericht Würzburg, HRB 17476. Contact [email protected] for privacy requests.

We are the controller for account administration, billing, support and our service-security processing. We process feedback submitted through a customer's app on that customer's instructions under our Data Processing Agreement. If you submitted feedback in another business's app, contact that business about your report; we assist it with your request.

2. Accounts and sign-in
We process your sign-in email, account and app identifiers, app name and origin, status and timestamps. For an individual professional subscribing personally, necessary contract processing is based on GDPR Article 6(1)(b). For a company's representatives, our basis is the legitimate interest in administering that business relationship, Article 6(1)(f). You must provide an email to sign in; without the necessary account and billing information we cannot provide the subscription.

We send a single-use email code and store its hash, expiry and attempt counts. Codes are valid for ten minutes and sessions for twelve hours. Essential first-party cookies maintain the sign-in challenge, session and Linear connection flow. Our application contains no advertising or analytics tags. Cloudflare may use security cookies when its applicable security features operate; its cookie information is at https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/.

For abuse prevention, the application stores keyed hashes of the email and network address with timestamps, rather than raw IP addresses in its sign-in rate records. The rate window is one hour. Expired codes, sessions and rate records are removed in maintenance batches, not necessarily at the instant they expire. Unresolved Linear connection attempts are retained for reconciliation rather than assumed completed on expiry. Our basis for security processing is Article 6(1)(f), supplemented by Article 6(1)(b) where necessary for an individual subscriber's contract.

Where customer API access is enabled, you can create app-scoped keys for setup, reading reports and, optionally, submitting reports. The secret is shown once; we store its hash, owner/app identifiers, name, scopes, creation/expiry/revocation times and a request-rate window and count. Keys expire within ninety days and can be revoked sooner. Expired or revoked key records become eligible for batched removal thirty days after expiry or revocation; account closure can remove them sooner. Do not put personal or sensitive information in key names. This processing supports the account and security purposes above.

3. Payments and contract evidence
Stripe hosts checkout and payment management. In normal Checkout, card numbers go directly to Stripe; our billing integration does not receive them. We retain customer, subscription and payment references, billing state and paid period, business name and billing address, and the exact business declaration and Terms accepted with their versions and acceptance time. We also retain the Checkout request and minimal authenticated event evidence for payment reconciliation. These technical records are not all invoices.

Where business verification is required, we retain the public business or registry link you submit, an optional registration number, its association with your billing profile, and the review decision, reviewer identifier, handling time and review/expiry timestamps. Submitting a reference does not itself verify the business. This workflow does not accept uploaded identity documents. We use these records to establish and review the business billing treatment and retain them only for the applicable purposes described in section 6.

For our German Stripe account, the contracting entities are Stripe Payments Europe, Limited and, for applicable regulated payment services, Stripe Technology Europe, Limited, both in Ireland. Stripe processes data on our behalf for some payment services and as an independent controller for purposes such as fraud prevention and legal obligations. See https://stripe.com/privacy and https://stripe.com/legal/dpa. Our bases are the contract or business-relationship interests described above and Article 6(1)(c) for applicable accounting duties.

4. Hosting, traffic and recipients
We operate the application on our Frankfurt server and operate our origin proxy and mail system. Cloudflare, Inc. (United States) provides DNS and the public TLS proxy in front of the service under our company's self-serve agreement. Proxied requests pass through Cloudflare, including network addresses, request headers and transmitted content. Report submissions therefore pass through Cloudflare as well; app log minimisation does not mean that Cloudflare never receives this information. Cloudflare's Data Processing Addendum forms part of that agreement: https://www.cloudflare.com/cloudflare-customer-dpa/. Its privacy policy is at https://www.cloudflare.com/privacypolicy/.

Application HTTP access logs contain the method, status, response size and duration, excluding request paths, queries, cookies and client IPs. Separate application operational logs contain sanitised worker events and maintenance counts. The edge proxy, Cloudflare and mail system have their own operational processing and logs. We use operational records for service delivery, security and fault investigation and retain them only as needed for those purposes and any incident or legal obligation.

Linear Orbit, Inc. (United States) receives content you approve for the workspace you connect, plus the identifiers and credentials needed to establish and operate that connection. Your use of that workspace is governed by your agreement with Linear: https://linear.app/dpa. Stripe receives billing data, not feedback reports through our payment integration.

Support messages are received and handled through our company-operated mail system. We process the sender's contact details and message to respond, using Article 6(1)(f), or Article 6(1)(b) for necessary contract enquiries from individual subscribers. Avoid including report content or sensitive information unless it is needed for the particular request. We do not copy customer reports into project research or use them to train AI models.

If you give an API key to a tool, integration or AI client, that recipient can use the key's scopes to access your app's data until expiry or revocation. Our optional local MCP connector runs in your chosen environment and passes the requested data to that client. It does not send reports to our internal research tools. You select the recipient and must consider its terms, data use and location before connecting it. Revoking a key stops further access but does not erase copies already obtained by that recipient.

5. International processing
Our Frankfurt application server does not make the whole service EU-only. Cloudflare operates internationally; Stripe and Linear can process data in the United States. Cloudflare's published DPA and Stripe's Data Transfers Addendum describe Data Privacy Framework and standard contractual clause mechanisms where applicable: https://stripe.com/legal/dta. Linear's DPA describes its international processing. The applicable mechanism depends on the recipient, processing role and transfer. You can contact us for information about the relevant safeguards and a copy where applicable.

We maintain recovery backups without an EU-only storage commitment for those copies. International processing, including recovery storage, must meet applicable GDPR Chapter V requirements. This is not a claim that all recipients or copies are located in Germany.

6. Retention and closure
Account access continues while the account remains open, including access to existing reports after a subscription ends. Report content is subject to the retention and removal rules in the DPA. To close your account, contact us from its established email address. We verify the request, arrange any requested export, resolve billing, suspend access, remove the requested report content and disable the Linear connection locally. We arrange and verify provider-side revocation separately; encrypted unresolved credentials are retained only as necessary to resolve that work. An issue already created in your Linear workspace is not deleted by removing our copy.

After closure, account/contact and financial evidence is retained only for a specific remaining accounting, dispute or necessary reconciliation purpose. Under §147 AO and §257 HGB, booking vouchers such as invoices generally have an eight-year period, qualifying business correspondence six years, and books and annual accounts ten years. The relevant calendar-year starting rule applies; statutory extensions can apply. We classify records by their actual purpose rather than treating every event or Checkout as an invoice. Other contract and payment evidence is kept only while needed for legal claims or unresolved transactions.

Routine support messages are removed by staff ninety days after resolution, except actual business/accounting correspondence subject to retention or evidence needed for an active dispute. Our deletion tools remove active database records or content logically; they do not promise immediate physical erasure of database storage or earlier recovery copies.

Recovery copies are restricted to restoration and retained only as needed for recovery or a legal obligation. Before restored data becomes accessible, we reconcile and reapply applicable removals and account restrictions. If post-snapshot removals cannot be established, affected restored data remains inaccessible until resolved. We do not promise automatic reconstruction of missing deletion history or a fixed backup rotation period.

7. Security
Public service connections use HTTPS. We restrict account access and database access and encrypt stored Linear credential envelopes in the application. Other database content is not application-encrypted. These controls do not amount to a claim that every system, storage layer or backup is encrypted.

8. Your right to object

You may object at any time, for reasons relating to your situation, to our processing based on legitimate interests. Contact [email protected]. We then stop that processing unless we establish overriding compelling legitimate grounds or need it to establish, exercise or defend legal claims.

9. Other rights

Subject to the applicable conditions, you may request access, correction, erasure, restriction and portability. Contact [email protected]; we may need to verify the request without asking for unnecessary information. You may complain to a supervisory authority, including the Bavarian State Office for Data Protection Supervision (BayLDA), https://www.lda.bayern.de. Our application does not make decisions with legal or similarly significant effects through automated profiling.