Back to Blog
An eSIM provider and the mobile networks carrying its service may observe connection metadata, but “browsing history” is too broad a label. Visibility depends on DNS and encryption. A network can generally measure destination IP addresses, timing, and data volume; domain visibility varies by protocol configuration. HTTPS normally hides the page path, form contents, passwords, and response body. The service provides mobile data, not anonymity.
Think in layers. The mobile carrier must route packets, so it can see that a device connected, when traffic flowed, how much moved, and which destination IP addresses received connections. A traditional unencrypted DNS query can also reveal the requested domain to the resolver and observers on that path. Encrypted DNS changes that exposure, while newer connection protocols can hide additional names. Results therefore depend on the phone, resolver, app, and protocol rather than simply on whether the SIM is embedded.
HTTPS creates an encrypted connection between the browser and website. Mozilla's HTTPS-Only documentation explains why browsers should prefer that protected connection. With HTTPS working correctly, the carrier normally cannot read the exact URL path, search terms, page content, password, or message body. It can still infer patterns from timing, volume, IP destinations, and other unencrypted metadata. Encryption protects transport; it does not prove that a website itself is honest.
DNS is a separate trust choice. Cloudflare's public resolver privacy documentation describes what its resolver processes and retains. Another resolver can use a different policy. Apple's Private Relay explanation shows one architecture designed so no single party sees both a user's IP address and requested website. These examples illustrate protocol choices; The service does not add either service to a data plan.
Private or incognito mode mainly changes what the browser retains on the device. It can discard local history and cookies after a session, but packets still cross the same mobile network. It does not create HTTPS, hide traffic from a carrier, or stop a website from recording an authenticated visit.
Encrypted DNS protects DNS questions between the device and chosen resolver. The resolver still receives the query, and the network still handles connections to destination IP addresses. A correctly configured VPN encrypts traffic between the device and VPN server, so the carrier mainly sees that server, timing, and volume. The VPN operator becomes a new trust point and may see destination metadata or any traffic that lacks end-to-end encryption.
For travel, choose these tools by threat model rather than advertising. A reputable organizational VPN may be required for work. An unknown free VPN can be a worse trust decision than the network it replaces. A co:sim plan works with the phone's supported security tools but is not itself a VPN, private relay, encrypted DNS resolver, or anonymous browsing product.
Use the plan page to confirm the underlying network, activation rule, and validity. The Japan data-only plan is one example of the details shown before checkout. Assign the co:sim profile to mobile data, turn off data roaming on the home line, and check the home carrier's voice and SMS fees separately. These line settings prevent accidental roaming; they do not change what HTTPS or a VPN protects.
Usually not when the website or app uses modern encryption correctly. HTTPS encrypts the browser connection, including the exact path, form entries, page body, and passwords in transit. End-to-end encrypted messaging can protect message content beyond ordinary transport encryption. The carrier still routes the connection and can generally observe destination IP addresses, timing, and data volume; DNS or older protocols may expose a domain name. Do not ignore certificate warnings, because they indicate that the protected connection may not be what the browser expected. A padlock also does not prove that the destination is trustworthy or that an account is secure. Use unique passwords and multi-factor authentication. The network sees metadata about encrypted traffic, not a simple copy of every page in browser history.
No. Private mode is primarily a local-device feature. It reduces browser history, cookies, cached form entries, and other traces kept after the private window closes. The mobile connection still travels through the carrier, DNS resolver, and destination service just as it would in a normal window. HTTPS may hide page paths and content, but that protection comes from HTTPS, not from the private-mode button. Websites can still record visits, especially when the user signs in, and employers may monitor managed devices through separate software. Use private mode when you want fewer traces on a shared phone or computer. Do not describe it as network anonymity. A co:sim data connection carries private-mode traffic without adding or removing those browser protections.
No. Encrypted DNS can prevent a local observer from reading plain-text DNS requests, which removes one source of visible domain names. The selected resolver still receives the question and applies its own logging and retention policy. After resolution, the mobile network still routes traffic toward destination IP addresses and observes timing and volume. Some modern protocols conceal more naming information, while other apps use their own resolver behavior, so there is no universal result from one toggle. Review the resolver's published policy and use operating-system support instead of an untrusted configuration profile. DNS does not encrypt web content, replace HTTPS, or stop account-level tracking. It narrows one part of the visibility chain rather than making the entire browsing session disappear.
A correctly configured VPN usually hides individual internet destinations from the mobile carrier by creating an encrypted tunnel to the VPN server. The carrier can still see the server's IP address, connection times, and total data volume. Trust moves to the VPN operator, which may be able to observe destinations and any traffic not independently encrypted. Apps can bypass a tunnel, configuration can leak, and a connection can drop unless a suitable kill switch is enabled. Review ownership, audit claims, jurisdiction, and retention policy instead of choosing by price alone. co:sim neither includes nor requires a VPN; it supplies the data transport beneath one. A VPN also does not prevent tracking after login, guarantee access to region-locked services, or repair a compromised device.
No. co:sim is a data-only travel connectivity service. Its eSIM profile authenticates access to supported mobile networks and carries internet traffic; it does not promise anonymity, erase carrier metadata, change browser history, or operate as a VPN. Security still depends on HTTPS, encrypted apps, current software, account controls, and any separate DNS or VPN service the traveler deliberately chooses. Mobile data can avoid an unknown café or airport Wi-Fi access point, which removes that local operator from the path, but the mobile carrier and other internet services remain involved. Keep the installation QR private, follow the plan's activation instructions, and use official support for connection problems. Treat connectivity and privacy as related but distinct decisions.
The practical answer is metadata, not a readable diary: understand each protocol layer before deciding which additional privacy tool you trust.
Mexico
1-day trip pass
From $2.99
Canada
1-day trip pass
From $2.99
Brazil
Valid 7 days
From $3.99
Instant delivery by email · Install before you fly
FAQGovernment alerts are broadcast to an area, not to a phone number, so a data-only travel eSIM can receive them. Here is which alerts need data, which do not, and what actually blocks them.
FAQSatellite SOS and satellite messaging run on a different path from your travel eSIM's data. Here is what each one needs, where each works, and which one your plan has nothing to do with.
FAQ“SIM not provisioned” is different from a QR-scan failure. Learn what the message means, what to check safely, and what support needs from you.
Valid 7 days
From $3.99
co:sim Team