universal1. About this policy
This policy explains how Universal Pets / UniversalPets.ai handles information for the website, desktop companion, Pocket phone app, optional product feedback, launch list and experimental Studio. Studio offers private account sign-in and pet-photo processing. We do not currently offer payments.
For questions or privacy requests, use our contact form and select “Privacy or deletion request.”
2. Information you provide
When you join the launch list, we collect your email address and consent to receive launch and early-access updates. You may also provide your first name, pet type, and preferred AI platform. Those additional fields are optional. When you contact us, we collect your email, optional first name, selected topic, and message.
If you apply for the beta, we collect your email, optional first name, Windows PC availability, Grok Build use plans, optional Android manufacturer, model and version, optional testing availability, and your required age and beta-contact consent. This is a separate application from the launch updates list. Do not send passwords, payment details, private AI conversations, or sensitive personal information through these forms. This marketing site does not ask you to upload pet photographs.
3. How we use information
We use launch-list information to send the updates you request, manage early-access interest, and understand aggregate interest in pet types and platforms. We use contact messages to answer questions, handle requests, investigate reported problems, and protect the service from abuse. We use beta application information to review applications, understand testing coverage, administer beta participation, and contact applicants about their application and related beta testing. Application information is separate from desktop or Android activity data. Application consent does not add you to general marketing. Applying does not guarantee an invitation or a date.
We do not sell your launch-list, beta application or contact information or use it for targeted advertising. If our practices change, we will update this notice and obtain any permission required before the new use.
4. Hosting, security, and service providers
Netlify hosts this website and processes form submissions for us, including beta applications. The beta application is collected as a separate Netlify form from the existing launch list and contact forms. Hosting and security services can process technical data such as IP addresses, request times, browser information, and security signals to deliver pages and detect abuse. Cloudflare is our intended DNS and edge provider; it may process connection and security data when traffic is routed through its services.
Service providers receive information needed to perform their functions. Netlify’s form service includes spam filtering. Access by the Universal Pets team is intended for administering the site and handling submissions. Provider practices are also described in their own privacy notices.
5. Cookies, local storage, and analytics
This site does not install advertising trackers. On public marketing pages, Google Analytics loads only after you allow it. It uses first-party cookies to measure visits, device/browser characteristics, broad interactions, and approximate city, region, and country derived by Google. Advertising personalization and Google signals are disabled. Private studio and download pages are excluded. We strip URL queries and fragments and do not send referrers, form contents, pet names, photos, account identifiers, or conversation content. Change your choice using Cookie settings in the footer. Declining optional analytics does not prevent using the site. Consent choices are saved for up to 180 days. Do Not Track, Global Privacy Control, and designated internal testing browsers suppress measurement. Google processes analytics data under its privacy terms: Google Privacy Policy. It stores an announcement-dismissal preference and your animation preference in your browser’s local storage. You can remove these preferences through your browser settings.
The website counts broad interactions such as page views, launch-button clicks, completed signups, platform interest, pet-species interest, and Trixie mood selections. A first-party Netlify endpoint stores daily aggregate counts by fixed page and event categories. These counters contain no email addresses, form text, pet photos, conversation content, IP addresses, browser identifiers, or individual event records. We honor Do Not Track and Global Privacy Control signals for these measurements. Hosting and abuse-prevention systems separately process technical request data, including IP addresses.
6. Pet photos, Studio and gallery permission
Studio asks for permission before sending pet photos to Google Gemini for safety screening and visual review, and to the selected image provider, Google or OpenAI, for creation. Uploaded images are resized and their metadata removed before private storage. Studio photos and temporary projects expire after seven days and have deletion controls.
Gallery permission is a separate, optional, unchecked choice. It covers approved pet artwork, animations and the pet name, followed by our publication review. It does not cover original photos or account details. Use Contact & Support to withdraw gallery permission. Joining the launch list grants no photo-processing or gallery permission.
7. Desktop connections and shared updates
The desktop companion uses configured local coding-agent reporters, supported hooks and connected browser pages. Local reporting can include an explicitly supplied task label and short progress sentence. Progress sharing is a separate choice from final-response previews. Gemini and Grok current assistant output is also a separate, optional choice for the connected page; it is not permission to collect your prompts, unrelated conversation history or hidden reasoning.
Shared update text is bounded and held locally in memory. Grok Build session findings can remain visible after the session closes so you can catch up before restarting the companion. This beta does not store a 24-hour content history. Preferences and content-free diagnostics can be stored locally. Disable sharing through the current source options to stop forwarding and clear captured content. Some session choices need to be made again after a restart; a session grant does not automatically become a remembered grant. Trixie and compatible local pet imports do not require a Universal Pets account.
Agent credentials remain with the originating tools. Connecting an agent is not an account-wide subscription to its conversations, and Trixie does not approve work on your behalf. AI platforms still process what you submit to them under their own policies.
Desktop attention reminders. After an accepted native Grok attention event, the candidate automatically saves a small local reminder, separately from optional text sharing. The journal stores an opaque session identifier, timestamps, app-run and generation identifiers, and record bookkeeping—not prompts, replies, tool input, task labels or terminal paths. It holds up to 64 pending reminders in two journal segments, each limited to 64 KiB and 256 records. Reminders stop being displayed after eight hours and can be dismissed; accepted closure or idle activity also retires them. Closing the app does not erase the journal. Expired or dismissed metadata may remain until bounded journal rotation removes it. Restored reminders are unconfirmed history, do not establish live contact and do not enable terminal navigation.
8. Universal Pets Pocket on your phone
Public demo and private test builds differ. The public Pocket web demo and Android 0.3.2 test build show an example feed and cozy play; they cannot pair with real agents. Private 0.4 Android Watch candidates add local pairing and native monitoring, still awaiting physical delivery, battery and release qualification. See current release status before following a test guide.
Local play. The demo feed is built into the app. Petting, nicknames, backgrounds, sound, vibration and motion preferences, and the moments journal are stored locally. Moments record the time, kind of moment and animation (at most 60 entries, up to 30 days), never agent data; Clear moments removes them. A portrait leaves the phone if you choose to share it. Pocket does not load analytics.
Private 0.4 Watch pairing. The computer sends lifecycle metadata, not prompts, transcripts, code, paths, tool output, replies or reasoning. The connection uses authenticated updates over HTTPS pinned to the confirmed computer. It connects directly over reachable local Wi-Fi, with no Universal Pets cloud relay or cloud push provider. This replaces the older developer-only plain-HTTP experiment; that older experiment is not the public demo or the 0.4 pairing guide. Do not use its links for current pairing.
The pairing QR or link contains a credential; keep it private. Camera access is used when you choose Scan computer; a paste-link fallback is available. Confirm the named computer before saving. Android stores the pairing record encrypted with a nonexportable Android Keystore key. Closing Pocket or selecting Stop does not remove the saved pairing. Use Unpair to remove it; retry if the app reports that removal could not be completed. Computer revocation withdraws live authority and alerts and attempts to clear saved pairing and recovery state.
Recovery storage. Private 0.4 Android Watch saves a replay cursor and a bounded recovery ledger of up to 32 source entries across restarts. These records contain source/event identifiers, app categories, states, generations and timestamps; they exclude free status text, custom source labels and response links. The ledger has no fixed age-based deletion promise. Nonsecret recovery/control preferences are not claimed encrypted. Android backup and device-transfer rules are configured to exclude the app’s data.
Optional notifications. Attention uses a known tool name and fixed status wording. The monitor supplies a generic public lock-screen version, but actual visibility depends on Android and lock-screen settings. Screen-off watching requires explicit Start, notification/channel readiness, battery exemption and recovery readiness. The PC must remain awake and reachable with Universal Pets running. Stop stops monitoring; an explicit saved Stop remains stopped until Resume or Start. If saving Stop fails, monitoring stops in the current session and the app asks you to retry before closing. Force Stop or phone restart ends screen-off watching; reopening can reconnect in the foreground unless explicitly stopped, and screen-off watching needs Start again. Do Not Disturb, Doze, OEM power controls and network changes may delay or suppress delivery. Physical qualification is unfinished.
Sharing a test report. An optional readiness report is created locally with build, readiness, control and last-contact information; it contains no event content or pairing credentials and is not automatically sent. Share it only if you choose. Watch activity is not sent to Universal Pets servers. Optional Studio/account library services are separate from Watch; automatic custom-pet synchronization is outside 0.4.
9. Accounts and your pet library
Studio uses Netlify Identity with Google sign-in. Account information is used to authenticate you and restrict access to your projects and pet library. Netlify Blobs stores private Studio records, library packages and preferences. A completed, signed pet is copied to the durable library only when you select Add to my library. That copy contains its manifest, animation atlas and review receipt, not source photos or private Studio review records.
Previously connected devices sync your selected pet, nickname, background and optional sound, vibration and motion preferences. Downloaded pets and preferences are cached locally for offline play. Native device credentials are stored in iOS Keychain or Android Keystore; the server stores a hash of the credential. Pairing requests expire after ten minutes and device sessions after thirty days. Signing out revokes the current reachable device session and clears private local downloads, preferences and cached portrait files. It does not delete your cloud library.
Device connection pages do not load optional analytics. Payments are not offered and we do not collect card numbers.
10. Retention and deletion
Studio photos and temporary projects expire after seven days. A pet you explicitly save to your pet library is retained separately so it remains available after its Studio project expires. During this early preview, request deletion of your account or cloud library through Contact & Support. Local sign-out alone does not remove cloud records. Expired pairing and device-session records are removed by scheduled cleanup.
We retain launch-list information while administering launch communications and early-access interest, unless you ask to leave the list or delete your information. We retain beta applications as needed to review applications and administer beta participation; no automatic expiry period is promised. Contact messages are kept as needed to address the request, maintain necessary records, and meet legal or security obligations.
Use the contact form to request deletion, correction, or removal from the launch list or beta application records. Include the email used for the application so we can find the record. We may need to verify control of that address. Limited information may remain where required for legal obligations, dispute handling, or security; service-provider backups may follow separate deletion cycles.
11. Your choices and rights
You may choose not to provide optional form fields or not to join the list. You can ask us to stop launch updates or withdraw beta-application contact consent at any time through the contact form. Depending on your location and applicable law, you may have rights to access, correct, delete, restrict, object to processing, receive a portable copy of information, withdraw consent, or complain to a supervisory authority.
We will assess and respond to requests as required by applicable law. Withdrawing consent does not affect processing that was lawful before withdrawal. We will not require a purchase to make a privacy request.
12. Legal disclosures and business changes
We may disclose information when reasonably necessary to comply with applicable law or valid legal process, protect rights and safety, investigate fraud, or enforce our terms. If the product or its assets are transferred, information may be included subject to applicable law and notice of material changes.
13. Children and international visitors
The launch signup and contact service are intended for adults aged 18 or older. We do not knowingly solicit personal information from children. If you believe a child submitted information, contact us so we can investigate and remove it where appropriate.
Providers may process information in countries other than your own, including the United States. Legal protections may differ. Where applicable, required transfer safeguards and processing grounds must be established for the services offered in your location.
14. Security and policy changes
We use HTTPS, limited form fields, spam controls, and restricted administrative access to reduce risk. No website or transmission method can be guaranteed completely secure. Please report suspected issues through our contact form without including secrets.
We may update this policy as the service evolves. The effective date identifies the latest version. Material changes will be communicated as appropriate and as required by law. Contact Universal Pets / UniversalPets.ai through Contact & Support.
15. Product feedback and ideas
Feedback is optional. The feedback form sends the category, your message and a submission reference to our Netlify product-feedback inbox. A reply email is optional. In the desktop form, you can choose whether to include the displayed app details; private conversations, pet photos and credentials are not attached automatically. Review your message before sending.
We use submissions to investigate problems, consider ideas and respond when you provide an email. Feedback does not subscribe you to a mailing list. Netlify separately processes request metadata and spam-prevention signals as described above. Feedback records are kept as needed to investigate and respond; use Contact & Support for a deletion request and include your submission reference if you have one. Do not include sensitive information in a feedback message.