Subprocessor List
Last updated: November 13th, 2026
These are the third parties that process personal data on our behalf, what each one does, and where it is. This list is part of the Data Processing Addendum.
We give at least 30 days' email notice before adding or replacing a subprocessor that processes personal data. You can subscribe to those notices in your portal under Notifications, or by emailing privacy@lasthourhosting.org.
1. Where your data actually lives
We would rather draw this than let you guess. Our servers, backups, and mail are in the United States. Two supporting services are not, and we say so on every page where we describe our infrastructure rather than only in fine print here.
| Layer | Provider | Where |
|---|---|---|
| Web, database, mail, backups (origin) | Subnet Digital LLC / EGI Hosting | United States |
| Content delivery (public static files) | Bunny.net | Global edge, including EU |
| DNS (zone records) | deSEC | Germany |
| Domain registration | Enom | United States |
| Card payments | Stripe | United States |
| European card payments | Mollie | Netherlands |
| Opt-in SMS alerts | SignalWire | United States |
2. Subprocessors
| Provider | Purpose | Personal data involved | Location |
|---|---|---|---|
| Subnet Digital LLC / EGI Hosting | Bare-metal and colocation hosting for our servers, network, and backups | All data held in the Services, including customer content; network-level IP addresses | United States |
| Bunny.net | Content delivery network for public static files and images | IP addresses of requesting visitors; publicly-requestable files only; no account data | Global edge (Slovenia-registered company) |
| deSEC | Authoritative DNS for domains we host | DNS zone records, which can include hostnames, mail records, and domain-verification tokens | Germany |
| Stripe, Inc. | Card payment processing | Name, email, billing address, card data (held by Stripe, not us), transaction records | United States |
| PayPal, Inc. | Payment processing where you choose PayPal | Name, email, transaction records | United States |
| Mollie B.V. | Payment processing where you choose Mollie | Name, email, transaction records | Netherlands |
| Enom, Inc. | Domain registration and renewal | Registrant name, address, email, phone for domains you register through us | United States |
| SignalWire, Inc. | SMS notifications you opt into (security alerts, ticket updates) | Mobile number, message content | United States |
What is not in that table because it is us. Our mail server (mail.lasthourhosting.org) and our backup infrastructure run on our own hardware, under our own staff, so they are not subprocessors and listing them as if they were would make this page less accurate, not more. Everything they hold is covered by section 4 below.
3. What is not on this list, and why
- No analytics processor. We do not use Google Analytics, Plausible, Matomo, or any other analytics service.
- No advertising or tag manager. We do not use ad networks, remarketing tags, or Google Tag Manager.
- No support desk SaaS. Support tickets are stored on our own servers, not in Zendesk or Intercom.
- No marketing automation. Marketing email is sent from our own mail infrastructure.
- No external font or script CDN. Fonts and scripts are served from our own domain.
- No session recording, heatmap, or error-tracking SaaS. We do not use FullStory, Hotjar, or Sentry.
Conditional processors. Two categories are only engaged in specific circumstances, and we would rather name them than have you find them in a packet capture:
- Bot protection on sign-up forms. Our own bot-detection code runs in your browser and sends nothing to a third party. If we enable a hosted challenge (Cloudflare Turnstile or Google reCAPTCHA) on a form, that provider receives your IP address and browser signals for that form only. Whatever is enabled is named here before it is switched on, and today the self-hosted challenge is the default.
- Automated ticket triage. Where we use a machine-learning service to sort an inbound support ticket, the ticket text is redacted first and the service receives no account name, no email address, and no attachment. It is used to route the ticket to the right person, not to answer you, and it never writes to your ticket. Today this runs on our own infrastructure.
4. Our own staff
Our staff are not subprocessors — they are us. Access to production systems is limited to named individuals, uses individual credentials, requires multi-factor authentication, is logged, and is reviewed when someone leaves. Access to customer content requires a support reason and is recorded in the audit log.
5. Legal process
We may disclose data to a government or law-enforcement body where the law requires it. That is a disclosure, not a processing arrangement, so it is not a subprocessor relationship. We review every request for legal sufficiency, challenge what we consider overbroad, notify the affected customer unless prohibited, and publish a transparency summary of the requests we receive.
6. Changes to this list
We will update this page and email subscribers at least 30 days before adding or replacing a subprocessor that processes personal data. You can object on reasonable data-protection grounds within 30 days; if we cannot resolve it, you may terminate the affected Service and we will refund the unused portion of any prepaid fee.
7. Questions
Email privacy@lasthourhosting.org.