Device and installation manual · adults 18+
Use an AI companion in your browser with no download
A browser session can be the cleanest compatibility test when you do not want an installed application. It still creates local and remote traces: cookies, account sessions, downloads, notification permissions and network requests. Use the official web address, isolate site permissions and understand what private browsing does before treating no download as no footprint.
Reviewed and updated
| Browser choice | Useful for | Local trace to check | Important limit |
|---|---|---|---|
| Normal profile | Reliable return visits | History, cookies, saved login | Shared profile can expose activity |
| Private/incognito window | Reduced local session persistence | Downloads and bookmarks can remain | Not network anonymity |
| Separate browser profile | Account and history separation | Profile folder and sync | Not offered on every mobile browser |
| Home-screen web app | Icon and standalone launch | Site storage and notifications | Still browser-dependent |
| Managed browser | Policy-controlled devices | Admin and network controls | User cannot guarantee privacy |
Run this device check in order
- 01
Reach the service from an official source and verify the domain.
- 02
Update the browser and record its version.
- 03
Open site settings before granting notifications, camera or microphone.
- 04
Use text first with optional permissions blocked.
- 05
Check password saving, autofill and browser synchronization.
- 06
Locate any download in Files or Downloads immediately.
- 07
Sign out and review site data when the test is complete.
No download does not mean no local data
A website can store cookies, local storage, cached files and service-worker data. A browser can retain history, autofill, saved passwords and open tabs. Downloads normally remain after a private window closes. Browser synchronization can copy history or credentials to another signed-in device depending on your settings.
Before testing, decide which browser profile to use and whether it syncs. Afterward, inspect the site-specific data controls rather than clearing all browsing data blindly. Removing site data can sign you out and reset preferences, but it does not close the provider account or retract files already uploaded.
Verify the destination before entering credentials
Use the provider’s official link or manually verify the domain shown in the address bar. Lookalike domains and sponsored search results can imitate familiar branding. HTTPS protects the connection to the named site; it does not prove the operator is the service you intended. Match the address against official documentation.
Do not install browser extensions, certificates or profiles merely because a page says they improve access. If a service redirects between login and product domains, note the destinations and ensure they are documented before continuing.
Control site permissions at browser level
Safari, Chrome and other browsers provide per-site controls for camera, microphone, location, notifications, pop-ups and downloads, but the menu path differs by platform. Start with Ask or Block. When you initiate a voice recording, grant microphone access only to the verified site and revoke it afterward if it is no longer needed.
A file picker can provide one selected file without broad gallery access. Conversely, granting a browser broad photo or microphone permission can affect more than one website depending on OS and browser controls. Review both browser site settings and operating-system app permissions.
Private browsing has a narrow purpose
Private or incognito mode is designed mainly to reduce what remains in the local browser profile after the session. It does not conceal the visited service from the network, employer, school, internet provider or service itself. Signing into an account still identifies that account to the provider. Bookmarks and downloaded files can remain.
Use it when reduced local history is valuable, not as a promise of anonymity. On a shared or managed device, avoid the session entirely if local or administrative visibility would cause harm.
Passwords, autofill and account recovery
A shared browser profile can offer to save a password, email address or payment form. Decline saving when other people use that profile. A separate password manager account may improve separation, but recovery email and notifications can still expose the service. Review those channels before creating an account.
If login fails, avoid repeated password resets until you identify cookie blocking, cross-site tracking protection, pop-up restrictions or an expired session. Test the official login page in an updated browser and record the error without exposing credentials.
Downloads and image handling
A browser download usually leaves the webpage’s storage boundary and enters the device file system. On iOS, inspect Files and the Safari download destination. On Android and desktop, inspect Downloads and the browser download list. Saved images may also enter Photos or a gallery and trigger cloud backup.
Choose the destination before downloading sensitive fictional media. Rename or move files only as your workflow requires, and remember that local cleanup says nothing about service-side retention.
Field note: leave the browser in a known state
A browser comparison is most useful when you know its starting state. Record whether third-party cookies, cross-site tracking protection, strict content blocking, VPN or managed-network filtering are active. These controls can influence login and embedded payment or media frames, but disabling every protection at once is not a valid diagnosis. Use the official site, make one temporary change, retry one harmless action and restore the setting if it does not matter. If a second updated browser works, document the difference instead of declaring the first browser unsupported for everyone.
At the end of a no-download test, sign out through the service interface, close the tab and inspect the browser’s site-data entry, password manager, autofill history, download list and open-tab synchronization. Remove only the local elements you intend to remove. A bookmark can remain even when site data is cleared; a downloaded file can remain after history is erased; a recovery email can remain after the browser session ends. This exit checklist is the practical difference between “I did not install an app” and the unsupported assumption that the device kept no trace.
Evidence boundary
What product documentation and the current interface can confirm
Use the provider’s official pages and the version open on your device. Record only what is stated or visible now. A screen can confirm that a control is presented to this account; it cannot prove behavior for every region, plan, operating system or future release.
- Official web domain and current browser support statement
- Browser version and site permissions visible now
- Whether the current interface supports the needed action
- Exact local destination of a harmless test download
- Sign-out and site-data behavior on this device
Version caveat: Browser storage, notification support, upload pickers and private-mode behavior vary by browser, operating system and account policy.
Device questions
Frequently asked questions
Is browser use more private than an installed app?
Not automatically. It changes the local control surface. Privacy depends on browser settings, device sharing, network visibility and provider practices.
Will closing an incognito tab delete a downloaded image?
No. Downloads can remain after the private session ends. Locate and manage them separately.
Can I add a browser service to my home screen later?
Often, if the browser and site support it. Follow the PWA guide and confirm what the resulting icon actually launches.
Optional next step
Apply the device checks to a current product surface
Only continue after you know which access method, permissions and notification settings you will accept. These links are sponsored; verify the current official interface and terms yourself.
Candy AIOpen the current product surface after completing the device preflight.Check current access →
OurDream AICompare the current app or web route on the device you intend to use.Check current access →
Joi AIInspect the available interface without assuming store and web parity.Check current access →
Darlink AIUse the guide first, then verify the exact media and permission flow shown.Check current access →Open the full product access directory
These are access links, not feature endorsements. Complete the compatibility checklist and verify the current product screen before granting permissions.
