Email Policy

How Mucuner approaches permission, relevance and responsible email delivery.

Effective date: [INSERT PUBLICATION DATE]

This page describes a policy framework. Keep only statements that match your real practices and technical controls. Do not claim consent records, suppression systems or unsubscribe handling unless they are implemented.

1. Types of email

Depending on the live service, email may be used for user-requested account verification, password resets, security alerts, support replies and other service messages triggered by a user's activity. Promotional or newsletter messages are separate from essential transactional messages.

2. Recipient permission and source

We send messages only to recipients for whom we have an appropriate relationship, request, permission or other lawful basis. We do not use purchased, rented, scraped or harvested email lists. We do not send unsolicited bulk email.

3. Marketing messages

If Mucuner offers marketing email, recipients will be asked to provide clear affirmative consent where required. The signup process should explain what messages will be sent. Consent records should be retained, and consent should not be bundled with unrelated terms or made a condition of a service where the law prohibits that practice.

4. Unsubscribe and preferences

Marketing messages will include a clear, working unsubscribe method. Requests will be processed within the period required by applicable law. Transactional messages necessary to provide a requested service may be treated differently, but will not be used as a way to disguise promotional content.

5. Bounces, complaints and suppression

Invalid addresses, hard bounces, spam complaints and unsubscribe requests should be promptly suppressed so that messages are not repeatedly sent to those addresses. We monitor delivery outcomes and investigate unusual complaint or bounce activity.

6. Message identification

Messages should accurately identify the sender, use truthful subject lines and include a valid way to contact the operator. Domain authentication such as SPF, DKIM and DMARC should be configured where supported.

7. Third-party email providers

We may use an email delivery provider to transmit messages. The provider processes message and delivery data as necessary to provide its service. The provider actually used should be identified in the Privacy Policy where appropriate.

8. Contact

Questions about email practices or a request to stop receiving optional email: contact@mucuner.com.