Skip to main content
Xish Community
Controlled development environmentXish Community is still completing its launch standard. Public policies remain drafts until formally reviewed and approved.

Policy foundation

Draft terms of service

A reviewable structure for future terms. It is not yet effective and introduces no price, payment or launch commitment.

Draft status and product owner

These draft terms are provided to structure business-owner and professional review. They are not yet effective terms of service and do not create a new price, payment obligation or public-launch commitment.

Xish Community is a commercial SaaS/PWA product of PBG Communications Ltd.

Authority and account responsibility

A person creating or administering a community should have authority to act for that community and should keep account credentials secure. Login accounts, Member Register records, roles, households, properties and financial responsibility are separate concepts.

The final terms must define eligibility, authority evidence and the process for disputed control before becoming effective.

Community records and acceptable use

Communities are expected to enter records lawfully, grant least-privilege access, correct errors through the available accountable workflows and avoid uploading or publishing content they are not authorised to use.

The effective terms still need professionally reviewed prohibited-use, moderation, complaint and enforcement provisions.

Financial and residential boundaries

Community finance records describe obligations, reported payments and accountable corrections; they are not bank accounts. Reported quotations and project finance records are not proof that Xish executed a payment.

Community-reported property, household, ownership and occupancy records are administrative records and are not legal-title or contractual-liability verification.

Plans, providers and service availability

The current Development plan is unpriced and reporting-only. This draft introduces no paid plan, automatic renewal, storage purchase, refund promise or enforced limit.

Provider availability, maintenance, security response and service-level wording must match the systems actually active when final terms are approved.

Suspension, termination and history

The final terms must define proportionate suspension, termination, export, retention and restoration procedures. Accountable records may remain where security, financial, governance or legal history must not be silently rewritten.

This draft does not authorise automatic suspension, deletion or migration of an existing community.

Intellectual property, complaints and legal terms

The effective document requires reviewed provisions for ownership, licences, feedback, complaints, liability, indemnity, governing law, dispute handling and changes.

No governing-law, jurisdiction, liability cap or broad disclaimer is asserted here without professional review and product-owner approval.