Terms

Who runs this

Hypertoire is published by one person, in France, reachable at hello@hypertoire.com. There is no company behind it and no team. The site, and every score uploaded to it, sits in the European Union: Scaleway hosts the site in France and keeps the scores on its Paris object storage, so an uploaded page stays in the Union at every step, including the minutes it spends being read. Two things leave it, both named below: the error reports the app sends itself, which carry no personal data, and a video once play is pressed on it.

What Hypertoire is

Hypertoire holds the pieces an account is working on and lays them out to be read from a device on the music desk. It slices a page of score into individual bars, which is what allows a passage to be looped, fingering to be marked on it, and a recording to be followed across it where one exists. A recording is optional: an imported piece has none, and it is complete without one.

The account

An account is one person: one address, one password; the address has to be one that reaches its holder, since that is how signing in works and how the account would be recovered, and the password stays with the holder, since anything done from an account is treated as done by them. An account holder has to be old enough to enter a contract where they live, and below that age the account belongs to whoever is responsible for them. It can be closed at any time, from its settings or by writing to the address above, and closing it deletes the library, the uploads and the marks made on them.

Uploaded scores

An uploaded score stays its owner's. It goes into one library, is never added to the shared catalog, is never shown to another account, and is never used to train anything: uploading a page grants Hypertoire no rights over it beyond what running the service takes, which is storing it, slicing it into bars, building a cover from its opening, and showing it back on the holder's own devices. Nothing else, and nothing at all once it is deleted. Material there is no right to put there must not be uploaded: an edition the holder owns may go in for their own use, but an edition they do not own, a scan sent to them to pass around, and anything meant for redistribution through the service, may not.

The shared catalog

Only the publisher puts anything into the shared catalog, and what goes in is public-domain editions, which is a judgement about a particular edition in a particular country and can be wrong: anything in the catalog that should not be there comes down while it is checked, and the address above reaches the person who can do that. It is a convenience rather than the product: the app is built for the pages an account brings to it.

Plans, payment and refunds

Three library sizes: Prelude holds one piece, Étude five, Sonata thirty, and once billing starts Étude is €5 a month or €50 a year, Sonata €20 a month or €180 a year, tax included and paid a month or a year at a time. The size is the whole library, and a catalog piece on a shelf takes a slot exactly as an import does.

There is no checkout yet: until there is, every plan is free and plans can be switched (with one move refused, a plan smaller than the library it would have to hold: the library comes down to the new size first, and nothing is hidden or deleted to make room) at no cost.

When there is a checkout: a first payment can be undone within thirty days, refunded in full and without questions, which sits on top of the withdrawal right French and European consumer law already gives a consumer and takes nothing away from it; a plan renews until it is cancelled, which stops the next renewal, leaves the plan running to the end of the period already paid for, and can be done at any time from the account settings or by writing to the address above; and a failed payment is notified before anything changes: an unpaid account drops to Prelude rather than losing its pieces, and the pieces over the cap become unreadable rather than deleted.

Artificial intelligence

No part of the app calls a language model. There is no Claude, no Gemini, no GPT and no other hosted model behind any screen here: no SDK for one is installed, no key for one exists, and no request goes to a model vendor, so nothing uploaded or typed is sent away to be answered on and nothing is sent away to train on either. Which also means nothing here is a chatbot or an assistant: nothing in it generates writing, pictures or sound, and nothing listens to playing, there being no microphone and no MIDI input. Support is answered by a person on every plan.

Machine learning does one job here, and it is not a conversation: it reads an uploaded page to find the bars and noteheads on it, and the title off the first one. That reading runs on models the service runs itself, on a machine rented for the minutes it takes: reading a page needs more computing power than the small machine serving the site has, and the rented one is in the European Union and named below. The models are open ones, and what runs them is rented hardware, not a model company being sent a page and asked about it.

What is kept

An email address and a hash of the password, so signing in works. The scores uploaded and the bars they were sliced into. The fingering marks, the library and the plan. Nothing else is collected, and none of it is sold, rented or shared for advertising, because there is no advertising.

Four companies touch it: Scaleway (France: hosts the site and stores the score images), Modal (rents the machine that reads an uploaded page, pinned to the European Union; the bars come back to the Paris storage and nothing stays on it once the import ends; it sees the page and nothing else, no email address and no account), Sentry (United States: stores errors and the logs of an import, so a failure can be diagnosed; what reaches it is the address of the page, the code that broke and the number of the piece being worked on, and no email address, no name and no IP address goes with it) and YouTube (serves a video, and only once play is pressed on one: until then no YouTube request is made from the page, the poster image coming from a cookieless host and the player itself from youtube-nocookie.com, and pressing play hands that video to Google under their terms).

Everything is kept while the account exists, and closing it deletes the lot, apart from anything the law requires be kept longer, such as invoices once billing exists; backups roll over within thirty days. The GDPR gives rights over all of it: a right to a copy of what is held, to have it corrected, to have it deleted, and to object to its being processed, with a complaint always available to the CNIL, the French data protection authority, and a request to hello@hypertoire.com will be carried out.

Cookies

Two, both necessary: one that keeps a session signed in and one that protects forms from being submitted from another site. There is no analytics cookie, no advertising cookie, and nothing that follows a reader off this site, which is why consent has never been asked for.

Availability, and keeping copies

Hypertoire is run carefully but on modest hardware by one person, so it can be down, it can be slow, an import can fail, and features can change or be withdrawn; a change that would cost an account something it paid for is announced first. A score is worth keeping a copy of elsewhere. This is the one thing in these terms worth acting on: the app holds a copy of a set of pages, not the only copy of them.

Liability is limited to what French law allows: nothing here excludes liability for death, personal injury, fraud, or anything else the law does not allow to be excluded, and beyond that, liability for any claim is limited to the amount paid in the twelve months before it, with indirect loss excluded.

Ending it

An account holder can stop at any time by closing the account. The publisher can close an account that breaks these terms, in particular one uploading material it has no right to or redistributing the catalog, and will say why. A paid account closed by the publisher without such a breach is refunded for the unused part of its period.

Changes to these terms

These terms change when the product does, and the date at the top is the version in force. A change that matters is announced by email before it takes effect, one that matters being a change to what has been paid for or to what is done with the data described above. Using the account after that is how the new version is accepted; otherwise the account can be closed, and any unused part of a paid period is refunded.