Private help routes

How can we help?

Choose the route that best matches what you need. Account, privacy, and security matters should always be handled privately.

Keep private values out of support messages.

Never send a password, OTP code, full invite code, access or refresh token, API key, recovery code, private key, push token, installation identifier, or payment details. Do not post sensitive matters publicly in Discord.

Contact Asiara

Use the route made for the issue.

These functional addresses are live for incoming mail. Support can also send and reply as `support@asiara.app`. The private destination mailbox is never published.

General helpsupport@asiara.app

OTP, device transfer, push, bugs, and general app help.

Beta accessbeta@asiara.app

Controlled-beta eligibility, invitation, and access questions.

Content correctionscorrections@asiara.app

Wrong dates, entities, summaries, links, duplicates, or sources.

Privacy and dataprivacy@asiara.app

Privacy questions and access, correction, deletion, or export requests.

Security concernssecurity@asiara.app

Compromise, data exposure, malicious links, or vulnerabilities.

Help categories

What to include safely

OTP email problems

Include your platform, app build, approximate attempt time, mailbox provider, and the safe error shown. Never include the OTP itself.

Email Support

Beta code questions

Explain whether the code was intended for a specific email or was unbound and include only the safe error category. Do not post or send the full code.

Email Beta Access

Device transfer or reset

Sign out from the old device when possible. Describe the old and new platform and the safe visible error, without private device identifiers.

Request device help

Push notification issues

Include Android or iPhone, app build, permission state, and the safe visible error. Do not include an Expo push token or installation ID.

Get push help

Bug reports

Include build, platform, screen, expected result, actual result, steps, frequency, and sanitized media if it helps.

Report a bug

Privacy or security

Use the dedicated private route. Share only the minimum information needed, and redact unrelated account or personal data.

Read security guidance

Response expectations

Clear status without false promises.

Asiara may use categories such as Received, Needs information, Under review, Known issue, Action taken, No change, Security escalated, and Closed. These explain progress without promising a guaranteed response time.

Support is founder-operated. New access waves may pause if the support queue exceeds safe capacity.