Help & Support — Precision in Every Interaction

Support at Arasaka is an extension of our engineering discipline. We resolve questions the way we design systems: with clarity, reproducibility, and respect for time. If you seek answers, you will get signal — not noise; structure — not ceremony. Below is a concise map of how to reach us and what to expect.

Topics We Handle

• General inquiries: basic information about programs, pages, and terminology.
• Product & research: documentation requests, non-confidential technical overviews, roadmap context.
• Investors & partnerships: participation criteria, process, and alignment checks.
• Careers: roles, process, relocation, non-traditional backgrounds.
• Media & speaking: official statements, interviews, and usage guidelines.

If your question falls outside these topics, we will route it to the correct custodian.

Response Standards

• Clarity first: we may request one clarifying sentence to remove ambiguity before acting.
• Written truth: decisions and answers are documented; links to artifacts when relevant.
• Respect for time: concise replies; summaries before detail; next steps explicit.
• Confidentiality: sensitive items moved to a verified channel without repetition via email.

Escalation & Priority

If your matter is time-sensitive, mark the subject line with [PRIORITY] and include one sentence describing impact and deadline. We triage by risk, scope, and reversibility.

Security & Vulnerability Disclosure

If you believe you’ve found a security or privacy issue, contact us immediately. Include a minimal reproduction path, affected surface, and expected impact. Do not share details publicly until coordinated with us.

• Scope examples: data exposure, auth bypass, misconfiguration, integrity risks.
• Out of scope: social engineering, expired demo endpoints, non-sensitive debug text.

We acknowledge receipt, assess severity, and coordinate remediation with clear timestamps.

Data & Privacy

We minimize collection, restrict access by role, and maintain audit trails. Requests for data access, export, or deletion should come from the verified address linked to the record, including a brief description of scope.

Contact

Email (all topics): [email protected]

Send Signal. Receive Structure.

Write one paragraph that defines your objective, the context, and the smallest proof you have. We will return a clear next step — or a clear “no” with rationale. Either way, you save time.

Start here: [email protected]