Legal
Subprocessors
Only vendors explicitly declared for this deployment appear below. Source-code support for a vendor is not treated as proof that the vendor is active.
- Operator
- RenderBoard operator (preview configuration)
- Effective date
- Not configured for this preview build
AI and extraction
May receive prompts, floor plans, masks, room or project context, and generated-output metadata when the corresponding AI or extraction feature is used.
Not declared for this preview build. Public release is blocked until the operator supplies a vendor list or explicitly declares none.
Object storage and delivery
May store or deliver uploaded plans, assets, generated renders, board exports, thumbnails, and related object metadata.
Not declared for this preview build. Public release is blocked until the operator supplies a vendor list or explicitly declares none.
Payments
May host checkout and billing-management pages and return customer, subscription, invoice, and transaction references to RenderBoard.
Not declared for this preview build. Public release is blocked until the operator supplies a vendor list or explicitly declares none.
Observability and incident response
May receive service errors, request metadata, performance traces, and operational logs when observability export is enabled.
Not declared for this preview build. Public release is blocked until the operator supplies a vendor list or explicitly declares none.
Due diligence and updates
Before release, the operator must reconcile these declarations with actual deployment configuration, confirm legal names and processing regions, execute required data-processing agreements, and document transfer safeguards where applicable. This page does not itself prove that those contracts exist.
Questions or objections about a processor can be sent to privacy@example.invalid. Material changes should be published with an updated effective date before the new provider handles customer data where required.