Privacy

Updated October 22, 2026

Account and service data

Arise stores your email address, verification status, an Argon2 password hash if you use a password, and a Google account identifier if you choose Google sign-in. Session and email verification secrets are stored as digests. We use this information to sign you in and protect your account.

Models and payments

When you use a hosted Mesh model, the request you submit is sent to the selected model provider to generate a response. Our wallet records your model choice, usage totals, charges and payment references. Stripe hosts checkout and processes payment details; Arise does not store your card number. Model provider and Stripe privacy policies also apply to their processing.

Memory and optional contributions

Your personal browser memory stays on your device. Member web memory provides reviewed site workflows. If you explicitly enable workflow contributions, Arise receives your account identifier, site domain, app version, tool categories and success or failure outcomes for review. These reports exclude typed text, page contents, screenshots, selectors and full URLs. You can stop contributions in Settings.

Messages and infrastructure

Support messages, your reply email and account identifier if signed in are delivered through Resend to our support inbox.

When you ask an agent to send email, the subject, message body and any attachments pass through the Arise API and Resend to your verified Arise account email address. Arise does not store the subject, body or attachments. We retain daily email counts and, for paid emails and refunds, wallet transaction records. Resend processes the message for delivery under its own privacy policy. Agent email uses a noreply address; replies are not monitored.

Hosting and security services may process technical request metadata to operate and protect the service.

Agent Browser mobile app

Agent Browser for Android and iOS is a standalone web browser and does not require an Arise account. In the current version, browsing history, bookmarks, open-tab details, browser preferences, and saved login credentials stay on your device and are not uploaded to Arise. The Android login vault is encrypted using a key held by Android Keystore. On iOS, saved login credentials are stored in device-only Keychain items and are not synchronized to iCloud. You can remove bookmarks, history, and saved logins using the app's controls. Website cookies and site data are handled separately by the browser engine. On Android, the GeckoView browser engine, developed by Mozilla, may also contact Mozilla servers in the background to fetch browser security data and check network connectivity. Those requests do not include your browsing history, saved logins or any Arise account information; Mozilla may see your IP address like any server you connect to, and Mozilla's policies apply to that data.

When you navigate to a website, your device connects directly to that site; the site and any third-party content it loads may receive normal web requests and store data under their own policies. When you search, your query is sent directly to the search provider selected in the app (Google or Naver). Arise does not proxy those requests or receive their contents. The privacy policies of the sites and search providers you choose apply to their processing. The current mobile version has no Arise account sync or desktop pairing.

Access, correction and deletion

Contact help@arisebrowser.com to request account access, correction or deletion. Payment and accounting records may need to be retained for applicable obligations. Sign out to revoke your current session. You control locally stored browser data through the app settings.