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, Google Analytics SDK, or Advertising ID integration.
Optional Founder’s Pass account, audio and text processing and technical crash reports are described separately below. These service records are separate from disabled usage and AI telemetry.
Optional Android crash reports
Starting with configured Android version 2.10.3, Summer offers Firebase Crashlytics for uncaught Java crashes. Reporting is off by default. It starts only after you enable it in Settings, explicitly close Summer, and reopen it. There is no Google Analytics integration through this feature. ANR (freeze) reporting and optional OS memory profiling are disabled in this update; no raw native-memory dump SDK is included.
If you opt in, reports sent to Google Firebase over HTTPS can include exception messages, thread stack traces, app version, device and operating-system diagnostics, and SDK-generated installation and session identifiers. These are used to diagnose and fix crashes. Summer adds no browsing breadcrumbs, custom browsing logs, URLs, account identifiers, or advertising identifiers. Exception messages can nevertheless contain values supplied by application code, so these reports are not guaranteed to be free of application-provided information.
Changing the preference requires closing and reopening Summer to fully apply. Turning reporting off saves that choice and requests disabled collection and deletion of unsent reports. Deletion is best-effort. Reports already handed to Firebase transport, including queued transfers, may still be delivered and cannot be recalled. Enabling reporting again authorizes sending retained reports from regular sessions.
When reporting may be active, private browsing is blocked until you turn reporting off and close Summer using the prompt. After reopening, repeat the private action. Cancelling or a failed preference save leaves private browsing blocked. Summer does not retain a private URL or action for this restart, and a fresh process with reporting off does not initialize Firebase.
Summer does not currently provide a per-user request mechanism for deleting uploaded Firebase crash reports. Google processes and retains reports under the Firebase privacy and security terms. This optional diagnostic feature is separate from website permissions and ordinary web browsing.
Technical crash reports on supported desktop builds
Supported packaged desktop builds enable privacy-filtered technical crash reporting by default. You can turn reporting off in First Setup or About, or use the private mode control for communication with Summer-operated servers. Turning reporting off deletes unsent reports and prevents future reports, but cannot retract a report already accepted by the collector.
Reports contain bounded technical incident and runtime details, not URLs, tab titles, browsing history, page or form contents, credentials, cookies, tokens, clipboard data, prompts, profile identity or private-window state. HTTPS requests carry ordinary connection metadata to the collector.
Reports are sent to the Hike Tech-operated collector at https://crashes.summerbrowser.com/v1/reports. Full reports are restricted to authorized Hike Tech operators and deleted automatically after 30 days, or earlier by an authorized operator. Bounded operator email notifications have separate provider and mailbox retention.
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.
Optional Founder’s Pass account and cloud processing
Founder’s Pass is optional on supported desktop and Android builds. You can use the browser without signing in to this service. Requesting an email sign-in code sends your email address to Summer’s hosted account service and to Resend, which delivers the code. Verifying a new email address creates a Summer account. Summer stores the email address and account identifier; sign-in codes and service-session tokens are stored as server-keyed hashes. The browser keeps its session credential in privileged profile storage on desktop or Android’s native Keystore-protected session store, rather than exposing it to websites.
When you request managed transcription, the recorded audio and any selected language are sent over HTTPS to Summer’s service at https://crashes.summerbrowser.com and forwarded to OpenAI to produce the transcript. Transcription happens before you review the returned text for insertion; reviewing or cancelling insertion does not retract audio already submitted for processing. Android uses temporary app-private recordings and attempts to delete them when the recording operation is disposed. The hosted audio inspector writes a private temporary probe file and attempts cleanup after the probe process ends. Founder’s Pass cloud operations are unavailable in private browsing. The desktop control for communication with Summer-operated servers also blocks these service calls.
On desktop, explicitly selecting Founder’s Pass cloud text or page translation sends the requested text or plain-text page fragments and target language to Summer’s service and OpenAI. Page loading and failure of on-device translation do not start cloud translation automatically. Android’s Founder’s Pass integration provides account access, linked sessions and managed dictation; it does not add Android cloud text or page translation, checkout or subscription-change controls.
The hosted service keeps account-linked paid periods, payment/order and provider references, hosted checkout URLs, usage quantities, operation identifiers, content fingerprints, and processing outcomes to enforce access, quota and replay checks. These service records are separate from the disabled usage and AI telemetry described above. The persistent Founder’s Pass database does not store raw audio, transcripts, translations, payment-card details or provider API keys. Desktop subscription checkout uses PayPlus’s hosted payment flow; Android can use the existing paid account. Session expiry and sign-out do not delete the account or its associated billing and usage records.
If you use My Devices to link profiles, a short-lived linking grant lets another authenticated group member obtain a separate, restricted service session for the same account allowance. The service stores the account’s group/member bindings and grant identifiers, status, expiry and hashed authentication proofs. Email sign-in tokens and allowance balances are not copied as Mesh records. Each linked device keeps its own service credential; linking does not give it email-session billing controls.
Summer’s service necessarily processes the submitted audio or text; OpenAI receives that content. Resend receives sign-in/deletion-verification recipients and codes, and the recipient and reference for a deletion-completion notice. Requests also carry ordinary network metadata to the receiving service. Temporary-file cleanup and provider storage settings are not promises of zero provider retention.
Deleting a hosted Founder’s Pass account
Use Delete Founder’s Pass account in account settings or the account-deletion page. Verify the existing email and explicitly confirm the request. Verification alone does not delete the account. The Summer operator processes confirmed requests within seven days, stops future renewal before erasure and removes hosted identity, sessions, linked-device credentials, usage records and remaining access. Deletion does not automatically issue a refund or erase local bookmarks, downloads, browser profiles or the separate Mesh identity.
Restricted payment/order/charge/refund and necessary replay records are retained for eight years after local erasure, longer where law or a documented legal hold requires. The actual accounting cutoff is checked before cleanup. Opaque former account/request references remain for eight years and until Summer’s associated retained payment records and restorable pre-erasure copies are gone. These references cannot sign in or grant paid access.
Completion evidence is retained for 90 days after local erasure. The notification address is removed when completion is recorded, or at its approved expiry if notification remains unresolved. Managed account-database backups are currently disabled. Any future backup copies have a maximum 30-day retention and require a deletion-safe restore procedure before use.
PayPlus may retain legally required payment records. Applicable requests for provider-held data follow the providers’ supported processes and lawful retention rules. Local account erasure does not promise zero provider retention. See PayPlus’s policy and Resend’s retention and deletion information. Use the contact channel below for questions about your account or records.
Language detection and page translation
Summer can offer translation when a page declares, or an already-installed on-device detector identifies, a language outside the active profile's understood languages. Page loading does not trigger a detector-model download.
With the on-device provider, translation starts only after the user selects Translate. Summer may download an allowlisted language model after that request and cache it locally. The model host receives the ordinary network metadata required for that download, but not the page text. Translation inference runs on the device, without a remote text-translation fallback. Language and site exceptions remain in the active local profile.
Desktop users can instead explicitly select the Founder’s Pass cloud provider. That choice sends the requested text to Summer and OpenAI as described above; it does not change on-device translation into an automatic cloud 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.