System Security

PERPOS is designed with multiple layers of security — from sign-in, per-user and per-organization data isolation, and data encryption through to audit logging — to protect our customers' business data and personal data.

PERPOS uses LINE Login as its primary sign-in method, so there is no separate password to set and remember, reducing the risk of password leaks. Authentication relies on the LINE account users already have, via the OAuth standard.

Every data table has Row Level Security (RLS) enabled on the PostgreSQL database. Each user and each organization can access only its own data; one organization's data cannot be read by another. System-level data access is restricted to controlled server-side components.

• Data and files are stored on Google Cloud with encryption.
• Output files, such as meeting-minutes PDFs, are stored privately and accessed through temporary links that expire automatically; they are not made public.
• Raw audio files are deleted immediately after processing; summary files and transcripts are deleted within 48 hours.

The system records important actions, showing who issued each command and what happened. Even jobs processed by background services carry a reference to the user who actually issued them, so that activity can be audited retrospectively.

Heavy jobs, such as transcription and PDF compression, run on separate services that can be called only with authorization and have scoped data access — they cannot touch unrelated users' data.

Customers' files and audio are not used to train AI models, and PERPOS does not sell or share personal data with third parties without consent. See also PDPA and our Privacy Policy, or contact us at [email protected].