StackScopesEmail categories
StackScopes email may include account verification, password reset, security notices, simulation completion, approval requests, incident notifications, billing communication, support replies, and product communication requested by a recipient.
Address collection
Addresses should come from an account relationship, a product action, a direct business request, or explicit permission. StackScopes does not permit purchased, rented, scraped, or unlawfully shared mailing lists.
Consent and preferences
Marketing communication requires appropriate permission and a clear way to unsubscribe. Transactional communication is limited to the account, security, billing, or product event that caused it.
Bounces and complaints
Hard bounces and complaints should be processed promptly, suppressed from inappropriate future sending, and monitored through the configured email provider. Sending systems should use rate limits, deduplication, audit records, and abuse controls.
Authentication and identity
Sending domains and identities should be verified and configured with appropriate authentication. Public website publication does not itself indicate that a sending quota or production-access request has been approved.
Transactional and marketing separation
Security, account, billing, approval, incident, and product-event messages should remain operationally separate from permission-based marketing communication. A person who leaves a marketing list should continue receiving only the transactional messages required for an active account or requested service.
Preference management
Recipients should be able to manage eligible communication preferences and unsubscribe from marketing messages without affecting necessary account or security notices. Suppression records should prevent inappropriate resending after an unsubscribe, hard bounce, or complaint.
Contact
Email-abuse concerns may be reported to abuse@stackscopes.com. Privacy questions may be sent to privacy@stackscopes.com.