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.

When an email is triggered

01

Account verification

TriggerSomeone starts an account or identity-verification flow.

A purpose-bound, expiring code verifies mailbox access. Codes are not a substitute for the local master password or offline recovery code.

Current statusImplemented in development; production transport pending

02

Contact invitation

TriggerAn owner chooses to invite a contact now, or a private arrangement reaches release.

A neutral invitation identifies the owner and proposed role. Unverified recipients receive no custom instructions, library content or recovery material.

Current statusImplemented; production delivery pending

03

Inactivity & recovery

TriggerThe configured timeline reaches warning, grace or authorized release.

Owner warnings precede release. An accepted and verified contact can receive a time-limited recovery claim; a separate mailbox code verifies the claim.

Current statusImplemented; production delivery and provider validation pending

04

Device & recovery security

TriggerA relevant device-binding or owner-recovery operation requires a security notice.

Owner notices help make pending device authorization and recovery activity visible. These are transactional account messages.

Current statusImplemented in development; production transport pending

THE INVITATION IS YOUR CHOICE

Accept, or decline. No password to create.

Accept an invitation

Accepting and verifying your email establishes the recovery-contact role. Recovery still requires authorized release and the owner’s offline arrangement.

Decline an invitation

A valid pending invitation can be declined. The implemented flow records a recipient suppression and cancels queued messages for that invitation.

Keep the arrangement private

Owners can choose private-until-release. This sends no setup or test email while active, and gives the unverified target no recovery authority.

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.