ConnLog uses service providers only where needed to provide, secure, bill, support, and maintain the platform. ConnLog will update this list when providers materially change. Provider names, locations, and safeguards should match the production deployment and signed provider terms.
| Provider | Purpose | Data categories | Location | Safeguards | Status |
|---|---|---|---|---|---|
| Self-managed VPS hosting | Hosting and infrastructure | Account, workspace, monitor, agent, alert, log, and backup data | Operator-managed servers; specific provider and region available on request | Provider DPA and transfer safeguards where the provider is outside the EEA | Required for the service |
| Transactional email provider (SMTP) | Account, verification, alert, and notification email delivery | Recipient email addresses, subjects, message IDs, delivery status, alert content | Operator-configured provider; region available on request | Provider DPA and transfer safeguards where required | Required when email is enabled |
| Stripe | Payment processing | Billing contact, payment status, customer/subscription IDs, tax/VAT data, checkout metadata | Stripe processing locations | Stripe DPA and transfer safeguards | Used only when paid checkout is enabled |
| Google OAuth sign-in | OAuth ID, email, name, avatar, tokens where stored | Google processing locations | Provider terms and transfer safeguards | Used only when Google login is enabled | |
| GitHub | GitHub OAuth sign-in | OAuth ID, email, name, avatar, tokens where stored | GitHub processing locations | Provider terms and transfer safeguards | Used only when GitHub login is enabled |
ConnLog does not currently use third-party analytics, external error-tracking/observability, or external support-ticket tooling. If any such provider is enabled in the future, it will be added to the table above before it begins processing personal data.
Questions about subprocessors can be sent to [email protected].