NyxEvoNyxEvo

Customer support

Support that starts with the right path.

NyxEvo supports the products we build. Palim is our current product, and its detailed support policy remains the authoritative guide for installation, updates, project recovery, accounts, diagnostics, and Beta limitations.

Open Palim supportEmail support

Current product

Palim

Professional workbench for complete writing projects. Support covers the currently published Palim preview and its documented account, update, and product paths.

Detailed support policyDownloads and release evidencePalim privacy notice

01

Contact and scope

Email [email protected] for product support, account access, privacy requests, or a suspected security issue. When possible, use the email address associated with your account.

Support is handled directly and does not currently include a guaranteed response or resolution time. This inbox is not monitored for emergencies or time-critical legal, safety, or business matters.

02

If work may be at risk

  1. Stop the action that appears to be causing loss or corruption. Do not repeatedly save, import, restore, or update the same project.
  2. Preserve the project folder, original files, recent exports, and independent backups. Test recovery only on a copy.
  3. Record the Palim version, operating system, expected result, visible result, and the last action that completed safely.
  4. Contact support before attempting broad repair or deleting any project material.

03

Report an issue clearly

Include only what is needed to understand and reproduce the problem:

  • Product version and release channel; operating-system version and device architecture.
  • A numbered sequence of actions, the exact visible error, whether it repeats, and the last known safe state.
  • Whether the issue also occurs in a fresh empty project, without attaching the affected manuscript.
  • For account requests, the outcome you need. Never include a one-time code or session token.

04

Share less by default

Palim diagnostics are generated locally and are not uploaded automatically. Review any diagnostic package before sharing it.

Do not send manuscripts, source files, prompts, generated text, complete local paths, raw logs, configuration files, access keys, passwords, session tokens, private keys, payment information, or AI credentials. If a content sample is necessary, create the smallest synthetic or redacted example you are comfortable sharing.

05

Security boundary

NyxEvo support will not ask for passwords, one-time verification codes, session tokens, API keys, private keys, payment credentials, or unrestricted remote-control access. Do not install remote-access software or disable operating-system security because of a support request.

Report suspected credential exposure or unauthorized account activity with the subject SECURITY, without including the secret itself.