Privacy
Octoplexity is designed for private documentation workflows. Source material, contact data, and usage signals should be handled with clear purpose, limited access, and explicit retention controls.
Contact data
When someone requests access, Octoplexity collects the information submitted in the form so the team can evaluate fit, respond to the request, and communicate about the product.
Documentation sources
Customer documentation should be stored privately, scoped to the owning organization, and processed only to provide the compiled context service.
Model training
Customer documentation is not used to train foundation models. Any model-assisted extraction or summarization should preserve provenance back to source spans.
Usage signals
Product usage, retrieval events, feedback, and error signals may be used to operate the service, improve context quality, detect abuse, and support customers.
Deletion and export
Organizations should be able to request deletion or export of their data, subject to security, legal, billing, and operational requirements.
Processors
Octoplexity may rely on infrastructure and service providers for hosting, storage, analytics, email, billing, and application operations. Those providers should be limited to the data needed for their role.