Overview
DigitalOcean is a cloud infrastructure provider offering virtual machines (Droplets), managed Kubernetes, object storage (Spaces), managed databases, and app hosting services. When DigitalOcean hostnames appear in a website's network requests, they indicate that the site operator is using DigitalOcean to host application backends, serve static assets from Spaces (object storage), or run API services — not that DigitalOcean itself is injecting tracking or analytics scripts onto the page.
What This Script Does
DigitalOcean as Infrastructure (Not a Client-Side Script)
- DigitalOcean does not inject client-side JavaScript onto third-party websites
- Requests to DigitalOcean-hosted endpoints represent the site operator's own code running on DigitalOcean infrastructure
- Static assets (images, CSS, JavaScript bundles) may be served from DigitalOcean Spaces at
<bucket>.digitaloceanspaces.comor a custom CDN domain fronting Spaces
Object Storage (Spaces) Asset Delivery
*.digitaloceanspaces.com— DigitalOcean's S3-compatible object storage CDN endpoint- Assets stored in Spaces are served globally via DigitalOcean's CDN edge network (built on Cloudflare)
- Cache-Control headers and CDN behavior are configured by the site operator, not DigitalOcean
- No cookies are set by Spaces delivery; assets are served as static files
API and Backend Requests
<subdomain>.<custom-domain>.compointing to a DigitalOcean Droplet or App Platform instance represents the site operator's own application server- These API requests are governed by the site operator's application code, not DigitalOcean
- DigitalOcean retains infrastructure-level logs (access logs with IP addresses) as a standard cloud provider practice
DigitalOcean's Data Processing Role
- DigitalOcean acts as a data processor under GDPR for data stored and processed on its infrastructure
- The site operator is the data controller responsible for determining the purposes of processing
- DigitalOcean's DPA is available at
digitalocean.com/legal/data-processing-agreement - DigitalOcean is a US company headquartered in New York and participates in the EU-US Data Privacy Framework
What DigitalOcean Does Not Do
- Does not inject advertising scripts, tracking pixels, or analytics on hosted sites
- Does not set cookies on the end user's browser on behalf of DigitalOcean (as distinct from the site operator)
- Does not share hosted data with advertising networks
Consent & Compliance
Consent category: Essential / Infrastructure
DigitalOcean is infrastructure. The site operator controls all code running on DigitalOcean and is responsible for the privacy implications of that code. Network requests to DigitalOcean-hosted endpoints are equivalent to requests to the site's own servers — the infrastructure provider does not add independent tracking. Under GDPR, DigitalOcean is a processor, and the operator's DPA with DigitalOcean satisfies Article 28 requirements. No consent is required for infrastructure use.
Should You Block This Without Consent?
No. DigitalOcean is hosting infrastructure. Blocking requests to DigitalOcean endpoints would break the site's own application functionality. There is no independent tracking or data collection by DigitalOcean that requires consent management.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
digitaloceanspaces.comEssentialFrequently Asked Questions
Does DigitalOcean require consent management?
No. DigitalOcean is cloud hosting infrastructure — not a client-side tracking script. Requests to DigitalOcean hostnames represent the site operator's own application code running on rented servers. DigitalOcean does not inject scripts, set advertising cookies, or collect visitor data independently of the hosted application.
What actually happens when a site uses DigitalOcean?
Assets stored in DigitalOcean Spaces (S3-compatible object storage) are served from *.digitaloceanspaces.com via a CDN edge network. API calls to DigitalOcean-hosted Droplets or App Platform instances are calls to the site operator's own backend. DigitalOcean retains standard infrastructure-level access logs as any cloud provider would.
How does ConsentStack handle DigitalOcean in consent flows?
ConsentStack classifies DigitalOcean as essential infrastructure and excludes it from consent banners entirely. Because DigitalOcean acts as a GDPR data processor under the site operator's control, no separate consent is needed. ConsentStack treats requests to DigitalOcean endpoints as equivalent to requests to the site's own servers.
Related Vendors
Manage consent for DigitalOcean
ConsentStack automatically detects and manages DigitalOcean trackers so your site stays compliant with global privacy regulations.