Subprocessors
Draft — last updated for Phase 3C.
Template — not legal advice. This page is a starting-point draft, not a document a lawyer has reviewed or approved for this business. It must be reviewed by qualified counsel before this product is offered commercially, and nothing on this page should be taken as a claim of legal or regulatory compliance.
The Service is built with a provider-independent design (see Security & privacy) — some rows below describe the KIND of subprocessor a given deployment would use rather than one fixed vendor, since the concrete choice (which storage bucket, which SMTP provider) is a deployment-time configuration decision, not hardcoded into the product.
| Subprocessor | Purpose | Location |
|---|---|---|
| Stripe | Payment processing and billing | United States |
| OpenAI | AI-generated documentation content (when AI_DRIVER is configured for it) | United States |
| Your configured cloud/object storage provider (e.g. Oracle Cloud Object Storage, AWS S3, MinIO) | Storage of screenshots, exports, and data-export archives | Depends on the region you configure |
| Your configured SMTP provider | Delivery of transactional email (verification, password reset, invitations, billing notices) | Depends on the provider you configure |
[Placeholder — before commercial launch, replace the generic storage/SMTP rows with the actual vendor(s) selected for production, and establish a process for notifying customers before adding a new subprocessor.]
Contact
Questions: support@processkit.local