Legal documents
Subprocessor List
Third parties supporting Cadvex Cloud, accounts, licensing and payments
Cadvex uses the following subprocessors and service providers. A provider processes only the data categories relevant to its function. Locations may include the provider’s configured region and other countries where the provider or its support subprocessors operate.
Current subprocessors and service providers
| Provider | Function | Data processed | Customer file content | Status / location |
|---|---|---|---|---|
| PostHog | Website and Cloud application analytics: cookieless page counting on the public website; with consent, heatmaps, session recordings, error diagnostics and signup conversion; server-side product-usage events | Cookieless page views (page address, referrer, campaign parameters, browser and device type, approximate country; the IP address is used only for a hash that changes daily); product-usage events from Cadvex servers linked to account and organization identifiers; consented browser identifiers; for signed-in users, account email, name, role and organization; page and screen interactions, form entries (excluding passwords, payment-card fields and one-time codes), Cloud screens as displayed, errors, coarse location and conversion events | Customer Content displayed on screen may appear in recordings; no uploaded files or 3D geometry; no Desktop app recording | EU Cloud via p.cadvex.com (browser) and eu.i.posthog.com (Cadvex servers); identifiers and recordings only with consent |
| Supabase | Database, authentication and private Cloud object storage | Accounts, organizations, legal consents, Cloud Customer Content, analyses, quotes, usage, Desktop licensing metadata and logs | Cloud files: yes; Desktop local manufacturing files: no | Active; production project configured separately |
| Render | Backend application hosting, Cloud CAD processing and production licensing API | Requests, account identifiers, Cloud uploaded files in transit/memory/temp storage, analysis results, logs and Desktop licensing requests | Cloud files: yes; Desktop local manufacturing files: no | Active; production backend |
| Cloudflare | Frontend hosting, reverse proxy, network security and content delivery | IP address, request metadata, authentication headers in transit and upload/download bodies routed through the service | Cloud content may transit; Desktop manufacturing files do not use Cloud upload path | Active; global edge network |
| Anthropic | Optional Cadvex Cloud AI-assisted drawing extraction | Complete selected drawing, prompt/context and structured extraction output | Drawings only; no STEP/STL geometry | Active for optional Cloud feature; no ZDR claim |
| Resend | Transactional email delivery and backend invitation email | Recipient email, confirmation/OTP/invitation/notification content | No manufacturing files | Active |
| hCaptcha | Signup anti-abuse/CAPTCHA when enabled | IP/network/browser/device and challenge-verification data | No manufacturing files | Planned/enabled for public independent signup only through Cadvex-controlled verification |
| Paddle | Cloud usage billing and Desktop subscription/perpetual checkout, tax, invoicing, refunds and fraud prevention | Billing identity, address, tax data, payment method metadata, invoices, subscription/license/payment events | No manufacturing files | Payment provider for paid Cloud/Desktop |
| Google Workspace | Business, support, privacy and legal email | Email addresses, correspondence and attachments voluntarily emailed to Cadvex | Only if voluntarily emailed | Active |
| Cloudflare Stream | Public demonstration video delivery, if used | Viewer network and engagement metadata | No manufacturing files | Used only where public demo video is enabled |
1. Desktop local-processing limitation
Cadvex Desktop manufacturing files, drawings, RFQs, analyses, quotes and local backups stay on the Customer-controlled device and are never sent to Cadvex or to any provider listed above, so no subprocessor processes them. The providers above may process account/licensing metadata or information the Customer chooses to send to support.
2. Changes to subprocessors
Cadvex may update this list when providers are added, replaced or materially changed. Where required by an applicable DPA or law, Cadvex will provide notice of a new subprocessor and an opportunity to raise a reasonable data-protection objection.