Wallpaper Cat
Privacy

Privacy notice

This is a product-facing draft for the website forms and their boundary with the desktop app. The publisher, data controller, and public contact emails will be injected by the operator at runtime; this copy does not invent a company, person, or address and is not a legal guarantee. Before publication, use the deployed configuration and applicable-law review as the source of truth.

Public controller and privacy contact: in preparation

The publisher, privacy contact, and public details are not configured yet; personal-data collection is not open to the public.

Scope and responsible party

This notice covers the Wallpaper Cat website, language preference, waitlist, confirmation and unsubscribe flow, and feedback form. Desktop saves and Steam features are separate from website form data.

The publisher, display name, data-controller identity, support email, privacy email, update date, and relevant operating address are injected by deployment configuration. Until configured, the page should show that these details are pending rather than presenting placeholders as a formal contact.

  • The website does not provide a game-account or cloud-backup service. Steam Cloud, statistics, and leaderboards are Steam features listed on the store, subject to the Steam client, settings, and applicable terms.
  • If the operator changes the purpose, provider, or retention period, the deployed configuration and public notice must be reviewed together.

What the website receives

When you actively submit the launch-notification form, the website receives your email, the locale selected at submission, the consent version, and form status, then sends a confirmation link. Confirmation records the confirmed state; the unsubscribe link lets you stop future notices.

When you submit feedback, the website stores the message, category, locale, consent version, and feedback status. A name is optional, and a contact email is optional; it is used to reply or associate the feedback only when you provide it. The website does not ask for your desktop save, fish names, window contents, or keyboard contents.

  • Waitlist: email, locale, consent version, confirmation state, unsubscribe state, and processing timestamps.
  • Feedback: category and message, locale, consent version; name and contact email are optional.
  • Confirmation and unsubscribe links use one-time tokens; tokens should not be exposed to third-party scripts or logs.

Storage, abuse prevention, and providers

Website data is stored in Cloudflare D1, and Cloudflare Turnstile is used for form abuse prevention. Resend is the planned email provider for confirmation, unsubscribe, or launch-notification messages. “Planned” is not a completed production configuration; before launch, the operator must confirm the actual provider, sender, and terms.

For short-term rate limiting, the service may turn a request IP into a short-lived hash. It is used to limit abuse windows rather than to permanently retain a plaintext IP; the exact window and key rotation are deployment settings to verify before launch. The website does not sell data, show ads, or add dedicated advertising or behavior analytics. The desktop app has no desktop telemetry promise in this scope.

  • Forms use same-origin requests and server-side validation; confirmation tokens should not enter third-party analytics or logs.
  • The operator must verify the actual region, terms, and transfer path for Cloudflare, Turnstile, and the email provider at deployment.
  • The desktop app does not use the website mailing list for pond features.

Local data in the browser and desktop app

The browser remembers a manually chosen website language in local storage and a language-only cookie. On the first root visit, Cloudflare's IP-country information suggests a language; unknown countries use English. This does not create a user profile. The app keeps pond data locally; Steam Cloud follows your Steam settings. Imported music, track names, selection, and playback mode remain in the local music library; importing does not upload music.

Website pages do not read the desktop app’s local save, and a website email cannot restore a pond. The final installer, uninstall behavior, and local-data erase flow still need verification on the release candidate.

  • Clearing site data in the browser clears that browser’s saved language preference.
  • Desktop-save retention and deletion depend on the final app implementation and operating-system installer/uninstaller behavior.
  • Development endpoints or test data are not presented as a production-service guarantee.

Retention targets in the development configuration

The following are target retention settings for the website backend, not a guarantee for every deployment, jurisdiction, or legal right. Before launch, the operator should confirm the actual values and make the page, database cleanup jobs, email provider, and external notice agree.

Pending launch-notification confirmations target 30 days. Feedback targets 180 days. An active confirmed subscription is kept until unsubscribe; a confirmed record after a notification is sent targets 90 days. Unsubscribe clears the email immediately; the current development worker targets 30 days for cleaning the remaining unsubscribed status row, and the operator must confirm whether production should use a different target. Retry records, audit records, backups, or legally required retention may have different periods and should be documented in the runtime configuration.

  • Development, preview, and production environments may have different cleanup jobs; this page does not turn a development value into a permanent promise.
  • Unsubscribe stops future notices and clears the email immediately; it does not necessarily erase security, audit, or legally required records immediately.
  • If cleanup jobs are not confirmed, public wording should say “retention target” and “subject to deployed configuration.”

Your choices and operator inputs

You can browse the website and manual without submitting an email. You can leave the optional name or contact email blank. A waitlist email should include confirmation and unsubscribe actions. Whether feedback receives a reply depends on whether you provide a contact email and whether the operator has configured an actual inbox workflow.

Before public launch, the operator needs to provide and inject the publisher/data-controller name, support email, privacy email, sender identity, email provider and region, applicable law, and a process for privacy requests. The operator must also confirm that D1, Turnstile, email, and cleanup settings match this notice.

  • Do not publish a sample email, placeholder domain, or unconfirmed name as a real contact.
  • For privacy or deletion assistance, use the formal privacy channel displayed on the page; until it is injected, the page should say that the channel is not yet open.
  • New analytics, advertising, desktop telemetry, live-weather services, or changes to Steam data handling require a review and an updated notice.

Boundary statement

This page explains current product design and development configuration. It does not replace legal advice, provider terms, data-processing agreements, or requirements in an applicable jurisdiction. If implementation, providers, publisher identity, or storage configuration changes, verify actual behavior before publishing an updated notice.

  • “Not found in reviewed code” has not been expanded into an absolute promise about future versions or differently packaged builds.
  • Website form data and the desktop app’s local pond data are kept as separate scopes.