Key takeaways
- No Outlook connection exists today. Calendar sync as a whole is planned for a later release.
- Whether Microsoft calendars are supported first is not yet decided.
- A sync would store only the meeting details a deal needs, under your deal permissions.
- Disconnecting would stop future sync without deleting history you were allowed to see.
Planned feature: not in Delsivo yet, and details may change before it ships.
Where Outlook calendar sync stands
Delsivo is being built with a small number of design partner funds. The PRD places email and calendar sync in its later phase, after the pilot and the first release. Funds that run on Microsoft 365 will reasonably ask whether Outlook is covered. The honest answer is that no provider has been chosen, and we'd rather ask design partners than guess.
What a calendar connection would read and store
Calendars hold far more than founder meetings: personal appointments, LP calls, portfolio board meetings. A connection that copied all of it into a deal workspace would be a privacy problem. The design principle is the opposite: take only what links a meeting to a deal.
| Data | Planned handling |
|---|---|
| Events with no founder or deal contact | Ignored, not stored |
| Matching events | Date, time, title and attendee emails needed to link the deal |
| Event descriptions and attachments | Not decided; the default would be not to copy them |
| Who can see a synced meeting | Only people with access to that deal |
| Logs | Connection, disconnection and permission changes recorded in the audit log |
Who owns the data from a synced meeting?
The fund. Founder data in Delsivo belongs to the fund as controller, and Delsivo processes it on the fund's behalf. A meeting linked to a deal would become part of that deal record, covered by the same retention settings and the same deletion rules. Deleting a deal removes its previews, indexes and derived copies, and a synced meeting would be no different.
Each team member would connect their own calendar. A partner's calendar would never be readable by an analyst just because both work at the fund.
How disconnecting would work
- 1A team member disconnects their calendar in their own settings.
- 2Delsivo stops reading new events at once.
- 3Meetings already linked to deals stay on those deals, so the record isn't rewritten.
- 4The disconnection is written to the audit log with who did it and when.
This follows the PRD's acceptance rule for every later integration: disconnect stops future sync without deleting authorized local history.
What to use in the meantime
- Record meeting dates and notes on the deal itself.
- Use founder call preparation in the first release to get a cited brief before each call.
- Keep a single deal record so the deal audit trail shows what changed after each meeting.