OrynosMusic
Temporary Free phase · 5,000 weekly credits after verification

All modules and models are included for verified accounts. Each render uses the displayed model credit cost. Purchased credits remain in your account; new purchases are paused.

Sign in and verify your email to activate Free access. Sign in · Create account

Privacy Policy

Last updated: October 20, 2026 · Consent text version 2026-08-09.1

1. Controller and contact

Mehdi Sakkal, Werthmühlenstr. 27, 49477 Ibbenbüren, Germany, is the controller for OrynosMusic. You can contact the controller at mehdisa172@gmail.com. Further details are available in the Legal Notice.

DAW plugin accounts

The Windows plugin processes audio locally. It does not transmit tracks, projects, project names or hardware identifiers. When you connect it, we process your account ID, username, email-verification state, membership entitlement, a random installation ID, credential hashes and connection timestamps. This is necessary to provide your account licence (Art. 6(1)(b) GDPR) and prevent account abuse (Art. 6(1)(f)). Your existing website login handles the password; the plugin never receives it. The server stores refresh credentials only as hashes; Windows encrypts the local sign-in cache with user-bound DPAPI. Your DAW project contains settings, not credentials.

Pending connection requests expire after ten minutes and are removed on subsequent account-protocol activity. Device sessions expire after 30 days of inactivity and are removed on subsequent activity. You can revoke them immediately in Settings. Existing signed licences remain usable for no more than 24 hours. Network IP addresses and request details are also subject to the hosting/security-log policy below. Device records are available in Settings; contact the controller for access, correction or deletion requests under the rights described in this policy. Uninstalling the plugin does not cancel a Pro subscription.

Orynos Studio desktop application

From version 0.2.0, input/output device discovery reads Windows device metadata without opening the microphone. Only an explicit Record action starts capture. Takes, plugin folder paths, scan fingerprints and settings remain on your computer; saved projects and recovery files may include recorded audio. Third-party VST3 plugins execute native vendor code and may have their own services and privacy policies. Scan isolation is a crash-recovery mechanism, not a security sandbox.

At normal startup, the desktop app refreshes a linked account's licence and checks HTTPS orynosmusic.com for authenticated update metadata. Update requests transmit ordinary connection information such as IP address, but no song, recording, project or plugin-folder list. Verified downloads are stored locally; same-terms updates can install automatically after session recovery. Changed terms require the normal setup review. The application adds no desktop advertising or third-party telemetry.

Local editing, playback, effects, project saving and ordinary WAV export run on your computer. Your project may contain source audio, track names and settings; it contains no account credentials. The desktop application has no third-party advertising or analytics code. From Studio 0.9.15, a verified account and valid signed licence are required before the workspace, audio devices and project recovery start. A still-valid cached licence permits temporary offline use; expired or revoked access blocks editing and audio while allowing existing work to be saved locally. Account linking uses the verified account/device protocol described above and the normal browser approval flow; the application never receives your website password. Saved sign-in is encrypted for your Windows user with DPAPI and can be shared with your other OrynosMusic native applications.

Export + Master is a separate optional action. Only after you confirm it does the application upload one exported WAV and your selected mastering settings to provide the requested website mastering service (Art. 6(1)(b) GDPR). Your full project is not uploaded. The server checks current model access, credits and the private account/device/job association. The upload carries a separate opaque DAW token, not your account refresh credential. Token hashes expire after six hours and are invalidated when the device is revoked or the account authentication version changes. Export association records are eligible for deletion after thirty days and are purged during subsequent DAW-session activity; existing credit/billing/security retention applies separately.

Studio reports its product and version after a successful online account check, using existing device credentials. The first report establishes a baseline; a higher version can count as a client-reported update, not proof of a completed installation. No song, project, plugin list or local file path is sent. Device baselines remain while the device session exists; anonymous daily aggregate counts remain afterward. Installer requests and successful update checks also contribute anonymous daily counts, without new cookies or IP-based identification. These first-party statistics support service maintenance under Art. 6(1)(f) GDPR. Reporting failure does not block Studio. The realtime VST plugin does not send version reports.

Cloud audio follows the queue, processing and five-minute completed-output retention described below. The five-minute window starts after processing completes. A downloaded local WAV remains on your computer until you delete it. Cancelling a queued export can refund reserved credits; stopping native waiting after processing begins leaves the server render running and a successful master can still spend credits. Uninstalling preserves user projects, unknown files and the shared saved account cache; sign out or revoke devices separately in Settings. Uninstalling does not cancel a subscription. Desktop details and the early-preview download: Orynos Studio.

2. Hosting, access and security logs

We use MC-HOST24 for server hosting and email services. MC-HOST24 is a label of Gericke KG, Mühlenstr. 8a, 14167 Berlin, Germany. Provider details are available in its legal notice and privacy policy.

When you access the service, the web server and any upstream hosting or proxy provider may process the IP address, requested URL, date and time, response status, transferred volume, referrer, browser and operating-system information. This is required to deliver the website, diagnose faults, protect the service and prevent abuse. The legal basis is Art. 6(1)(f) GDPR. Security logs are kept only for as long as they are needed for those purposes and any statutory claims.

Transactional email is sent using the mail.mailfive24.de SMTP service over authenticated TLS. Only the address and message information needed for delivery are sent there, not your uploaded recording. The controller remains your contact for questions about its infrastructure recipients and the retention applicable to a particular record.

3. Accounts and persistent login

For an OrynosMusic account we process a user ID, username, password hash, email address, any pending email change and verification state, membership rank, credit allowance and purchased balance, render-credit records, supporter status, public-recognition preference, account timestamps, any moderation restriction and its reason, and authentication state. Registration requires an email address. The password itself is never stored in plain text. Processing is necessary to create and operate the requested account and audio service (Art. 6(1)(b) GDPR).

Supporter usernames appear in the public supporter thanks only when the supporter actively enables that setting in account settings. It is off by default, is not ranked by contribution, and can be withdrawn without changing supporter status.

OrynosMusic uses one signed, first-party session cookie. It contains a random visitor identifier and may contain login state, supporter state, an API-key fingerprint and the consent record; it never contains the password or a raw API key. The cookie is HttpOnly, SameSite=Lax, limited to path “/” and is marked Secure in the HTTPS production configuration. After login or a privacy choice it has a sliding lifetime of up to 30 days. The optional browser API-key grant expires internally after 12 hours even if the session cookie remains. The cookie is required for authentication, security, request ownership and remembering your privacy choice (§ 25(2) no. 2 TDDDG; Art. 6(1)(b) and (f) GDPR).

When you publish a community post, comment, pack or artist profile, your selected public name and membership badge may be shown with it. Your email address, private credit balance and private recordings are not made public by that publication.

Personal API access and account administration

If you create a personal API key in Settings, the complete key is shown once. We store its random identifier, a cryptographic hash, creation time, last-use time and any revocation time, associated with your account. API calls use your account's current model permissions and credit balance; private jobs remain account-owned when a key is replaced. You can rotate or revoke the key in Settings. Password changes, password resets and confirmed email changes revoke existing keys. Processing provides your requested API access (Art. 6(1)(b) GDPR) and protects account access (Art. 6(1)(f)). Do not include keys in public URLs, messages or project files.

The operator can manage account ranks, credit allowances, engine restrictions, verification status and moderation. Administrative audit records store the responsible administrator, affected account or content, action, time and before/after values; these can include account details, balances and a moderation reason. Account-linked completed-render records also support weekly and lifetime credit totals and weekly engine-usage statistics. Access is restricted to the authorised operator. The purposes are account administration, abuse prevention, resolving disputes and service maintenance (Art. 6(1)(b) and (f) GDPR). These records are distinct from the short-lived audio buffers and remain subject to the retention and rights sections below.

4. Audio processing and community content

Uploaded tracks and stems are processed to provide the requested analysis, mastering or mix. The application's private upload and rendering workflow uses memory during queueing and processing. For verified website sessions, finished audio has a five-minute download timer that runs only while a result tab is visible and focused. It pauses when the tab loses focus. Native app and API results retain a five-minute wall-clock window after completion. A reusable private upload expires after five minutes without activity; its timer is renewed after analysis or processing. Audio in an active analysis, queue or render is kept for that operation and protected from idle expiry. Unneeded processing buffers are released after processing or failure; finished website audio is removed when its focused time is used up or one hour after completion, whichever comes first. Native app and API audio is removed five minutes after completion. These results then become unavailable for download. The website sends short first-party presence messages while a result tab is focused and a pause message when it leaves focus. Temporary random viewer identifiers, request sequence numbers and remaining-time state are held with the result in RAM; they are not an account activity history and are removed with it. Queue waiting is bounded to 30 minutes and rendering has a separate mode-dependent limit of up to two hours; these safeguards do not shorten a successful download window. Private render audio is not written to the application's audio library or used to train a general model. Published packs, community posts, comments and Linktree profile information remain stored until they are deleted or the account is removed. The legal basis is Art. 6(1)(b) GDPR and, for content you choose to publish, your instruction to make it public.

Premium workspace tools can store account-owned titles, notes and structured settings such as presets, collection plans, review markers or domain setup notes. These records are private to the signed-in account unless you separately publish or share content. The generic workspace does not upload audio. You can delete individual workspace records.

Custom sound, Discord and optional feedback

Custom sound profiles store a profile name and measured spectral, loudness, dynamics and stereo statistics under your account. Reference audio is analysed for up to 60 seconds per file and is not retained after processing. You can delete your saved profiles in Studio settings.

If you connect Discord, we store your verified Discord ID, display name and connection date. The connection requests identity access only. Access tokens are not stored; we request revocation after checking the identity. Disconnecting removes the saved identity link.

Optional render feedback saves your account ID, render ID, selected engine, satisfaction answer, timestamp and comment in a private text file for service-quality review. The retention period is 180 days; expired records are removed during daily maintenance while the service runs, and on startup. The legal basis is Art. 6(1)(f) GDPR, our interest in diagnosing problems and improving the tools; do not include sensitive personal information in your comment. You can ask us to delete your feedback or object to that processing. Private render receipts used to authorize feedback expire after 30 days. Feedback does not publish your recording or provide a licence to train on it.

Help requests

When you use the Help form, we process your name, email address, subject and optional message to answer your request. The application sends these details from noreply@orynosmusic.com to support@orynosmusic.com through the authenticated TLS mail service described above. Your address is set as Reply-To; no audio or attachment is submitted by this form. Help-form content is sent as email and is not added to an application support-message database. Hashed form-submission claims prevent duplicate delivery in application memory; they expire after two hours and are removed on subsequent form activity or restart. Abuse limits also use short-lived sender/email hashes. The email remains in the support mailbox for handling and any necessary follow-up or legal record. The legal basis is Art. 6(1)(b) GDPR for account or service support and Art. 6(1)(f) for other enquiries and abuse prevention. Do not send passwords, API keys or sensitive personal information. You can contact the controller about access to or deletion of your request.

Illegal-content and security reports

The illegal-content reporting form processes the content URLs, category, explanation and good-faith declaration you submit, together with your name and email where required. For notices concerning the child sexual abuse or exploitation offences specified in the form, you may omit your name and email. The notice is sent privately from noreply@orynosmusic.com to support@orynosmusic.com through authenticated TLS. If you provide an email address, we also attempt to send an acknowledgment containing only the reference and receipt time, without repeating the reported content. The form does not fetch the reported URLs, accept attachments or publish the notice. It does not create a separate application notice-content database.

A reference, receipt time and delivery status can be held temporarily in your signed session and in hashed duplicate-delivery claims. Claims expire after two hours and are removed on subsequent reporting-form activity or restart. Short-lived abuse limits use sender/email hashes. Notice correspondence, decisions and any evidence needed for review remain in the support mailbox and are kept as necessary for handling, applicable legal obligations and legal claims; the five-minute audio rule does not apply to these records. Security reports sent to the same address are handled privately for investigation and remediation. The legal bases are Art. 6(1)(c) GDPR for applicable legal notice-handling obligations and Art. 6(1)(f) for service security, abuse prevention, assessment of reports and legal claims. Reporter details are not routinely published or forwarded to the reported user; disclosure may be required by law or necessary for an appropriately assessed legal process. Do not include unrelated sensitive information, passwords or API keys.

5. Browser storage selected by you

  • Your selected light or dark theme is remembered when you choose it.
  • One compatibility storage entry stores mix settings only after you use “Save session”; no audio is stored there.
  • One compatibility storage entry stores a mastering preset when you choose to save it.
  • One compatibility storage entry stores only the last time a post-download support prompt was shown, so the non-blocking prompt stays hidden for 30 days.
  • Recent render timing, stored separately for workflow and model, helps estimate waiting time in that browser. It contains a timing ratio, not your name, recording or audio.

These entries support your selected interface settings and requested tools; they are not used for cross-site tracking. Saved settings can remain until you overwrite them or clear the browser's site data. You can remove them using your browser’s site-data controls.

Optional render notifications

When you enable render notifications, we associate this browser's push subscription with your verified account. It contains a delivery address and browser-generated encryption keys. Subscription details are encrypted in the account database using a separate server notification key; they are not published or shared with other accounts. Permission is requested only after you choose to enable notifications. You can turn them off for this device in Settings or revoke the permission through your browser or device.

Your browser selects its push delivery service, commonly Apple, Google, Mozilla or Microsoft. That service receives the technical delivery address, connection metadata and an encrypted notification payload. The message includes a render reference, whether it is a master or mix, its expiry and a link back to OrynosMusic. It contains no song name, audio, email address, password or API key. Your account is checked again before sending and before accessing the completed audio. Notification permission does not reset the remaining download time or extend the one-hour website RAM limit. The ready page uses the same focused-time budget as the original result tab.

Subscriptions expire after 90 days without being enabled again. Pending render associations are eligible for deletion after one day, and delivery records after the recorded notification expiry; cleanup runs during subsequent notification processing. Disabling the device subscription deletes it and its pending associations. Changes to account authentication invalidate the previous notification access. Delivery can be delayed or blocked by your connection, Focus mode, battery controls or the platform's notification settings.

6. Premium billing through Paddle

When you choose a paid plan, the checkout is provided by Paddle as the authorised reseller and merchant of record. Paddle processes the contact, location, billing and payment information needed to present taxes, take payment, prevent fraud and fulfil the purchase. OrynosMusic does not receive or store complete card or bank-account details. Paddle describes its own processing and international transfers in its privacy notice.

OrynosMusic stores the account-to-Paddle customer mapping, subscription, product, price and transaction identifiers, subscription status and period dates, transaction status, currency and Paddle-calculated total, short-lived checkout intents, entitlement state, and a hash plus technical status for received billing events. These records are used to grant the purchased Premium functions, prevent duplicate webhook processing, provide account support and meet contractual, accounting and legal obligations. No uploaded audio is sent to Paddle. Checkout is loaded only after you actively choose a plan.

Withdrawal and cancellation functions. When you use the online withdrawal function (“Withdraw from contract here” / Vertrag hier widerrufen) or the cancellation function (“Cancel contracts here” / Verträge hier kündigen), OrynosMusic stores the details you enter: name, email address, contract or account reference, the type of declaration, an optional reason, the requested effective cancellation date, the request time, and a reference number. A receipt is available for immediate download, with confirmation sent by email. A delivery failure is kept in a private retry queue; message body and recipient are cleared from that queue after successful delivery and sent queue metadata is removed after 30 days. Only a signed-in account owner can trigger automatic end-of-period cancellation; other declarations and requested dates are recorded for manual handling. Legal basis: Art. 6(1)(b) and (c) GDPR (performance of the contract and compliance with statutory consumer-protection obligations, §§ 312k, 356a BGB). These records are kept for as long as statutory documentation and limitation periods require and are then deleted.

7. Advertising only after opt-in

No advertising tag, advertising iframe or preconnection to an advertising domain is made before you actively select “Accept optional advertising”. If you decline, the website remains fully usable without these ads. Your signed consent record stores the choice, time, purpose, named vendor and text version for up to 30 days. The legal basis for device access is § 25(1) TDDDG and for the related personal-data processing Art. 6(1)(a) GDPR.

To demonstrate when consent was granted or withdrawn, OrynosMusic also keeps a pseudonymous receipt for up to 1095 days. It contains a keyed hash of the browser visitor ID, the choice, time, purposes, named provider and consent-text version. It does not contain the raw visitor ID, IP address or user-agent string. This record supports the controller's accountability and legal defence obligations under Art. 5(2), 7(1) and 6(1)(f) GDPR.

The advertising service is Adsterra (AD MARKET LIMITED and ADMEDIA LLC FZ). The provider's privacy policy, effective June 29, 2026, identifies AD MARKET LIMITED in Cyprus and ADMEDIA LLC FZ in the United Arab Emirates as the companies jointly referred to as Adsterra. AD MARKET LIMITED lists Christaki Kranou 49, Germasogeia, 4041 Limassol, Cyprus, as its address. After consent, content is requested from effectivecpmnetwork.com and highperformanceformat.com. The provider and its advertising partners may process IP address, browser and device properties, approximate location, advertising identifiers, viewed page/ad placement, clicks and other ad interactions to deliver, secure, measure and potentially personalise advertising or build an interest profile. Current provider information is available in its privacy policy and cookie list.

OrynosMusic places every advertising tag in an opaque-origin sandbox that blocks access to OrynosMusic cookies, account state, parent-page content and browser storage. This isolation does not prevent the provider or content embedded by it from processing the network, device and interaction data described above after consent.

Depending on the campaign, the provider may involve advertisers, measurement, fraud-prevention and delivery partners. This can involve recipients outside the EEA. A transfer requires the applicable safeguards under Art. 44 et seq. GDPR; consent to advertising does not by itself replace those safeguards. The provider’s current partner, retention and transfer information should be reviewed before the advertising integration is enabled in production.

You can withdraw or change the choice at any time using the advertising switch in your profile settings or the switch below. Withdrawal takes effect for future loading and removes all ad frames from OrynosMusic. Cookies already written by a third-party provider cannot be deleted by OrynosMusic; use the provider’s opt-out and your browser’s site-data controls for those entries. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.

8. Recipients

Data is disclosed only where required to operate the service: to the hosting and infrastructure providers used by the operator, to email transport providers for account verification, password reset, help requests, content or security reports and legal or billing confirmations, to Discord when you choose to connect its identity, to Paddle when you initiate or manage a paid plan, and only after advertising consent to the advertising provider and its disclosed delivery partners. Public content is visible to website visitors by design. Data may also be disclosed when legally required.

9. Retention and deletion

Account data and content you publish are retained while the account or content remains active. Verification tokens expire after 24 hours and password-reset tokens after one hour; only token hashes are stored. Login and consent state expire as described above. Billing records are retained for the subscription lifecycle and for any longer period required by tax, accounting, fraud-prevention or legal-claim rules. Data may be retained longer only where statutory retention, security investigation or legal-claim obligations require it. You may request account or content deletion using the controller contact above.

10. Your GDPR rights

  • Access (Art. 15), rectification (Art. 16) and erasure (Art. 17 GDPR)
  • Restriction (Art. 18) and data portability where applicable (Art. 20 GDPR)
  • Objection to processing based on legitimate interests (Art. 21 GDPR)
  • Withdrawal of consent at any time (Art. 7(3) GDPR)
  • A complaint to a data protection supervisory authority, including the LDI NRW

11. Security and changes

OrynosMusic uses HTTPS in production, restrictive browser security headers, hashed passwords, rate limits and sandboxed advertising frames. No internet service can guarantee absolute security. This notice and the consent version will be updated when purposes, vendors or storage practices materially change; a new advertising consent will then be requested.

Confirm your email address to receive subscription and account notices.