contact
xeve is built and run by Kevin John. There is no support queue and no ticket robot — every message goes to [email protected] and is answered by a person.
Email [email protected] for anything to do with your account: a tracker that stopped syncing, a day of data that looks wrong, an integration that will not connect, billing, or a question about what xeve collects. One person reads that inbox and replies, usually within one working day and always within three. Include the platform you are on (macOS, Windows, iOS or the web dashboard), the app version from the tracker's menu, and the date range you are looking at — that is almost always enough to reproduce a problem without a second round trip.
The backend, the trackers and the dashboard are open source. File bugs and feature requests as issues on GitHub, where they are public, searchable, and get linked to the commit that closes them. If you are not sure whether something is a bug or a question, email instead — it is easier to turn an email into an issue than to discover a support question three weeks later at the bottom of an issue thread.
Report suspected vulnerabilities to [email protected] with "security" in the subject line, and please do not open a public issue first. Every user's data is isolated by Postgres row-level security, so anything that looks like one account reading another's rows is treated as the highest severity and gets a same-day acknowledgement. Include the request you sent, the response you got, and the account you were signed in as. Reports made in good faith will never be met with legal action.
You can export everything as CSV or JSON from the dashboard at any time, and delete your account and all of its data from settings — both are self-service and neither requires emailing anyone. If a deletion does not complete, or you need written confirmation that it did for compliance reasons, email [email protected] and it will be handled by hand. The privacy policy sets out what is collected, where it is stored, and how long it is kept.
For press, podcasts, integration partnerships or anything else that is not support, email [email protected] with what you are working on and your deadline. The brand name is xeve, always lowercase, and the canonical URL is https://xeve.io. Logos and product screenshots can be requested by email.
API questions have their own answer: the developer documentation covers the REST API, OAuth 2.0 scopes and the MCP server, and there is a machine-readable OpenAPI description at /openapi.json. If you are building an agent that needs xeve data, start there rather than by email — most of what would be asked is written down.