Subprocessor Registry

Effective and last updated: August 5, 2026

FEY uses the processors and service providers below to help deliver the Services. We refer to them as subprocessors on this page. A provider receives only the personal data reasonably needed for the applicable service, and not every provider receives every category listed.

This registry distinguishes providers acting for FEY from services that you connect to, direct FEY to use, or that independently determine how they process information. Those independently controlled services are described separately below and are not FEY subprocessors for those activities.

Current processors and service providers

Amazon Web Services (AWS)

  • Service and purpose: Production cloud infrastructure, including application hosting, databases, object storage, encryption-key services, backups, security controls, and operational logs.
  • Personal data: Account and technical identifiers; wallet, portfolio, order, transaction, alert, subscription, chat, agent, and support data; IP addresses; device and request metadata; and operational logs.
  • Processing location and transfers: FEY's primary production region is AWS Asia Pacific (Tokyo), Japan. AWS support, security, resilience, and listed subprocessors may involve processing or access in other countries under AWS's published terms.
  • Provider information: AWS Privacy Notice and AWS Subprocessors.

Expo (650 Industries, Inc.)

  • Service and purpose: Hosting the public FEY website, distributing app updates and builds, and routing mobile push notifications.
  • Personal data: IP address and request metadata; device, app, build, update, and project identifiers; push tokens; and notification routing information and content.
  • Processing location and transfers: Primarily the United States. Expo's published subprocessor list identifies additional provider locations, and international processing may occur under Expo's published terms.
  • Provider information: Expo Privacy Policy and Expo Subprocessors.

Privy (Horkos, LLC d/b/a Privy)

  • Service and purpose: Authentication, account linking, embedded-wallet creation and management, wallet policies, and authorized signing requests.
  • Personal data: Account and authentication identifiers; email, phone, or linked-profile information when used to sign in; device and IP data; wallet addresses and identifiers; and signing, policy, and transaction-request metadata.
  • Processing location and transfers: The United States and other locations where Privy and its service providers operate. Privy's wallet infrastructure is globally distributed, and international processing may occur as described in its privacy information.
  • Provider information: Privy Privacy Policy and Privy Wallet Security Architecture.

RevenueCat, Inc.

  • Service and purpose: Mobile subscription purchase validation, entitlement management, webhook delivery, and subscription reconciliation.
  • Personal data: FEY user identifiers; app and device metadata; product and entitlement identifiers; purchase receipts or tokens; transaction, renewal, refund, and billing-status metadata.
  • Processing location and transfers: United States. RevenueCat states that customer data is stored on AWS in the United States and describes cross-border transfers in its published privacy and data-processing terms.
  • Provider information: RevenueCat Privacy Policy and RevenueCat Data Processing Addendum.

PostHog, Inc.

  • Service and purpose: Product analytics, performance and error measurement, website interaction analytics, and masked website session replay.
  • Personal data: Opaque analytics identifiers; device, browser, IP, and request metadata; app and website interaction events; page URLs; subscription tier and coarse feature-state information; performance and error data; and masked replay data. FEY does not intentionally send chat content, wallet addresses, order details, or raw portfolio values to PostHog.
  • Processing location and transfers: PostHog Cloud offers United States and European Union project regions. FEY routes data to its configured project region; PostHog support and listed subprocessors may process data in other locations under its published terms.
  • Provider information: PostHog Privacy Policy and PostHog Trust Center.

SigNoz

  • Service and purpose: Hosted observability for application and infrastructure logs, metrics, traces, exceptions, reliability monitoring, and incident investigation.
  • Personal data: Service, route, request, timing, and status metadata; IP addresses and technical identifiers when present in telemetry; error messages and stack traces; and infrastructure or account identifiers included in operational events.
  • Processing location and transfers: The cloud region assigned to FEY's SigNoz workspace. SigNoz offers multiple cloud regions; support and listed subprocessors may involve processing in other countries under its published terms.
  • Provider information: SigNoz Privacy Policy and SigNoz Cloud Regions.

twitterapi.io

  • Service and purpose: Verifying connected-X follow and repost eligibility, retrieving public X post data, and powering X-post alerts selected by users.
  • Personal data: X account identifiers and handles; follow and repost status; public post data; alert handles and filter criteria; and technical request metadata.
  • Processing location and transfers: AWS-hosted infrastructure. The provider's public privacy notice does not identify a specific AWS region; processing or access may occur where the provider and its infrastructure operate.
  • Provider information: twitterapi.io Privacy Policy.

User-directed and independently controlled services

The following services are not listed as FEY subprocessors for the activities described here. When you connect an account, approve an action, or use one of these services through FEY, the provider or public network may receive information directly from you or from FEY at your direction and may process it under its own terms and privacy notice.

  • OpenAI and ChatGPT: Your connected ChatGPT account is used for agent conversations and related user-requested processing. OpenAI Privacy Policy.
  • Lighter: The current trading venue for user-approved orders, positions, and related wallet activity. Lighter Terms.
  • Coinbase: A user-selected provider for funding or withdrawing to a wallet. Coinbase Privacy Policy.
  • Relay: A user-selected cross-chain transfer and bridge service. Relay Terms and Privacy Information.
  • X: A social network account that a user may connect for eligibility checks and alerts. X Privacy Policy.
  • Apple and the App Store: App distribution, App Store subscriptions and payments, and device notification delivery. Apple's role can vary by service and applicable law. Apple Privacy Policy.
  • Public blockchains, including Ethereum and Base: Wallet addresses, transaction details, and other onchain activity submitted to a public network are public and may remain available independently of FEY. No single network participant acts as FEY's subprocessor for public ledger activity.

Changes and questions

We may update this registry as the providers supporting FEY change. If a change is material, we will update this page and the effective date and provide any additional notice required by applicable law or our contractual commitments.

For questions about this registry, or to ask about notices of material changes, email contact@fey.trade.