Privacy by design

What Diarised can and can't see.

Diarised is three separate parts that don't share credentials: the public desk people talk to, a booking engine that is plain code, and a private planner only you use. Here's what each one can see.

The three parts

How the three parts of Diarised connect Visitors talk only to the public desk. The public desk receives open time slots from the booking engine. The booking engine reads only busy times from your calendars, and receives weekly rules from your private planner. Only you talk to the private planner, which can read your calendar with your consent. Visitors Public deskAI Booking enginePlain code You Private plannerAI · owner only Yourcalendars open slots only weekly rules only busy times only with your consent
Visitors only ever reach the public desk. Nothing flows back from the desk to your calendars or planner.

AI · talks to visitors

The public desk

Answers people on your desk page and website widget.

Can see

  • Your published profile, FAQs and fee text
  • Open times allowed by this week's rules, as one-time slot tokens
  • The conversation in front of it

Can't see

  • Your calendars: event names, attendees or places
  • Your other enquiries and what they're worth
  • Your goals, VIP list or private planner

It can't send email or touch a calendar. Its only connection outside Diarised is to the AI model provider.

Plain code · no AI

The booking engine

Works out free times, places holds and makes bookings.

Can see

  • Busy and free times from the calendars you choose, without titles or details
  • Your meeting types, holds, bookings and weekly rules

Can't see

  • Your private planner's notes and goals

It writes only to its own Diarised calendar and never moves or edits your other events.

AI · only you talk to it

Your private planner

Helps you plan your week and reviews it with you on Friday.

Can see

  • Your calendar in detail, with your separate consent
  • Your goals, protected windows and VIP list

Can't see

  • Your visitors: it never talks to them

It hands the rest of Diarised one thing: a compiled set of weekly rules, such as “offer 5 outside slots and keep Monday and Thursday mornings closed”.

How they're kept apart

Separation you don't have to take on trust.

  • Separate services, separate keys. The public desk, the booking engine and the planner run as separate services, each with only the credentials it needs.
  • Enforced by the database. Each part has its own database role. The public desk's role has no access to private tables, whatever anyone types into a chat.
  • One thing crosses over. The only link from private to public is a compiled set of weekly rules, checked against a fixed format.
  • Probing is refused. Questions that try to work out where you are get generic answers, are rate-limited and are logged.
  • Everything is logged. Every calendar write, rule change and decision goes into an audit log.
  • You can pause it. One switch replaces your desk with a simple contact message.
  • Conversations stay yours. Only you can review your desk's conversations, which are kept for 90 days by default.
  • AI that says so. Your desk tells every visitor it's an AI assistant, and AI models must pass our safety tests before they're allowed on the public desk.

Who helps us run it

The companies that process data for Diarised.

Hosting
Our own servers at Hostinger, in the United Kingdom.
AI models
Anthropic, OpenAI or OpenRouter, chosen by us for each part of the product.
Email
Resend, which sends from its EU region and keeps account data in the United States.
Calendar
Google, only if you connect Google Calendar.
Payments
PayFast, for rand billing.

This page describes how Diarised is built. Our full privacy notice for desk owners and their visitors, with POPIA details, is published before launch. Questions: hello@diarised.si. Last updated 8 November 2026.

A front desk that knows when to stay quiet.

Apply to be one of the first to try it.

Apply for a founding place