Security and Data Handling
This page describes where Monjiro stores documentation and other data, and how it is protected. Use it for your security review before adopting Monjiro. It describes current operations and does not guarantee any specific level of service. It may change as operations improve.
Overview
| Item | Details |
|---|---|
| Cloud platform | Amazon Web Services (AWS) |
| Data storage location | Tokyo region (except for some logs) |
| Encryption in transit | TLS 1.2 or later between the browser and Monjiro |
| Encryption at rest | The database and files are encrypted |
| BYOK API keys | Stored encrypted in AWS Secrets Manager |
| Database backups | Taken automatically every day and kept for 7 days |
| Data after deleting an organization | Erased 30 days after the organization is deleted |
| Log retention | 30 days |
Data storage location
Documentation, images and other files, the history of AI chat questions and answers, and account information are stored in the AWS Tokyo region.
The following information is sent or stored outside Japan.
- Information used for AI answers: To generate an AI answer, the question and the related documentation content are sent to an AI service. With Monjiro's AI, they are sent to OpenAI (United States). For details, see the Privacy Policy.
- Logs for protection against unauthorized access: Logs from the WAF (a system that blocks malicious traffic) are stored in an AWS region in the United States for 30 days.
- Delivery: Public sites are delivered through a CDN (Amazon CloudFront), so traffic may pass through locations outside Japan that are close to the viewer.
Encryption of communications and data
Communication between the browser and Monjiro is encrypted with TLS 1.2 or later. HTTP requests are redirected to HTTPS.
The database and files are stored encrypted using AWS features.
Separation of data between organizations
Row-level access control is implemented in the database to prevent data from being read or written across organizations.
The database is placed in a network that cannot be reached directly from the internet.
Sign-in and passwords
Sign-in is authenticated with Amazon Cognito. Passwords are managed by Amazon Cognito and are not stored in Monjiro's database. For how to sign in, see Sign-in and passwords.
Permissions of organization members are divided by role, such as Owner and Admin. For details, see Organizations and members.
You can also limit who can view a public site by IP address or email address (Team plan and above). For details, see Restrict access.
Protection against unauthorized access
A WAF is in place to help prevent malicious traffic.
Storage of BYOK API keys
The API key itself registered for BYOK is stored encrypted in AWS Secrets Manager, not in Monjiro's database. The database stores only the first 10 characters of the key, for display on screen, and the name of the storage location. For this reason, the API key itself is not included in database backups.
- When registered: The key is saved after confirming that it can be used with the AI service.
- When used: The key is read only when generating an AI chat answer. The key that was read may be kept in server memory for a short time.
- Display: After it is saved, the full key is not shown on screen (only the first few characters are shown).
- When changed or deleted: When you register a different key or press "Delete", Monjiro runs a process to erase the previous key from AWS Secrets Manager.
- When an organization is deleted: The key is erased immediately, without waiting for the 30-day retention period.
For details, see BYOK (using your own API key).
Payment information
Payments are processed through the payment service Stripe. Card information is not stored by Monjiro.
AI chat and data
According to OpenAI's published policy, information sent to Monjiro's AI (the OpenAI API) is not used to train AI models.
Organizations using BYOK send information to the AI service chosen by the user (Anthropic, OpenAI or Google) with the user's API key. In this case, the handling of the information is governed by the terms between the AI service provider and the user.
The operator of the documentation can review the questions readers asked the AI chat and the answers in the history.
Backups
Database backups are taken automatically every day and kept for 7 days. Backups are used to recover from outages and for no other purpose.
Backups are an operational measure. Keep your own copies of your documentation as needed (see the Terms of Service).
Erasing data after an organization is deleted
Data is handled as follows after an organization is deleted.
| Data | Handling |
|---|---|
| Documentation, files, and question and answer history | Kept in an inaccessible state for 30 days after the organization is deleted, then erased |
| BYOK API keys | Erased immediately when the organization is deleted |
| Previous versions of erased files | Erased within 7 days of erasure |
| Database backups | Erased information may remain in backups for 7 days |
| Access logs and error logs | Kept for 30 days, then erased |
| Contract and billing records | Kept by the payment provider (Stripe) and by us for the period required by law |
Deleting an organization does not delete users' accounts.
Uptime and outage notices
For the uptime target and service credits, see the Service Level Agreement (SLA). Information on outages and maintenance is posted on the status page.
Contact
For security questions not covered on this page, contact support@kairotech.jp.