Skip to content

jdsika

My feedback

7 results found

  1. 774 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    jdsika supported this idea  · 
    An error occurred while saving the comment
    jdsika commented  · 

    high prio!

  2. 222 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    jdsika commented  · 

    I strongly support an official Proton Calendar API. I would like to highlight a requirement complementary to the proposed local CalDAV Bridge: secure, standards-based integration with hosted applications, business automation platforms and AI agents, without compromising Proton Calendar's end-to-end encryption.

    1. The requirement: authorized remote interoperability

    A local CalDAV Bridge would solve desktop and locally hosted integrations, but it does not fully address applications running in the cloud.

    Business applications need to perform operations such as:

    - Query authorized calendar availability.
    - Create, update, reschedule and cancel appointments.
    - Manage attendees and invitations.
    - Retrieve selected events when explicitly authorized.
    - Detect calendar changes through synchronization or event notifications.
    - Create or attach Proton Meet links when scheduling meetings.

    These capabilities are necessary for booking systems, workflow automation, enterprise applications and AI assistants.

    2. Rely on established standards

    Please prioritize existing protocols rather than introducing an entirely proprietary integration model:

    - CalDAV (RFC 4791) and iCalendar (RFC 5545) for calendar interoperability.
    - iTIP/iMIP (RFC 5546/6047) for scheduling and invitation workflows.
    - OAuth 2.0 with PKCE or equivalent standardized delegated authorization.
    - Standardized incremental synchronization and conflict detection.
    - A documented client SDK where cryptographic operations cannot safely be performed by a conventional server-side API.

    An eventual JMAP Calendars implementation could also provide a modern JSON-oriented interface as that standard matures.

    3. Preserve E2EE by design

    The API should not require Proton's servers to decrypt private calendar data.

    Instead, please evaluate complementary integration models:

    A. Limited cloud-accessible operations

    Expose narrowly scoped capabilities such as authorized Free/Busy queries or appointment scheduling, without disclosing unrelated event titles, descriptions or attendee information.

    These operations should remain opt-in because even availability metadata can reveal sensitive information.

    B. Trusted client-side SDK

    Provide an official SDK capable of handling encryption, decryption and authorized calendar operations within a user-controlled environment.

    Applications requiring decrypted information would explicitly become trusted endpoints. Proton should document this trust boundary and avoid exporting private keys to unrelated third-party services.

    C. Secure organizational automation

    Support carefully scoped, revocable integration credentials and approved automation identities, with transparent auditing and explicit organizational controls.

    Unattended integrations should have a supported authentication and key-management model rather than relying on undocumented APIs or storing ordinary user login credentials.

    4. Apply least-privilege authorization

    Ideally, applications could request separate permissions for:

    - Free/Busy information only.
    - Read access to selected calendars.
    - Creating events.
    - Updating or deleting authorized events.
    - Managing meeting invitations.

    Users and administrators should be able to review and revoke these permissions independently.

    5. Why this matters

    Organizations considering migration from Google Workspace or Microsoft 365 need to preserve their existing integration capabilities.

    For example, Haven Evergreen is an enterprise knowledge-management application that could benefit from user-authorized calendar and scheduling integrations. The same requirement applies to many independent productivity and automation tools.

    Without an official integration mechanism, organizations must choose between maintaining their existing workflows and adopting Proton's privacy-focused ecosystem.

    Recommendation: Deliver the local CalDAV Bridge for conventional clients and a complementary, officially supported developer SDK or constrained API for secure remote automation.

    Interoperability and E2EE should be complementary design objectives, not mutually exclusive choices.

    jdsika supported this idea  · 
  3. 1,072 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    jdsika supported this idea  · 
    An error occurred while saving the comment
    jdsika commented  · 

    I strongly support an official, bidirectional Proton Calendar Bridge. The goal should be interoperability through established standards without weakening Proton's end-to-end encryption (E2EE). This is important for desktop clients, accessibility tools, scheduling services, local AI agents, and business applications such as Haven Evergreen.

    1. Implement standard protocols

    - CalDAV (RFC 4791): discover calendars; read, create, update, and delete events.
    - iCalendar (RFC 5545): standard event data, UIDs, recurrence, time zones, and attendees.
    - iTIP/iMIP (RFC 5546/6047): interoperable invitations, replies, changes, and cancellations.
    - WebDAV Sync (RFC 6578): incremental synchronization; use ETags/conditional writes for conflict detection.
    - CardDAV (RFC 6352): a useful separate extension for contacts.

    Compatibility with existing clients such as Thunderbird should not depend on reverse-engineering undocumented Proton APIs.

    2. Keep encryption/decryption on trusted endpoints

    Like Proton Mail Bridge, a Calendar Bridge could synchronize encrypted data with Proton, decrypt it locally under the user's control, and expose an authenticated CalDAV endpoint only to authorized local applications. It should bind to localhost by default, keep keys in protected storage, and never require Proton's servers to receive plaintext event contents or decryption keys.

    CalDAV does not itself provide E2EE. An application granted access to decrypted events becomes an additional trusted endpoint; Proton should document this boundary rather than imply that data remains end-to-end encrypted after export to a third party.

    3. Offer granular, revocable authorization

    Ideally support per-calendar permissions and separate scopes for:

    - Free/Busy only, without titles or descriptions;
    - read-only access;
    - creating events;
    - modifying or deleting events.

    Provide application-specific credentials, explicit consent, revocation, and safe handling of private versus business accounts. Never treat a network-exposed bridge as equivalent to a localhost-only interface.

    4. Support real scheduling operations

    A useful implementation needs accurate Free/Busy, stable event IDs, recurring events, organizer/attendee semantics, notifications on updates or cancellation, and safe handling of simultaneous changes. Where feasible, an authorized integration should also be able to create or attach a Proton Meet link. These should be documented capabilities, not assumptions about basic CalDAV support.

    5. Address remote automation without server-side decryption

    A local bridge is valuable, but hosted booking systems and automation agents also need a supported integration path. Please consider a complementary official client SDK or delegated mechanism for narrowly scoped availability and booking operations. A trusted client could perform the cryptographic work; the hosted service would receive only the minimum authorized data. Access to full decrypted calendars should not be the default.

    Why it matters

    Organizations considering a move from Google Workspace or Microsoft 365 need standards-compliant calendar integration, not merely manual ICS import/export. Haven Evergreen is one example of a knowledge-management application that could benefit from user-authorized scheduling integration; the same applies to numerous other independent tools.

    Suggested delivery order: (1) officially supported local CalDAV Bridge with documented E2EE trust boundaries; (2) granular authorization and reliable sync; (3) an optional, privacy-preserving remote integration mechanism.

  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    jdsika shared this idea  · 
  5. 36 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    jdsika supported this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    jdsika shared this idea  · 
  7. 4,126 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    jdsika supported this idea  · 
    An error occurred while saving the comment
    jdsika commented  · 

    This feature is needed asap, please!