OpenPlanr
  • Workflow
  • Protocol
  • Features
  • Agents
  • GitHub
  • npm i -g openplanr

Trust

Subprocessors

Last reviewed September 25, 2026

This page identifies the service providers OpenPlanr uses to operate the hosted product and describes the role and information involved in each relationship.

  1. What this list covers
  2. Current subprocessors
  3. User-selected sign-in providers
  4. International processing
  5. Changes to this list

What this list covers

OpenPlanr uses the providers below to process information on our behalf when operating the Hosted Services. They receive only the information needed for the described service and are governed by our agreements with them and their applicable privacy and security terms.

This list does not cover services that a customer independently connects to local OpenPlanr tools. Those services are selected and controlled by the customer.

Current subprocessors

  • Clerk

    Authentication and identity

    Account and profile details, authentication identifiers, verified email addresses, session and device information, multi-factor configuration, organization membership and invitation metadata, and identity security events.

    Clerk privacy information
  • Resend

    Transactional product email

    Sender and recipient addresses, the invitation or account-notice content required for delivery, and bounded delivery status and message identifiers.

    Resend privacy information
  • Vercel

    Web application hosting and delivery

    Web requests, IP and device metadata, session-related request data, performance measurements, and information needed to render the requested public or authenticated page.

    Vercel privacy information
  • Cloudflare

    Edge, application, database, and object-storage services

    Request and security metadata and hosted organization, project, artifact, review, sharing, audit, and operational data required to provide the company and sharing services.

    Cloudflare privacy information

User-selected sign-in providers

A user can choose Google or Microsoft to authenticate. Those providers process the sign-in request and account data under their own terms and privacy policies. OpenPlanr receives the verified identity information made available through Clerk; it does not receive the user's Google or Microsoft password.

International processing

These providers may process information in more than one country. Where applicable law requires a transfer mechanism or other safeguard, we rely on the contractual and legal mechanisms available for that provider and processing relationship. Provider documentation linked above contains current details about its own locations and subprocessors.

Changes to this list

We update this page when a provider is added, removed, or changes its material purpose. Questions about a provider or its role can be sent to support@openplanr.dev. See the Privacy Policy for more information about how we handle personal information. Security concerns should be sent to security@openplanr.dev.

OpenPlanr · GitHub · npm · openplanr.dev · MIT License · Privacy · Terms · Security · Subprocessors