Privacy Policy

Last updated: November 4, 2026

Deutsche Fassung: Datenschutzerklärung. In case of discrepancies between the language versions, the German version prevails.

1. General Information

AUDIOPATCH ("we", "us") handles your personal data confidentially and in accordance with the General Data Protection Regulation (GDPR) and applicable German data protection law.

Contact: info@audiopatch.net

2. Hosting & Infrastructure

This website and the web application are hosted on Cloudflare Pages (Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA). When you visit our website, Cloudflare may process technical data such as your IP address, browser type, and access time for security and performance purposes. Cloudflare is certified under the EU-US Data Privacy Framework.

The optional online functions (real-time collaboration, license verification, feedback and bug reports, analytics) run on Cloudflare Workers. License records and technical counters (see sections 7 and 13) are stored in Cloudflare Workers KV, a key-value database operated by Cloudflare.

3. Local Data Storage

AUDIOPATCH stores all project data exclusively in your browser's localStorage. No project data, audio configurations, input lists, or patch plans are transmitted to our servers. Your data remains entirely on your device.

4. Real-time Collaboration

When you use the optional Collaboration feature, project data is temporarily stored on our Cloudflare Workers infrastructure to enable real-time synchronization between participants. This data is:

• Encrypted in transit (TLS)
• Automatically deleted after 30 days of inactivity
• Not used for any purpose other than enabling the collaboration session

5. Analytics

We use a privacy-friendly, cookieless first-party analytics system hosted on Cloudflare Workers & D1 to understand how our platform is used (such as feature usage, session duration, and country-level region). No IP addresses, personal identifiers, or project contents are stored; instead, an irreversible daily session hash is generated in memory and discarded immediately. No tracking cookies or persistent identifiers are stored on your device. You can opt out at any time by setting localStorage key _ap_no_track to 1 (or pressing Ctrl+Shift+Alt+A in the app).

6. Payment Processing

Payments for AUDIOPATCH Pro subscriptions are processed by Paddle.com Market Limited (Judd House, 18-29 Mora Street, London EC1V 8BT, United Kingdom), acting as our Merchant of Record. Paddle is an independent controller for the processing of your order, payment, billing, tax and fraud-prevention data. When you make a purchase, Paddle collects and processes:

• Your name (if provided) and email address
• Payment information (credit card, PayPal, etc.)
• Billing address and country (for tax calculation)
• Transaction history

We do not receive or store your payment details. Paddle handles all payment data in compliance with PCI-DSS standards. For more information, see Paddle's Privacy Policy.

To provide the license, our server retrieves data about your transaction, subscription and customer record from the Paddle API (status of the subscription, subscription and customer identifiers, and, where needed, your name and email address). Name and email address obtained this way are processed in memory only, for example to send you the activation email (section 8), and are not stored in our database or in your license token.

7. License Verification & Device Management

AUDIOPATCH Pro uses a cryptographically signed license token that is stored locally in your browser (localStorage, key _ap_token). AUDIOPATCH does not use user accounts or passwords.

• Token content: plan (tier), expiry date, issue date, an internal license ID, and the Paddle subscription ID and transaction ID. The token contains no name and no email address. It is valid for 30 days and is renewed automatically while your subscription is active and the app can reach our server.
• Tokens issued before this update may still contain the name and email address given at checkout. They are replaced automatically by a token without these data the next time the license is refreshed while you are online.
• Server-side license record: in Cloudflare Workers KV we store one technical record per license: license ID, plan, subscription status and expiry, Paddle subscription, transaction and customer IDs, technical flags (for example "blocked" or "activation email sent") and timestamps. New records contain no email address and no name. For licenses issued manually by us, the record additionally contains an internal label (a pseudonym chosen by us) and the license token.
• Legacy records: license records created before this update may additionally contain name, email address and an internal note. These legacy records are being migrated and then deleted; until their deletion they remain stored in our database.
• License check: when you activate a license, and afterwards periodically while the app is open (at most about every 5 minutes and when you return to the app tab), the app sends the token and your device ID to our server. The server verifies the signature and the license record and, at most about once per day per license, asks Paddle for the current subscription status. If the server cannot be reached, Pro stays available until the token expires.
• Device ID: on first use of Pro your browser generates a random device ID and stores it in localStorage (_ap_seat). It is not derived from hardware or personal data, but it is a pseudonymous identifier (not anonymous): it recognizes the same browser installation. Our server does not store the device ID itself, only a keyed hash (HMAC-SHA-256, shortened) per license together with a timestamp. The device ID remains in your browser after signing out until you delete the site data.
• Device limit: Tech and Trial licenses can be used on 2 devices at the same time, Company licenses on 10. If a further device is activated, the device activated earliest is signed out. The limit is only enforced during online checks.
• Sign in by email: if you enter the email address of your subscription in the app, our server looks up the customer and active subscription at Paddle. Only if an active subscription exists, an activation link is sent to the email address stored at Paddle (never to a different address). The response shown in the app is always the same, whether or not a subscription exists. The email address is processed in memory only; for rate limiting only a keyed hash of it is stored for at most one hour.
• Subscription management: the button "Manage subscription" in the app asks our server to create a one-time link to your Paddle customer portal. The link is not stored by us. Alternatively, you can use the public Paddle portal: Paddle customer portal.
• Abuse protection: to protect license, login, feedback, bug report and admin functions against automated abuse we count requests per shortened SHA-256 hash of the IP address (for IPv6 only the /64 prefix is used) or per keyed hash of the email address. The counters expire automatically after 10 minutes to 1 hour. The hash is not salted; because the number of possible IPv4 addresses is limited, such a hash is treated as a pseudonymous personal data item, not as anonymous data. IP addresses are not stored in clear text by our application.

8. Email Delivery (Resend)

We use Resend (Resend, Inc., USA) as email service provider and processor. Resend sends:

• the activation email after a purchase or trial start, and the sign-in email you request in the app. These emails are sent to the email address stored at Paddle and contain your name (if stored at Paddle), your plan, and the activation link and activation code (your license token). Please do not forward these emails: the link and code give access to your license.
• feedback and bug reports you submit in the app (section 9) to us as the operator.

Resend processes recipient address, message content and delivery data and keeps delivery logs for a limited period according to its own settings. We have concluded a data processing agreement with Resend (Art. 28 GDPR). The transfer to the USA is safeguarded by the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) contained in this agreement. We have switched off open and click tracking for these emails. See Resend's Privacy Policy.

9. Feedback & Bug Reports

If you submit feedback through the optional in-app survey, we receive your rating, your free-text answers, an optional contact email address and the date. The feedback is stored in Cloudflare Workers KV (the latest 500 entries, for no longer than 365 days) and forwarded to us by email via Resend. A survey without any text answer is neither stored nor forwarded. We do not store your IP address with the feedback; for rate limiting only a hash is used as described in section 7. Please do not enter personal data in the free-text fields that you do not want us to process.

Bug reports. If you send a bug report, feature request, question or hardware request through the report window in the app, we receive your message, its category and, only if you enter them, your name and email address (used solely to reply). In addition, technical information is sent automatically and shown to you in the window beforehand: app version, browser, operating system, language, theme, whether collaboration is active, project architecture (festival or single act) and a timestamp. The project name and position names are only sent if you tick "Attach current project". Optionally you can attach the current project file (JSON), a screenshot or another file (max. 2 MB) and, for hardware reports, device data. The report is sent by email via Resend (section 8) to info@audiopatch.net; our server does not store the report. For rate limiting (max. 5 reports per hour) only a hash of your IP address is kept for one hour (section 7). The email remains in our mailbox until we delete it. Please do not attach data that you do not want us to process.

10. Cookies & Local Storage

AUDIOPATCH does not use cookies for tracking or advertising. We use localStorage (not cookies) for local application state, user preferences and, for Pro, the license token (_ap_token), the device ID (_ap_seat) and a timestamp of the last license check (_ap_last_check_ts). Reading and writing this information on your device is strictly necessary to provide the service you request and is based on Section 25(2) No. 2 of the German Telecommunications Digital Services Data Protection Act (TDDDG).

11. Legal Bases

• Art. 6(1)(b) GDPR (performance of a contract): license verification, device management, activation and sign-in emails, subscription management for Pro customers.
• Art. 6(1)(f) GDPR (legitimate interests): secure and stable operation of the website and servers, protection against abuse (rate limiting), product improvement through feedback, and handling of the bug reports, support requests and hardware requests you send us.
• Art. 6(1)(a) GDPR (consent): the optional contact email address you enter in the feedback form as well as the optional name, email address, project file and attachments you enter or attach in a bug report. You can withdraw your consent at any time with effect for the future.
• Payment, billing and tax processing is carried out by Paddle as an independent controller on its own legal bases (see Paddle's Privacy Policy).

12. Your Rights (GDPR)

Under the GDPR, you have the right to:

• Access — request a copy of your personal data
• Rectification — correct inaccurate data
• Erasure — request deletion of your data
• Restriction — limit processing of your data
• Portability — receive your data in a machine-readable format
• Objection — object to processing based on legitimate interests
• Withdrawal of consent — with effect for the future

To exercise any of these rights, contact us at info@audiopatch.net. We can delete the license data stored by us (license record and device records, including any legacy records containing your email address). If your subscription is still active, a new technical license record without name and email address is created the next time your license is verified, unless you cancel the subscription. Data held by Paddle and Resend is deleted by these providers; you can contact them directly, and we will support such requests.

13. Data Retention

We retain personal data only as long as necessary for the purposes described above:

• Collaboration data: deleted after 30 days of inactivity
• License records: kept while the subscription is active and deleted automatically 30 days after cancellation, pause or expiry of the subscription. Active records expire automatically if they have not been confirmed by Paddle for 70 days. Licenses blocked by us remain stored (without name and email address) until we delete them.
• Device records (hashed device IDs): removed when you sign out a device, when the license ends, and in any case automatically 70 days after the last change
• Abuse-protection counters: expire automatically after 10 minutes to 1 hour
• Technical processing markers (Paddle notification IDs, activation email markers): expire automatically after 7 days or 10 minutes
• Feedback: kept for up to 365 days and limited to the latest 500 entries; older entries are removed automatically when feedback is saved or listed. Deletion on request is possible at any time.
• Bug reports: not stored on our server; the email remains in our mailbox until we delete it (deletion on request is possible at any time)
• Legacy license records with name or email address: kept until their migration and deletion (see section 7)
• Subscription and payment records at Paddle: according to Paddle's Privacy Policy and statutory retention periods
• Emails and delivery logs at Resend: according to Resend's retention settings
• Analytics data: anonymized daily session metrics without personal identifiers

Our application does not write email addresses or license tokens into its server logs.

14. Supervisory Authority

You have the right to lodge a complaint with a supervisory authority. The responsible authority is:

Der Hessische Beauftragte für Datenschutz und Informationsfreiheit
Gustav-Stresemann-Ring 1, 65189 Wiesbaden, Germany

15. Changes to this Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision.