Nausika is maintained by a single person. For day-to-day feedback, bug reports, and feature requests there is a public issue tracker; for legal, security, and privacy matters the email addresses below route to the same maintainer but help us triage.
Public feedback & bug reports
Open an issue on the public feedback repository: github.com/nausika-app/nausika-feedback/issues. Anyone with a GitHub account can file. The repository contains no source code; it exists purely as a discussion and triage queue, so issues are searchable, comment threads are public, and progress is visible. Use it for:
- wrong, surprising, or empty results from a tool call,
- missing or stale place data (a faster path is the in-AI proposal flow — see below),
- feature requests and ideas,
- questions about how the server behaves.
Please do not use the public tracker for privacy, security, or license-takedown matters — those go to the dedicated email addresses listed below.
Getting in touch
The primary contact is hello@nausika.app. Use the dedicated addresses when they apply:
- privacy@nausika.app — data subject requests under GDPR (access, rectification, erasure, portability). See Privacy for the full procedure.
- takedown@nausika.app — license claims on contributed or sourced data (ODbL, CC BY). See Credits for the upstream sources.
- security@nausika.app — vulnerability reports. The machine-readable
contact lives at
/.well-known/security.txt.
Emails are answered by the maintainer. There is no formal SLA, but most messages get a reply within a few days.
Reporting an issue with a tool call
When the AI assistant returns a wrong, surprising, or empty result from a Nausika tool, send a short note to hello@nausika.app with as much of the following as you can capture:
- The tool name (for example
nausika_marine_forecast). - The exact prompt your AI used to produce the call.
- The response you got versus the response you expected, and why.
- Your account email if the call was authenticated, so we can correlate it with the right user history.
For tricky cases we may ask for the request ID that ships in the tool response — it lets us pull the matching server-side log entry and replay the call.
Reporting wrong place data
Marina, anchorage, and harbor entries can be stale or wrong. The fastest path to a fix is
the proposal flow built into the MCP itself: ask your AI assistant to call
nausika_submit_proposal with the corrected attributes (or a deletion reason) and
a short rationale. Every AI-driven proposal is reviewed by a human maintainer before it
lands in the public dataset, so changes are intentional and auditable.
If the proposal flow does not fit your case (for example a structural data-model issue or a bulk correction), email hello@nausika.app with the place name, coordinates, and what is wrong.
Status & outages
Nausika does not currently publish a real-time status page. The MCP endpoint at
mcp.nausika.app is monitored continuously, and operational notices for material
outages — extended downtime, data-source incidents, breaking schema changes — are posted to
/log. Subscribe via RSS if you want passive
notification.