Data Handling & Privacy Commitments

Scope of This Notice

This privacy notice applies to the Jaxo mobile application and any associated features, including the cropping workspace, progress overlay tools, playback sticker placement, chapter marker system, and the one-tap render-to-library pipeline. It governs the relationship between you as a user of the application and the Jaxo development team.

Jaxo is designed as a standalone creative tool. You are not required to establish a profile, provide identifying credentials, or maintain a continuing account relationship to access any feature within the application. All creative operations described in this notice begin and end at the device level unless explicitly noted otherwise.

Processing Landscape Overview

Our design philosophy prioritizes on-device execution. Before describing individual data categories, it is important to establish the broader operational model that shapes every decision in Jaxo.

Device & Technical Information

When Jaxo is active, certain non-identifying technical signals may be observed solely to ensure functional stability and rendering performance across diverse hardware configurations.

Media & Project Handling

Source Footage Access

Jaxo reads video assets only when you explicitly select them through the system media picker or import mechanism. Each imported clip is processed within the application sandbox for the duration of your editing session. Source files remain in their original location outside Jaxo and are not copied, duplicated, or mirrored externally without your initiation of an export action.

Project State & Drafts

When you place progress overlays, position follow-along stickers, mark chapter boundaries, or define crop regions, Jaxo preserves these edit decisions locally. Draft projects contain only the parameterized coordinates for each edit decision, not embedded copies of the underlying frames.

Rendered Output

The one-tap render pipeline assembles your edit decisions with the source footage on-device and writes the completed file to your designated media library, per the permissions you grant. Jaxo does not retain a server-side copy of rendered output.

Local Storage Practices

Jaxo relies on the standard sandboxed storage mechanisms provided by the host operating system. Information retained on-device may include:

• Project metadata — Crop boundaries, progress overlay timings, sticker coordinates, and chapter marker positions for saved drafts.
• Preference state — Your selected default aspect ratio, preferred export quality preset, display theme choice, and similar interface settings.
• Temporary render buffers — Intermediate frames written during export and cleared automatically upon completion or cancellation of the render task.
• Thumbnail previews — Low-resolution visual references generated to accelerate the draft loading experience.

All locally stored items are removed when you uninstall the application from your device, or when you individually clear saved drafts from within the application interface.

Network Transmission & Connectivity

Jaxo functions without a persistent network connection. The editing and rendering pipeline operates in an offline-capable manner. Limited network activity may occur under the following circumstances:

1. Application update checks — Performed through the distribution platform through which you obtained Jaxo, using standard platform-provided channels.
2. Diagnostic telemetry (opt-in only) — Aggregated, non-identifying performance signals may be submitted solely if your device-level settings permit such reporting and if you have explicitly enabled the option within the application.
3. Third-party embedded components — Any auxiliary service integrated with Jaxo may initiate network calls as described in the third-party providers section below.

We do not operate a central ingestion pipeline for your creative work product. Your edits, chapter markers, and rendered clips are not transmitted for server-side processing, review, or storage under default operating conditions.

Third-Party Service Providers

Jaxo may incorporate a limited set of technology components maintained by external providers. These components operate under their own respective governance frameworks.

Distribution & Infrastructure Providers

The platform through which you acquired Jaxo handles installation, updates, and any optional crash reporting or analytics features offered as part of its standard SDK. You should consult the privacy documentation of the respective distribution platform to understand their independent practices.

Media Encoding Libraries

Jaxo relies on industry-standard, open-source media encoding libraries to assemble the final rendered output. These libraries execute entirely on-device and do not establish outbound network connections in the course of performing their encoding functions.

Optional Diagnostic Providers

If and only if diagnostic sharing is enabled, an external crash aggregation service may receive device exception reports. These reports are limited to stack traces and technical state at the moment of failure, and never include the contents of your video projects or media library.

Permission Model & Access Requests

Jaxo will only request the minimum system permissions necessary to deliver its stated creative functionality. Each permission is requested at the moment it is required, accompanied by a brief explanation of why the access is being sought.

You may modify or revoke any previously granted permission at any time through the system-level application settings on your device. Revoking a permission may limit access to a corresponding feature but does not alter Jaxo's core commitment to on-device processing.

Safeguards & Security Posture

While no software environment can guarantee absolute security, Jaxo implements layered, proportionate safeguards appropriate to the nature of the information within its scope.

• Sandbox isolation — Jaxo operates within the restrictive application container enforced by the host operating system, preventing unauthorized cross-access to unrelated app data.
• No server-side project repository — The absence of a central project upload pipeline inherently eliminates the class of risks associated with cloud-hosted media repositories.
• Minimal transient state — Intermediate render frames are written to temporary storage with automatic cleanup hooks triggered on process termination.
• Responsible disclosure handling — Reports of potential vulnerabilities received at our contact channel are triaged, investigated, and remediated within a reasonable timeframe.

We periodically review and adapt our security posture as the threat landscape and processing environment evolve.

Retention & Removal Practices

Because Jaxo's model is device-centric rather than server-centric, retention is largely under your direct control.

On-Device Retention

Saved project drafts, preference settings, and thumbnail previews persist on your device until you take affirmative action to delete them. You may remove individual drafts from within the Jaxo interface, or remove all associated data by uninstalling the application through your device controls.

Diagnostic Data Retention

For users who have opted into diagnostic reporting, aggregated exception logs are retained by the third-party diagnostic provider for a fixed window aligned with their standard data lifecycle policies. We do not maintain a separate, independent archive of these logs beyond what is necessary to investigate an active defect report.

User Controls & Available Choices

You retain meaningful control over how Jaxo interacts with your device and information. The following controls are available to you without requiring any profile creation or identity verification:

• Adjust individual system permissions from your device settings screen.
• Delete individual saved drafts from the project library inside Jaxo.
• Enable or disable optional diagnostic telemetry from the in-app settings panel.
• Change default export presets, aspect ratios, and interface themes to match your creative workflow.
• Uninstall Jaxo entirely to remove all locally stored project data and preferences.

Younger Audiences & Age Considerations

Jaxo is not intentionally designed for, nor marketed toward, individuals who have not reached the age of digital consent as defined by applicable laws in their jurisdiction. The application does not deploy features that would distinguish the age of a user, nor does it attempt to verify age through identity checks.

In the unlikely event that we become aware of information submitted on behalf of an individual below the relevant consent threshold, we will take reasonable steps to remove that information from any systems within our control and ensure it is not further processed. Parents, guardians, or trusted adults who believe a younger user has provided information may contact us using the channel described below.

Updates to This Notice

Our privacy commitments may be revised from time to time as we add features, refine processing logic, or respond to new regulatory guidance. When material changes occur, we will present an updated notice prominently within the application interface on your next launch, prior to your continued use of the affected functionality.

Non-material changes, such as clarifying language or reorganizing section structure for readability, may be made without a dedicated in-app prompt. In every case, the effective date displayed in the information card at the top of this document will reflect the most recent revision.

Contact Channel & Questions

If you have questions regarding this notice, the data practices of Jaxo, or wish to submit a report related to privacy or security, please direct your correspondence to our dedicated channel. We aim to respond to substantive inquiries within a reasonable period after receipt.

When submitting a privacy-related inquiry, please include sufficient detail to allow us to understand the nature of your question and locate any relevant records, should any exist.