SECURITY AND PROCUREMENT
This page lists materials to review before adopting NinjaFlow and their current availability. It does not guarantee contract terms, retention periods, an SLA, an audit conclusion, or an individual environment.
The following points describe the current configuration and data-handling controls available for adoption review.
An owner can configure the email domains allowed for a company account. Domains are checked both when an invitation is sent and when a person joins, and email addresses that do not meet the setting are not accepted. Changes can be reviewed before they are saved.
A setting can enable information to be shown separately by project. Owners and administrators can view all projects for necessary administration. When support staff review all projects, the operation is recorded.
Encryption is used for communications and for storage managed by the underlying platform. Additional encryption with keys managed by us is limited to recovery archives.
Complete deletion by tenant cannot currently be performed from this service. Retention and deletion conditions are explained before adoption after reviewing the intended environment and contractual requirements.
Only published materials can be opened from this page. Items in preparation or not offered are not presented as published documents.
A contract attachment for reviewing data-processing terms for an individual engagement. It is not a standard published document and is available only when an individual contract is agreed.
In preparation
This is not a promise of standard availability.
Material for reviewing retention periods, deletion, and how deletion scope is confirmed. A formal public document is in preparation.
In preparation
This catalogue does not guarantee a retention period.
Material for reviewing how data-processing subprocessors are identified, including managed AI inference provider changes. No published list is currently available.
In preparation
Anthropic and OpenAI AI-inference entries remain under legal review. This does not represent a published subprocessor list.
Material for individually reviewing service levels and support scope. NinjaFlow does not present an SLA as a standard offering.
Not offered
A standard SLA is not offered.
Material that distinguishes generation history, customer-facing operation records, and NinjaFlow internal developer records. A formal public document is in preparation.
In preparation
This does not promise audit trails or audit reports.
Material for reviewing the project-level separation setting and the boundary between the NinjaFlow managed service and customer-managed or individual environments. A formal public document is in preparation.
In preparation
This does not promise individual environments or data separation as standard features.
NinjaFlow is operated by the Japanese entity identified below.
Company websiteFor service operations, developers may review limited administrative records. This is NinjaFlow internal operation, not a customer-facing feature, report, or audit report.
The scope, export method, and retention conditions for records visible to customers are organized after reviewing the intended environment and contractual requirements. They are not promised as a standard feature.
The standard NinjaFlow managed service is not the same offering as customer-managed AI, customer-managed storage, or a dedicated or individual environment. Individual operation requires requirements definition and individual quotation after reviewing connectivity, responsibility boundaries, operating, and audit requirements.
Each service communicates with the database and storage (Supabase) over HTTPS (encrypted in transit).
For adoption and pre-contract questions, review the official consultation intake, including its purpose, retention approach, and notification scope.
Review official consultation intakeThe individual data-handling consultation channel is in preparation. This page does not accept requests until a channel is configured.