Umbra · service information
A direct line to Umbra.
Account help, calculation questions, privacy requests and bug reports: admin@umbra.wiki.
Updated
Contact support
Write to admin@umbra.wiki. This is the support mailbox for Umbra, not a live consultation or emergency service. There is no guaranteed response time. Opening the email link launches your mail app; nothing is sent automatically.
Account and data help
For a sign-in problem, tell us which method you used and the error message. Never send a password, one-time code, sign-in link, API key or session cookie. Use the password-reset option in the sign-in window if you need a new password.
For an export or account deletion, open Profile and find Account data controls. Signing out is a separate action and does not delete saved work. If those controls fail, contact support from the account email where possible; do not send identity documents unless a necessary verification step is explicitly agreed.
Report a bug
Include the page or feature, what you tried, what you expected, what happened, and the approximate time with your timezone. Device, browser version and whether the problem occurs on mobile data or Wi-Fi are useful. A screenshot with private information hidden is welcome.
If an error shows a request identifier, include it. Remove personal questions, birth details, email addresses and token-bearing URL parameters from screenshots or copied logs. Do not attach your full account export to a routine bug report.
Report a calculation or interpretation issue
Name the chart or spread type and the displayed method/version, then describe the specific discrepancy. Start without sending someone’s full birth data or journal. We can agree on the minimum example needed to reproduce it.
A source citation or exact rule is useful when challenging an editorial conclusion. A symbolic interpretation that does not resonate and a calculation that uses the wrong input are different issues; both can be reported.
Security and urgent situations
Report a suspected security issue privately to the same mailbox. Describe the affected feature and safe reproduction steps without collecting another user’s data or testing beyond your own account.
If someone is in immediate danger, use local emergency services or direct human support. Do not wait for this mailbox or an interpretation to respond.