Data processing
Confirm the processing arrangement before sensitive use.
Teams completing privacy, security or procurement review should agree a data processing addendum that matches the actual Knoy deployment and AI model route. A final standard addendum is not published on this site.
Project accessRole-based
Owner, editor and reviewer roles are represented in the application.
AI routesConfigurable
Gateway, OpenAI or Anthropic routes may be used depending on deployment.
Processing regionConfirm per route
The public codebase does not guarantee a single Australian model-processing region.
RetentionAgreement required
Customer schedules, backup handling and deletion timelines must be documented.
Information needed for review
- Customer organisation, project type and categories of project data.
- Required hosting region and restrictions on cross-border processing.
- Permitted AI providers, models and provider retention or training terms.
- Retention, deletion, incident notification and subprocessor requirements.
- Required security evidence, access roles and audit information.
Request the current procurement pack
Email support@knoy.app with your organisation, intended use, sensitivity constraints and review timeline. Knoy should not accept restricted data until the relevant arrangement is agreed.