Privacy
Updated 10 October 2026
Who handles your data
Gordon Friebe, trading as Primecoder, is responsible for the website and Undo Machine licence service. Contact gfriebe@primecoder.de; see the legal notice for operator details.
Your music stays on your computer
Instrument setups and snapshots are stored locally. Buying or activating Full does not upload your sounds, snapshots or DAW project. Device reports are sent only when you choose to submit them, as described below.
Purchases, activation and recovery
Paddle processes checkout, billing details, payment and receipts as the reseller. I do not receive your full card details. Paddle handles its own data processing under the Paddle privacy notice. The checkout loads Paddle’s payment tools; these can process connection and device information and use cookies needed for checkout.
The licence service stores purchase and customer references, the purchased product, payment and refund status, activation records and a one-way identifier derived from each installation’s public key. These connect a verified purchase to your computers and help prevent unauthorised activation. They do not contain your instrument settings or music.
If you request licence recovery, I use your purchase email to check your purchase with Paddle and send a verification code through Mailtrap. The service keeps a one-way email identifier and code identifier; the delivery queue holds the email and code encrypted. Recovery codes expire after ten minutes. This expiry does not automatically delete purchase or recovery records.
Purchase and activation records are kept to provide your continuing licence, handle refunds and meet applicable accounting and legal requirements. Recovery records currently require manual deletion. Contact me to ask about access or deletion; records needed for an ongoing licence or legal obligation may need to be retained.
Contact messages
Contact messages are private. I store the text you submit, your email address if supplied, a submission reference and the time. I use these to answer you—not for marketing.
Your submission is saved on my server before I confirm it. Mailtrap sends an email notification to my Google-hosted inbox; delivery failures are retried. Mailtrap and Google process the notification, including the information you submitted. You do not need an account with either service to contact me.
Website copies are automatically removed after 180 days. Email copies and replies are kept in my mailbox while I handle your request. Please don’t include passwords, private recordings or other sensitive information.
To limit spam, I keep a keyed, one-way representation of the network address with a request counter for up to one hour. Raw addresses are not saved in the messages database or application request logs. The form does not set cookies or automatically publish device suggestions.
To request deletion, contact me with enough information to find your message. If you need an alternative to the form, write to app@primecoder.de.
Device suggestions & app reports
Website device suggestions can omit an email. App device reports require one so I can follow up. Device suggestions and reports are stored privately on my server for review. They include the device details and information you choose to send. In the app you can preview the exact report, optionally include MIDI recordings, port names and notes, and enter a required reply email. If you have purchased Full, the app can retrieve your purchase email after proving ownership of its activated installation and prefill it. The address is cached in encrypted storage on your computer. You can enter an address yourself if the lookup is unavailable. Nothing is sent until you choose Send for review. MIDI recordings may include sound settings and patch names.
A submission creates an unreviewed device record. Only reviewed device information and images are published in the catalogue; the submitted recording and reply address remain private. Supporting reports are retained for device research until manually removed, rather than expiring with contact messages. You can request removal using the contact details above.
Mailtrap sends a notification to my Google-hosted inbox containing the device name, reply address and a private review reference—not the MIDI recording. Developer replies, requested test instructions and experimental download links are emailed to the address on your report through Mailtrap. You can reply to these emails or ask me to stop follow-up emails. The submission form uses short-lived, one-way network counters to limit abuse. It does not set a visitor account cookie.
Catalogue updates & administration
The app downloads approved device information and thumbnail images over HTTPS, checks for updates daily, and keeps an offline copy on your computer. These downloads do not upload your instrument setup or recordings. The private catalogue editor uses an eight-hour sign-in cookie available only to the administrator.
About voting
Vote for devices you’d like me to support. Votes are a signal of interest, not a delivery promise or a verified one-person poll.
No account. No email.
When you first vote, this site sets a random, first-party browser cookie. It lets me remember your choices and lets you remove a vote. It lasts up to one year and isn’t used for advertising or analytics.
The server stores a one-way identifier, your selected device IDs and vote times. Only aggregate totals are public. Votes are removed from the active database after a year unless renewed; the cookie has the same maximum lifetime. You can also remove a vote by clicking its button again.
Keeping it useful
To slow automated voting, the service briefly counts requests using a one-way representation of the network address. It keeps that counter in memory for at most ten minutes; it does not save the raw address in the voting database or application request logs. Server infrastructure error logs may contain connection information.
Clearing cookies or using another browser can defeat browser-level deduplication. I treat the totals as guidance, not a competition or a commitment to build something.
Website connections and traffic
The website server receives your network address, requested page, time and browser information to deliver pages and protect the service. Private access logs are rotated daily with 14 rotated logs retained. Private traffic reports mask network addresses and remove query strings and referring pages. I use Plausible, hosted on my own server at stats.primecoder.de, to count page visits, referral sources and download-button clicks. This website analytics uses no cookies and does not track you across websites. A download-button click is not a record of an installation. I do not send contact-form contents, licence details or device recordings to Plausible.
Installer downloads
Amazon Web Services (AWS) delivers installer files from its S3 storage in Stockholm, Sweden. Your browser connects directly to AWS, which receives your network address and the request information needed to deliver the file.
Installer downloads are counted by day, version and platform. These totals count download starts, not individual people or completed installations. The download counter stores no network addresses, cookies, browser details or referring pages. Download routes do not write access logs; infrastructure error logs may still contain connection information. Aggregate totals have no automatic expiry.
Optional app usage reports
Newer app versions offer an optional usage-sharing choice in Privacy. Sharing is off until you allow it. Reports contain daily app activity and feature milestones, bounded failure categories, the supported instrument or DAW type, app and system versions, and a random installation identifier. They contain no patch contents, MIDI recordings, project names, email addresses or raw diagnostic logs. They are not linked to purchases or website downloads.
Usage reports are retained for up to 90 days. Only reports from the last seven days are sent; older unsent reports are cleared when the app next runs. Turn sharing off in Privacy to clear unsent reports and stop future collection. Resetting the identifier starts a separate record; previously received reports expire within 90 days. The server necessarily receives a network address to handle the connection, but it is not stored in the usage database or access logs. Infrastructure error logs may contain connection information.
Update-feed requests are counted separately by UTC day, without an installation identifier, network address, referring page or browser details. These are request totals, not unique users. Aggregate totals have no automatic expiry.
The app’s Feedback form sends only the message, optional reply email and setup summary you choose to include. It uses the private contact inbox described above; sending feedback does not enable usage sharing.
Why this information is used
Purchase, activation and requested recovery information is used to perform the software licence agreement. Records required by law are kept to meet legal obligations. Handling enquiries, reviewing voluntary contributions, preventing abuse and maintaining the website are legitimate interests. Optional submissions are limited to what you choose to send. Optional app usage reporting is based on your consent, which you can withdraw in Privacy.
Your data rights
You may request access, correction, deletion, restriction or a portable copy of personal data where applicable, and object to processing based on legitimate interests. Write to gfriebe@primecoder.de. You may also complain to your local data protection authority, including the Berlin Commissioner for Data Protection and Freedom of Information.
Your choices
Browsing does not require a voting cookie. It is set only when you vote. To remove your choices, use the “Voted · undo” buttons before clearing the cookie; once the cookie is gone, I cannot identify those anonymous votes for you.