ZKal is designed to create gravity towards community-sovereignty and non-custodiality, making it easier for tech communiies to degoogle and regain control over their calendar data.

It provides a self-hosted (proxied) calendar feed with a web-based widget that integrates multiple .ICS feeds, allowing for a gradual transition away from Google Calendar.

Features

• Semaphore Integration: Users access ZKal through Semaphore, maintaining anonymity while proving group membership.

• Distributed Calendar Administration: Supports multiple ICS feeds, allowing different rooms or groups to operate on various systems without an all-or-nothing switch from Google Calendar.

• Proxied Calendar Access: Users access all event data through a self-hosted proxy, preventing back-ends from seeing subscribers, attendees, IPs, etc.

• RSVP and Event Creation: Users can add to their calendar anonymously, or RSVP publicly within the Semaphore group.

Trust Model

zKal's starting point is to allow for:

• Users interact with a self-hosted zKal server, hosted by their own community. RSVP and subscriber information is stored there, and under their stewarship.
• User access is granted by proving group membership using a semaphor.
• No event information is sent to back-end calendar providers.
• Users can optionally RSVP, disclosing their email address to the zKal server and others
• Users can interact anonymously, even with their zKal server, which sees only their IP and their group membership proof.