1. Scope and acceptance
These draft terms are intended to cover the pipipong.com website and the publicly downloadable macOS beta build. The current technical preview does not require an application, name, email address, or invitation. Testers may still need to review final terms and build-specific information separately when installing or using the client.
A user who does not agree to the terms in force at that time should not install or use the beta client. Anyone participating for an organisation should make sure they are authorised to do so.
2. Free beta status
Pipipong is currently in public free beta. The v0.9.5 technical preview is available for Apple silicon Macs running macOS 14 or later; the app bundle currently appears as Voice Router Pet. Features may be incomplete, change, pause, or contain errors. Windows remains in development, with no public test date announced.
The current Mac build is ad-hoc signed and has not been notarized by Apple. Gatekeeper may therefore show a warning, and first launch may require Control-clicking the app in Finder and choosing Open. This is a technical preview, not a Developer ID-signed, Apple-notarized production release.
A "free beta" does not promise that a future public version will be free. Any later pricing, features, or eligibility changes should be announced before they take effect.
3. Direct download and access
Access to the current Mac technical preview begins with the direct download; there is no application queue or invitation requirement. Availability may still be changed or paused for security, capacity, legal, or product reasons, and current access does not guarantee access to future builds or services.
Use the official download page and published checksum where available. Do not repackage a modified copy, misrepresent its signing or notarization status, or present it as an official Pipipong release. Follow the documented Finder opening method instead of disabling system-wide security protections.
4. Permitted use and prohibited conduct
A tester may evaluate Pipipong only on devices, accounts, files, and applications they are authorised to use. Pipipong must not be used to infringe rights, bypass access controls, distribute malware, perform unauthorised surveillance or automation, disrupt a service, or carry out unlawful activity.
Users must not instruct the product to access data or systems they are not entitled to use. The permitted scope for security research, reverse engineering, and vulnerability testing, together with the reporting process, still needs to be defined in the final testing rules.
5. Task confirmation and user responsibility
Pipipong aims to show its task interpretation, action scope, and risks, then request confirmation before sensitive actions. Users still need to review voice transcripts, execution plans, permission requests, file differences, and final results—especially for deletion, overwrite, sending, payment, publication, or account changes.
Users should keep backups of important data and stop a task when it moves outside the expected scope. Any automation tool can misunderstand a request or fail during execution and cannot replace the user's judgement on critical decisions.
6. AI output and third-party tools
Pipipong may connect Codex, APIs, or other available tools chosen by the user. AI-generated content may be inaccurate, incomplete, or unsuitable for a particular purpose and should be checked before it is adopted, submitted, or published.
Third-party services may have separate accounts, fees, limits, licences, and privacy terms. Pipipong should not be understood as guaranteeing that every third-party service will remain available or suit every task. Actual support depends on the build notes.
7. User content and uploaded assets
Users retain rights they lawfully hold in their content and must have permission to provide task material, photographs, reference images, code, files, or other content. Users must not upload material that infringes copyright, trade marks, privacy, image rights, or other rights.
Custom-pet generation and community sharing have not launched. Before either is enabled, final terms must define the licence needed to process user assets, ownership of generated material, public-sharing choices, deletion, and complaints. This draft does not grant a broad content licence beyond what is needed to provide the requested service.
8. Pipipong intellectual property
Rights in the website, client, brand, character design, interface, documentation, and related technology remain with their respective owners. Beta access permits evaluation under the final terms and does not transfer intellectual property.
The brand-use guide and media permission process for Pipipong are awaiting confirmation. Placeholder structure on the press page is not permission to use a logo or asset publicly.
9. Feedback
Testers may voluntarily submit bug reports, experience notes, and improvement ideas. The final terms should explain how feedback can be used without treating a user's underlying content or confidential information as ordinary feedback. Remove unnecessary personal or confidential data before submitting it.
10. Privacy and data processing
Personal information and task data should be handled according to the privacy notice, product settings, and task prompts in force at the time. Before choosing third-party AI or granting microphone, file, or application access, users should understand the relevant data path.
11. Changes, suspension, and termination
Beta features or access may be changed or suspended to protect security, fix problems, manage capacity, or address abuse. Material changes should be explained in advance where practical, except in an urgent security situation.
A user may stop using the beta and request deletion of any related personal information through the process available at that time. Uninstallation, data export, and deletion procedures are still to be confirmed for the released client.
12. Beta risk, warranties, and liability
Beta software is provided in a testing state and may be interrupted, misinterpret requests, act incorrectly, or lose data. An unverified build should not be used for life-safety, medical, legal, financial, critical-infrastructure, or other high-risk decisions.
Any warranty disclaimer, indemnity, and liability cap must be drafted for the operating entity, applicable law, and consumer rights that cannot be excluded. This draft does not attempt to impose an absolute exclusion that may be invalid or unfair.
13. Applicable law and disputes
The operating entity, applicable law, jurisdiction, and dispute-resolution process have not been determined. The final terms must add those details while preserving consumer rights that cannot lawfully be excluded where the user lives.
14. Contact us
Contact channel for questions about these terms, beta access, or rights: official contact email to be confirmed and published by the product owner.