Security & Data Access

Your data remains yours # — Link to section

Storing files with Kasai Cloud does not transfer their ownership. Processing is limited to operating the service for you and the purposes explained in the Privacy Policy. Kasai Cloud does not sell personal information, use private files for advertising profiles or train AI models on their contents without separate informed permission for a future feature.

Encryption: an accurate boundary # — Link to section

The app’s service connections require HTTPS and certificate validation. This protects data in transit over those connections; it does not mean the storage service cannot process file contents. Kasai Cloud does not present this service as end-to-end encrypted or zero-knowledge. No blanket claim of encryption at rest, independently certified security or a particular production TLS configuration is made here.

Account and sharing controls # — Link to section

Authentication is separated from file-storage access. Connected clients use device credentials rather than retaining your main password as the long-term storage credential. The product supports listing connected devices and revoking device access. Public links support permissions, password protection, expiry and revocation; private previews and media requests use authenticated access.

Protect your device too. Browser session storage and locally saved offline files are not end-to-end encryption and cannot protect against every compromised-device or malicious-script scenario. Link revocation does not erase copies already downloaded.

Administrative access # — Link to section

Administrative access must be limited to authorised personnel for reasonably necessary technical operations, security, fraud or abuse investigation, legal compliance, lawful requests or support expressly requested by you. Server, database and recovery operators can technically reach customer data outside application permissions. The product does not enforce a separate approval for every such access, and production access procedures still require operational verification.

Selected administrator sign-in, account and administrator-membership events, deletion maintenance commands and recovery checks have metadata-only application auditing. This does not cover every login, customer lookup, file view or infrastructure change. Local administrators can alter local logs; these are not an immutable audit trail. No dedicated limited-access support role is currently implemented.

Support without handing over your password # — Link to section

You should never need to give Kasai support your password or device credentials. Start with an explanation, error message or carefully redacted screenshot. If support needs to view relevant content, that access should be expressly requested or authorised by you, limited to what is necessary and handled through an agreed secure method. Do not make a private file public simply to get help.

Infrastructure and backups # — Link to section

File storage is kept separately from application source, but this is not a security boundary against privileged server operators. Provider identities, processing countries, complete backup coverage, expiry schedules and production recovery safeguards require confirmation; consult the Subprocessors register for its current status. Recovery tooling can compare pseudonymous deletion records with a restored system, but independent preservation of current records and operational reconciliation are still required. File versions, trash and offline copies do not promise a complete device backup or a guaranteed disaster-recovery outcome.

Deletion and recovery # — Link to section

Choose Account → Delete account in the app to initiate deletion without contacting support. Password verification, an applicable second factor and explicit confirmation protect against accidental deletion. Confirmation is irreversible: access is disabled immediately, credentials and shares are revoked, and a background process removes owned data, including versions and trash. Failed operations remain incomplete and are retried; an in-app receipt reports progress. Backups and limited justified records are handled separately, with no fixed expiry period promised. The Privacy Policy describes the process and device-copy limits.

Responding to incidents # — Link to section

Our incident-response approach is to assess reports, investigate suspected security incidents, contain harm and take appropriate corrective action. We will notify affected users, business customers and regulators when legally required, using the applicable legal requirements rather than an unverified universal notification deadline. A detailed production incident-response process remains subject to operational confirmation.

Responsible vulnerability disclosure # — Link to section

Use the security contact to describe the affected component, reproducible steps and potential impact without including other people’s content or live credentials. Test only on systems and accounts you are authorised to use. Do not access unrelated files, disrupt service or publish exploit details before a reasonable opportunity to investigate. This page does not create a bug-bounty payment promise.