Security
Security white paper
This translation is provided for reference only. In the event of any discrepancy, the Japanese version shall prevail.
1. Introduction
This document describes WriteVideo's approach to security.
Service overview
WriteVideo is an AI-powered SaaS platform for video generation. It provides functions such as automatic video generation from PowerPoint and PDF, and AI narration generation.
2. Location and jurisdiction
WriteVideo is provided by X, Inc. (Toranomon, Minato-ku, Tokyo). The Company is a Japanese corporation, and the overall management of the development and operation of the service and its main business processes are carried out in Japan.
The system runs in Amazon Web Services (AWS) data centers in Japan, and customer data is stored in Japan. We implement redundancy across multiple sites.
3. Encryption
All data in transit and data at rest is encrypted.
Encryption of communications
All communications are encrypted with TLS 1.2 or higher.
Encryption of data at rest
-
File servers: server-side encryption (SSE-S3 / SSE-KMS)
-
Databases: encryption with AWS managed keys
-
Backup data: all stored encrypted
4. Data management
Backup
-
Important data (project files): real-time backup
-
Other data: backup created every 24 hours
Data retention and deletion
For the Business Plan, we delete the data we hold at the request of the Subscriber.
Multi-tenant isolation
Each organization's data is logically isolated, and access control is implemented at both the application layer and the database layer.
5. Authentication and access control
We use Amazon Cognito as our authentication platform.
-
Enforcement of a password policy
-
Support for multi-factor authentication (MFA)
-
Permission management through role-based access control (RBAC)
-
Session timeout settings
6. Development practices
-
Mandatory code review
-
Vulnerability scanning of dependency libraries
-
Security testing before deployment to the production environment
-
Regular security checks
7. Monitoring and log management
-
Recording of API operation logs with AWS CloudTrail
-
Aggregation of application logs with CloudWatch Logs
-
Integrated monitoring and alerts with Datadog
-
Detection of and notification about unauthorized access attempts
8. Incident response
When a security incident occurs, we respond following a process of detection, containment, eradication, recovery and post-incident analysis.
| Level | Description | Target response time |
|---|---|---|
| Level 1 (Critical) | Serious impact on business continuity | Within 15 minutes |
| Level 2 (High) | Impact on critical systems or customer data | Within 1 hour |
| Level 3 (Medium) | Limited impact, internal systems only | Within 4 hours |
| Level 4 (Low) | Minor impact, isolated event | Within 48 hours |
For serious incidents, we will notify the Subscribers who may be affected by a reasonable method.
9. Business continuity
Availability
-
Service uptime: operated with a target of 99.9% (excluding maintenance)
-
Service hours: 24 hours a day, 365 days a year (excluding maintenance)
-
Redundancy across multiple Availability Zones
Threats anticipated
We have drawn up a business continuity plan (BCP) that anticipates system failures, network failures, cybersecurity incidents, data center failures, natural disasters, the spread of infectious diseases, etc.
10. Compliance
Laws and regulations complied with
-
Act on the Protection of Personal Information (Japan)
Company certification
-
PrivacyMark (certified by JIPDEC)
Infrastructure certifications (AWS)
AWS, which we use as our platform, holds the following certifications.
-
SOC 1/2/3
-
ISO 27001, 27017, 27018
-
ISMAP (Security assessment system for government information systems)
-
PCI DSS Level 1
11. Contact
For security inquiries and vulnerability reports, please contact us at the address below.
Email: info@xinc.co.jp
