Serving businesses in McKinney, Collin County, and North Texas

Contact(469) 837-2333
Collin County Networks

Trust / Shared responsibility

Know who is responsible for what.

A secure website, mailbox, or domain is not the work of one company. The customer, Collin County Networks, and the underlying providers each control different parts of the service.

See the responsibility map Ask a trust question
  • Customer ownership stays visible
  • You publish after you pay
  • No blanket security guarantee

Responsibility map

Three parties. Clear boundaries.

This summary explains the normal division of work. Your order, service description, and applicable provider terms control when they are more specific.

Your business and approvals

  • Provide accurate business, registrant, and billing information.
  • Supply lawful content and confirm you have permission to use it.
  • Protect mailbox passwords, Stripe, registrar, and other customer-controlled accounts.
  • Review website content and publish it yourself from Website Studio. Approve material DNS changes you ask us to make.
  • Keep contact and renewal information current.

The service we manage

  • Build and operate the website within the purchased plan and scope.
  • Configure Google-managed hosting and SSL for supported websites.
  • Provision purchased CCN mailboxes and the mail DNS those mailboxes need.
  • Carry out approved DNS and domain work with documented ownership.
  • Limit administrative access to the work being performed.
  • Communicate material service issues and provide a support path.

The underlying platforms

  • Google Cloud supplies the hosting, certificate, and DNS capabilities CCN configures.
  • Stripe processes checkout and payment-card information on its hosted flow.
  • The hosted-email provider supplies mailbox storage, webmail, and mail transport that CCN provisions after checkout.
  • Registrars and registries control domain availability, registration rules, and registry operations.
  • Each provider operates under its own service terms, maintenance, and technical limits.

How safeguards enter the work

Protect the decision points that matter.

Risk cannot be eliminated. It can be reduced by making ownership, access, approval, and recovery decisions explicit.

Review the service terms

  1. Confirm ownership

    Record the business owner, domain registrant, billing contact, and authorized approver before important changes.

  2. Limit access

    Use only the permissions needed for the purchased work and avoid sharing passwords or one-time codes through public forms.

  3. Publish from Studio

    Prepare website changes in the private draft. You publish after the plan is paid. CCN does not review pages before that click. Ask us before a material DNS change we would make for you.

  4. Keep recovery possible

    Maintain current contacts, portable domain ownership, and a clear support route if access or service is disrupted.

What makes CCN better

A faster, safer platform stack—not a plugin pile.

CCN runs on a purpose-built Google Cloud cell in Dallas (us-south1). Public pages, customer portal, payments, and domain services are separated into edge, runtime, and data layers so each part does one job well.

  • Fast public edge — Marketing pages are static HTML behind a global load balancer, not a heavy CMS database on every visit.
  • Split sensitive work — Checkout, webhooks, registrar calls, and portal APIs run as separate Cloud Run services with their own access boundaries.
  • Secrets stay off the storefront — Stripe and registrar credentials live in the runtime layer, not on collincountynetworks.com.
  • Ledger-backed purchases — Orders, entitlements, and 30-day refund eligibility are recorded in a customer ledger—not inferred from email receipts alone.
  • Private draft before publish — Website Studio drafts open in an authenticated private preview through a dedicated renderer before you put anything on your domain.
Production cellprod-cell-001
Platform architecture Edge · Runtime · Data

Three isolated Google Cloud projects—public control plane, confidential services, and restricted customer data.

01
Edge layercollincountynetworks.com · static marketing · TLS at the load balancer
Fast
02
Runtime layerPortal · site renderer · Stripe checkout · domain search · lead ingest · Dallas Cloud Run
Split
03
Data layerVerified Firebase auth · order ledger · customer media · restricted access
Locked
Region: us-south1 (Dallas)Built for Collin County & North Texas

Purpose-built services

Payments, registrar integration, and domain discovery are separate microservices—not one monolithic site builder with dozens of plugins.

Fail-closed by default

Lead forms, checkout, auth, and preview surfaces reject unknown configuration instead of silently falling back to unsafe behavior.

Local latency

Customer workflows run in Dallas, close to Collin County businesses, instead of bouncing through a generic shared builder region.

Human accountability

The architecture supports local phone and email support. You publish the site yourself after a paid plan.

Static edge deliveryFast marketing pages without a CMS database on every visit.
Secrets off the storefrontPayment and registrar keys stay in the runtime layer.
Dallas platform cellProduction runs in us-south1 near Collin County.
Private Website Studio previewDrafts render through an authenticated site-renderer before publish.

Need a specific answer?

Ask about the service you plan to buy.

Tell us whether your question concerns a website plan, design package, business email, domain, DNS record, Google-managed hosting or SSL, or Stripe checkout.

Direct contact(469) 837-2333jeremiah.minardo@collincountynetworks.com

No borrowed guarantees

Provider controls do not certify every customer system.

CCN does not claim that a service is invulnerable, continuously available, or certified to a framework unless a specific current document says so.

Read the privacy policy Read the terms