Privacy policy

Google sign-in

Google sign-in is optional. When you choose it, we request your Google account identifier, email address, and basic profile information, including your name. We use the identifier and email to create or recognize your account, and your name to initialize your account and workspace. Connecting Google to an existing account requires an explicit account-linking step.

The requested permissions are openid, email, and profile. We do not request Gmail, Drive, contacts, or access to your Google browsing history. We do not request refresh tokens or retain Google access tokens for later use. Google identity information is used for account access and the related account features described here, including displaying your name in a workspace. We do not sell Google identity information or use it for advertising or model training.

Temporary sign-in records contain hashed proofs and encrypted information needed to complete the flow. These flows expire; expired proofs cannot be used to sign in. Expiry does not mean every associated record is immediately erased.

Account and workspace data

We store account details such as your name, email, password hash when you use a password, security settings, and sessions. The service also processes workspace memberships, roles, profile settings, proxy configuration, extension assignments, activity, and usage records to provide the features you use.

Local browser profile data is stored on your device. Choosing cloud profiles sends supported browser-state snapshots to the service. Local profile metadata and usage can also be sent for workspace reporting. Websites you visit, proxy services, and extensions you install handle information under their own policies.

Support requests include the messages and diagnostic details you submit. Email sent to the service, when receiving is available, includes sender and recipient details, message content, and attachment metadata. Avoid sending passwords, secret keys, or browser profile archives in support messages.

Who can access information

When payments are available, Stripe processes checkout and billing-portal payment details. We retain workspace billing identifiers, selected plans, payment status, invoices or order references, and purchased access periods to provide and support the service. Card numbers and card security codes are entered directly with Stripe; our application does not store them. Proxy suppliers, including Proxy-Cheap, receive the order configuration needed to allocate a connection and process traffic sent through that connection. A proxy does not make that traffic private from the provider or destination website.

Workspace permissions determine what other members can see and manage. Authorized members may see your name, email, activity, and shared profile information. Authorized staff can access account, operational, and support information to administer the service, resolve requests, and investigate problems.

Railway provides hosting, database, and object storage for the service. Resend processes recipient details and message content for the emails we send. Google processes your sign-in with Google. Cloudflare provides domain and DNS services; the site is not currently routed through Cloudflare’s traffic proxy. Information may also need to be disclosed to comply with applicable law or address misuse of the service.

Storage and security

We use HTTPS for the public service, access controls, password hashing, and encryption for selected sensitive records and stored objects. Other account and workspace records are held in the service database behind access controls.

Cookies keep you signed in and protect authentication flows. Browser storage remembers interface preferences and temporary sign-in state. Retention depends on the record and its purpose; account, support, security, and backup records may remain after you stop using a feature. Contact the operator about retention or removal of your information.

Your choices

You can edit account details, review sessions, and change support-reply email preferences in Settings. You can also review brwse.io in your Google Account’s third-party connections. Removing Google access does not by itself delete your brwse.io account or workspace data.

Completing password recovery disconnects Google sign-in and ends existing brwse.io sessions. Your account and workspace remain, and authenticator MFA remains enabled if you set it up. Contact the operator to request access, correction, or removal of information beyond the available account controls.