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.

  • 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 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.

How the platform is organized

Separate services with defined responsibilities.

CCN's website platform uses Google Cloud projects for edge delivery, application runtime, and customer data. The core Cloud Run services are deployed in Dallas (us-south1); payment, email, domain, and other providers operate their own systems. This overview is not a claim that every workflow or provider runs in one region.

  • Static public edge — Marketing pages are static HTML delivered through a global load balancer and content delivery network.
  • 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.
  • Draft before publish — Guest Website Studio drafts are kept in the browser. Signed-in saved drafts use an authenticated private preview. Neither path publishes a website until you take the publish action with an eligible paid plan.
Production cellprod-cell-001
Platform architecture Edge · Runtime · Data

Separate Google Cloud projects organize public delivery, application services, and customer data. Access controls and provider responsibilities still require ongoing review.

01
Edge layercollincountynetworks.com · static marketing · TLS at the load balancer
Public
02
Runtime layerPortal · site renderer · checkout integration · domain search · core Cloud Run services
App
03
Data layerFirebase identity · order ledger · customer media · access controls
Data

Separate application roles

Checkout, registrar integration, and domain discovery have separate application roles. Their external providers retain their own service and availability boundaries.

Protected account actions

Account, checkout, and saved-draft actions require the applicable identity, authorization, and configuration checks. This is not certification of every connected service or external intake.

Defined runtime region

The core Google Cloud runtime is in Dallas. Public edge delivery and external providers use their own infrastructure; location alone does not establish response time or availability.

Human accountability

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

Static edge deliveryStatic marketing HTML through a load balancer and content delivery network.
Secrets off the storefrontPayment and registrar keys stay in the runtime layer.
Dallas core runtimeCore Cloud Run services use us-south1; provider infrastructure varies.
Private Website Studio previewGuest drafts stay in the browser; saved account previews require authentication.

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. CCN does not claim that a service is invulnerable, continuously available, or certified to a framework unless a specific current document says so.

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

Monday through Friday, 10:00 a.m. to 4:00 p.m. Central Time.

Message us

Review the privacy notice before sending personal information.