Compliance Infrastructure

Acceptable Use Policy

Guidelines for Transactional Integrity and Network Security

1. Policy Overview

This Acceptable Use Policy (AUP) governs the use of Martamar Logistics Technology's communication infrastructure, routing engines, and API endpoints. By initializing a network node on the Martamar platform, you agree to adhere to these standards, designed to protect the reliability of critical logistics communications.

2. Permitted Use: Transactional Notifications

Martamar's infrastructure is strictly reserved for **Transactional System Alerts** related to the courier marketplace and logistics lifecycle. Permitted messaging categories include:

Proof of Delivery (POD): Digital receipts and signature confirmations.
Chain of Custody Transfers: Notifications regarding the legal transfer of assets between hub operators and drivers.
Security Credentials: One-time PINs and authorization codes for package release.
SLA Monitoring: Automated alerts regarding transport delays or route deviations.
Identity Verification: Vendor onboarding and technical contact confirmation.

3. Strictly Prohibited Content

The use of Martamar for any of the following activities will result in immediate cryptographic key revocation and termination of service without prior notice:

Marketing & Newsletters: Any promotional content, sales offers, or "warmup" marketing campaigns.
Third-Party Lists: Sending to any recipient who has not initiated a logistics transaction with the vendor.
Affiliate Marketing: Use of our infrastructure for lead generation or affiliate tracking.
Deceptive Routing: Manipulating email headers, spoofing "From" addresses, or obfuscating the origin of the event trigger.
Prohibited Industries: Messaging related to high-risk sectors outside of logistics (e.g., gambling, pharmaceuticals, or multi-level marketing).

4. Technical Requirements

To maintain high deliverability and system health, all vendors must comply with the following technical specifications:

A. Domain Authentication

All dispatching nodes must be authenticated via SPF, DKIM (at least 2048-bit keys), and DMARC with a "quarantine" or "reject" policy.

B. Rate Limiting and Burst Control

While Martamar is built for high-burst traffic, vendors must utilize our queue management API to ensure that message spikes do not exceed the pre-allocated node capacity. Spikes exceeding 500% of the baseline without prior coordination may be throttled to protect network stability.

// System Header Requirement for All Transactional Payloads
X-Martamar-SLA: CRITICAL_ASSET_MOVE
X-Martamar-NodeID: [SECURE_NODE_ID]
X-Martamar-EventHash: [HMAC_SHA256_SIG]

5. Monitoring and Enforcement

Martamar utilizes automated **Content Inspection Algorithms** to ensure compliance. Our systems monitor:

Bounce Thresholds: Nodes exceeding a 2% hard bounce rate are automatically flagged for manual review.
Complaint Rates: A spam complaint rate exceeding 0.05% will trigger immediate suspension of the API key.
Payload Analysis: Random sampling of message bodies to ensure the absence of marketing keywords and the presence of mandatory logistics tracking data.

6. KYB (Know Your Business) Verification

Martamar does not provide "anonymous" infrastructure access. All enterprise clients must complete a Business Verification process, providing legal registration documents and valid physical addresses within their operating region. Failure to maintain accurate corporate records is grounds for termination.

7. Cooperation with Infrastructure Providers

As Martamar utilizes upstream infrastructure partners (such as Mailgun Technologies) for global delivery, all users are additionally bound by the AUP of our respective providers. Any violation that jeopardizes Martamar's reputation or IP health will be prosecuted to the full extent of our B2B Service Agreement.

For questions regarding this policy or to request a temporary burst limit increase for large-scale logistics deployments, please contact our Infrastructure Ops team at ops@ibastekstil.com.