Legal information

Applies to MonoSynth v0.0.3-alpha at monosynth.app. Last updated .

Quick heads-up: MonoSynth is completely free! Everything you play, create, or tweak stays in your browser and is never sent anywhere. Keep in mind it’s still an unfinished alpha, so it comes as-is without any warranty. If you drop us a line via the contact form, your message gets emailed to us, and you'll get a copy too.

As of September 7, 2026, this site uses no cookies and zero third-party embeds. We keep track of visits in just two ways (detailed in our Privacy section): a lightweight analytics tool that leaves no trace on your device, and standard server logs showing page requests. Neither can identify you, and you can turn off the analytics tool with a single click.

Who operates this site

MonoSynth is built and operated by Micca Dev, the software development brand of Spectrovibe OÜ, a private limited company registered in Estonia and entered in the Estonian Business Register. Micca Dev is a brand and not a separate legal person: the company is the contracting party, and it is the data controller for the limited processing described under Privacy below.

Reaching us
The CONTACT link at the foot of every page. It opens a form that goes straight to a person, and it is the fastest route.
By e-mail
micca@monosynth.app
Company details
Our registry code and registered address are published in the Estonian Business Register, which is the authoritative source for them and is free to search by company name. They are not repeated here.

Terms of use

This is free, and using it is the agreement

MonoSynth costs nothing, requires no account and asks for no payment details. By loading and using it you accept these terms. If you do not accept them, the remedy is simple and complete: close the page. Nothing is left running on your machine and nothing has been sent anywhere.

It is an alpha, and there is no warranty at all

MonoSynth is provided "as is" and "as available", with no warranties, conditions or guarantees of any kind, whether express or implied. That includes, without limitation, any implied warranty of merchantability, of fitness for a particular purpose, of accuracy, and of non-infringement.

This is a work-in-progress alpha version. It is incomplete by definition. It may produce wrong sounds, unexpected levels, or no sound. It may stop working in a browser it worked in last week. Features will change, be renamed, or be removed. A patch saved by one version may fail to load in the next. There is no service-level promise, no uptime commitment, and no obligation on us to keep the site running, to keep it free, or to keep it at all.

Two practical consequences, because they are the ones that actually cost people something:

Limitation of liability

To the fullest extent permitted by law, the company is not liable for any loss or damage arising from your use of, or inability to use, MonoSynth. That includes lost work, lost patches, lost time, damage to equipment or hearing, and any indirect, incidental, special or consequential loss.

Nothing here removes rights you cannot be deprived of. If you are a consumer in the EU, your statutory rights are unaffected, and nothing on this page limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be excluded.

What you may and may not do with it

Use it to play, to design patches, to learn, to teach, and to make music. Recordings you make with it are yours; we claim no rights in your audio, your patches or your compositions.

Please do not:

Intellectual property, and why this is not a copy of anything

MonoSynth is an independent tribute to a classic 1978 Japanese semi-modular monosynth. It was written from published specifications and from a photograph of a front panel. It is not affiliated with, endorsed by, or connected to any instrument manufacturer, and no manufacturer's code, samples, firmware, ROM or artwork was used in making it.

Where a manufacturer's name or a model name is used in connection with MonoSynth, it is used nominatively - to state factually what a particular circuit is modelled on, and for no other purpose. Those names are the trade marks of their respective owners. Nothing on this site carries them. MonoSynth's own icon, shown in the browser tab, is original artwork belonging to the operator named above and is not derived from any manufacturer's mark.

The mathematics came from freely published literature and is cited so that anyone can check it. In particular:

Every source listed above is published and freely available, so the provenance of the mathematics can be checked by anyone who wants to, against the literature rather than against our word for it. If you believe something here infringes your rights, please get in touch with the specifics and we will look at it properly and quickly.

Changes, and ending it

These terms may change as the project does; the date at the top of this page is when they last did. We may change, suspend or withdraw MonoSynth at any time without notice - it is an alpha given away for free, and promising otherwise would be a promise we could not keep.

Governing law. These terms are governed by the law of Estonia, and disputes fall to the Estonian courts. If you are a consumer resident elsewhere in the EU, this does not deprive you of the protection of the mandatory rules of your own country's law, nor of the right to bring proceedings there.

Privacy

There is remarkably little to say here, and that is the design rather than an omission. MonoSynth has no user accounts and no database. The instrument is a single page of JavaScript that generates its audio on your own machine; the server that hands it to you is a static web server, and it has nowhere to put anything about you even if it wanted to.

What it does have is a count of visits, collected two ways and described one after the other below. Neither identifies you, neither reaches anything you play, patch or save, and the first of the two can be switched off.

What never leaves your browser

Your playing, your patches, your knob positions, your patch cables, your MIDI configuration and any audio you feed into the external signal processor are not transmitted anywhere. There is no upload, no telemetry, no crash reporting and no "improve the product by sharing usage data". The audio never leaves the audio thread in your browser.

MonoSynth asks for microphone access once, when you switch the instrument on, and releases the microphone again immediately. The permission is used to read the NAMES of your audio devices, which is also what your browser requires before it will name your loudspeakers. Granting it does not open the microphone: nothing is listening until you press ON under the SIGNAL IN socket, and you can decline and still use the instrument in full. When you do use the external signal processor, the audio is processed locally by the page and is never recorded, stored or sent. Revoking the permission in your browser ends it immediately.

What is stored on your machine

MonoSynth uses your browser's localStorage. It sets no cookies. Nothing in the list below is readable by us or by anyone else - it lives on your device, under this site's origin, and is sent nowhere.

monosynth.patch.<name>
A patch you chose to save, under the name you gave it.
monosynth.autosave
The patch you are working on, so a reload or an accidental tab close does not lose it.
monosynth.midi.<name>
monosynth.midi.active
Your MIDI interface profiles - which controller sends which CC - and which of them is in use.
monosynth.input
monosynth.output
Which audio input the external signal processor listens to, and which output the instrument plays through, if you have chosen either in Settings. Each is the identifier your browser gives that device for this site alone, with the name it had when you chose it, so the right one comes back next time. Choosing an output needs a Chromium browser; everywhere else the instrument follows your system setting and nothing is stored for it.
monosynth.consent
Your answer to the storage notice, with the date and the version of the notice you answered. This is the record that stops you being asked again.
monosynth.tour
That you have been shown the guided tour, with the date and whether you finished it or skipped it. This is the record that stops the tour opening itself every time you come back; Tour in the footer reopens it whenever you want it.
monosynth.probe
Written and immediately deleted, to find out whether this browser permits storage at all. It never persists.

All of the above is "strictly necessary" in the sense of the ePrivacy Directive: each entry exists only to provide something you explicitly asked for - to save a patch, to keep your settings, to remember your privacy choice. That is why the notice on this site tells you about them rather than asking permission for them. Asking whether we may remember the patch you just pressed SAVE on would be a question with one honest answer.

You can delete all of it at any time by clearing site data for monosynth.app in your browser's settings. Nothing is kept anywhere else, so that deletion is complete and immediate - and it is also irreversible, which is the other half of the advice to export your patches.

The COPY LINK button produces a URL with the whole patch encoded in its fragment - the part after the #. Browsers do not send a fragment to the server, so pasting one here reaches no one but the person you send it to. It does mean that a patch link is the patch: if you post one publicly, you have published that patch.

The part before the # is a different matter, and this is the honest half of that sentence. A shared link carries three ordinary utm_ parameters - utm_source, utm_medium and utm_campaign - which say only that the link was made by COPY LINK or printed on a patch sheet. Parameters are sent to the server, so if analytics is on for whoever opens the link, their visit is counted as having arrived from a shared patch rather than from nowhere in particular. They describe the link and not the person: there is nothing in them identifying you, the patch, or the machine either of you is sitting at, and they are the same three values in every link anybody makes. You can delete them from a link before you send it and the patch still loads.

The analytics, when it is on, is configured not to read the fragment at all - so a visit opened from a patch link is counted as having come from a shared patch, and which patch is not part of what is counted.

Cookies, and the notice

No cookies here at all. Anonymous analytics is on by default, you can switch it off whenever you like, and switching it off also turns off patch storage. The notice you saw on your first visit covers the browser storage listed above, plus that one optional extra:

Strictly necessary
Your patches, the autosave, your MIDI profiles, which audio input and output you chose, whether you have seen the guided tour, and this choice. All of it stays in your browser and is never sent anywhere. Without it, the instrument forgets everything the moment you reload the page.
Analytics
We count which parts of the instrument actually get used, so the next version follows what people play instead of guesswork. It is Umami, running on our own server at a.micca.dev - no third party, no cookies, nothing stored on your machine, and no tracking across other sites. It records page views, audio starts, which factory presets get loaded, patch saves, exports, shares, MIDI connections, PANIC presses, whether you accept or decline this notice, whether you skip the guided tour, and which of the YouTube or Instagram buttons you follow. It never sees your patches, their names, anything you type, or your IP address, which is hashed and kept only as a country. Accepting also switches on patch storage - saving, factory presets, import, export and share links - and saved MIDI setups, so a controller you have learned comes back next time. Decline and the synthesizer still works in full. You can change your mind here any time, and nothing you have saved is ever deleted.

Your answer lives in monosynth.consent, along with the date and which version of this notice you were answering. Change it or take it back at any time from the Cookies link in the footer of every page - withdrawing is exactly as easy as agreeing was, which is a requirement rather than us being nice about it. If this notice ever changes in a way that could change your answer, we raise its version and ask you again, because your old answer was to a different question. That happened on 7 September 2026, when analytics stopped being a plan and became the collector described above.

Analytics here does not run on consent, and we would rather tell you that than let you assume otherwise. Article 5(3) of the ePrivacy Directive - the rule that makes sites ask - is about storing things on your device or reading what is already there, and this collector does neither. What it does handle is your IP address, which our own server hashes with a rotating salt and keeps only as a country. The basis is our legitimate interest in knowing which parts of the instrument get used, kept as narrow as we could make it: one site, our own server, no profile, no advertising, nothing shared with anyone.

You can say no, and saying no also turns off patch storage. Article 21 gives you an absolute right to object, and we do not weigh anything against it. Decline stops the analytics script straight away, and that objection sticks - we never reset it by rewriting this notice. It also means no saving or naming patches, no factory presets, no import or export, and no share links. The synthesizer itself is untouched: every knob and key behaves identically, and nothing you have already saved is deleted - it is just out of reach until you accept, and back the moment you do. That is a deliberate trade rather than a technical one. The instrument is free, and knowing what people actually play is how we decide what to build next. You are entitled to disagree, and declining is how.

One honest caveat about that switch. It stops the analytics script, which is one of the two ways visits are counted here. It does not stop the second one - the count taken from the web server's own log - and it cannot, for a reason worth reading rather than taking on trust: Web server logs, and the second visit count explains it, including the part that does not flatter us.

Web server logs, and the second visit count

Like every web server, the one serving this page writes an access log. For each request it records the IP address, the time, the path requested, the HTTP status, the amount of data sent, and the browser's user-agent and referrer strings. This is ordinary server operation - it is what makes it possible to see that the site is up, that a deploy worked, and that nobody is attacking it.

Since 7 September 2026 those log lines are also counted. When the log shows that one of this site's four pages was requested, that one fact - which page, and when - is added up in the same Umami instance on our own server that the analytics script reports to, under a separate heading so the two counts are never mixed. It is the crudest possible measurement: a number of page requests. It knows nothing about what you did afterwards, how long you stayed, or whether you came back.

Why bother, when there is already an analytics script. Because a great many people block it - reasonably - and a count that misses everyone with a content blocker is not a count of visitors, it is a count of visitors without content blockers. The server log is the only place the site can see that a page was served at all.

And here is the part we would rather state than have you discover. The Decline switch in the storage notice stops the analytics script. It does not stop this count, and it cannot: to know that a particular request came from someone who had objected, the server would have to be told who you are on every request - which would mean putting a marker on your device and reading it back, and that is precisely the thing this site does not do. Honouring an objection here would require more tracking than ignoring it. So the server-side count is taken from every request, including yours, and it is limited instead: no identifier, no cookie, nothing joined to anything, nothing about you kept once the number has been added up.

Purpose
Operating and securing the service, and counting page requests. Legal basis: our legitimate interest in running a working, un-attacked website and in knowing roughly how many people it reaches (Art. 6(1)(f) GDPR).
What leaves the log
For a request for one of this site's pages: which page, and when. Your IP address is used to separate one visitor from another on the day and is turned into a salted hash and a country before it is stored - the same treatment the analytics script's is given, and the salt rotates. The full log line, with your address in it, stays on our server.
Retention
The log is capped in size and rotated - it holds only the most recent traffic and older entries are discarded automatically as new ones arrive. Nothing is archived, exported, or copied off the machine. What survives is the count, which is not about anyone in particular.
Sharing
Nobody. The logs and the counts stay on our own server. There is no analytics provider, no log aggregator and no third party of any kind - which is what makes the paragraph above a description of our own server's behaviour rather than of somebody else's product.
Objecting
Article 21 applies here as it does everywhere else, and the switch in the storage notice is not the way to use it, for the reason given above. Write to us and say so: an address can be excluded from the counting by hand. That is a worse mechanism than a switch and we are not going to dress it up as a better one.

Contact messages

If you use the contact form, we process what you put in it. This is the only part of the site that involves personal data in any substantial sense, so it is set out in full.

What is collected
Your name, your e-mail address, your subject line and your message - the four fields you filled in. Nothing else about you is added to the message.
What it is used for
Reading and answering your message. Nothing else. It is not used for marketing, is not added to a mailing list, and is not profiled.
Legal basis
Answering a message you chose to send us - our legitimate interest, and yours, in a reply (Art. 6(1)(f) GDPR), or taking steps at your request before entering into an arrangement where that is what you have written about (Art. 6(1)(b)).
The copy to you
A copy of your message is sent to the address you gave, from noreply@monosynth.app, so you have a record of what you wrote and can tell that it went through. That address is not monitored - mail sent to it is delivered and kept, but nobody reads it. Use the contact form, or the address at the top of this page, if you need an answer.
Where it goes
To a mailbox on our own mail server, in Estonia. The form posts to this site's own origin and the message is turned into e-mail by a small service on the same machine. There is no form provider, no CRM, no helpdesk platform and no third-party e-mail service in the path. Your message does not leave the EU. The copy sent to you, of course, travels to wherever your own mail provider is.
Anti-abuse
To stop the form being used to send spam, the service briefly holds your IP address in memory to count how many messages have come from it recently. It is not written to a database and is discarded within the hour. Your IP address is also in the ordinary server log described above.
Retention
Your message stays in the mailbox for as long as it takes to deal with it, and while it is useful as a record of the exchange. Ask us to delete it and we will.

What we do not do

Your rights

Under the GDPR you have the right to ask for access to the personal data we hold about you, to have it corrected or erased, to have its processing restricted, to object to processing based on legitimate interests, and to receive it in a portable form. Given the above, in practice this concerns contact messages and server logs, and nothing else.

Get in touch. There is no form to fill in and no verification hoop beyond establishing that you are the person whose message we are talking about. We will answer within a month.

Complaints

Tell us first, and please be specific. Bugs, wrong behaviour, something on this site that reads as untrue, a privacy concern, or a rights claim - use the CONTACT form in the footer, or the address at Who operates this site. A complaint that names the browser, what you did and what happened is one that can actually be acted on. We read everything and we would much rather hear about a problem than not.

If a bug report is about the instrument, the most useful single thing you can include is the build identifier below, which names the exact commit you were running. Copy the whole block into your message. 

version: reading...
commit:  reading...
variant: reading...
built:   reading...

If you are not satisfied with how we handle personal data you have the right to complain to a data protection supervisory authority. Ours is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee). You may also complain to the supervisory authority in the EU country where you live or work.

Changes to this page

This page changes when the site does. The date under the title is when it last changed, and it is the only place that date is kept - there is no archive of previous versions, because for a page this size a changelog would be longer than the page.

If a change affects what is stored on your machine or what is done with anything you send us, the version of the storage notice is raised as well, and you are asked again rather than silently carried over.

Plain language has been preferred to legal formality throughout. Where the two conflict, this page means what it plainly says.