General Mailcore Terms

Service format

Mailcore provides two products that can be connected separately. Business email includes mailboxes, webmail, IMAP/SMTP, email DNS records, and technical guidance. Email API is intended for expected service messages from the client's application, such as receipts, order updates, sign-in codes, and product notifications.

Registering an account, creating an organization, or submitting a request does not by itself activate a paid service, production sending, or an API key. Before production launch, the domain, use case, limits, and sender are reviewed, and the terms and access are confirmed separately.

Before switching the domain

The client provides the domain, mailbox count, migration requirements, and an authorized contact. Mailcore checks current MX, SPF, DKIM, and DMARC, prepares mailboxes, and defines control tests. Production MX changes only after agreement, outgoing-delivery verification, and completion of the mandatory pre-launch conditions published on the website.

Client responsibilities

• have the right to manage the connected domain and provide accurate information;
• protect passwords, devices, and administrative contacts and report lost access without delay;
• store API keys only on the server, revoke compromised keys promptly, and never transmit them through URLs or client-side JavaScript;
• use Email API only for messages recipients expect because of their action, agreement, or a service event;
• create mailboxes only for authorized users and promptly close access for former employees;
• comply with the Acceptable Use Policy, applicable law, and third-party rights;
• retain independent copies of critical data until the backup system has been commissioned and recovery verified.

Delivery and availability

Mailcore operates its infrastructure but cannot guarantee delivery of every message, a specific recipient folder, or uninterrupted third-party networks and email systems. A message may be rejected because of recipient policy, sender reputation, an invalid address, malicious content, exceeded limits, or legal requirements.

Security and abuse

We may rate-limit or temporarily stop outgoing sending if we detect compromise, a spike in bounces or complaints, phishing, spam, or other abuse. An urgent restriction may be applied before contacting the client if continued sending creates risk for recipients or the service's shared reputation. Complaints are handled under the abuse desk procedure.

Suspension and termination

The parties agree the termination and data-export process in individual terms. Mailcore may suspend or terminate the service after a material or repeated policy violation, an attempt to bypass safeguards, unauthorized use, or non-payment after notice, unless security requires an immediate stop.

Privacy

Processing of requests, account data, logs, and email content is described in the Privacy Policy. For questions about data and the service, write to support@mailcore.uz.

Changes and individual terms

Before paid or production use begins, Mailcore and the client separately document party details, service scope, price, limits, and support procedure. Those agreed terms take precedence over the general description on this page. We will update the document date after a material change to these general terms.