MelogniteMelognite
Data protection

PRIVACY POLICY: Melognite (melognite.com & melognite.app)

Last updated: 31 October 2026 (composition on our server, guest preview, rate limits and fair-use counter in 3.6 to 3.6c; certificates created and sealed on our server in 3.4b; hosting and server logs in 3.1; usage records and signing service in 3.4b; separate cancellation and withdrawal pages in 3.4c; embeds 3.10; recipients and transfers in 4 and 5; retention in 6; your right to object in 7)

1. Controller

Casa Santa Solutions UG (haftungsbeschränkt) (Amtsgericht Wuppertal, HRB 37143), represented by Kristina Julia Stüwe, Beethovenstraße 14a, 42579 Heiligenhaus, Germany · hello@melognite.app. No data protection officer has been appointed; the statutory appointment thresholds are not met. Data-protection enquiries: hello@melognite.app.

2. Scope

Covers melognite.com (informational website) and melognite.app (service). Where third parties act as independent controllers (e.g. the payment provider), their own notices apply additionally.

3. Processing activities, purposes and legal bases

3.1 Server log files (both sites). IP address, date/time, requested resource (for composition requests: the address of the action, not the recipe), referrer, user-agent, to deliver and secure the service. Art. 6(1)(f) GDPR (our legitimate interest in delivering the pages and in detecting attacks). The logs are deleted after 30 days. Hosting processor for both sites, including our backend server: IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany, under an Art. 28 data-processing agreement.

3.2 Scripts, samples and fonts: served by us. All scripts, instrument samples and web fonts used by the Website and the App are hosted on our own servers (IONOS, Germany). No content-delivery network and no third-party font service is contacted when you load our pages. Our pages load no third-party payment script; the checkout described in 3.4a is a separate page hosted by our Merchant of Record and opens only when you actively start a purchase.

3.2a Web fonts. All typefaces are self-hosted under their respective font licences (SIL OFL 1.1; ITF Free Font License; see the Licenses page). Your IP address is not transmitted to Google, Fontshare or any other font provider.

3.3 Account & passwordless sign-in (App): a one-time code or sign-in link by email. Email address, authentication tokens/links, login timestamps, to provide the account. Art. 6(1)(b).

3.4 Subscriptions, payments, entitlements. Payments for paid plans are handled by our Merchant of Record, FastSpring (the FastSpring contracting entity named at checkout and on your receipt), an independent controller for payment data (we do not receive full payment data). We receive limited subscription/entitlement data (e.g. email, plan, status, subscription ID) via signed server notifications, stored on our backend (our server at IONOS, Germany, and our managed database at Supabase, hosted in the EU). Art. 6(1)(b). FastSpring is based in the USA; the payment transaction you request is processed there (Art. 49(1)(b) GDPR; FastSpring additionally relies on its own transfer safeguards). MoR privacy notice: fastspring.com/privacy.

3.4a Checkout page. Our sites load no payment script in normal use. When you actively start a purchase or open subscription management, you are taken to a checkout or portal page hosted by FastSpring; only then does FastSpring receive your IP address and may set strictly functional cookies for the checkout you requested. Legal basis: Art. 6(1)(b) GDPR and § 25(2) TDDDG (necessary for the service you explicitly request).

3.4b Usage records & file fingerprint. To run your plan we store, per account, the usage records it needs: the identifiers of songs you have counted (genre + seed number), the fingerprints (hashes) of exported musical versions, timestamps and your plan context. Where songs are composed on our server (3.6), each composition step by a signed-in user is checked against these records before the result is delivered; replaying or changing a song you already counted does not count again. In addition we record usage events (which kind of action was used on a counted song, e.g. „vary melody“, and when) to recognise abuse and to see which features are used; these events are kept for 13 months and then deleted. These records contain no audio and no musical content beyond those identifiers; we treat them as pseudonymous personal data. Legal basis: Art. 6(1)(b) GDPR for allowances and billing; Art. 6(1)(f) GDPR for abuse prevention and feature statistics (our legitimate interest in a secure, fairly metered service and in improving it; you can object, Section 7). Every export is accompanied by a provenance certificate (generation seed, recipe parameters, engine generation, export timestamp, SHA-256 digests of the exported files; see Terms 4.3b) that contains no name, email address or account identifier; it is created on our server together with the export. The certificate is then signed with our key by our signing service (a function running at Supabase, see 3.4); only its SHA-256 hash is forwarded by that service to an independent time-stamping authority (freetsa.org, RFC 3161), which therefore receives no personal data. The signature and time-stamp are written into the certificate and not stored by us beyond the request log (Section 3.1). Legal basis: Art. 6(1)(b) GDPR (the provenance record you request) and Art. 6(1)(f) GDPR (abuse prevention). Retention: Section 6.

3.4c Cancellation and withdrawal requests. When you use our cancellation page or our withdrawal page, we process the details you enter (name, email address, plan, type of request, requested date, reason or message) and the time we received them. To carry out a cancellation, we look up the matching subscription at our Merchant of Record, FastSpring (subscription and account ID, plan, billing dates and the name on the FastSpring account, which we only compare with the name you entered), cancel it there with effect from the end of the current billing period where the case is clear, and send you a confirmation by email (via Resend, see 3.5) stating the date your subscription ends. The confirmation contains a personal link that lets the account holder keep the subscription if the request did not come from them. To run this, to recognise duplicate or abusive requests and to protect your subscription against cancellations by third parties, we keep a record of each request: a reference number, a keyed hash of your email address (never the address itself), a masked form of it (e.g. a***@example.com), the FastSpring subscription and account ID and the product (plan) concerned, the result of the name comparison, the outcome and the relevant dates; it contains no name and no free text. For abuse protection we also keep a keyed hash of your IP address that changes daily and is deleted after two days. Legal basis: Art. 6(1)(b) and (c) GDPR (performing the contract; § 312k BGB) and Art. 6(1)(f) GDPR (protection against cancellations by third parties and abuse). Retention: the record is deleted 400 days after the request or after the end of the cancelled subscription, whichever is later; the emails themselves are kept as business correspondence for the statutory retention periods.

3.4d Checking a certificate (/verify/). When you check a sealed certificate at /verify/, the page sends the text of the certificate to our composition server (3.6), which rebuilds the piece on the engine generation named in the certificate and returns, for every track, only whether its fingerprint agrees. The seal check and the comparison with files you attach run in your browser; attached files are not uploaded. The certificate contains no name, email address or account identifier (3.4b), and you do not need to be signed in. The server keeps no copy of the certificate after answering and does not log its content; your IP address is processed as for any request (server log 3.1; rate limits as a keyed hash, 3.6b). Legal basis: Art. 6(1)(f) GDPR (our legitimate interest, and that of anyone relying on a certificate, in verifiable provenance of exported music).

3.5 Transactional email (Resend). Login (magic-link) and service emails are sent via Resend, Inc., 2261 Market Street, San Francisco, CA, USA, as our processor under an Art. 28 data-processing agreement, processing the recipient email address, the transactional message content (including one-time sign-in codes and links) and delivery/log metadata; Resend hosts and stores this data, including message content, in the United States. Even where an EU sending region is used, Resend stores account, log and delivery metadata in the United States; these transfers are safeguarded by the EU Standard Contractual Clauses and the EU-US Data Privacy Framework. Legal bases Art. 6(1)(b) and (f). Resend privacy notice: resend.com/legal/privacy-policy.

3.6 The generator itself: composition on our server. Melognite is deterministic. Songs are composed on our own server (IONOS SE, Germany; see 3.1); while we move genre by genre, some genres may still compose in your browser. To create, change or export a song, the App sends the song recipe (genre, seed, style and your settings) to our server, which returns the notes and, on export, the files (MIDI, ZIP, provenance certificate). If you are signed in, each request also carries your sign-in token; the server reads your account ID and email address from it to recognise you, and checks your plan and allowances at our account database (Supabase, see 3.4) before it delivers the result. The server keeps no copy of the recipe, the notes or the files after answering, and it does not log their content. What is kept is described in 3.4b (usage records of your account) and 3.6a to 3.6c (counters). No audio, no MIDI files and no sketches are stored; your own browser keeps your working state, history and Takes locally on your device (3.8). No content profiling. Legal basis: Art. 6(1)(b) GDPR (providing the App you use; for guests, the preview you request, see 3.6a) and Art. 6(1)(f) GDPR (protecting the composition engine against copying and misuse).

3.6a Guest preview (without an account). Without an account you can hear up to three songs per 48 hours, each as an excerpt of at most one minute, without export, without MP3 and without beta genres. To count these previews we do not use cookies or any storage on your device. Instead our server computes, for each request, a keyed hash (HMAC-SHA-256 with a secret key) of your IP address; IPv6 addresses are first shortened to their /64 network, IPv4 addresses are hashed in full. For each preview we store this hash, the time and an identifier of the song (derived from genre and seed) in a database on our server; the IP address itself is not stored by this function. Entries are deleted once they are 48 hours old. Before delivering a guest preview the server also asks our account database whether the seed is reserved; that request contains no data about you. Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest: to offer a free preview without requiring an email address, while keeping it short enough that the free account remains the way to use Melognite, and protecting our server capacity and composition engine against automated mass use. We have weighed this against your interests: the hash does not reveal your address to anyone without our secret key, it is kept for only 48 hours, it is not combined with other data, not used for profiling and not shared. A counter on your device would be easier to circumvent and would itself require access to your device (§ 25 TDDDG); requiring an account would mean collecting more data. Several people sharing one connection (e.g. a household or office network) share the three previews. You can object at any time (Section 7).

3.6b Rate limits (all users). To protect the service against overload and automated misuse, our server counts requests per account and per keyed IP hash (as in 3.6a) within short windows (at most one hour). These counters are held in working memory only; they expire with their window and are lost on every restart; nothing is written to disk. Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in a stable, secure service; the counters are short-lived and contain no address).

3.6c Fair-use export counter (accounts). To enforce the daily fair-use limit for exports, our server stores, per account and genre, the number of exports of the current day (UTC) in its local database. These entries are deleted after three days. Legal basis: Art. 6(1)(b) GDPR (the allowances of your plan) and Art. 6(1)(f) GDPR (preventing mass extraction).

3.7 Launch-notification / newsletter (Brevo). If you submit your email for launch news, we process it for that purpose on your consent (Art. 6(1)(a)), using double opt-in; withdraw any time (unsubscribe link), without affecting past processing. This is operated through our email-marketing processor Brevo (Sendinblue SAS, 106 boulevard Haussmann, 75008 Paris, France) under an Art. 28 data-processing agreement, processing your email address, the double-opt-in confirmation and technical delivery metadata within the EU. Brevo privacy notice: brevo.com/legal/privacypolicy.

3.8 Cookies & local storage. We set no analytics or advertising cookies. The App stores the following data locally on your device (localStorage/sessionStorage); none of it is stored on our servers. Where a row says so, it is sent to our server as part of a request and not kept there (3.6):

You can clear all of this at any time via your browser’s site-data settings. Any storage that is not necessary in the above sense (incl. embeds, 3.10) is set only with prior consent (§ 25(1) TDDDG).

3.9 Analytics / error tracking. Currently none. We do not use analytics or error-tracking services.

3.10 Embedded third-party content. We currently embed no third-party content (videos, social posts, players). If we introduce such embeds, they will load only after your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR), and we will update this notice first.

3.11 Rights reports („report a seed“). If you use the report form to tell us that a generated result infringes your rights, we process the seed, the genre, any share link, your description of the work and your reasoning, your name and email address and the capacity in which you act, plus the time of receipt. Purposes: (a) blocking the reported seed, (b) assessing the report, (c) replying to you, (d) documenting who reported what and when; this is what protects both sides if a report is later disputed. Legal bases: Art. 6(1)(c) and (f) GDPR (handling notices of infringement; defending against claims; preventing misuse of a procedure that blocks before it checks). Providing the data is voluntary, but without the seed we cannot act at all. Recipients: no one beyond us, unless a legal claim makes disclosure necessary. Retention: the report and our decision for three years from the end of the year of the decision; attached files for twelve months; longer while a dispute is pending. Blocked seeds are kept indefinitely as a bare number without any personal data attached; a block that expires would silently undo itself.

3.12 Seed reservation. When you reserve a seed we store, linked to your account: genre, seed number, date, guaranteed term, the FastSpring order reference and the digest of your reservation code (never the code itself). A public register lists genre, seed number, date and scope of active reservations, without any personal data. To keep our promise verifiable we also keep, without any link to a person, a counter per genre and seed of how many accounts have exported that seed („release marks“); this counter is not deleted with an account. Legal basis: Art. 6(1)(b) GDPR (performance of the contract). Retention: for the guaranteed term of the reservation and the statutory retention periods for invoicing data.

Do you have to provide data? You need not give us any data to read our pages. To use the App with an account you must provide an email address (3.3); without it we cannot open an account. To buy a plan, FastSpring needs the payment data it asks for. Everything else is voluntary unless a section says otherwise.

4. Recipients / processors (summary)

Hosting IONOS SE (DE, melognite.app and melognite.com, incl. all scripts, samples, self-hosted fonts and the composition server; the recipe and the notes go to no other recipient); backend, sign-in & managed database Supabase (contracting party Supabase Pte. Ltd, 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513; processor under an Art. 28 data-processing agreement; data hosted in Ireland (EU); third-country access see Section 5); transactional email Resend, Inc. (USA; SCC/DPF, see 3.5); newsletter Brevo / Sendinblue SAS (FR, EU, see 3.7); payments FastSpring (Merchant of Record) (independent controller, USA; no payment script on our pages, checkout is hosted by FastSpring and opens only on checkout intent). Data-processing agreements are in place with our processors.

5. International transfers

We keep your data in the EU wherever we can. Transfers outside the EU/EEA happen in these cases: (a) Resend (USA, transactional email, see 3.5): EU Standard Contractual Clauses and the EU-US Data Privacy Framework; (b) Supabase: your data is hosted in Ireland (EU); our contracting party Supabase Pte. Ltd (Singapore) and its affiliates and sub-processors may access it from Singapore or the USA (e.g. for support and operations), safeguarded by the EU Standard Contractual Clauses in the data-processing agreement; (c) FastSpring (USA, independent controller): when you buy, FastSpring processes your data in the USA because that is necessary for the purchase you request (Art. 49(1)(b) GDPR); when we look up or cancel your subscription at FastSpring on your request (3.4c), we transmit the data needed for that on the same basis; (d) consent-based embeds, if we introduce them (3.10): your explicit consent (Art. 49(1)(a) GDPR). You can obtain a copy of the Standard Contractual Clauses from us (hello@melognite.app).

6. Retention

Only as long as necessary: server logs 30 days; guest preview counter (keyed IP hash, time, song identifier; 3.6a) 48 hours; rate-limit counters (3.6b) at most one hour, in working memory only; fair-use export counters (3.6c) 3 days; composition requests (recipe, notes, files; 3.6) not stored; account data for the account's life then deleted/anonymised, subject to statutory tax/commercial retention (up to 6 to 10 years) for invoicing data; usage records (3.4b) for the life of the account plus the statutory retention periods that apply to billing records, usage events (3.4b) for 13 months; newsletter data until withdrawal. Account deletion: email hello@melognite.app and we delete your account and its usage records within 30 days, except data we must retain under statutory duties; residual copies in our routine backups expire with the backup rotation. An active paid subscription must be cancelled first (Section 3.4).

7. Your rights

Access (Art. 15), rectification (16), erasure (17), restriction (18), portability (20), objection (21), and withdrawal of consent (7(3)) any time. You may complain to a supervisory authority, in particular the competent Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Düsseldorf. Contact: hello@melognite.app.

Guests (3.6a, 3.6b). We cannot tell who is behind a keyed IP hash, and we do not collect extra data to find out (Art. 11 GDPR). Rights under Articles 15 to 20 therefore apply only if you give us the information that lets us find your entries: send us the IP address you used and the approximate time; we then compute the hash, answer your request and, on objection or erasure, delete the matching entries. Entries are deleted after 48 hours anyway.

Your right to object (Art. 21 GDPR)

Where we process your data on the basis of our legitimate interests (Art. 6(1)(f) GDPR; marked as such in Section 3, in particular server logs 3.1, usage events 3.4b, guest preview counter 3.6a and rate limits 3.6b), you have the right to object at any time, on grounds relating to your particular situation. We then stop the processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. If you object to the guest preview counter, we delete your entries. A short email to hello@melognite.app is enough.

8. Automated decision-making

We do not use automated decision-making with legal or similarly significant effects (Art. 22 GDPR).

9. Security; children; changes

Appropriate technical/organisational measures (incl. TLS). Not directed to children under 16; no knowing processing of their data without parental consent. We may update this notice; the current version applies.