Elit Run
This page describes how Elit Run processes local archives, cloud integrations, shared sessions, and browser-side storage. It is intended as a product-level privacy statement and PDPA notice for operators and users working with .wapk archives in the browser.
1. Scope
Elit Run is a browser-first launcher for .wapk archives. This notice covers the way the product handles archive content, session state, cloud-storage integrations, shared-session features, and limited browser-side configuration data.
This page does not replace any organization-specific privacy notice that may apply when Elit Run is deployed by a company, school, agency, or other data controller.
2. Default Processing
When you open a local .wapk file, Elit Run decodes the archive, previews files, and runs the browser sandbox inside the current browser tab. Those steps occur locally unless you deliberately enable a feature that sends data to an external provider or to the active Elit Run server.
3. Cloud Providers
If you choose Google Drive or OneDrive, Elit Run sends authentication requests and archive read or write traffic directly to Google APIs or Microsoft Graph so the selected file can be opened or synchronized.
Those providers operate under their own privacy notices, data-location choices, retention periods, and security controls. You should review the relevant provider notice before using those flows.
4. Shared Sessions
When join or public sharing is enabled, Elit Run exchanges the shared package snapshot, route state, join key, and later session updates through the active Elit Run server so invited participants can access the same working session.
Operators should treat shared-session data as potentially sensitive whenever the underlying archive or route state contains personal, confidential, or regulated information.
5. Browser Storage
Elit Run may store limited convenience settings in the current browser, including the Google client ID, OneDrive client ID, OneDrive tenant, and the timestamp of the PDPA acknowledgement. Identity-provider SDKs may also create their own cache or token entries under browser site data.
6. Operator Duties
The person or organization deploying Elit Run remains responsible for identifying an appropriate lawful basis under the PDPA, verifying authority to process the archive, and ensuring that any personal data opened, synchronized, or shared through the service may be processed lawfully.
7. Data Subject Rights
Requests relating to access, correction, deletion, restriction, objection, or complaint should be handled by the operator or organization controlling the archive data, because Elit Run acts primarily as a technical tool and does not independently determine the purpose of each archive's content.
8. Production Readiness
Before production use, the deploying organization should supplement this page with its controller name, privacy contact channel, retention schedule, cross-border transfer wording if applicable, and any internal security or incident-reporting commitments required by policy or law.
9. Contact Note