What can the operator see?
Email is handled by the service while it is forwarded. TODO: document the exact logs, account data, and access available to the operator. Do not treat aliasing as anonymity. OpenPGP can protect message content for a configured recipient, but it does not remove metadata.
Where does it run?
It runs as a self-hosted AnonAddy deployment operated by one person. TODO: publish the hosting location and infrastructure details if the owner wants them public.
What happens during an outage?
The service is best effort. Mail may be delayed or rejected while the application or mail path is unavailable. There is no public status page or uptime promise.
Can I delete my account?
TODO: confirm the account deletion workflow and what data, aliases, logs, backups, or soft-deleted records remain.
Are attachments supported? What are the size limits?
AnonAddy supports attachments, and its upstream documentation says they are included when OpenPGP encryption is enabled. TODO: verify the deployed attachment behavior and maximum message size for idler.me. No local numeric limit is published.
Is OpenPGP required?
No. It is optional. Add a public key to encrypt forwarded messages when the application supports it. Encryption does not make the service anonymous and may require decryption or processing by the service for replies and sends.
What is not allowed?
No spam, bulk sending, account farming, abuse of shared domains, or marking forwarded messages as spam. Accounts may be disabled for abuse. Report suspected abuse through the private channel used for your invitation. TODO: publish a public abuse contact if one is intended.