EMAIL & RECIPIENT CHOICES
Every message
should have a reason.
Aeterna’s email flows support account access and an owner-configured recovery arrangement. This website does not collect subscriptions, send email or offer a mailing-list signup.
Recipient controls before launch
The current invitation flow supports acceptance and decline. Self-service withdrawal after acceptance is not yet available. Its behavior must be finalized before production launch. Questions or unwanted-email reports can be sent to the address on the contact page.
What belongs in a notification
After acceptance and verification, a message may contain limited instructions about where to find offline materials. Aeterna does not automatically attach library files or include the emergency recovery code or server-held release secret. Owners must keep passwords and other secrets out of custom instructions. Email providers can see recipient addresses and rendered message text.
Delivery status is not a promise
AWS SES is selected for production notification delivery in the Singapore region. SES delivery, bounce and complaint handling exists in code; AWS event configuration and live-send validation are still pending. Account-verification and some security notices currently use a separate development transport. Provider acceptance does not establish delivery, reading or recovery completion.
Unexpected invitation?
You do not need to accept. Use the decline option in a valid invitation when available. For questions or unwanted-email reports, use the public contact address on the contact page.