Perfect Wiki uses the following third-party service providers ("sub-processors") to deliver the Perfect Wiki service. Each is bound by a contract requiring confidentiality and appropriate security measures, including a GDPR-compliant Data Processing Agreement where applicable.
Infrastructure
| Sub-processor | Purpose | Data category | Location |
|---|
| Google Cloud Platform (Google LLC) | Primary hosting — Firestore database, Cloud Storage, Pub/Sub, Compute | All customer data | US, Ireland, Germany (region selected closest to customer; Enterprise can pin) |
| Cloudflare, Inc. | CDN, DDoS protection, TLS termination at the edge | Request metadata in transit | Global |
AI & search
| Sub-processor | Purpose | Data category | Location |
|---|
| OpenAI, L.L.C. | LLM and embedding generation for AI search and Q&A | Wiki content and queries sent to the AI assistant; API data is not used to train OpenAI models | US |
| Algolia, Inc. | Full-text search indexing of wiki content | Wiki titles and indexed content | US / EU |
| Qdrant Solutions GmbH | Vector database for semantic search | Vector embeddings derived from wiki content | EU |
Communications
| Sub-processor | Purpose | Data category | Location |
|---|
| ActiveCampaign / Postmark (Wildbit, LLC) | Transactional email (sign-in codes, notifications) | Recipient email, message contents | US |
| SendPulse Inc. | Email delivery | Recipient email, message contents | EU/US |
Operations
| Sub-processor | Purpose | Data category | Location |
|---|
| Functional Software, Inc. (Sentry) | Error monitoring, application performance monitoring | Stack traces, request metadata, minimized PII | US |
| PostHog Inc. | Product analytics | Pseudonymous usage events | US / EU |
| GitHub, Inc. | Source code hosting, dependency scanning | Source code; no customer data | US |
Integrations (used only when the customer enables the integration)
| Sub-processor | Purpose | Data category | Location |
|---|
| Microsoft Corporation | Microsoft Teams app, Microsoft Entra ID SSO, Microsoft Graph (for SharePoint sync, etc.) | User identity, tenant metadata, integration content | Per Microsoft Online Services |
| Slack Technologies, LLC | Slack app integration | User identity, workspace metadata, integration content | US |
| Google LLC (Workspace APIs) | Google Workspace SSO, Drive / Docs sync where enabled | User identity, integration content | US |
| Telegram Messenger Inc. | Telegram integration where enabled | Chat metadata | Global |
Billing
| Sub-processor | Purpose | Data category | Location |
|---|
| FastSpring, Inc. | Subscription billing and payment processing | Billing contact, payment-method metadata | US |
Notification of changes
Perfect Wiki will update this page whenever a sub-processor changes. Customers under a signed Data Processing Agreement are notified by email at least 30 days before a new sub-processor begins processing their personal data, providing the customer a reasonable opportunity to object before the change takes effect.
Questions about sub-processors: [email protected].
Last updated: 2026-05-21.