Privacy Policy
Product-specific information from the documents bundled with this app.
Bundled document version: 2026-09-12. Publisher: WebbieFourth.
This document concerns the Portraint browser app. References to offline documents and policy screens describe screens inside the app, not this website. Other Portraint products have separate policies.
Scope and contact
This policy describes how this product handles information. Website operators, VPN providers, DNS resolvers, mail providers and platform services have their own privacy practices. For questions about your information or applicable privacy rights, contact WebbieFourth at webbiefourth@gmail.com.
Browsing and local records
The browser processes website addresses, page content and navigation state to display the pages you request. Regular tabs, history, bookmarks, preferences and download metadata can be stored locally, including through the existing Keychain-backed stores. Websites can store cookies and other site data in WebKit. Downloaded files may remain in their selected storage location or in another app after you export them. Available history, site-data, download and privacy controls have different scopes; do not assume one action erases every copy.
Private browsing and identity controls
Private tabs use nonpersistent WebKit website storage and are excluded from ordinary browsing-history recording. Information you explicitly save, bookmark, download, copy, share or send to support can remain outside that private session. Private browsing and identity controls do not make you invisible to websites, your network or all fingerprinting methods, and are not a guarantee of forensic erasure.
On-device content rules
The browser loads bundled ad and tracker rules locally. The app does not download these rule lists at runtime or send page addresses to a publisher filtering service for a blocking decision. Native WebKit rules can block requests or hide matching page elements, so filtering changes what loads or is displayed. Reader Mode separately reformats a page when you request it. These browser features are not the DNS-only Content Guard provided by the standalone Protection app.
Networking still occurs
Browsing, search, website subresources and downloads communicate with the services involved. The selected search engine receives submitted searches. Enabled DNS-over-HTTPS communicates with the selected resolver; it protects DNS transport, not all device traffic. WireGuard and OpenVPN use the selected server and profile; Tor and bridges contact the services needed for their route. Network diagnostics can contact test endpoints. Your network, resolver, VPN operator and destination services may observe information according to their roles. These information screens themselves request no online documents and do not start or change a connection.
Site permissions and threat checks
Popup Allow and Block decisions are stored per site origin in the existing Keychain-backed storage. Ask removes the saved decision. Private-tab popup decisions stay in memory for that tab and are not persisted. Explicit blocked-website rules are stored separately in Keychain and apply to matching navigation and download destinations in regular and private tabs. They are not inferred from browsing. Unblocking removes only that user rule, not threat protection. Forensic wipe removes both records. Unapproved popup attempts are stopped; after choosing Allow popups, repeat the action. Threat checks use a separate bundled HaGeZi TIF MINI snapshot and native WebKit rules without sending browsing addresses to a reputation service. Lists update with app releases, can become outdated, may contain false positives and do not certify downloaded files as safe. Threat blocks have no user bypass.
Profiles, permissions and device features
VPN profiles and sensitive connection material use the existing local and Keychain-backed storage. The browser and its own extensions share the data needed for routing; the standalone Protection product has separate storage. Optional app-lock, motion and privacy-shield features use device capabilities and permissions. Camera-based privacy checks and device authentication are not a promise of protection against every observer. Removing the app may not remove every Keychain record, exported file or system VPN/DNS configuration.
Counters and diagnostics
Connection counters are shown locally. Development and operating-system diagnostics can contain hostnames, navigation events, timestamps, route state, profile labels and error details, and recovered diagnostic entries can persist between runs. They should not be treated as anonymous. Review logs before sharing them and do not include passwords, private keys or sensitive profiles. Private browsing does not guarantee removal of operating-system or development logs.
Support and policy changes
Opening these policy and notice screens sends no support email and does not fetch documents. If you choose to email support, your mail provider and the support inbox receive what you send. The publisher does not use browsing activity to sell advertising or build marketing profiles. Contact support with access or deletion requests relating to information you have sent us. Do not include information unnecessary for your request. Rules and these documents are revised through app updates. Contact the email below for privacy questions; this policy does not limit applicable legal rights.