Mewie notices rhythms, not secrets.
Last updated: July 7, 2026.
Mewie is built as a local-first Mac companion. Her personality comes from simple signals on your Mac, not from reading private content. Markus Skov (enkeltpersonforetak, org.nr 920 721 869, Norway) is the controller for Mewie website, purchase, license, and support data.
Contact
Email support@mewie.app for privacy questions, support, refund requests, license help, or GDPR rights requests.
What Mewie can use
Mewie can use cursor position, app focus, typing rhythm, timers, explicit user actions, and local agent event kinds such as thinking, waiting, done, or failed.
What Mewie does not read
Mewie does not read typed text, prompts, code, terminal output, screenshots, messages, documents, browser contents, full local paths, full license keys, or receipt signatures.
Cookies and local storage
Mewie does not set first-party cookies on the website. The website uses two functional localStorage keys — mewie-pet-hidden (whether you hid the corner companion) and mewie-last-price (the last price shown, so buy buttons stay informative if the pricing service hiccups) — plus two functional sessionStorage keys: mewie-demo-video-played (a demo play is only counted once per visit) and mewie-ph-banner-dismissed (whether you closed the launch banner, for the current visit only). None of them are advertising or cross-site tracking identifiers.
Mewie does not show a cookie banner because the current website does not use non-essential cookies or non-essential local storage tracking. If that changes, Mewie should ask for consent before using non-essential tracking technology.
Website events
The website sends first-party events to licenses.mewie.app so checkout, release, community, demo, and pricing problems can be understood without third-party analytics. Event names are page_view, demo_video_play, download_click, trial_cta_click, community_click, checkout_click, checkout_session_failed, and pricing_unavailable.
Those events may include limited metadata: landing path, campaign/source parameters from the page URL, external referrer host, visible release version/build, CTA location, and page kind. Normal request metadata such as IP address, user agent, and timestamp may be processed by the server or hosting provider to deliver and secure the service.
Trial, licensing, checkout, and updates
The 7-day free trial starts inside the Mac app, not on the website, and no card is required. Trial and license activation send entitlement and device activation metadata to the licensing backend so the trial window, one active Mac, transfers, refunds, and deactivations can be verified. The backend should not store raw trial device identifiers; it uses hashed device/IP values and redacted receipt metadata for enforcement and support.
Checkout uses Stripe, and Mewie receives purchase and license metadata needed to deliver the license email, activate the app, handle refunds, and provide support. Sparkle update checks read the public appcast, and the website fallback reads the public release manifest.
Providers
Mewie uses Stripe for checkout and payment processing, Resend for transactional license email, Namecheap Private Email for support email, Namecheap for domain-related services, and hosting providers for the website, licensing API, logs, and delivery infrastructure. These providers process data only as needed for their service roles.
Checkout attribution
When you start checkout, the website may send privacy-safe source details to the licensing backend, such as campaign/source parameters, landing path, external referrer host, and the visible release version/build. It does not start trials, call trial endpoints, or send private browsing contents, typed text, license keys, device identifiers, or desktop activity.
Support reports
Support reports are redacted by design. They may include version, build, privacy signal status, diagnostics, and local counts, but not private content, full paths, license keys, activation receipt signatures, prompts, messages, or document contents.
Community
Mewie links to r/mewie for feature requests, launch notes, and Mewie setups. The app and support reports do not send Reddit usernames or community data. License/payment help stays at support@mewie.app.
Retention
Mewie keeps data lean. Website events are kept for about 90 days, and server logs are kept only as long as useful for security, debugging, and basic service health. Purchase, refund, and license records are kept as long as needed for activation, accounting, fraud prevention, legal obligations, and support. Support emails are normally kept for up to 24 months so support history can be understood. The mewie-pet-hidden and mewie-last-price localStorage values stay in your browser until you change the setting or clear browser data.
Legal bases and GDPR rights
Mewie processes data to provide the product and license service, fulfill legal obligations, and protect legitimate interests such as fraud prevention, security, support, and service reliability. Where consent is required, you can withdraw it.
If GDPR applies to you, you can request access, correction, deletion, restriction, portability, or objection. You can also lodge a complaint with your local data protection authority. Some records may need to be kept where required for accounting, legal, security, or dispute reasons.