ObservOne
Platform
Cell towers
Tower portfolios at scale.
DAS & small-cell
In-building coverage + AHJ-ready.
Public safety / ERRCS
NFPA 1221 by construction.
Data centers
Power train + cooling envelope.
EV charging
OCPP fleet + NEVI uptime.
Drone & UAV
Part 107 + Remote ID, live.
Copilot
About
Who we are, why we ship.
Customers
References under NDA.
Careers
Build the NOC of the next decade.
Support
Operator-grade response, around the clock.
Trust
Security + compliance.
Contact
Sign inTalk to engineering

Platform

OverviewCopilotTrust & compliance

Solutions

Cell towersTower portfolios at scale.DAS & small-cellIn-building coverage + AHJ-ready.Public safety / ERRCSNFPA 1221 by construction.Data centersPower train + cooling envelope.EV chargingOCPP fleet + NEVI uptime.Drone & UAVPart 107 + Remote ID, live.

Company

AboutWho we are, why we ship.CustomersReferences under NDA.CareersBuild the NOC of the next decade.SupportOperator-grade response, around the clock.TrustSecurity + compliance.
Talk to engineering
Legal

Sub-processors.

Draft — not legal advice

This document is a templated draft, pending counsel review.

The text below is generic SaaS baseline language intended to communicate intent while the formal version is being finalised with our counsel. Do not rely on it for compliance, procurement, audit or any legally binding decision. For the current binding version applicable to your engagement, contact privacy@observone.com.

Effective2026-05-11
Versionv0.1 (draft)
Jurisdiction[PLACEHOLDER: Delaware, USA]
Contents
  1. Overview
  2. Current sub-processors
  3. Onboarding & change notification
  4. Customer objection rights
  5. Contact

1. Overview

ObservOne engages a small number of third-party service providers ("sub-processors") to help us deliver the Service. Each sub-processor is bound by data protection terms consistent with the obligations in our Data Processing Addendum and our privacy notice.

This page lists the sub-processors currently engaged. We update it whenever we add, remove or materially change a sub-processor relationship, and we notify customers as described in § 3.

The roster below is illustrative pending counsel and procurement review. Final names, purposes and processing locations will be confirmed against our actual vendor contracts before this page is removed from draft status.

2. Current sub-processors

Sub-processorPurposeData categoriesProcessing location
[PLACEHOLDER: Amazon Web Services, Inc.]Cloud infrastructure (compute, storage, database)All Customer DataUS, EU, AP — per tenant region pinning
[PLACEHOLDER: Cloudflare, Inc.]CDN, WAF, DDoS protection, DNSNetwork metadata, IP addressesGlobal edge network
[PLACEHOLDER: Vercel Inc.]Marketing site + auxiliary frontend hostingVisitor logs, contact form submissionsUS, EU
[PLACEHOLDER: Datadog, Inc.]Application performance + infrastructure monitoringTelemetry, logs (PII scrubbed), tracesUS, EU
[PLACEHOLDER: Resend / Postmark / SendGrid]Transactional email deliveryRecipient email, message contentUS
[PLACEHOLDER: Stripe, Inc.]Payments processing (if applicable to tier)Billing contact, payment instrumentUS
[PLACEHOLDER: Linear / Jira / Notion]Internal issue tracking, customer support ticketsCustomer contact, support ticket contentUS
[PLACEHOLDER: Slack Technologies, LLC]Customer communication via Slack ConnectCustomer contact, message contentUS
[PLACEHOLDER: HubSpot / Salesforce]CRM, marketing communicationsBusiness contact, marketing preferencesUS
[PLACEHOLDER: Posthog / Mixpanel / Amplitude]Product analytics (consented)Anonymised usage metadataUS, EU

Customer Data is pinned to its region of origin by default. Multi-region replication is opt-in per tenant.

3. Onboarding & change notification

Before a new sub-processor is engaged for the processing of Customer Data, we will:

  • Conduct due diligence against our vendor security and privacy criteria
  • Enter into a written data protection agreement consistent with our customer commitments
  • Update this page with the new sub-processor and its details
  • Notify customer account administrators by email at least [PLACEHOLDER: 30 days] before the new sub-processor begins processing Customer Data

Customers who subscribe to change notifications via their account settings receive the same notice automatically. The same process applies to material changes in purpose, data categories or processing location for an existing sub-processor.

4. Customer objection rights

A customer may object to a new or changed sub-processor on reasonable grounds related to data protection within [PLACEHOLDER: 30 days] of notification. We will work in good faith to accommodate the objection, including by proposing a commercially reasonable alternative.

If no reasonable accommodation is possible, the customer may terminate the affected portion of the Service for cause and receive a pro-rated refund of any pre-paid fees, as further described in our terms of service and Data Processing Addendum.

5. Contact

Privacy team — privacy@observone.com

To subscribe to sub-processor change notifications, contact the privacy team or enable the option in your tenant settings.

Questions or requests under this document? Write to privacy@observone.com. Material changes are versioned and announced via the changelog.
ObservOne

Operator-built observability for towers, DAS, ERRCS, data centers, EV chargers and drone fleets. Distributed team of critical-infrastructure specialists around the globe.

Platform

OverviewAlertsAutomationCopilotCompliance

Solutions

Cell towersDAS & small-cellPublic safety / ERRCSData centersEV chargingDrone & UAV

Resources

API docsStatusChangelog

Company

AboutCustomersCareersSupportContactTrust
© 2026 ObservOne, Inc. · All rights reserved
PrivacyTermsSecuritySub-processors