Privacy Policy

Last updated: September 10, 2026

1. Introduction

Nexting Inc. ("we", "us", "our") operates the Nexting iOS and Android apps, Nexting for Mac, Windows, the Nexting wearable hardware, and nexting.ai. This policy explains what we collect, who can see it, where it lives, and how long we keep it.

Different parts of Nexting handle data differently. End-to-end encryption does not mean Nexting can see nothing. It protects specific Agent content. Nexting-operated services (speech-to-text, Voice History, hosted Nexting AI chat, remote desktop signaling, diagnostics) are processed by us or our processors so those features can work.

2. What we collect

2.1 Account

What: Email address and authentication credentials.
Who processes it: Nexting; Supabase (authentication only).
Where it is stored: Nexting database (email encrypted at rest) and Supabase Auth.
How long: While the account exists.
How you remove it: Delete account in Settings → Account → Delete Account.

2.2 Nexting AI conversations

What: Chat text you send to hosted Nexting AI, and the replies.
Who processes it: Nexting cloud; the hosted AI engine we run for Nexting AI; model providers used to generate replies.
Where it is stored: Nexting servers, encrypted at rest. We hold the keys so history can sync across your devices. This is not end-to-end encryption.
How long: Until you delete the conversation or the account. We do not auto-delete chat history.
How you remove it: Delete a thread in the app, or delete the account.

2.3 Agent conversations (Claude Code, Codex, Cursor, Grok)

What: Session text, terminal, approvals, and Agent media for agents that run on your computer.
Who processes it: Your computer runs the agent. Nexting cloud relays between your phone and that computer. With Advanced Privacy on, the cloud only stores and relays ciphertext for this content.
Where it is stored: Your computer; Nexting may keep an encrypted-at-rest transcript copy for history and offline sync.
How long: The cloud transcript copy until you clear it or delete the account. Files on your computer follow that computer.
How you remove it: Clear in the app, or delete the account (cloud copy). Local agent files stay on your computer until you delete them there.

2.4 Voice for speech-to-text

What: Microphone or hardware audio, streamed so we can turn it into text.
Who processes it: Nexting cloud STT; ByteDance Volcengine (streaming recognition); Groq Whisper (file fallback). On iPhone, Apple on-device recognition may also run locally.
Where it is stored: Audio is sent to those STT processors to produce text. We do not keep a separate STT archive.
How long: Processed to produce a transcript, then discarded by the STT path.
How you remove it: Stop speaking or cancel. Empty or noise-only recognition is not saved to History.

2.5 Voice History (replayable recordings)

What: Audio plus transcript when a take produces real text (home, hardware, or in-chat hold-to-speak). Empty recognition does not create a card.
Who processes it: Nexting. Advanced Privacy does not move this off Nexting STT or hide the clip from our Voice History service.
Where it is stored: Nexting object storage and database, under your account. Playback uses a short-lived signed URL.
How long: Up to 30 days, and at most 200 clips per account. Older clips drop out of History.
How you remove it: Delete one clip, delete a session’s clips, or delete the account.

2.6 Screenshots, photos, and attachments

What: Images and files you attach in chat.
Who processes it: Nexting object storage (to deliver the file). Agent engines on your computer may also receive the file.
Where it is stored: Nexting object storage and database metadata. The phone also keeps a local cache.
How long: Cloud: 3 days normally; 2 hours if you are over the 500 MB cloud quota. Local cache: 3 days or 200 MB, whichever hits first.
How you remove it: Delete in Settings → Storage, or wait for expiry.

2.7 Remote desktop video

What: Live picture of a computer you already signed into with the same Nexting account.
Who processes it: Encrypted live stream (WebRTC DTLS-SRTP) between your phone or Mac and that computer. Nexting cloud does not sit in the video path as a recorder. Chat end-to-end keys are not used.
Where it is stored: We do not record or archive the screen. We store enrollment and session metadata (which computer, online / busy / closed). Your phone may cache a small cover thumbnail.
How long: Metadata while the computer stays enrolled. Thumbnails on the phone until cache cleanup. Live frames are not kept.
How you remove it: Pause or turn off remote on the computer; leave that device; or delete the account.

2.8 Diagnostics

What: Crash reports, failed requests to our domains, coarse app version and device type.
Who processes it: Nexting; Sentry (hashed user id, not email or name). User-sent feedback mail includes version, device type, and signal type only.
Where it is stored: Diagnostic processors and our logs.
How long: Operational logs for a limited period. Account-deletion audit records are kept so we can show the account was deleted.
How you remove it: You cannot delete a crash report after it is sent. Do not send feedback if you do not want that metadata mailed.

2.9 Dictionary, devices, and billing metadata

What: Custom recognition words; bound hardware and login devices; subscription status and usage.
Who processes it: Nexting. Apple or Stripe for payment.
Where it is stored: Nexting database. Apple and Stripe hold payment records.
How long: While the account exists. Payment records follow Apple or Stripe rules.
How you remove it: Edit dictionary words; unbind or leave a device; delete the account. Deleting the account does not cancel Apple or Stripe billing — see section 7.

3. How we use your information

To provide Nexting AI, Agent relay, voice, and remote desktop
To authenticate your account and manage your subscription
To transcribe speech and keep Voice History you can replay
To diagnose crashes and connection failures on our domains
To send important service notifications

We do not sell personal data. We do not use your conversations, recordings, or attachments to train our own AI models.

4. Advanced Privacy (end-to-end encryption)

Advanced Privacy is on by default for Agent content.

It covers: Claude Code, Codex, Cursor, and Grok content between your authorized phone and computer — chat, terminal, approvals, Agent media, and related push previews.

It does not cover: speech audio, transcripts, Voice History, hosted Nexting AI chat, remote desktop video, dictionary words, diagnostics, or account and billing metadata.

If a covered Agent path cannot encrypt safely, sending stops. It does not silently fall back to plaintext.

Nexting AI hosted chat is encrypted in transit (TLS) and at rest. That is not the same as end-to-end encryption: we hold the keys so the product can show history on your other devices.

5. Device permissions

With your permission, the phone app may use Bluetooth, microphone, speech recognition, camera (QR pairing and attachments), photos, and — if you enable the matching skills — contacts, calendar, reminders, location, HealthKit, or HomeKit. HealthKit data is not shared with third parties for advertising. These permissions are used to fulfill a request you started.

Nexting for Mac asks for Screen Recording only during an authorized remote session, Accessibility to inject mouse and keyboard while you are being controlled, and Automation to type into local agents. Those prompts appear on the Mac, never from the phone.

6. Processors

Supabase — sign-in
Cloudflare — site, API edge, and object storage for Voice History and attachments
ByteDance Volcengine — streaming speech-to-text
Groq — file speech-to-text (Whisper)
Apple — App Store billing, push notifications, and on-device speech when used
Stripe — website billing (we do not store full card numbers)
Sentry — crash and failed-request diagnostics (hashed id)
Hosted model providers — to generate Nexting AI replies (conversation context; not used by us to train models)

Claude Code, Codex, Cursor, and Grok on your computer are your engines. Nexting relays; we do not operate those vendors’ accounts for you.

7. Delete account vs cancel subscription

Deleting your Nexting account deletes the account and the Nexting-held data listed above, as far as our systems allow, including conversations, Voice History, and cloud files we can reach. It does not cancel an auto-renewable subscription.

App Store / Apple ID: cancel in Apple’s subscription settings, or in the app via Manage Subscription. Apple continues charging the Apple ID until you turn auto-renew off, even if the Nexting account is gone. Cancellation takes effect at the end of the current period. Payment is charged to your Apple ID at confirmation of purchase. Subscriptions automatically renew unless auto-renew is turned off at least 24 hours before the end of the current period. Your account is charged for renewal within 24 hours prior to the end of that period.
Website / Stripe: cancel in the billing portal from the website billing page, including subscriptions started from Android. Deleting the Nexting account does not stop Stripe from charging the saved payment method.

Cancel the subscription first if you want billing to stop. Then delete the account if you also want the data gone.

8. Your controls

Read and delete conversations in the app
Play or delete Voice History clips
Delete cloud files in Settings → Storage
Turn Advanced Privacy off (Agent content then uses TLS plus at-rest encryption with keys we hold)
Revoke OS permissions in system settings
Delete your Nexting account on iPhone or Android in Settings → Account → Delete Account. Nexting for Mac does not delete the account from the Mac window.

We do not currently offer a separate “export my data” file. What you can see in the app is the data we keep for the product.

9. Children's privacy

Nexting is not directed at children under 13. We do not knowingly collect their data. Contact us if you believe we have.

10. Changes

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the "Last updated" date.

11. Contact

If you have questions about this Privacy Policy or your data, contact us at:

[email protected]