SeaSoup
Support

Get help without sharing your phrases.

Use this page when something breaks or you need a clear path to report it. Keep private content out of public posts. We can usually help from versions, steps, and a metadata-only diagnostic summary.

Keep private: phrase bodies, clipboard contents, customer data, credentials, tokens, private URLs, scripts, and captured screen context should not appear in public issues or screenshots.

Include

  • Astramar version and build.
  • macOS version.
  • Where it happened: launch, permissions, palette, insertion, triggers, library, import/export, billing, AI, or Team Preview.
  • What you expected and what happened instead.
  • Steps to reproduce using sanitized examples.
  • A metadata-only diagnostic summary from Settings when available.

Leave out

  • Actual phrase or template content.
  • Clipboard history.
  • API keys, OAuth tokens, passwords, certificates, or signing data.
  • Customer names, ticket bodies, or captured application context.
  • Full private filesystem paths when a short redacted path is enough.

How we prioritize

UrgentPossible data loss, security exposure, a broken public download, or a launch-wide failure with no workaround.
HighCritical workflow failure, repeated crash or hang, broken restore or billing path, or a severe permission/insertion defect.
NormalRecoverable defects, narrow compatibility issues, usability problems, or enhancement ideas.

If you fear data loss

Stop repeating imports, migrations, or destructive edits. Keep the original file and any recovery copies. Use Astramar’s reveal, backup, restore, and diagnostic controls before deleting or replacing library data.

Billing and refunds

Paid Pro is not generally available yet. When purchases open, restore, cancellation, and refund guidance will match the published billing channel for your install.

Optional tips that support SeaSoup’s work live on the separate Support development page. Those payments never unlock Pro, skins, or other Astramar features.