Snapshot 136304
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
Introducing News: 200M articles indexed live Back to DPA Data sub-processors Last updated Oct 11, 2026 This page lists the sub-processors that Context.dev uses to provide its Services. These sub-processors process personal data on behalf of Context.dev in accordance with our Data Processing Addendum (DPA). Context.dev maintains contracts with all sub-processors that include appropriate data protection obligations. We will update this page when we add or remove sub-processors. If you have questions about our sub-processors, please contact us at privacy@context.dev. Sub-Processor List Google Cloud Platform https://firebase.google.com Service: Authentication, Database, Storage Location: United States Purpose: User authentication, account data storage, organization data storage, usage history tracking, and file storage for organization avatars and temporary logo uploads. Data Types Processed: User account information (email, name, UID) Organization data (name, member lists, subscription information) API usage history Uploaded files (organization avatars, temporary logo files) Stripe, Inc. https://stripe.com Service: Payment Processing and Billing Location: United States Purpose: Processing subscription payments, managing billing information, handling tax ID collection, and managing customer payment methods. Data Types Processed: Payment card information (processed by Stripe, not stored by Context.dev) Billing addresses Tax identification numbers Subscription and invoice data Customer email addresses PostHog, Inc. https://posthog.com Service: Product Analytics and User Identification Location: United States Purpose: Product analytics, user behavior tracking, feature usage analysis, error tracking, and user identification for product improvement. Data Types Processed: User identification data (user ID, email) Event data (feature usage, errors, interactions) Device and browser information IP addresses (anonymized where possible) Databuddy Analytics, Inc. https://www.databuddy.cc/data-policy Service: Website Analytics Location: Processing locations vary by hosting provider; see Databuddy’s data policy Purpose: Website analytics, page views, outbound link clicks, conversion events, and web performance measurement. Data Types Processed: Page view and referrer data Visitor and session identifiers Device and browser information Conversion event properties Web performance measurements Approximate location derived from IP addresses Google https://marketingplatform.google.com Service: Google Ads and Google Tag Manager Location: United States Purpose: Marketing analytics and conversion tracking for advertising campaigns. Data Types Processed: Page view data Conversion events Device and browser information IP addresses RB2B https://www.rb2b.com Service: Website Visitor Identification Location: United States Purpose: Identifying business visitors to our marketing pages so our team can follow up on inbound interest. Only loaded for visitors who have granted marketing consent. Data Types Processed: Visitor name and job title Work email address LinkedIn profile URL Company information Page view data Device and browser information IP addresses Chatwoot https://www.chatwoot.com Service: Customer Support Chat Location: United States Purpose: Providing customer support chat functionality within the product dashboard. Data Types Processed: Chat messages User identification (if provided during chat) Device and browser information IP addresses Resend, Inc. https://resend.com Service: Transactional and Marketing Email Delivery Location: United States Purpose: Sending transactional and marketing emails, including account notifications, billing emails, security alerts, and product updates. Data Types Processed: Recipient email addresses Sender email addresses Email content (subject line and body) Sub-Processor Changes In accordance with Section 5.2 of our DPA, Context.dev will notify customers of any intended changes to our sub-processors at least fourteen (14) days in advance, giving customers sufficient time to object to such changes. To receive notifications about sub-processor changes, please contact us at privacy@context.dev. Additional Information For more information about how Context.dev processes personal data, please review our Data Processing Addendum and our Privacy Policy.