Privacy Policy
Last Updated: January 1, 2026
Jiroshi (“we”, “our”, “us”) provides a headless learning management platform that enables instructors and developers to build and manage course platforms using APIs.
This Privacy Policy explains how we collect, use, store, and protect personal information when you use our platform, APIs, dashboards, and services. By using Jiroshi, you agree to this Privacy Policy.
1. Information We Collect
We collect only the information required to operate the platform.
1.1 Instructor Information
When an instructor creates an account, we may collect:
- Name or display name
- Email address
- Account credentials
- Generated API keys
- Basic account and usage metadata
1.2 Student Information
Student data is collected on behalf of instructors (tenants) and may include:
- Identifier (email, phone number, or custom identifier chosen by the instructor)
- Authentication credentials (securely hashed)
- Enrollment and access data
Jiroshi does not determine the identifier format or student data schema - this is controlled by the instructor.
1.3 Technical & Usage Information
We may automatically collect:
- IP address
- Request metadata (timestamps, endpoints, response codes)
- Logs required for debugging, rate limiting, and security monitoring
2. How We Use Information
We use information strictly to:
- Authenticate users and API requests
- Provide platform features and access control
- Maintain security and prevent abuse
- Monitor system performance and reliability
- Communicate service-related updates
We do not use personal data for advertising, profiling, or resale.
3. Content Delivery & Media Access
At the current stage of the platform, course media (including videos and static assets) may be served using static URLs or similar delivery mechanisms.
While we take reasonable measures to restrict unauthorized access, we cannot guarantee complete prevention of content copying, redistribution, or misuse. Instructors are responsible for deciding what content they upload and how it is distributed.
4. Payments
At this time, Jiroshi does not process, store, or handle payment information. Payments, if any, are handled externally by instructors using third-party tools.
This policy will be updated when native payment functionality is introduced.
5. Data Ownership & Role
Instructors own and control the student data they collect. Jiroshi acts as a data processor, providing infrastructure and APIs. Instructors are responsible for compliance with applicable laws regarding student data.
6. API Key Security
API keys are used to authenticate and authorize access to Jiroshi APIs. We implement reasonable safeguards such as secure storage, access controls, and rate limiting.
Responsibility: Instructors are responsible for securely storing their API keys. Secret keys must never be exposed in client-side or public environments.
7. Data Storage & Security
We use reasonable technical and organizational measures to protect data, including secure password hashing, token-based authentication, and encrypted communication (HTTPS).
No system is completely secure, and users acknowledge inherent risks when using internet-based services.
8. Data Retention
Data is retained while accounts remain active. Logs and technical data may be retained temporarily for security and debugging. Instructors may request account deletion, subject to technical and legal limitations.
9. Data Sharing
We do not sell or rent personal data. Data may be shared only with service providers required to operate the platform, to comply with legal obligations, or to protect platform integrity or user safety.
10. Cookies & Tokens
Authentication tokens may be stored in HTTP-only cookies for browser-based clients. Cookies are used strictly for authentication and security purposes.
11. Children’s Privacy
Jiroshi is not specifically designed for children. Instructors are responsible for ensuring compliance with local laws when providing access to minors.
12. Changes to This Policy
We may update this Privacy Policy as the platform evolves. Significant changes will be communicated via the platform or documentation.