Skip to content
AE INDUSTRIESAI FOR INDUSTRIAL AUTOMATION
HomeAboutMissionCareers
ENGINEERED FOR INDUSTRIAL AUTOMATION
Home/Legal

DOCUMENT ARCHIVE

AEOS ERP Subprocessors

Service providers, their processing purposes and location disclosures, and the process for provider changes.

Download document MD Current document ↗
On this page
  • 1 Scope
  • 2 Infrastructure and communications
  • 3 Native AI services at customer onboarding
  • 4 Hosting access and processing locations
    • Supabase
    • Vercel
    • Railway
    • Upstash
    • Resend
    • Firebase and Apple notification delivery
    • Cloudflare Turnstile
    • OpenAI API
    • Anthropic API
    • ElevenLabs
  • 5 Independent services and customer-selected connections
  • 6 Changes and objections
← All legal documents

AE Industries Inc | Version 2026-11-17-web-3 | Version date November 17, 2026

Canonical page: https://aeindustries.ai/legal/subprocessors

1 Scope

AE Industries Inc uses the providers below to deliver AEOS ERP. This page supports Annex D of our Data Processing Addendum. A provider receives only the information needed for the enabled service and permitted purpose. A customer's selected modules, devices and integrations determine which providers process its information.

The listed legal names come from each provider's standard terms for the relevant service. An account-specific agreement may identify a different contracting affiliate. AE purchases Supabase directly; its standard contracting entity for that route is identified below. The list identifies service providers and their roles, without representing that every provider processes every customer's records.

2 Infrastructure and communications

Provider and legal entity Service purpose Customer personal data Location information
Supabase — Supabase Pte. Ltd. under the direct-purchase route Database and private file storage Stored ERP records, documents, signatures and attachments AE-hosted service region: Northern Virginia, United States; separate backup/access details in section 4
Vercel — Vercel Inc. Web hosting and request processing Submitted requests, service content, IP/device and technical metadata AE-hosted service region: Northern Virginia, United States; other processing/access details in section 4
Railway — Railway Corporation Background workers and malware scanning Task payloads and uploaded content needed for processing or scanning AE-hosted service region: Northern Virginia, United States; other processing/access details in section 4
Upstash — Upstash, Inc. Redis queues and operational processing Queued task payloads and technical data AE-hosted service region: Northern Virginia, United States; other processing/access details in section 4
Resend — Plus Five Five, Inc. System and customer campaign email delivery Addresses, message content, enabled attachments and delivery/engagement information Provider processing/access details in section 4
Firebase — Google LLC under the standard Google APIs terms Android and iOS push notifications Push tokens, notification title/body/data and delivery metadata Provider processing/access details in section 4; Apple's push service participates in underlying iOS delivery
Cloudflare Turnstile — Cloudflare, Inc. Careers and application-page bot protection Relevant request, device, network and security signals Provider processing/access details in section 4

Provider entity references: Supabase terms, Vercel DPA, Railway terms, Upstash DPA, Resend DPA, Firebase terms and Google APIs terms, and Cloudflare DPA. These links identify the providers' published terms; AE's commitments to customers are in the AEOS agreement.

3 Native AI services at customer onboarding

The native AI offering includes the following providers for authorized assistive tasks within the purchased and enabled features. AI is on by default for included features, and organization administrators can disable it for their organization. Relevant feature disclosures identify the task, provider and permitted data. AI voice calls, including recruiting screening calls, are excluded from the initial offering.

Provider and standard U.S. legal entity Service purpose Customer personal data Location information
OpenAI — OpenAI OpCo, LLC Native AI assistance within authorized modules Task prompts, selected records/context, outputs and usage metadata External AI processing locations are described in section 4; application hosting does not establish inference residency
Anthropic — Anthropic, PBC Native AI assistance within authorized modules Task prompts, selected records/context, outputs and usage metadata External AI processing locations are described in section 4; application hosting does not establish inference residency
ElevenLabs — Eleven Labs Inc. Native AI services within the non-voice-call onboarding offering Content and metadata needed for the selected non-call task, as disclosed with the feature External AI processing locations are described in section 4; application hosting does not establish inference residency

AE and AE-engaged providers may not use customer data to train general-purpose AI models. Authorized inference for customer tasks remains permitted. Customers must arrange qualified human review before relying on AI for consequential decisions. Voluntary EEO responses are restricted to authorized HR/compliance uses and excluded from candidate screening and AI ranking.

Provider entity references: OpenAI Services Agreement, Anthropic Commercial Terms and ElevenLabs terms. Account-specific terms and settings govern the provider route; this page does not promise zero retention or an unselected regional configuration.

4 Hosting access and processing locations

AE has confirmed us-east-1 (Northern Virginia, United States) as the hosting region for AEOS ERP hosted services. Supabase-managed database backups remain in the selected project region. A separate uploaded-file backup destination was provisioned in Amazon S3 in us-east-1 (Northern Virginia, United States) during the November 17, 2026 setup review. At that review, the scheduled backup job and restoration test had not been completed, and separate uploaded-file backups were not operational.

AE personnel and contractors may access production customer data for administration or support only while physically in the United States, including while traveling. The supplier disclosures below describe separate provider operations and do not relax that AE personnel restriction.

The following is a dated summary of official provider disclosures reviewed November 17, 2026. Published locations describe the relevant provider's service footprint; they do not mean every location receives every customer's information. Enabled features, selected regions and the applicable provider arrangement determine the actual route. Where a provider uses regional or worldwide descriptions, those descriptions are retained rather than converted into an unsupported closed country list. Corporate addresses alone do not establish processing locations. A provider's other products are not added to AEOS merely because they appear in its register.

Supabase

Core database and Storage hosting and managed database backups follow the project region. Under AE's direct purchase, Supabase Pte. Ltd. is the Singapore primary processor and Supabase, Inc. is the United States support/operations affiliate. Supabase's register also identifies Hungary for ConfigCat and United States locations for its other listed onward companies. These company-country entries are not an exhaustive access-location guarantee. Supabase separately describes globally distributed support, operational logs in EU data centers and global CDN delivery. The cited disclosures do not enumerate every support country or individual EU log-storage country. See the residency FAQ and October 12, 2026 register.

Vercel

Vercel's register lists United States locations for most providers, Spain for Tinybird analytics, and United Kingdom for Plain customer support; other support platforms are listed in the United States. Its DPA identifies primary U.S. processing and permits operations where Vercel and its subprocessors operate. Its delivery network is global. These disclosures do not give an exhaustive country list for Vercel employees' remote access or make the application-compute region a limit on all network processing. See the provider register, DPA section 13 and network documentation.

Railway

Services and attached volumes follow their selected deployment region; primary provider operations are in the United States. Railway's register identifies infrastructure in the United States or selected Railway region, storage in the United States, EU and Singapore, Cloudflare delivery in the United States, EEA and user's location, and Fastly delivery as global. Most operational, communication and issue-tracking entries are United States. The register covers multiple services and does not separately enumerate every employee support-access country. See the provider register, data-residency documentation and DPA.

Upstash

Redis data follows the configured primary and read regions. Upstash's DPA permits worldwide processing needed for the service. Its subprocessor register lists vendor addresses, including United States, Ireland and Denmark entries relevant to infrastructure, logging or communications; these addresses are not proof of server or staff-access locations. Singapore and United Kingdom entries for other products such as Context7 do not establish AE's Redis processing chain. Upstash does not supply a closed Redis support/processing country list in the cited materials. See Redis regions, DPA section 3 and the provider register.

Resend

Resend describes United States storage for customer data, including message content, delivery logs, webhook payloads and account records. Its current register labels every listed provider USA, including the support platform. Sending regions are separately selectable in the United States, Ireland, Brazil or Japan; those options do not mean AE uses each region. Message delivery also reaches recipients' systems. The register does not separately enumerate all employee remote-access countries. See data locations, sending regions and the November 5, 2026 provider register.

Firebase and Apple notification delivery

Firebase Cloud Messaging is a global service: data may be stored or processed where Google or its agents maintain facilities. It has no closed FCM-specific country list or U.S.-only location commitment in the cited materials. Google identifies Firebase Inc. in the United States for service maintenance and technical support. The Firebase register identifies U.S.-headquartered support vendors, but headquarters does not establish their staff-access countries. Google's broader affiliate maintenance/support footprint includes Argentina, Australia, Austria, Belgium, Brazil, Canada, Chile, Czech Republic, Denmark, Finland, France, Germany, India, Indonesia, Ireland, Israel, Italy, Japan, Luxembourg, Malaysia, Mexico, Netherlands, New Zealand, Philippines, Poland, Portugal, Singapore, Slovakia, South Korea, Spain, Sweden, Switzerland, Taiwan, United Kingdom and United States. This is a provider-wide footprint, not a representation that every location processes AE's FCM data. See Firebase privacy, Firebase subprocessors and Google's register.

Apple-device delivery uses Apple Push Notification service, a platform transport outside core FCM. The reviewed materials do not establish an APNs-specific exhaustive country list or U.S.-only routing. Apple's general privacy policy describes worldwide transfers and generally U.S. storage; it is not an APNs-specific location guarantee. See FCM architecture and Apple privacy. AE's selected app and developer arrangements determine the applicable contractual chain.

Cloudflare Turnstile

Turnstile's Siteverify API has no regionalization guarantee in Cloudflare's localization documentation. Published affiliate support locations include Australia, Canada, France, Germany, India, Japan, Malaysia, Mexico, Netherlands, Portugal, Singapore, South Korea, Sweden, Switzerland, United Arab Emirates, United Kingdom and United States. Support vendors additionally use United States, EEA, Japan and Australia locations. These support disclosures do not constitute an exhaustive Turnstile network-processing country list; product-specific suppliers for unrelated Cloudflare services are not automatically part of the Turnstile chain. See localization compatibility and the Cloudflare service register.

OpenAI API

The published API infrastructure countries are Australia, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, India, Indonesia, Ireland, Italy, Japan, Malaysia, Mexico, Netherlands, New Zealand, Norway, Poland, Singapore, South Africa, South Korea, Spain, Sweden, Switzerland, United Arab Emirates, United Kingdom and United States.

Published customer-support processing countries are Australia, Brazil, Canada, France, Germany, India, Indonesia, Ireland, Italy, Japan, Netherlands, Philippines, Singapore, South Africa, South Korea, Sweden, Switzerland, United Arab Emirates, United Kingdom and United States. Affiliate operational support includes United States, Ireland, United Kingdom and Japan. Support processing depends on the information supplied in a support case; some support services are elective. Moderation and other operational processing have their own listed purposes. Cloudflare routing uses nearby facilities, with regional controls for eligible requests. See the October 14, 2026 register.

Configured regional API storage and inference controls apply only to eligible features and data. They do not establish that all support or system data stays in that region. See API residency.

Anthropic API

Anthropic describes United States commercial-data storage and default inference routing across the United States, Europe, Asia and Australia. Supported requests can be configured for U.S. inference. Its infrastructure providers and some routing/security services are described as worldwide. Published support vendors include United States, South Africa and Canada locations. Affiliate customer-data-access countries are United States, United Kingdom, Canada, Ireland, Switzerland, France, Japan, Germany, South Korea and Australia. Support, safety review and incident response remain distinct from an inference-region selection. See commercial locations, API residency, the provider register and affiliate disclosure.

ElevenLabs

ElevenLabs describes standard U.S. storage; its infrastructure register permits non-Enterprise processing in the United States, EU or Singapore. Enterprise processing follows the applicable selected hosting arrangement; India is listed for the conditional India-residency route. Published support tools are in the United States and United Kingdom, and moderation tools include United States and EU locations. Affiliates are described as global, with named locations in United Kingdom, Poland, Japan, United Arab Emirates, India, Ireland, Netherlands, Singapore and Switzerland.

Other service-dependent entries include worldwide LLM processing and Indonesia, Malaysia, EU, Singapore or United States synthetic-media processing. Those entries do not authorize unselected media features or voice calls in AEOS. The actual non-call feature and provider route govern applicability. A storage-region selection does not exclude international support or moderation. See the provider register, residency documentation and DPA section 13.

The U.S. customer offering does not restrict the nationality of people represented in customer data. This schedule does not override a narrower location restriction expressly agreed with Customer. Provider links are evidence for this dated disclosure, not a mechanism to amend an accepted Agreement automatically. Changes remain governed by DPA sections 7 and 10 and section 6 below. Questions may be sent to privacy@aeindustries.ai.

5 Independent services and customer-selected connections

Apple's push service is an underlying participant in Firebase's iOS delivery path. Its presence does not by itself mean AE has separately appointed Apple as a direct subprocessor. Independently selected email/calendar, accounting/bank-data, AI/MCP and other connections can receive information when a customer authorizes them. Their role depends on the applicable contracts and data flow. AE's own handling remains subject to the DPA.

HubSpot on getaeos.io, AE's own CRM and any enabled Meta or Google marketing technologies support AE's own website, inquiry and advertising purposes as described in the Privacy and Cookie notices. Those purposes do not authorize disclosure of customer-controlled ERP records to advertising providers. AE subscription-payment processing is distinct from customer ERP finance records. The Privacy Notice explains information AE handles for its own account, billing and relationship purposes. Nothing on this page permits AE or AE-engaged providers to sell customer ERP data, use it for their own advertising or train general-purpose AI models on it.

6 Changes and objections

For a planned addition or replacement of a subprocessor, AE gives customers at least 30 days' advance written notice. Customers may object on reasonable privacy or security grounds within 15 days after receiving notice. If a reasonable objection cannot be resolved, the customer may terminate the affected services, owe no future fees for those services and receive a prorated refund of unused prepaid fees, as provided in DPA section 7.

A genuine security or service-continuity emergency can require shorter notice. AE will promptly explain the change, and the same objection and remedy rights remain available. Posting an updated list does not replace direct notices required by the DPA. Notices use the customer's designated privacy/incident contact in its subscription record. Keep that contact current and send questions or objections to privacy@aeindustries.ai, attention Privacy Officer.

Back to top ↑All legal documents →
AE INDUSTRIESAI FOR INDUSTRIAL AUTOMATION

Applied research.
Industrial automation.

Build with us ↗
© 2026 AE Industries Inc.
AboutMissionCareers
RESEARCH / ENGINEERING / INDUSTRIAL AUTOMATION
LEGAL & PRIVACY
LegalPrivacyTermsDPACookiesSubprocessors