Hosting and Provider Schedule
Document ID: PROVIDERS-v1. Review edition: October 2, 2026.
This schedule describes providers used for the applicable purchased services. It is supplied with the Order Form. Policy links identify official sources; they do not make the client a party to FOH's accounts or replace FOH's Terms. Feature-specific providers apply only when that feature is included. This is not a promise that every listed feature is active for every client.
Hosting and traffic protection
| Provider | Role and information handled | Location and limits |
|---|---|---|
| Vultr / The Constant Company, LLC | Origin server, site files, application data, and enabled server backups | Standard origin: Atlanta, Georgia, United States. Separate backups and provider operations need not remain in Atlanta. |
| Cloudflare, Inc. | DNS, reverse proxy, CDN, TLS, and traffic protection available under the configured plan; processes requests, IP addresses, DNS data, and operational logs | Global edge network. Standard configuration is proxied DNS with Full (strict) TLS, not Cloudflare Tunnel. Paid security features and regional processing controls require a separate order. |
| GitHub, Inc. | Code repositories, version history, and deployment collaboration | Access and storage depend on repository configuration and provider policies; not an all-US residency commitment. |
| Internet Security Research Group / Let's Encrypt | Origin HTTPS certificates and renewal | Domain names appear in public certificate-transparency records. |
Cloudflare does not manage FOH's application code or operating system. FOH maintains those layers within the purchased scope. No provider is described as guaranteeing absolute privacy or security.
Providers used for optional features and operations
| Provider | Use and data |
|---|---|
| Anthropic | Commercial AI assistance for chat and website changes; prompts and the content or code needed for the request. |
| Twilio SendGrid | Transactional mail, including site inquiries and portal notices; recipient addresses, message content, and delivery metadata. |
| Twilio and/or Apple messaging services | Login-code delivery where configured; phone number and message. The actual channel depends on portal configuration. |
| Stripe | Payment processing when a Stripe payment method is selected; billing information and payment details entered directly with Stripe. |
| Microsoft 365 | FOH business correspondence and administration; emails and attachments. |
We do not promise a US-only location, zero retention, or a particular certification for these services. Client-owned ordering, reservation, registrar, email, advertising, and social accounts have their own terms and costs.
Official provider policies
- Cloudflare: Self-Serve Subscription Agreement, application service terms, Privacy Policy, and Data Processing Addendum.
- Vultr: Terms of Service, Acceptable Use, Anti-Spam, Privacy, subprocessors, and SLA.
- GitHub: Terms and Privacy.
- Anthropic: Commercial Terms and DPA.
- Twilio / SendGrid: Terms and DPA.
- Stripe: Services Agreement and Privacy.
- Microsoft: Privacy.
- Apple: Privacy.
- Let's Encrypt: Repository of policies and Privacy.
Practical use restrictions
Ordinary restaurant pages and inquiries are the standard use. Do not send prohibited or infringing material, spam, malware, raw card data, or sensitive regulated records through the site or portal. Cloudflare's Free plan restricts collecting or processing credit-card information; use an approved provider-hosted checkout. Video and large-file delivery may require a dedicated media product under Cloudflare's CDN terms. FOH will identify and quote required upgrades before enabling affected features. A provider SLA applies to the eligible account and service under its own procedures; it is not an FOH website uptime guarantee.
The current provider description is at https://fohrestaurants.com/providers. The copy attached to the signed packet records the disclosure made at signing. Material changes are handled under the Terms of Service.