Terms of Service

Last updated: August 9, 2026

This is the agreement between you and me. I wrote it in plain English on purpose. If something in here doesn't make sense, email me and I'll explain it — I'd rather answer the question now than argue about it later.

Who this agreement is between

Hub City Web is a trade name used by NapCarr LLC, which is the contracting party for everything on this page. The assumed-name certificate for “Hub City Web” is not yet on file.

The business is owned and run by Oscar Napoles. There are no employees. When this page says "I," "me," or "my," that means Oscar. When it says "you," that means you personally, or the business you're signing up on behalf of — and by signing up you're confirming you're allowed to enter agreements for that business.

Some work is done with an independent contractor, and I'll tell you when that's the case.

These terms cover:

Using hubcityweb.com
Buying anything from me — a subscription, a one-time item, or a deposit
Any work I do for you, unless we sign a separate written agreement that says otherwise

If we do sign a separate written agreement and it conflicts with this page, the signed agreement wins.

By using the site or buying a service, you accept these terms. If you don't accept them, don't buy anything and don't use the site.

What I actually sell

Here's an honest description of each thing. What's included in your engagement is whatever you and I agree to in writing before work starts — email counts as writing.

Monthly website presence management — starting at $100, $200, or $300 per month depending on your team size

Depending on the plan and what we agree, this can include: managing your domain and DNS, hosting, SSL, backups, keeping software updated, small content edits, setting up your Google Business Profile, correcting your local listings, routing your contact-form submissions to you, and automated customer intake.

Two of those words get oversold everywhere, so here's exactly what they mean when I say them:

Backups. Your site's files are kept in version control and in Netlify's deploy history, so I can roll a broken change back to a previous version. That's what backup means here. There's no separate offsite backup and no tested disaster-recovery process unless we scope one.
Local listings. I'll set up and correct your listings on the directories we agree on, and re-check them when you ask or when something about your business changes. There's no software watching them continuously.

Monthly private AI services — starting at $500, $1,000, or $2,000 per month

This would be a private AI endpoint, scoped and built for you, that indexes your own documents — PDFs, SOPs, contracts, invoices — and runs on infrastructure you control. What it actually does, and where your documents actually live, gets written down and agreed before you pay anything, because nothing about this is off the shelf.

Two things you need to know before you buy it:

It's delivered by an independent contractor, not by me personally. I scope it, I'm your point of contact, and I'm responsible to you for it under these terms — but the technical build and operation is done by someone else. See "Third parties, and the contractor" below.
As of the date at the top of this page, no client has been onboarded to this service yet. There's no track record to point at. If you buy it, you're first, and I'm telling you that up front rather than letting you find out later.

One-time purchases

$149 one-page starter site.
$249 Full Build — a multi-page site, storefront or booking flow. $249 up front, then $35 a month for hosting, the TLS certificate, the domain renewal calendar, backups, and up to three small edits a month turned around inside 48 hours. Cancel any month.
$100 deposit — reserves a slot for a full custom build. It applies to the cost of that build. It's not a separate fee on top.

"Starting at" means starting at

Every published price is a starting point. Every build is custom-scoped, so what you actually pay depends on what you actually need. I'll give you a number in writing before you owe anything, and I won't change that number mid-project without telling you first and getting your OK.

What's not included, unless we specifically agree it is: anything not written into your scope. New pages, new features, redesigns, ad spend, third-party tool subscriptions, photography, copywriting, and rush work are all separate. If you ask for something outside scope, I'll tell you it's outside scope and quote it before I do it.

Billing

Payments run through Stripe. Stripe handles the card. I never see or store your card number. Your card data is governed by Stripe's own terms and policies, not mine.

Monthly plans:

Your subscription bills automatically on the same day each month until you cancel.
The first charge is on the day you sign up. That day becomes your billing date.
If your billing date doesn't exist in a given month (the 29th, 30th, or 31st), Stripe bills on the last day of that month.
Subscriptions are billed in advance for the coming month.
There's no minimum term on the published monthly plans. If a custom engagement ever has one, it'll be written into your scope and I'll point at it before you agree to anything.

Refunds, cancellation, and what happens when a payment fails are governed by the Refund and Cancellation Policy at hubcityweb.com/refund.html, which is part of these terms. I keep those rules in one place on purpose — two copies of a refund rule drift apart, and then nobody knows which one is real.

Price changes: I can change prices. If I change the price of a plan you're already on, I'll email you at least 30 days before it takes effect. If you don't want the new price, cancel before it starts — that's your out, and using it is fine.

Taxes are your responsibility where they apply, unless stated otherwise on your invoice.

What I need from you

About any timeline I quote you. Any turnaround I put in writing — on this site, in an email, or out loud — assumes you get me what I need to do the work: content, photos, logins, approvals, and answers, in a timely way. The clock starts when I have those, and it pauses when I’m waiting on them. That is not a technicality, it is just how the work goes. If something is going to be late on my end, I’ll tell you before the date, not after.

The work only goes as fast as the information does. This is where most projects stall, so it's worth being clear.

Content. Your text, photos, logo, menu, hours, prices, service list. If you want me to write or source something, that's a scoped item, not an assumption.
Access. Some work requires me to get into accounts you own — your domain registrar, Google Business Profile, Shopify, hosting, email. You're giving me permission to act on your behalf inside those accounts only for the work we agreed to, and only for as long as we're working together. I'll ask before doing anything destructive. You can revoke my access at any time, though it may stop me from doing the work you're paying for.
The right to use what you give me. When you hand me text, photos, logos, fonts, videos, or reviews, you're confirming you actually have the right to use them. I can't verify that for you. If someone comes after you for using material you didn't own, that's on you, and you agree to cover me for claims that come from material you supplied.
Responses. If I'm waiting on you for content, approval, or access, the project waits too. If a project sits idle for a long stretch with no response from you, I may close it out and treat any remaining work as a new engagement.
Legal compliance on your side. Your business, your claims, your prices, your licensing, your industry rules. I build what you tell me to build. I'm not your compliance department.

Who owns what

This is the clause that causes real fights, so I'm going to be specific.

Your stuff stays yours. Your content, your logo, your photos, your text, your customer data, your documents in the AI service — yours, always, from day one. I don't take ownership of any of it. I do need permission to use it to do the work, and I'd like permission to show the finished site in my portfolio — tell me if you'd rather I didn't, and I won't.

Your domain is yours. Wherever possible I register it in your name, on your account. If it's sitting in an account of mine, it's still yours and I'll transfer it to you on request once your balance is settled. I don't hold domains hostage.

Your finished site is yours once it's paid for. When you've paid the one-time build in full, I assign ownership of the finished, custom parts of that site — the page designs, the layout, the custom code written specifically for you — to you. If that assignment doesn't take effect for any technical legal reason, you have an unlimited, permanent, exclusive, paid-up license to use, change, and move it, which is the practical equivalent. On request I'll sign a one-page assignment so you have a signed document in your file. Until the build is paid in full, I still own it and it stays on my hosting.

The underlying tooling stays mine. The templates, components, scripts, snippets, style systems, checklists, and processes I build with are mine. I reuse them from project to project, and I'll keep doing that. You get a permanent, paid-up license to keep using them as part of your site, forever. What you don't get is the right to resell them or hand them to another agency as a starter kit.

Third-party pieces belong to third parties. Fonts, stock photos, plugins, and paid tools are licensed from whoever makes them, on their terms. Some of those licenses can transfer to you and some can't. I'll tell you which is which for anything I put in your site.

AI service ownership. Your documents, and the answers generated from them, are yours. The models, software, and infrastructure tooling behind the endpoint aren't mine to give you — they belong to the contractor and their vendors. Your written scope will spell out exactly what license you get, and what happens to your deployment if the contractor and I stop working together.

When a plan ends — what happens to your site

This is the one place this rule is written. The Refund and Cancellation Policy points here rather than repeating it, so there's only ever one answer.

Stopping a monthly plan does not take away a site you already paid for. Here's what actually happens:

The monthly plan stops at the end of the period you've paid for. Hosting, SSL, backups, edits, and listing management — all of it ends.
Your live site goes offline at that point, because the hosting was part of the plan. Same rule whether you cancelled or a payment failed and the subscription ended. If you want the site to stay up, tell me before your last paid day and I'll hand you the files so you, or whoever comes next, can host it somewhere else.
You keep ownership of the paid-for build. If your build is paid in full, ask and I'll send you a copy of the site files — HTML, CSS, images, content. No charge, no ransom. The one thing I can't hand over is anything licensed from a third party beyond what that license allows.
Your domain transfers to you on request, once your balance is settled. Registrars run their own transfer rules, including a 60-day lock after a domain is first registered or transferred, so the timing isn't fully in my hands — but the domain goes to you.
If the build is not paid in full, I keep ownership of the custom work until it is. You still get your own content back — your text, your photos, your logo, your data. That's yours regardless.
Unpaid balances are still owed. Cancelling doesn't erase what's already due.
I don't delete your files out of spite, and I'm not going to promise a retention window I'd need a reminder system to honor. I keep a copy for a while after a plan ends, and you can ask for it any time — so ask early rather than late.

For the AI service: where your documents live, and whether any copy ever exists outside your own infrastructure, is written into your scope before you pay. Whatever the scope says, when the engagement ends I remove my access, ask the contractor to remove theirs and confirm it in writing, and delete anything on my side.

Third parties, and the contractor

I don't run any of this on hardware in my garage. Real services do the heavy lifting, and their terms and outages apply to you too:

Netlify — hosting for hubcityweb.com and for client sites, including the contact form
Stripe — payments
Google Workspace — my email
Google Fonts — the typefaces the site loads
jsDelivr — the content delivery network that serves the animation library the site uses
Calendly — booking, loaded when you click the booking button
Domain registrars — whichever one holds your domain
An independent contractor — would build and operate the private AI service

I have no control over these companies. If one of them has an outage, changes its pricing, changes its terms, or loses data, I'll help you deal with it, but I can't be responsible for their failures.

About the contractor, plainly: the private AI service isn't built by me. It's built by an independent contractor I bring in. That means a person outside my business may need access to your systems and your documents in order to do the work. Before that happens, I will have a written confidentiality agreement in place with that contractor covering your material, and the no-training requirement described in my privacy policy will be a written term of it. If you want to know who they are before you buy, ask me and I'll tell you.

I remain your point of contact and I'm accountable to you for the service under these terms. But I'm not going to pretend a one-person shop is a whole company.

The honest limits of what I can promise

Read this part. It's the part everybody skips, and it's the part that's most different from what other agencies put on this page.

I don't have any certifications, and I'm not claiming any. Not HIPAA. Not SOC 2. Not PCI. Not ISO. Not GDPR certification. No audits. None of it exists here, and nobody has assessed this business against any of those standards.

That matters most for healthcare. Healthcare businesses are a market I want to serve, so I want this unmistakable: I am not a HIPAA business associate, I cannot sign a BAA, and you must not send me protected health information. Not by email, not through a contact form, not in a document set for the AI service. If your work involves PHI, we need to talk about that specifically before anything starts — and the honest answer may be that I'm not the right fit.

I don't promise uptime. No percentage, no SLA, and no monitoring. There's one person here and no monitoring infrastructure that could stand behind a number. If something breaks and you tell me, or I catch it, I fix it.

I don't promise a response time or a delivery date unless I've written a specific date into your scope for a specific piece of work. I try to answer fast because I care about my clients. That's a habit, not a term of this agreement.

I don't promise results. Not rankings, not traffic, not phone calls, not sales. Anyone who does promise those is guessing or lying.

On security, here's exactly what's true: hubcityweb.com is served over HTTPS. My email runs on Google Workspace. Card numbers are handled by Stripe and never touch my systems. Beyond that, I make no claims about encryption, storage, or the security controls of any system, including my own or my vendors'. There are no user accounts, logins, or passwords on hubcityweb.com today. There's no analytics software installed on it today. An AI chat widget is planned but is not live. If any of that changes, this page and the privacy policy change with it.

Everything is provided "as is." To the fullest extent Texas law allows, I disclaim all warranties — express or implied — including merchantability, fitness for a particular purpose, and non-infringement. Software breaks. Vendors go down. Nothing online is guaranteed.

Limitation of liability

To the fullest extent the law allows, I'm asking you to agree to the following:

My total liability to you for any claim is capped at what you actually paid me in the three months before the claim came up. For a one-time purchase, it's capped at what you paid for that purchase.
I'm not liable for indirect losses — lost profits, lost sales, lost customers, lost data, lost goodwill, or business interruption — even if I knew they were possible.
I'm not liable for the failures of third parties, including hosting, payment, domain, email, and AI vendors, and including outages, breaches, and price or policy changes on their side.
I'm not liable for problems caused by material you gave me, changes you or someone else made to your site or accounts, or your use of your own accounts.

This is a one-person business. That cap is small because the business is small. I'd rather you know the real number now than discover it during a dispute.

Some claims can't be capped or disclaimed by agreement under Texas law — including fraud, willful misconduct, and personal injury caused by my own negligence — and this section doesn't try to. If any part of it is unenforceable, the rest still stands.

Ending the agreement

You can cancel a monthly plan at any time. How to do it, and what you get back, are in the Refund and Cancellation Policy at hubcityweb.com/refund.html. Short version: no notice period, no fee, no runaround.

I can end an engagement too. I'll give you reasonable notice and a copy of what you've paid for. I may end it immediately if payment is significantly overdue, if you ask me to do something illegal or deceptive, or if you're abusive to me. That last one is rare, and I mention it because integrity runs both directions.

When it ends: what you already paid for stays yours, unpaid balances are still owed, and the rules in "When a plan ends — what happens to your site" apply.

Acceptable use of hubcityweb.com

Don't try to break into it, scrape it at volume, overload it, or use it to send anything illegal or abusive. The content on the site — text, images, layout, and code — is mine, except for client logos and work shown with their permission. Don't copy it wholesale for your own agency site.

Information on the site, including plan pages, is a description of what I offer, not a binding quote. A binding number comes from me in writing, for you.

Changes to these terms

I can update this page. If I make a change that materially affects an active client, I'll email you about it rather than quietly editing the page. The "last updated" date at the top always reflects the current version. Continuing to use the services after a change means you accept the updated terms.

Governing law

These terms are governed by the laws of the State of Texas, without regard to conflict-of-laws rules. Any dispute goes to the state or federal courts located in Lubbock County, Texas, and we both agree to that.

Before anyone files anything, email me. Most disputes in a business this size are a misunderstanding that a phone call fixes.

How to reach me about these terms

Email: contact@hubcityweb.com

Business: NapCarr LLC, doing business as Hub City Web — Lubbock, Texas, USA

That email is the fastest way to reach me, and it reaches me directly. There's no ticket queue and no one else to route around.