Terms of Service

========================================================================
XEMPORA TERMS OF SERVICE
========================================================================

Welcome to Xempora. By registering an account on this node, you agree
to abide by the following operational parameters and system guidelines.
Infrastructure oversight is maintained by XemCore.

1. ARCHITECTURE & INTENDED USE
------------------------------------------------------------------------
* Xempora is a decentralized microblogging platform designed for short,
punchy updates, open dialogue, and real-time linear timelines.
* This node actively federates across the open Fediverse and public open
social networks (including ActivityPub and ATProto/Bluesky).
* Content you publish publicly will broadcast across these external
networks and cannot always be retroactively modified or deleted from
downstream external servers once transmitted.

2. USER RESPONSIBILITIES & CONDUCT
------------------------------------------------------------------------
To ensure network health and a constructive environment, users must:
* Maintain a human-centric presence.
* Refrain from deploying uncoordinated automated spam bots or scripts
that flood local or federated timelines.
* Refrain from launching data-scraping activities or malicious attacks
against the local server infrastructure.
* Do not utilize this platform to coordinate illegal activities, promote
harm, or distribute malicious software.

3. DATA & RESOURCE MANAGEMENT
------------------------------------------------------------------------
* System instances are tuned to be highly performant. The administration
reserves the right to enforce reasonable text character boundaries
and attachment upload parameters to maintain low land-impact
overhead and server efficiency.
* Inactive profiles or accounts generating excessive structural database
errors may be pruned following standard system maintenance reviews.

4. LIMITATION OF LIABILITY
------------------------------------------------------------------------
* Service is provided "as-is" and "as-available" without warranties of
any kind.
* While automated background backups are utilized to safeguard network
continuity, the administration is not liable for data loss or temporary
federation sync delays caused by upstream hosting anomalies.

5. MODIFICATIONS & TERMINATION
------------------------------------------------------------------------
The administration reserves the right to modify these parameters or suspend
access to individual nodes if local system stability or community safety
is compromised.

For direct network inquiries, infrastructure support, or assistance,
please contact the system administrator (@Tin Tin).
========================================================================

Rules

1. ========================================================================
2. XEMPORA COMMUNITY RULES
3. ========================================================================
4. To maintain an optimal, high-performance microblogging environment, all
5. accounts managed under XemCore must adhere to these five core rules:
6. 1. ONE-COLUMN FEED CLARITY
7. ------------------------------------------------------------------------
8. * Keep updates concise. Do not abuse line breaks or massive whitespace
9. blocks that intentionally disrupt the linear flow of the timeline.
10. * Use appropriate tags for long multi-post threads so public global
11. feeds remain readable for everyone.
12. 2. MEDIA OVERHEAD CONTROL
13. ------------------------------------------------------------------------
14. * To keep server storage impacts and database land-impact overhead low,
15. optimize your images and video attachments before uploading.
16. * The administration reserves the right to prune cached federated
17. media or limit large automated binary payloads to protect bandwidth.
18. 3. HUMAN-CENTRIC CHRONOLOGY
19. ------------------------------------------------------------------------
20. * Explicitly label any automated or interactive scripts as "Bots".
21. * Uncoordinated automated accounts that flood public streams or
22. heavily tag unconsenting nodes will have their federation permissions
23. instantly revoked.
24. 4. FEED INTERACTION ETIQUETTE
25. ------------------------------------------------------------------------
26. * No cross-network harassment, targeted brigading, or intentional
27. disruption of users across connected ActivityPub or ATProto spaces.
28. * Respect privacy—do not publicly broadcast private direct messages
29. or system diagnostic data without the consent of all parties.
30. 5. INFRASTRUCTURE INTEGRITY
31. ------------------------------------------------------------------------
32. * Do not bypass local node permissions, spoof digital identities,
33. or attempt to inject rogue scripts into the Flarum or Friendica code
34. environments.
35. ========================================================================

Privacy Statement

At the time of registration, and for providing communications between the user account and their contacts, the user has to provide a display name, a username and a working email address. The names will be accessible on the profile page of the account by any visitor of the page, even if other profile details are not displayed. The email address will only be used to send the user notifications about interactions, but wont be visibly displayed. The listing of an account in the node's user directory or the global user directory is optional and can be controlled in the user settings, it is not necessary for communication.

This information is required for communication and is passed on to the nodes of the communication partners and stored there. Users can enter additional personal information that may be transmitted to the communication partner's accounts.

At any point in time a logged in user can export their account data from the account settings. If the user wants to delete their account they can do so at https://xempora.com/settings/userexport. The deletion of the account will be permanent. Deletion of the data will also be requested from the nodes of the communication partners.