Who this policy covers
This policy covers Summer Browser, published on Google Play by Tal Shalti and developed under Hike Tech Ltd, together with services operated by the Summer developer team. It applies to the Android, iOS, and desktop versions of Summer where the described feature is available.
Data Summer does not collect
Summer does not send browsing history, tabs, bookmarks, credentials, autofill records, payment-card records, cookies, searches, private profile data, or Mesh identity material to a Summer-operated collection server. Summer does not include an advertising SDK, analytics SDK, or Advertising ID integration.
Data stored on the device
Depending on the platform and features used, Summer stores tabs, bookmarks, settings, download metadata, site-permission decisions, language preferences, Summer App settings, and other browser state locally. Completed download files are stored in user-visible device storage or another destination the user selects.
Protected Summer App settings and Mesh secrets use platform-protected storage. On Android this uses Android Keystore-backed encryption; on iOS it uses a non-synchronising, device-only Keychain service. The offline Mesh experience creates or restores identity material locally and does not start discovery, signalling, routing, record storage, peer transport, or a public network.
Web browsing and third-party services
Summer is a web browser. When a user opens a website or uses a search provider, that destination receives ordinary network information such as the IP address, requested URL, browser headers, and data the user chooses to submit. Websites can set cookies and apply their own privacy terms. Summer can open both HTTPS and HTTP addresses; HTTP traffic is not encrypted by the website.
Websites, search providers, operating-system stores, and services opened through Summer are not operated by Summer unless they explicitly say otherwise. Their collection and sharing practices are governed by their own policies.
Camera, microphone, notifications, uploads, and downloads
A website can request camera or microphone access only through Summer's permission flow and the operating system's permission controls. If the user allows access, media is delivered to the website the user is visiting; Summer does not keep a separate copy or send it to a Summer server. Users can revoke saved site decisions in Settings or in device settings.
Notifications are optional and are used for enabled download-completion alerts, enabled bundled Summer App alerts, or a foreground website after the user allows that exact site. Summer does not operate a remote push-notification service for websites. Uploads, downloads, sharing, and opening external apps happen only after a user action and send data to the destination the user selected.
Summer Apps and address suggestions
Mobile Summer Apps are reviewed TypeScript modules bundled with the installed application; the mobile app does not download or evaluate remote Summer App code. A Summer App may receive only the capabilities declared in its manifest and provided by the mobile host. The bundled Captain Word provider contributes address suggestions but does not receive the user's bookmarks or tab data.
On versions that offer website artwork, enabling Load website artwork may contact the public website and its declared artwork host for a bounded set of displayed suggestions. Those requests contain no browser cookies, referrer, browsing history, or raw address-bar query, but the destination receives ordinary network information including the user's IP address and requested URL.
Translation features
On supported versions, translation starts only after the user selects Translate. Summer may then download an allowlisted language model and cache it locally. The model host receives the network metadata needed for that download, but not the page text. Translation inference runs on the device, and Summer has no remote text-translation fallback.
Retention, deletion, and security
Local data remains until the user deletes it through Summer or device controls, removes a download, resets the relevant setting, or uninstalls the app. Disabling the Mesh Summer App preserves its local profile and seed so that it can be recovered; deleting the app's device data removes that local copy. Users should keep their device and recovery material secure.
Summer limits privileged operations to reviewed native adapters and uses operating-system security controls for protected values. No software can guarantee absolute security, and the security of a visited website or third-party service remains that provider's responsibility.
Age suitability
Summer provides unrestricted access to the web and is not directed to children. Its Google Play target audience is adults aged 18 and over. Summer does not knowingly operate a service that collects personal information from children.
Changes to this policy
This page will be updated when Summer's data handling changes. The effective date at the top shows when the policy was last materially reviewed.
Contact
Privacy questions and reports can be sent to talshalti1@gmail.com. Do not include passwords, authentication tokens, payment-card details, private profile data, or unredacted logs in an initial report.