Lumiction Inc. (株式会社Lumiction) — Service: "Futari Sankyaku (二人三客) FC Portal" — Version 1.2 — Revised 23 October 2026 — Owner: Naoto Toda, Representative Director (Information Security and Privacy Officer). Address: 4-6-1-1314 Kachidoki, Chuo-ku, Tokyo, Japan. Contact: n-toda@lumiction.com.
1. Purpose and scope
This policy defines how Lumiction Inc. ("we") protects the confidentiality, integrity and availability of information processed by the Futari Sankyaku FC Portal (https://23-fc-portal.com), including data obtained from TikTok Shop through the TikTok Shop Open API on behalf of authorized sellers (franchisees), maker (supplier) data, and personal data of users. It applies to all staff, contractors and systems involved in operating the service.
2. Governance and responsibilities
- The Representative Director is accountable for information security and approves this policy and exceptions to it.
- Access to production systems is limited to named engineering staff. Every person with access must follow this policy and complete onboarding on secure handling of seller and personal data.
- This policy is reviewed at least annually and whenever the service, the law, or platform (TikTok Shop) requirements change.
3. Infrastructure and network security
- The application is hosted on Render (Singapore region) as a managed web service behind Cloudflare, which provides DDoS mitigation and TLS termination. The database is a Render managed PostgreSQL instance reachable only through Render's private network (internal connection string); it is not exposed to the public Internet.
- All external traffic is served over HTTPS only (HSTS enabled). Security headers (Content-Security-Policy, X-Frame-Options DENY, X-Content-Type-Options nosniff, Referrer-Policy, Permissions-Policy, COOP) are set on every response.
- Application and database run as separate services with separate credentials. No shell access to production is granted except through the hosting provider's audited console.
- Rate limiting is applied to authentication, code-verification and sensitive write endpoints, keyed on the verified client IP.
4. Access control and authentication
- The portal has three roles (franchisee, maker, headquarters admin) with separate, server-enforced sessions. Every data access is scoped to the authenticated principal; cross-tenant access is denied server-side.
- Sessions are HMAC-SHA256 signed cookies (HttpOnly, Secure, SameSite=Lax) with a 2-hour idle timeout for standard sessions. Admin sessions are invalidated when the admin credential is rotated.
- User passwords are hashed with scrypt (random 16-byte salt). Verification and reset codes are generated with a cryptographically secure RNG, stored hashed, expire in 15 minutes and are limited to 8 attempts per address.
- Cross-site request forgery is mitigated with SameSite cookies plus Origin/Referer validation on all state-changing API requests. Malformed paths (e.g. duplicate slashes) are rejected before routing.
- Production secrets (API keys, encryption keys, database credentials) are stored only in the hosting provider's encrypted environment configuration, never in source code or chat. The application refuses to start in production if required secrets are missing or left at default values.
5. Data classification, protection and encryption
Information is classified into four levels; handling rules follow the level.
| Level | Examples | Handling |
| Restricted | API secrets and encryption keys, TikTok Shop access/refresh tokens, bank account numbers, password hashes, verification codes | Stored only in encrypted environment configuration or encrypted at the application layer (AES-256-GCM); never logged, exported or shown in full; access limited to the application itself and named engineers |
| Confidential | Seller order, settlement, finance and inventory data from TikTok Shop; buyer names/addresses on orders; franchisee and maker contracts and invoices | Encrypted in transit and at rest; visible only to the owning tenant and HQ roles; not shared with third parties; deleted per the retention schedule |
| Internal | Operational documents, audit logs, aggregated statistics | Access limited to staff; no public exposure |
| Public | Marketing pages, legal pages, product catalog information makers choose to publish | No restriction |
- Data in transit is encrypted with TLS 1.2 or higher. Data at rest is encrypted by the managed database and storage providers.
- TikTok Shop access and refresh tokens are additionally encrypted at the application layer with AES-256-GCM (random IV per record) before being stored; plaintext tokens are never logged or returned to clients.
- Bank account numbers are encrypted with AES-256-GCM using a key derived from a dedicated secret; only masked values (last 4 digits) are shown in the UI. Payment card numbers are never received or stored by us; cards are tokenized client-side by the payment provider (Stripe) and only a token is stored (PCI DSS SAQ A model).
- Uploaded images are validated by content (magic bytes), renamed to random file names and served with a sandboxed Content-Security-Policy.
6. TikTok Shop data handling
- We access TikTok Shop data only after the seller (franchisee) has explicitly authorized our app through TikTok's OAuth flow, and only within the scopes granted (shop information, orders, fulfillment, products/inventory, finance/settlements, returns). OAuth state values are single-use, HMAC-signed and expire after 10 minutes.
- Webhook messages are accepted only with a valid signature computed with the app secret; unsigned or mis-signed messages are rejected before any processing. Events are processed idempotently.
- TikTok Shop data is used solely to provide the service to the authorizing seller and to calculate royalties as agreed in the franchise contract. It is not sold, shared with third parties for their own purposes, or used for advertising.
- When authorization is revoked, stored tokens are removed and erasure of the collected TikTok data is queued. Verified contract termination or account-erasure requests stop access and synchronization. Personal data, raw payloads, addresses, external identifiers and retry queues are erased; only minimal pseudonymous accounting data is retained. Requests are normally handled within 30 days after ownership verification. Database fences prevent re-ingestion. Local erasure and backup/processor completion are recorded separately.
7. Logging, monitoring and audit
- Security-relevant events (logins, failed logins, admin actions, data exports, authorization changes) are written to an audit log with timestamp, actor, verified client IP and action.
- Application logs never contain passwords, tokens, card or bank numbers, or verification codes. Error responses to clients are generic; details are logged server-side only.
- Service health (including database connectivity) is monitored by the hosting provider; failures trigger alerts to the operations contact.
8. Secure development and vulnerability management
- All code changes are reviewed and type-checked before deployment; deployments are automated from the main branch of a private repository.
- Dependencies are checked for known vulnerabilities (npm audit) before each release; high/critical findings are fixed before deployment.
- A security review of the full application (authorization, authentication, input handling, XSS, CSRF, crypto, headers) is performed at least twice a year and after major changes; findings and remediation are documented. The most recent review was completed in September 2026.
9. Backup and business continuity
- The paid Render PostgreSQL database uses continuous backups for point-in-time recovery (3–7 days depending on the workspace plan); logical exports are retained by Render for 7 days. Deletion records must be applied before any recovered database is put back into service. Exported/off-provider copies are inventoried and removed separately.
- Uploaded files are stored on durable object storage or a persistent disk with provider redundancy.
10. Incident response
- Suspected security incidents are triaged within 24 hours of detection. Affected credentials and tokens are rotated immediately; the root cause is fixed and documented.
- If an incident affects TikTok Shop data or sellers, we notify TikTok Shop and the affected sellers without undue delay and no later than 72 hours after confirmation, in accordance with platform requirements and the Act on the Protection of Personal Information (Japan).
- Security contact: the address shown on the Privacy Policy page (https://23-fc-portal.com/legal/privacy/).
11. Sub-processors
| Provider | Purpose / data |
| Render (Singapore) | Application hosting, managed PostgreSQL (all service data) |
| Cloudflare | DNS, DDoS mitigation, TLS edge; object storage for uploaded images (R2) |
| Resend | Transactional email (verification and reset codes, notifications) |
| Stripe | Card tokenization and royalty billing (card data never touches our servers) |
| Anthropic | External inference is disabled by default. Enabling it requires approval of the data inventory, processing countries and provider terms. The coach continues to provide local rule-based analysis. |
12. Compliance
We comply with the Act on the Protection of Personal Information (Japan), the TikTok Shop Partner terms and API/data policies, and the Specified Commercial Transactions Act for our own commerce. Personal data handling is described in our Privacy Policy.