Processing method can vary by tool and file type. Many edits run on our servers so you don’t need installs or powerful hardware. We aim to keep processing scoped to what’s required for the edit. If a tool supports local processing in the future, it will be labeled clearly.

Retention depends on whether you save a project or run a one-off export. We try to minimize retention by default, and we’ll document the retention rules per tool and plan. If you need shorter retention, use projects sparingly and delete exports you no longer need.

When you delete content, it’s removed from your workspace and scheduled for permanent deletion from storage. Some operational logs may persist briefly for security and abuse prevention, but they don’t include your raw media content.

Your files are used only to provide the editing features you request. If we ever offer an opt-in program (for example, to improve automated features), it would be explicit and optional.

Access is tied to your account and any sharing settings you enable. Team and shared-project features, when enabled, will show exactly who has access and what they can do (view vs edit).

Data is transmitted over HTTPS. Stored files are kept in encrypted storage. If you need advanced controls (like customer-managed keys), that can be added later as part of enterprise-style plans.

You can try the free plan without entering payment details. If you decide to upgrade for higher limits or premium tools, you can add billing then.

Free limits may apply to file size, minutes processed, exports, or concurrent jobs. When you hit a limit, the UI will tell you what you hit and your options (retry later, reduce file size, or upgrade).

You’ll be able to change plans from your account settings. Upgrades take effect immediately; downgrades typically apply at the next billing cycle so you keep what you paid for.

Limits can include maximum upload size, max duration, queue/concurrency limits, or monthly processing minutes. Exact limits will be listed in the pricing page and inside each tool before you upload.

Most users prefer a single plan that unlocks a set of tools and higher usage limits. If you later want “pay only for what you use,” that can be supported with tool-based add-ons.

You can open multiple tools in different tabs and run multiple jobs, but the number of simultaneous processing jobs may be limited by your plan to keep things stable.

Opening multiple editors is fine. If you start several processing tasks at once, extra jobs may queue depending on your plan and current load.

Aqua Editor is designed as a toolkit. Export from one tool and continue in another. We’ll add “recipes” and saved workflows so common pipelines can be repeated with one click.

The goal is usable outputs even on the free plan. If any experimental or premium feature requires a watermark on free, the tool will clearly disclose it before exporting.

You’ll be able to share via link or by inviting specific accounts. Permissions can be view-only or editable depending on the feature set and plan.

Early versions support handoff-style collaboration (share access, duplicate, export). Real-time multi-user editing can be added later with versioning and conflict handling.

Many tools can work without an account for quick edits. Accounts unlock saved projects, history, and sharing. If a tool requires sign-in (for storage or longer jobs), it will prompt you.

Mobile and tablet support depends on the tool and file sizes. For long videos and advanced editors, desktop is recommended. We’re optimizing the UI for touch over time.

Use the latest Chrome or Edge for the smoothest performance. Safari and Firefox may work depending on feature requirements (like advanced media APIs). We’ll list known limitations in Docs.

Aqua Editor is web-based. You upload, edit, and export without installing software. If we release a desktop helper for faster uploads or local processing, it will be optional.

Since many features rely on server-side processing and storage, offline mode is limited. Some lightweight interactions may still work if already loaded, but exporting typically requires connectivity.

Most tools support standard formats like MP4, MOV, MP3, WAV, PNG, JPG, and more. Exact supported formats can vary per tool — we’ll list them on each tool page.

We plan to expose automation for batch workflows and integrations (webhooks, endpoints, or CLI). If you have a specific automation need, we can prioritize it.

Batch processing depends on the editor. Over time we’ll expand support for batch inputs, bulk exports, and saved presets to apply edits across multiple files.

For long edits, saving a project reduces risk. If a job is running server-side, it may continue even if your tab closes; you can revisit the tool to check job status. We’ll improve autosave over time.