Appintellect — Sub-processors
DRAFT — NOT LEGALLY REVIEWED. Fill in
{{placeholders}}, have counsel review, then remove this banner.
Last updated: 2026-04-23
This page lists every third-party data processor Appintellect engages to help deliver the Service. Each is bound by a written data processing agreement with terms at least as strict as the commitments in our own DPA.
If we add or replace a sub-processor, we update this page and email every active pilot contact at least 30 days in advance. See the DPA §10 for the objection process.
Current sub-processors
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Google Cloud Platform (Google LLC) | Compute, Postgres, blob storage, networking | All customer crawl data (screens, logs, anomalies, settings) and account metadata | us-east1 (South Carolina, USA) |
| Google Gemini API (Google LLC) | AI inference — screen understanding, navigation decisions, diff classification | Screenshots + accessibility trees from the active crawl, sent per-call through the Customer's own Gemini API key | US regional endpoint (as selected by Google) |
| {{email_provider}} | Transactional email — onboarding, security notices, breach notifications, sub-processor change notices | Contact name + email + message content | {{email_provider_region}} |
| {{observability_provider}} | Application performance monitoring, error aggregation | Service logs, traces, error stack traces. Customer crawl contents (screenshots, app logs) are not shipped here — only our own service telemetry. | {{observability_region}} |
Historical changes
| Date | Change | Notice sent |
|---|---|---|
| 2026-04-23 | Initial publication | N/A — pilot launch |
Why the list is short
During the pilot we deliberately run on a minimal sub-processor set:
- No third-party analytics in the dashboard. We do our own first-party request logging and nothing else.
- No CDN for static assets yet — the dashboard is served directly from our GCP project. When this changes (likely Cloudflare or GCP Cloud CDN), it will appear here first.
- No customer support platform — pilot support runs through email to {{support_contact_email}}, not a SaaS helpdesk. A helpdesk (Zendesk, Intercom, or similar) is a likely Phase 2 addition and will be listed here with 30 days notice before it goes live.
Contact
Questions about a specific sub-processor or our vendor-diligence process: {{privacy_contact_email}}.