Legal
Terms of service.
The terms we work under: written scopes, fixed prices, your accounts, and your ownership after handover.
Effective date: August 26, 2026
Agreement
These terms apply when you use this site, book a call, or commission work from Zeptic Flow. Booking a call or approving a scope means you accept them. Questions first: nakib@zepticflow.com.
The service
We build custom automation systems and manage GoHighLevel accounts. Every build is scoped in writing with a fixed price and a fixed date, and you approve the scope before anything starts. Work not in the written scope is not part of the engagement until we agree it in writing.
Your accounts, your ownership
Systems are built inside accounts you own and can log into. After handover, the accounts, the data and the workflows are yours. There is no black box to rent from us, and ending an engagement never takes your systems away.
Those accounts run on third-party platforms (for example n8n, GoHighLevel, OpenAI, HeyGen, telephony carriers). Their terms, their fees and their availability are between you and them; we configure them, we do not control them.
Payment
One-time builds are paid as set out in the written scope. Managed GoHighLevel accounts are billed monthly per account, with no long-term contract; cancel anytime and the subscription ends at the close of the paid period. Fees already paid for work already delivered are not refunded.
Handover and fixes
Every build includes a handover (a walkthrough recording and notes on how to change each part) and a window after handover in which fixes are free. After that window, support continues on a monthly plan if you want it, or the system is fully yours to run and modify.
What we do not promise
An automation system improves how fast and how consistently you respond; it does not manufacture demand. Results depend on your offer and your inbound volume, and we do not guarantee revenue outcomes. Outages or policy changes at third-party platforms and carriers are outside our control, though we will help you work around them.
Acceptable use
Systems we build must not be used for spam, unlawful messaging, or contacting people who have not consented to be contacted. Business texting in the US requires carrier registration before sending, and messaging through any system we build must respect those rules.
Liability
To the extent the law allows, our liability for any claim arising from an engagement is limited to the fees you paid for the specific work the claim concerns.
This site
The content of this site belongs to Zeptic Flow. Do not republish it wholesale. Case studies describe real systems and stay anonymous until the client has given written permission to be named.
Changes
If these terms change, the new version is posted here with a new effective date. The terms in force when you approved a scope are the ones that govern that engagement.