Sub-Processors

Last updated: February 2026

SFDevTools uses the following third-party sub-processors to deliver our service. A sub-processor is any entity that processes customer data on our behalf.

Infrastructure Sub-Processors

Sub-Processor Function Location Optional
Netlify Application hosting and static site delivery for the web app (app.sfdevtools.com) and landing page (sfdevtools.com) USA No
Deno Deploy Serverless runtime hosting for the backend API (api.sfdevtools.com) USA No
Supabase Managed PostgreSQL database, user authentication, and file storage USA No
Upstash Serverless Redis cache for performance optimization (token caching, query result caching, metadata caching) USA Yes - platform operates without it
Resend Transactional email delivery for authentication magic links USA No

Data Processing Sub-Processors

Sub-Processor Function Location Optional
Salesforce Customer-initiated OAuth connections to Salesforce orgs. API calls are proxied through our backend on behalf of the user. USA N/A - user-initiated

What Data Is Processed

  • Netlify: Serves static assets and application bundles. No customer data is stored.
  • Deno Deploy: Processes API requests including Salesforce API proxying. Stateless - no data persisted at the edge.
  • Supabase: Stores user accounts, encrypted Salesforce OAuth tokens (AES-256-GCM), query history, session state, and dashboard preferences. All tables enforce Row Level Security.
  • Upstash Redis: Caches decrypted tokens (90 min TTL), SOQL query results (user-controlled TTL), and metadata describe results (1–12 hr TTL). All entries are ephemeral.
  • Resend: Receives your email address solely to deliver authentication magic link emails. No other data is shared.
  • Salesforce: Your Salesforce org data is accessed only through authenticated API calls you initiate. We do not store query results beyond optional caching.

Changes to This List

We will update this page when sub-processors are added or removed. For questions, contact us at support@sfdevtools.com.