Privacy
EuroMail is private transactional email infrastructure operated by Arcaniz LLC for its software ecosystem.
Last updated October 30, 2026
What we process
Applications submit service-related messages for their users. EuroMail processes sender and recipient email addresses, subject lines, reply-to addresses, application tags, message content, project identifiers and delivery events. Please keep sensitive information out of subjects and tags.
When receiving is configured, EuroMail also processes incoming service correspondence, raw MIME, attachments, threading identifiers and spam/virus verdicts so authorized project operators can read and reply to messages.
Private operator accounts include names, email addresses, password hashes, project permissions and session records. Authentication may process IP addresses and user-agent information. The public informational pages do not require an account and do not set authentication cookies. No advertising or analytics scripts are included in these pages.
Why we process it
We use this information to authenticate operators, authorize applications, queue and send expected transactional messages, diagnose delivery problems, enforce sending limits and suppress recipients after permanent bounces or complaints. The application that triggered a message remains the place to manage the underlying account or service preferences.
Message content and retention
Outbound HTML and plain-text payloads are encrypted in the database while awaiting dispatch. The implementation clears stored bodies after provider acceptance or final failure and expires pending payloads after 24 hours. Cleanup depends on the background worker running; encrypted copies may remain in backups according to the operator’s backup policy.
Inbox bodies and operator reply history are separately retained as encrypted database content for 90 days from the incoming receipt, with worker cleanup. Raw inbound MIME and attachments remain in a private S3 bucket and follow its separately configured lifecycle and backup policy. Archive and trash are mailbox states, not immediate deletion. Subjects, sender addresses, previews and attachment metadata are operational metadata.
Operational metadata and message events use a configurable retention period, defaulting to 90 days for completed messages. This includes subjects and email addresses. Suppression records remain until an authorized operator determines that removal is appropriate. Account, session, infrastructure-log and backup retention depend on their operational configuration; the message-retention period does not apply to all of those records.
Infrastructure and delivery providers
EuroMail uses PostgreSQL for application records and its durable queue. When configured for sending, Amazon SES processes message content and addresses for delivery; Amazon SNS returns delivery, bounce and complaint events. When receiving is enabled, SES stores incoming MIME in private Amazon S3 and sends a separate SNS notification for processing. Hosting, reverse-proxy and AWS systems may retain operational records under their own configurations. We do not claim a specific data-residency arrangement or certification.
Cookies and access
The separate operator console at app.euromail.net uses host-only session cookies for private authentication. Those cookies are not configured for the public site or sibling hosts. Sending API access requires a project API key; authorized console operators can reply from their enabled project mailboxes.
Questions and requests
Contact Arcaniz LLC at info@euromail.net for privacy questions or requests concerning EuroMail records. Include the relevant application and message context, but do not email passwords, API keys or other secrets. For the application account itself, contact that application’s support channel.