Trust & FAQ
Automation connects to important business systems. Here is exactly who owns what and what happens after delivery.
Who owns the workflow and connected accounts?
You do. The workflow, documentation and configuration delivered for your project belong to you after payment. We recommend running it in your own n8n or Make account, not ours.
How are API keys and credentials handled?
Credentials should stay in your own accounts and credential store. We ask for the minimum access needed to build and test, never ask you to send secret keys in plain chat, and remove temporary access when the work is complete.
Do you provide backups and error alerts?
Yes, when included in the selected package. The Business package includes error handling and alerts. Managed Automation adds health checks, connection maintenance and a monthly report. We confirm the exact backup and alert scope in the quote.
Can I maintain the system myself after delivery?
Yes. Every delivery includes an importable workflow, a one-page specification and a walkthrough video. You can operate it yourself, or keep us on a monthly retainer for monitoring and fixes.
What if I cancel managed support?
The workflow remains yours. We stop the recurring support at the agreed billing boundary, provide the current documentation and handover notes, and you keep control of your accounts and data.
Who is responsible for hosting?
Our default is your own hosting or platform account, so you keep ownership and billing control. If you ask us to host or manage it, the hosting cost and responsibilities are listed separately in the quote.
Our Delivery Commitments
Clear ownership
Your accounts, data and delivered workflow stay under your control.
Documented handover
You receive the files and instructions needed to run the system without us.
Defined scope
Development, hosting and managed support are separate line items, agreed before work starts.