Terms of Service

Who you're dealing with

Zoevin, a sole proprietorship operated by Chris Bounds in Roseville, California. No separate corporation or LLC is registered for Zoevin today; if that changes, this page will name the entity.

"I" and "me" mean Chris Bounds. "You" means whoever's using this site or buying a service.

Contact: chris@zoevin.io
Phone: Email is the contact of record until a phone number is published here.
Mail: Mailing address is provided on engagement letters when required.

Engagement terms come first

For any paid automation work there's a separate written agreement — a statement of work that names the process, the systems in scope, and the handover date.

Those documents are incorporated here by reference, and where they conflict with anything on this page, they win. This page is the general baseline. The engagement documents are the specific deal, and the specific deal governs.

Nothing on this website is an offer to build anything. An engagement begins when both of us sign.

No warranty of a particular outcome

This is the clause that matters most, so it's in plain words.

An automation does the bounded job we wrote down. It does not guarantee time saved, headcount change, or a process that never needs a person.

What that means concretely:

• I build the workflow named in the engagement, in the systems you already license, during the window you signed for.
• Work outside that scope is a new engagement, or no.
• After handover, running the workflow is yours. I do not stay on-call.
• A platform change, a renamed field, or a permission change can stop a working workflow.

So I don't promise a particular business result, and I don't offer any guarantee of uptime, compliance, or a particular audit outcome.

What I do promise: the handover record, runbook, and rollback notes we agreed, and that the workflow matches the written scope on the day access is removed.

Services are provided as-is beyond that promise. To the extent California law allows, I disclaim implied warranties of merchantability and fitness for a particular purpose. Day-to-day operation of what I build stays with you.

Limitation of liability

• Engagement claims. Total liability capped at the fees you paid me for that engagement.
• Website-only claims (no fees paid): capped at one hundred dollars.
• No consequential damages. I'm not liable for indirect, incidental, special, consequential, or punitive damages — including lost profits, data, business, reputation, or interruption — whether or not mentioned in advance.
• What the cap doesn't cover. Gross negligence, willful misconduct, or fraud; and anything California law says can't be capped.

A solo practice can't absorb enterprise-scale consequential damages. If your risk profile needs more coverage, tell me during scoping and we'll talk about what's actually workable.

Deliverables, methodology, and who owns what

Your workflow is yours. On payment in full you own the workflow I deliver, including the runbook, rollback notes, and operating notes specific to your environment. Use it internally and hand it to your IT provider. No extra permission needed and no per-copy fee.

Your data is yours. Anything you give me stays yours. I hold it under the engagement's confidentiality and retention terms and I don't use it for anything outside your engagement.

My methods are mine. I keep ownership of the underlying methodology, checklists, templates, tooling, and the general knowledge and experience I bring. Owning the workflow doesn't transfer the machinery that produced it.

What I may reuse. General skill and know-how, and non-identifying, aggregated observations about common process patterns. Nothing that names you, describes your environment, or could reasonably be traced back to you. If I ever want to use something recognizable, I'll ask in writing first, and no is a complete answer.

Site content. Text, layout, and graphics on zoevin.io belong to me. Quote a passage with attribution, that's fine. Republishing whole pages isn't.

Payment

Free fit consult. No fee. It is a conversation about one real process that is eating the week. You do not pay to ask whether a build is even a fit.

Published automation fees. Discovery and build fees are listed on the automation page. They are fixed fees by scope, not hourly rates. Anything outside the published ladder is quoted in writing before work starts.

Build work gets scoped in writing. The process, the systems, the exception path, and the handover date live in the statement of work.

Invoices. Terms are net 15 unless the statement of work says otherwise. If an invoice goes 30 days past due I pause work and hold deliverables until it clears, and I'll tell you before that happens rather than after. Sales tax where it applies. Expenses only if the statement of work says so, and only with receipts.

Using this site

Ordinary use is welcome. A few limits.

• Don't attack, probe, scan, or attempt to break this site, except under the terms on the responsible disclosure page. That page grants real permission and real safe harbor. Take it.
• Don't scrape the site to build a marketing list.
• Don't submit someone else's personal information through the contact form.
• Don't use the form to send malware, spam, or anything unlawful.
• Don't impersonate anyone, including me.
• Don't misrepresent what's on this site, particularly around what I'm qualified to do.

Information on this site is general and educational. It isn't legal advice, isn't a compliance opinion, and isn't a substitute for an assessment of your actual environment.

I may suspend access for anyone abusing the site.

Governing law and disputes

California law governs these terms, without regard to conflict-of-laws rules. Exclusive venue and jurisdiction sit in the state and federal courts serving Placer County, California.

Before filing anything, both of us agree to try to resolve it directly for 30 days. Most disputes in a business this size are a misunderstanding about scope, and a phone call fixes them faster than a filing does.

Changes to these terms

I can update this page. The date at the top changes when I do.

Changes apply going forward. They don't rewrite a signed engagement, and they don't retroactively change terms you already bought under. For a material change I'll email anyone with an active engagement.

If any part of these terms turns out to be unenforceable, the rest stays in force.