CONTACT

Talk to a person.

Everything arrives in one inbox and a human reads it. Say what it is about below and the email leaves with the right subject line already on it.

[email protected] · open in your mail app

Write a message.

This builds the email and hands it to your own mail app. Nothing is sent from this page and nothing is stored here: you send it yourself, and the copy stays in your sent folder.

Something is broken or behaving oddly.

To [email protected]
Subject Support

What to put in it

A message with these five things in it usually gets an answer on the first reply rather than the third.

  • The email address or username on the account.
  • What you did, what you expected, and what happened instead.
  • Roughly when it happened, and the timezone you are in.
  • Browser and device, or the installed app if that is what you use. The checkbox fills this in.
  • A screenshot, if there is anything to see. Attach it in your mail app.

Never send a password, a recovery code or an API key. Nobody at Aelius will ask you for one, and support does not need one to help you.

Where each one lands.

One inbox, sorted by subject line. If you would rather write from your own mail app, these are the exact lines to use.

  • Support and bug reportsAnything in the chat, the installed app, image generation or uploads. Support — [what broke]
  • Account and sign-inEmail changes, two-factor trouble, a subscription question. Account — [your username]
  • Access, correction or deletion of your dataSet out in §16 of the Privacy Policy. Answered inside 30 days, and usually well before that. Privacy Request — [Your Username]
  • GDPR rights, for EU and EEA usersThe rights themselves are listed in §10 of the Privacy Policy. GDPR Request — [Your Name]
  • CCPA rights, for California residentsThe rights themselves are listed in §11 of the Privacy Policy. CCPA Request — [Your Name]
  • Security disclosureInclude the steps to reproduce it and what it exposes. Please give us a reasonable window to fix it before publishing, and do not test against other people's accounts to prove the point. Security — [what is affected]
  • Abuse and safetySomeone using Aelius to harm others. Child safety reports are handled ahead of everything else — see the Usage Policy. Abuse report — [what and where]
  • Copyright and other legal noticesA DMCA notice needs the elements listed in §11 of the Usage Policy. One that is missing them cannot be acted on. DMCA Notice — [the work]

Who you are writing to.

Aelius is built and run by a small team on hardware it owns. There is no outsourced support desk between you and the people who can actually change the thing you are writing about.

Support

The helpdesk inbox

The right address for almost everything: bugs, accounts, privacy requests, security disclosures, abuse reports and legal notices all arrive here and are sorted by subject line.

  • Email[email protected]
  • TimingNo call centre, so no hold music, and no automated first reply either. Most messages are answered within a day or two. Privacy and data requests are answered inside 30 days by policy, normally sooner.

Direct

William Struloeff

Lead developer. The one to use for press, partnerships and questions about the project itself. Support questions get a faster answer at the helpdesk address, because that is the inbox being watched.

Before you write.

The questions this inbox gets most, answered here so that you do not have to wait for the answer.

How quickly will I hear back?

There is no ticket queue and no automated first response, which cuts both ways: a real person reads your email, and that person is sometimes asleep. Most messages are answered within a day or two. Privacy and data requests are answered inside 30 days by policy, and in practice much sooner.

Can I just ask Aelius instead?

For how something works, yes, and it is faster. Open a chat and ask. What it cannot do is see your account, reset anything or act on a privacy request — those need a person, which means email.

Is there a phone number or a live chat?

No. Email is the only support channel, deliberately: a written thread keeps the whole history in one place and you keep a copy of it. The Discord contact above is the lead developer personally, not a staffed support line.

I want my chats and my account deleted.

You do not need us for that. Open Settings → Data in the app: it exports everything in your account, wipes your chat history, or deletes the account and its contents outright.

Email is for what that page cannot cover — you are locked out of the account, or you want a formal written answer under the GDPR or the CCPA.

I found a security bug. What do you want me to do?

Email it with Security as the first word of the subject, including the steps to reproduce it and what it exposes. Please give us a reasonable window to fix it before publishing, and do not test against other people's accounts or data to prove the point — a description is enough.

Will you use what I send you to train a model?

No. Support email is not training data, and neither are your conversations. Nothing you write is sold or handed to advertisers. The Privacy Policy is the binding version of that.

Do you take feature requests?

Yes, and they get read. The useful ones describe the problem rather than the solution: what you were trying to do, and what got in the way. That survives contact with a design that turns out different from the one you pictured.

Most questions already have an answer.

Ask Aelius first. It is free, it needs no account, and it will not put you in a queue.