This policy applies to any audio file, temporary chunk, merged processing file, queued analysis file, derived metric set, analysis summary, and related upload metadata handled by Marisonus.

When a signed-in user uploads a file to their workspace, Marisonus uses the source audio to run the analysis and create the account history entry.

After analysis completes or terminally fails, the stored source audio is deleted. The retained account record is the analysis history entry, together with core metadata such as filename, file size, timestamps, status, and generated metrics or recommendations.

In the current launch configuration, member analysis history is also subject to an automatic retention window of 7 days unless the user deletes it sooner or Marisonus extends that window later.

During a demo upload, Marisonus may temporarily store upload chunks and a merged processing file long enough to validate the audio and run analysis.

If async processing is enabled, the raw demo file is placed in queue storage and is deleted from that processing location after the analysis succeeds or permanently fails.

The analyzer may keep a temporary session-backed copy of the resulting analysis output so the demo user can be redirected into the analysis view.

Async job records and derived result payloads can remain in the database after the raw demo file has been deleted for operational and abuse-prevention reasons, but the current launch configuration is set to purge completed demo-derived records after 24 hours and failed demo jobs after 72 hours.

Abuse and security event records tied to demo access are configured to remain for up to 30 days for internal review and platform protection.

Access is intended to be limited to the uploader, authorized Marisonus personnel who need access for support, security, abuse review, or operational maintenance, and infrastructure processors running storage or compute on our behalf.

Uploads are not intended to be searchable or visible to other customers by default.

By default, uploaded audio is used to provide the requested analysis, maintain service reliability, investigate abuse or failures, and secure the platform.

Registered user uploads should not be treated as reference-library material, training material, or public showcase content unless the user separately consents or agrees in writing to that use.

No customer upload should be auto-promoted into a shared reference-track or self-learning corpus just because it passed through the analyzer. That requires a distinct, explicit consent flow.

If a demo user actively selects the optional improvement-consent checkbox, or a signed-in member separately opts in through the analyzer prompt, Marisonus may retain the upload or its outputs longer for service-improvement work, calibration, evaluation, or future reference-model development.

That optional consent is separate from the required confirmation that the user accepts the legal terms and has the right to upload the material.

Declining that optional improvement consent must not block the ordinary analysis flow.

For signed-in member uploads, the current implementation can copy an opted-in file into an internal genre-based `reference_library_imports` folder used for internal review and future calibration workflows.

If Marisonus builds an internal improvement or reference corpus from opted-in material, the safer approach is to keep it internal-only, separate it from the customer workspace, and minimize direct identifiers such as account-linked filenames wherever practical. The current implementation does not automatically expose opted-in files publicly or move them into a customer-visible reference collection.

At the current launch stage, those opted-in internal reference imports are intended to remain stored until the uploader requests deletion through support or Marisonus removes them internally.

Registered account uploads: source audio deleted after analysis; derived analysis history currently retained for 7 days unless the user deletes it sooner or requests broader account deletion.

Demo upload chunks and raw processing files: retained only for the time required to validate, queue, and analyze the upload, then deleted from temporary processing storage.

Completed demo-derived metrics, result payloads, and async job metadata: retained up to 24 hours. Failed demo jobs: retained up to 72 hours. Abuse and security event records: retained up to 30 days. These windows are intended to be enforced by a scheduled purge cycle in production.

Registered users can delete individual analysis history entries or clear their full saved analysis history through the product's authenticated deletion flow.

Requests covering broader account deletion, anonymous demo sessions, or opted-in internal reference imports go through the public support/privacy workflow on the contact page.

Anonymous demo users do not currently have a self-service deletion console in this repository. They should provide identifiers such as upload time, filename, and approximate session details, and they should submit the request promptly if they want manual review before the short demo-retention window expires.

You must only upload material you are authorized to submit and you must ensure that the upload does not violate copyright, privacy, confidentiality, or contractual restrictions.

Marisonus may temporarily block anonymous demo access when the service detects repeated invalid nonces, honeypot triggers, suspicious upload behavior, or other signs that the demo flow is being abused rather than used for normal evaluation.

A manual review may follow when abuse or security controls trip repeatedly, when upload behavior looks automated, or when incident severity reaches a level that requires staff review. That review is limited to the minimum information needed to protect the service, such as timestamps, IP-derived security metadata, request paths, upload identifiers, and incident history.

Manual review outcomes may include removing queued raw demo files, keeping only minimal abuse metadata, extending a temporary IP block, or lifting the block if the activity is found to be legitimate. Refund, legal, or deletion questions tied to that review can be raised through the contact page.