Channels
In-app chat and email both feed the same support queue. Use whichever fits your workflow.
Response times
Times are measured during business hours in your billing region.
Critical incidents (Vibely is down, data integrity at risk) are handled outside business-hours queues for all paid plans.
What we cover
- Bugs in the Vibely product — UI glitches, sandbox failures, model misbehaviour, billing miscalculations
- Account and billing issues — sign-in problems, plan changes, refunds for actual product issues, invoice questions
- Connector auth problems — OAuth flows that don’t complete, scope issues, key rotation guidance
- Publishing problems — DNS, TLS, custom domains, access controls
- GitHub / EAS / Expo sync issues — anything Vibely orchestrates on your behalf
What we don’t cover
- Bugs in your generated code. Vibely writes the code, but you own and review it. We’re happy to advise on the right pattern; we don’t debug your app.
- Third-party service outages. If Stripe, Supabase, GitHub, or EAS is down, talk to them. We’ll surface their status when it affects Vibely.
- Custom integrations beyond the catalog. We can usually point you at the right pattern but won’t write the integration for you.
- Architectural advice on production systems. For deep architecture review on production deployments, talk to us about a custom engagement.
Status page
Real-time status at status.vibely.sh covers:- The build engine and sandbox availability
- Auth and billing
- The connector gateway
Security disclosures
Email contact@chatmana.in with details. We’ll:- Acknowledge receipt within one business day
- Triage privately and coordinate a fix timeline
- Credit you in the public advisory after the fix ships, if you’d like
Compliance and trust
- SOC 2 Type II — current report available on request under NDA
- GDPR / data processing addendum — available for the Business plan
- Trust centre — trust.vibely.app
Next
FAQ
Pre-purchase questions and common worries.
Troubleshooting
First-line recovery for common failure modes.