Draft for review. This page describes how Wishew's public website and browser-based app use cookies and similar technologies. It is working text, not an approved legal notice. The details must be checked against the live production configuration before this policy is finalized.
What This Policy Covers
Cookies are small pieces of information that a website asks a browser to store and send back on later requests. Similar technologies include browser local storage and tags that record an interaction. This policy covers Wishew's website and browser-based app. The native iOS and Android apps use platform storage rather than browser cookies; our Privacy Policy explains personal data handling across the Services.
Sign-In and Service Cookies
The browser-based app uses first-party, HTTP-only cookies to keep a signed-in session: wishew_at carries the access credential and wishew_rt is used to renew it. The browser sends these cookies to Wishew's API; app JavaScript cannot read them. They are cleared when the web session is ended. Their maximum age follows the configured refresh-session lifetime, which currently defaults to 30 days and may differ by environment.
When a visitor follows a shared Wishew link, wsh_aid may hold a signed, anonymous identifier so Wishew can recognize subsequent share-link activity. Its configured lifetime is one year.
Blocking these cookies may prevent sign-in or affect the related service feature.
Browser Storage and Preferences
The browser-based app may store limited information on the device, such as language preferences and onboarding progress. It also stores a random browser-installation identifier in local storage (wishew:web-installation-id) for a weak continuity signal used by the service. That identifier is not a hardware identifier. It remains until browser storage is cleared or the app's privacy reset removes it.
Browser storage is separate from cookies, but this policy includes it because it can also retain information between visits.
Analytics and Marketing
Wishew uses its own service activity data to understand how the platform is used. Where an optional advertising integration is enabled and the applicable marketing choice permits it, a provider's tag may use cookies or similar identifiers for attribution and conversion measurement. For example, the browser-based app has an optional Google Ads conversion tag that can use a Google click cookie (_gcl_aw). The tag is not a feature of the public landing page itself.
The exact optional technologies, provider settings and retention periods must be verified before this draft is approved. This page does not itself provide a consent control. The availability of controls for optional technologies also needs confirmation before the policy is finalized.
Third-Party Services
Payment, identity verification, top-up and withdrawal flows may open pages or interfaces run by other providers. Those providers may set their own cookies or use similar technologies under their own notices. Review the provider's notice when using its service.
Your Choices
You can usually inspect, block or delete cookies and local storage in your browser settings. Removing essential session cookies will sign you out or interrupt a feature. If you have questions about optional technologies, this draft or Wishew's data practices, contact support@wishew.com.