Gemini Spark vs QwenPaw

Gemini Spark

Google's help pages state what Spark confirms before doing, how to delete its remote browser and code data, and the risks of prompt injection. Spark has no public API, Google calls it experimental, and it runs only with Keep Activity on, the setting under which chats are used for model training and human review.

QwenPaw

Mail tools ask for approval by default, automatic mail handling may not delete permanently, and the security docs list what each sandbox backend fails to enforce. Usage data is sent by default, the default approval level passes every tool call no rule flags, and no privacy policy or security advisory is published.

Gemini Spark

1. Do not plan an integration against Spark. No public API or MCP server was found, and a person must hold a Google AI Pro or Ultra subscription
2. Expect a confirmation request before sends, edits, purchases and web form submissions, and note that bulk changes to private Google Tasks run without one
3. Delete remote browser data and remote code execution data in Gemini Spark Settings after a sensitive session. Deleting a task thread or Gemini Apps activity does not remove them
4. Keep within 15 running tasks and 50 active schedules. A schedule does not run when 15 tasks are running or the usage limit is reached
5. Treat every safety statement here as Google's own description. None was tested, and no message was sent to the service

QwenPaw

1. Set QWENPAW_TELEMETRY_DISABLED=true before qwenpaw init --defaults or qwenpaw app. Both send usage data without asking
2. Set approval_level to STRICT or SMART in agent.json. The default AUTO runs every tool call no guard rule flags
3. Set dm_policy and group_policy to allowlist with allow_from on each channel. Both default to open
4. Set QWENPAW_AUTH_ENABLED=true before binding beyond 127.0.0.1. Requests from localhost skip login even then
5. Keep mail tools on ask for send_message, delete_message and delete_thread, and turn on Mail Access Control with automatic handling