Terms of Service

Draft prepared 5 October 2026 · Effective date: set before launch

1. Operator and acceptance

HACALL Holo is operated by legal operator name not provided — complete before launch, based in country not provided — complete before launch. These terms are a draft and are not ready to govern public accounts. Before launch, the operator must decide how users will be shown and accept the final terms, and have the final wording reviewed for the intended markets.

Privacy questions: add a public legal/privacy contact email before launch. Read the Privacy Policy draft for the information handled by the app.

2. Service

HACALL Holo provides username-based accounts, private text and hologram voice messages, profile holograms, and personal or commercial audio channels with product or service presentations. The service is not for emergency communications. Features and availability may change; no uptime commitment is currently stated.

3. Eligibility and accounts

HACALL Holo is for adults aged 18 or older only. People under 18 may not create an account or use the service. The app requires users to confirm this age requirement during account setup and sign-in; this is a self-declaration and does not independently verify age. The operator should confirm whether additional age-assurance measures are required for the intended launch markets.

Keep your password and private recovery code safe, and protect devices signed in to your account. HACALL Holo does not collect an email address or phone number for account recovery. A forgotten password can be reset only with the private recovery code created for your account; without that code, the encrypted key vault cannot be recovered. You are responsible for activity on your account and for signing out of shared devices.

4. Private chats and channel content

The current client encrypts private chat messages and voice-message audio before sending them to the service. The service stores encrypted chat payloads and the metadata needed to route them. This draft does not certify the cryptographic design or replace an independent security review.

Channel episodes, channel descriptions, product information, and images are different from private chats: they are stored as channel content and can be viewed by signed-in users through the app. Do not publish material you do not have permission to share.

5. Your content and conduct

You keep ownership of content you submit. To operate the features you choose, the service needs permission to store, process, transmit, and display that content to you and the people you select or to signed-in channel viewers. The final scope and duration of that permission must be confirmed by the operator and qualified counsel before these terms are activated.

Do not use HACALL Holo to break the law, threaten or harass others, impersonate someone, distribute content without rights, interfere with the service, or attempt to access another person's account or data. You can block other users within the app.

6. Commercial channels and payment status

The current app describes a 12-month free period for commercial channels and a $5/month plan afterward. The code enforces the plan gate, but checkout and payment processing are not connected. No subscription payment is currently collected by this build. The operator must not advertise active checkout or charge users until a payment provider, taxes, billing frequency, renewal, cancellation, refund terms, and paid-access process are implemented and this section is updated.

7. Account deletion and service limits

You can delete your account from Me → Account → Delete account after confirming with your current password. The current app removes the account's profile photos, sessions, channel, episodes, product listings, blocks, and message records involving that account from its active database; your username becomes available to others. Other participants will no longer see those message records in HACALL Holo. Backup retention and the time to remove data from infrastructure backups are not specified. Those details must be established before launch; see the Privacy Policy draft for local browser storage details.

The operator may need to restrict or suspend accounts to protect users or the service, but suspension and appeal procedures have not been defined in the current app and must be reviewed before publication.

8. Third-party services

The current build uses Replit hosting and PostgreSQL, Google Fonts, and cdnjs-hosted Three.js. Their services have their own terms and privacy practices. The operator must confirm the complete provider list and any applicable notices before launch.

9. Terms that still require legal review

Governing law and courts, formal notice methods, warranty wording, liability limits, termination procedures, and change-notice periods have not been supplied or resolved. They are intentionally not invented here. A qualified lawyer should complete and review these terms before public registration.

10. Items to resolve before publication

• Insert the legal operator, operating country, contact email, minimum age, and effective date.
• Decide and implement the final acceptance flow and rules for suspensions, appeals, and account deletion.
• Keep checkout described as inactive until payments, cancellation, and refund processes are actually live.
• Have qualified counsel review this draft for the intended markets.