Issue Intake
Use this guide for bugs, account or billing problems, video playback issues, VTT and Atlas problems, and
desktop app failures. Include enough relevant detail for the problem to be investigated without exposing
private work.
Last updated:
August 9, 2026
Useful details
- Product name and account email or username.
- Affected page, channel, campaign, or video URL when relevant.
- Timestamp with timezone and whether the issue is still happening.
- Browser and operating system, or desktop app and version.
- Steps to reproduce, expected result, and actual result.
- A sanitized screenshot or recording when it does not expose private content.
Mark urgent impact clearly
- Say if the site or a core product is unavailable.
- Say if you cannot access your account, a paid feature, or an active session.
- Say if you suspect a security incident, unauthorized access, data loss, or harmful content.
- For routine bugs, mention whether a workaround exists.
Aethera support is not an emergency service. If someone is in immediate danger, contact the appropriate
local emergency service.
Protect private work and account data
Do not send passwords, API keys, payment details, seed phrases, sign-in callbacks, private messages, raw
logs, private projects, maps, recordings, or campaign content. If I need more evidence, I will ask for one
specific redacted item.
What happens next
I review reports by impact. Account access, safety, suspected security incidents, billing problems, and
possible data loss come before routine bugs and feature requests. I track confirmed product defects for
investigation and release work; a confirmed issue may be scheduled rather than fixed immediately.
Aethera is built and operated by one developer. The inbox is not monitored around the clock, and I cannot
promise an acknowledgement or fix by a set time. See
how reports are prioritized.