Support
Codaegis uses a docs-first support posture. Public docs, FAQs, and agent-ingestible guidance should answer ordinary questions without founder-managed support.
Public routesupport@codaegis.com
Use this route for support, billing questions, refund requests, cancellation help, privacy requests, deletion/export requests, and security intake unless Codaegis later splits contacts.
What support can help with
- Account access questions.
- Stripe billing questions.
- Refund or cancellation routing.
- GitHub connection setup for the admitted PR-review path.
- Understanding what a governed packet means and does not authorize.
- Export, packet-history, billing receipt, and hard-stop questions if those features are activated.
What support does not include
- Custom implementation work.
- Manual repository repair.
- Emergency incident response for customer systems.
- Legal, security, compliance, production, merge, deploy, or warranty approval.
- Deciding whether a customer's code should merge or deploy.
- Public API, SDK, CLI, Cursor, VM-agent, autonomous writeback, or non-PR work-family support unless separately admitted.
Response and data posture
- Codaegis does not promise an SLA, priority support, guaranteed response time, 24/7 support, uptime commitment, or custom service work unless later terms explicitly say so.
- Support should not inspect private repository, pull-request, packet, or code content unless the customer explicitly provides it or gives permission.
- Customers should not send secrets, production credentials, private keys, unrelated source code, regulated data, or customer data unless Codaegis asks for a narrow artifact and the customer is permitted to share it.
- Support, billing, privacy, refund, security, and account communications may be retained as needed for service history, billing, fraud, security, legal, and operational continuity.