What this draft covers
This draft describes the intended privacy boundaries of Xish Community. It is provided for product, business-owner and professional review and is not yet an effective privacy notice.
Xish Community is a product of PBG Communications Ltd. Communities remain responsible for the member and operational records they choose to manage, while Xish operates the platform and its guarded support systems.
Information the platform may handle
Depending on the tools a community enables, records may include account identity, membership details, roles, community operations, financial obligations and receipts, communications, residential administration, files, projects and support diagnostics.
Not every community uses every category. Optional tools remain separately governed, and private records are not made public by this website.
Why information is used
Information is intended to provide account access, community administration, accountable histories, requested support, security controls and the specific community tools a person is authorised to use.
This public information layer does not use behavioural advertising, fingerprinting, session replay or cross-site personalisation.
Visibility and responsibility
Community visibility is controlled by tenant separation, roles, permissions, record ownership and explicit audience rules. Platform roles do not silently become community administrators or members.
Some histories are intentionally append-only for accountability. Private wording may have a separately approved retention or redaction path while minimal canonical history remains.
Providers and processing
Xish uses infrastructure and service providers only for capabilities that have been separately configured and approved. The effective notice must accurately name active hosting, database, authentication, email, payment, storage and security providers before public launch.
This draft does not claim that infrastructure creates no operational logs. Provider locations, safeguards and international-processing details still require professional review.
Retention, correction and rights requests
Retention depends on the record and its accountability purpose. Corrections normally create linked history instead of silently rewriting an earlier decision.
The process for access, correction, objection, deletion, complaints and other rights requests requires an approved public privacy contact and reviewed procedure before this notice can become effective.
Security and changes
Xish is designed around least privilege, server-only secrets, guarded mutations, forced row-level security where appropriate and explicit provider and payment gates. No system can promise absolute security.
An effective notice will identify its approval date, effective date, change-notice method and public contact. None has been assigned to this draft.