Privacy and Local Data

Data that stays on your machine by default

• Projects, conversations, and local workspace files.
• Email bodies, meeting audio, transcripts, and summaries.
• Local memory, plugin diagnostics, and private content returned by connected apps.
• Credentials for locally configured providers. Cloud connected-app authorization credentials are handled separately by the hosted service.

Data the account service handles

• Account identity and subscription status.
• Device binding, feature entitlements, and signed offline licenses.
• Quota and usage metadata that contains no private content.
• Cloud connection identifiers, scopes, status, and authorization credentials.
• Cloud generation task status, costs, and output links used to retrieve results.

When content can leave your device

When you explicitly choose a cloud model, a remote connected app, or another third-party service to complete a task, the selected content required for that operation may be sent to the corresponding service. Nexts is expected to state the target service and authorization scope in its permission and connection screens.

Cloud AI requests can pass through Nexts gateways; connected-app actions pass through the connector service. Web search sends queries to the configured provider. The Chrome extension passes browser information needed for a task to the desktop app, which may send relevant content to the chosen cloud model. Remote access uses a gateway to relay the connection. Local-first does not mean that these operations stay entirely on your device.

The website, Nexts App, and companion Chrome extension (also named NextsAI or Nexts AI) share the Nexts Privacy Policy and Nexts Terms of Service. These URLs remain unchanged. For account or cloud-data deletion requests, contact info@nexts.ai; deleting cloud records does not delete local workspace files or copies held by third-party providers.