Skip to content

MIN.ECO

Privacy Policy

Last updated: 21 August 2026

This Policy describes the personal and related data that the MIN.ECO service (the website www.min.eco and the workspace) actually processes when providing accounts, a release catalog, moderation, distribution, and payouts. It is not a claim of GDPR, CCPA, or other specialized-regime compliance unless those processes have been separately adopted.

Contact for personal-data matters: ceo@min.eco.

Who processes data

Data is processed in the course of operating the min.eco service. Public project materials do not state a legal entity name, registered address, or registration number. This document therefore refers to the operator as min.eco / MIN.ECO, and requests are sent to ceo@min.eco.

Categories of data processed

The service processes categories of data that a user or organization submits in the workspace, as well as data needed to operate the account and security:

  • account data: name, email address, password as a cryptographic hash, role, activation status, and service tokens for activation and password reset;
  • organization membership and organization type (personal catalog or label catalog);
  • artist and release metadata: titles, dates, genres, languages, identifiers (including UPC/ISRC and artist identifiers on digital platforms if you provide them), lyrics, rights information, and moderation status;
  • uploaded files: artwork and audio, plus technical file information (name, type, size, checksum, duration, and similar parameters);
  • contributor information: name, roles, and, if provided, IPI and society;
  • payout data: taxpayer ID (INN), account number, BIC, recipient full name, request amount and status, and account balance;
  • moderation correspondence: notes, rejection reasons, and related operational records;
  • system audit events;
  • security technical data: IP address and related request signals used for rate limiting and login protection;
  • the contents of messages you send to the service contact address.

There is no separate in-product support-ticket system: inquiries are received by email.

Purposes

Data is used only to operate the service:

  • account creation and authentication;
  • sending activation and password-reset emails;
  • managing the catalog of releases, tracks, and artists;
  • distribution operations and related workflows;
  • moderation of submitted releases;
  • balance accounting and processing payout requests;
  • security, abuse prevention, and rate limiting;
  • responding to messages sent to the contact address;
  • operational audit of actions in the system;
  • release-status notices and service messages to the email provided at registration, to the extent provided in the terms of use.

The service does not use data for advertising profiling and has not added analytics or marketing trackers on public pages.

Infrastructure and processors

The following are used to store data and deliver the service:

  • a PostgreSQL database (hosted on Supabase);
  • object file storage (Supabase Storage);
  • an email service provider connected over SMTP (the specific vendor is set in server configuration and is not named in this text);
  • website hosting and reverse-proxy infrastructure used to deliver the site and application programming interface.

Cookies

Sign-in uses a strictly necessary session cookie. Details are in the Cookie Policy.

Retention

Data is kept for as long as necessary to provide the service and meet legal and operational obligations, including maintaining the account, catalog, payouts, and security audit. This document does not set a separate calendar retention schedule.

User requests

Depending on applicable law, you may be able to request access, correction, restriction of processing, or deletion of personal data. There is currently no self-service account deletion in the workspace. Send a request to ceo@min.eco. We will consider the request in light of the law and operational constraints (for example, records that must be kept for payouts, security, or other obligations).

This section is not a promise of GDPR, CCPA, or other specialized rights-regime compliance until the corresponding procedures are separately adopted.

Security

Passwords are stored as a hash. The sign-in session cookie is not accessible to page scripts. Catalog file access goes through an authorized application programming interface, not permanent public links. Despite the measures taken, no method of transmission or storage on a network is completely secure.

Changes

We may update this Policy by publishing a new version on the Site. The date at the top of the page shows when the text was updated.

Contact

Personal-data requests: ceo@min.eco.