Effective date: November 6, 2026 · Version: 2026-11-06.1
This disclosure forms part of the Data Processing Addendum for Hillclimb, operated by Desiderata LLC. Providers receive only information needed for their assigned functions. This list names our direct providers and identifies the distinct identity-provider roles of Google and GitHub. Our providers use their own subprocessors under their data-processing terms, linked below; ask us for the current list. A provider's independent account or security processing may have a different legal role, as described in the Privacy Policy.
Hillclimb uses no analytics, advertising, error-tracking, payment, or AI model providers.
Service providers
| Provider | Function | Location |
|---|---|---|
| Vercel Inc. | Application hosting, functions, scheduled jobs, approximate visitor location | United States; distributed infrastructure |
| Databricks, Inc. (Neon) | Hosted Postgres database | United States (AWS us-east-2); no region promised |
| Cloudflare, Inc. | Object storage (R2) for evidence files | Provider-determined; no region promised |
| Plus Five Five, Inc. (Resend) | Sign-in-code and invitation email | United States |
Vercel Inc. — application hosting
Vercel runs the Hillclimb website, console, REST API, and MCP server, and the scheduled job that delivers and retries outbound trigger events every minute. Every request passes through it, so data can include all account and Customer Personal Data handled by a request, file names and metadata (file contents move directly between your browser or agent and Cloudflare R2), and Vercel's own request logs (IP addresses, paths, and timestamps). When someone opens a share link, Vercel supplies the approximate city, region, and country derived from their IP address, which Hillclimb stores with the visit. Vercel is based in the United States and operates distributed hosting and support infrastructure. Hillclimb's functions run in Vercel's iad1 region (Washington, D.C.) by default; Vercel's edge network and support infrastructure operate elsewhere, and no exclusive region is represented here. See Vercel's data-processing terms.
Databricks, Inc. (Neon) — database
Neon hosts the Postgres database that holds Hillclimb's structured records: accounts, sessions, sign-in links and tokens, API-key hashes, organizations, members, teams, invitations, all tree content (goals, outcomes, evidence text, plans, comments, events), share links and visits, triggers and their secrets, usage counts, sign-in rate-limit counters, OAuth clients, consents and tokens, records of accepting our terms, and the names and emails kept for deleted accounts. Neon also keeps point-in-time restore history for the database. Neon, LLC is a subsidiary of Databricks, Inc., which is the contracting party for Neon's service under its Product Specific Schedule (Neon) and the Databricks data-processing terms it incorporates. The database region is chosen in the Neon project, not in Hillclimb's code; no exclusive region is promised here. The production database runs in AWS us-east-2 (Ohio, United States), and its application functions run in Vercel's iad1 region (Washington, D.C., United States). We may move them; we do not promise a region. See Neon's data-processing terms.
Cloudflare, Inc. — file storage
Cloudflare R2 stores files attached to evidence (images, video, text, JSON, PDFs, and archives up to 100 MB each) and serves them through signed links that expire after 10 minutes for upload and 5 minutes for download. Data includes file contents and names, and any personal information inside them, plus Cloudflare's technical delivery records. Cloudflare is based in the United States and operates distributed infrastructure. The storage bucket uses Cloudflare's automatic location and is not restricted to a jurisdiction; this listing is not a promise of US-only or regional storage. See Cloudflare's data-processing terms.
Plus Five Five, Inc. (Resend) — transactional email
Resend delivers sign-in codes and organization invitations. Data includes recipient email addresses, message content (the code, or the organization's name, the inviter, and the invitation link), delivery status, and technical delivery records. Tree content and files are not sent by email. Its primary processing is in the United States, with supporting providers as described in its arrangements. See Resend's data-processing terms and provider disclosures.
Google and GitHub — sign-in
Google LLC and GitHub, Inc. provide optional OAuth sign-in. Signing in exchanges basic identity information: name (or GitHub login), email address, profile image link, verification status, the provider's account identifier, and access, refresh, and ID tokens, which Hillclimb stores with the account. The scopes requested are openid, email, and profile for Google and read:user and user:email for GitHub. Sign-in does not grant access to Gmail, Drive, repositories, or other content, and Hillclimb sends no tree content or files to Google or GitHub. Each processes its own account and sign-in information under its own terms: Google Privacy Policy and GitHub General Privacy Statement. Both operate globally; no exclusive processing region is promised.
Google and GitHub are disclosed here for completeness as identity providers the person chooses. That role does not make them Subprocessors for Customer's content.
Other recipients and locations
Recipients chosen by Customer or its users are not Desiderata's Subprocessors merely because Hillclimb delivers data to them at their direction:
- AI agents and MCP clients that users connect act with that user's permissions and send what they read to their own providers.
- Outbound trigger destinations chosen by an organization's owners or admins receive signed event messages, including the acting person's identifier, name, and email address.
- Share-link recipients can read what a share link covers.
- OAuth client metadata hosts: when a client identifies itself with a metadata URL, Hillclimb's server fetches that URL from the client's host.
Their independent processing is described in the Privacy Policy and their own terms. If Desiderata appoints one to process Customer Personal Data on Customer's behalf, it must meet the DPA's requirements for that role. Fonts are self-hosted and involve no font provider.
Hillclimb is offered to businesses in the United States, and the providers above host and process its data in the United States; section 10 of the DPA explains where processing happens. A provider's headquarters does not establish every location its distributed infrastructure uses. Contact hello@hillclimb.me for actual deployment regions and relevant provider information. Each listed provider is engaged under its data-processing terms linked above.
Changes and objections
We will give notice at least 10 days before adding or replacing a Subprocessor by updating this page, whose version and date change with each update, as the DPA requires. To have notices emailed to your privacy contact, ask hello@hillclimb.me. Notice will identify the provider, its function, and relevant countries. Send reasonable data-protection objections to hello@hillclimb.me during that period. The DPA explains resolution, suspension, and termination rights. Earlier versions of this disclosure are available on request.