Privacy-by-default controls intended for a B2B SaaS product.

Privacy by design in the product

The live runtime uses explicit organisation context, customer-partitioned uploads and exports, product-owned auth, verified-email sign-in, and audit/security logging intended to reduce accidental cross-customer exposure and support investigation when needed.

• Optional public analytics stays off until configured and consented to.
• Public contact requests are stored in the database rather than flat files.
• Secret-bearing auth email content is not written to operator logs in production mode.

Controller and processor model

For customer-uploaded operational data, the customer will generally act as controller and the provider will generally act as processor or service provider under the contract. For provider-run account, security, and public-enquiry data, the provider acts as controller for that processing.

• The exact role split is governed by the signed commercial agreement and any DPA.
• Customer-specific privacy questions can be routed through the contact path before rollout.

Rights handling

Individuals may request access, rectification, erasure, restriction, objection, or portability where applicable. Identity must be verified before disclosing or changing personal data.

• Requests can be submitted through the contact route using the data-rights topic.
• Customer users should also notify their Admin Review user where organisation-held workflow data is involved.

Processors, subprocessors, and transfers

Hosting and service operations may involve infrastructure or support providers. Where personal data is transferred internationally, an appropriate transfer mechanism should be used where required by applicable law and the governing agreement.