Your calendar, your crew, your clients

Where your calendar lives

• Your bookings are stored in a PostgreSQL database run by Supabase.
• Every table is protected by row-level security. The database itself refuses to return a row to anyone who does not own it, so a bug in a screen cannot show your calendar to somebody else.
• The keys that can bypass that protection never leave our servers and are never in the code you download.

What your crew sees

• Each person opens a private link. It shows only the jobs assigned to them, and nothing else on your calendar.
• Your crew never sees prices, invoices or what clients owe.
• No accounts means no passwords for them to reuse or lose. If a link is ever shared by mistake, you can replace it.

What visitors to your booking page see

• Free or busy, never what you are busy with. The details of your bookings are not sent to the page.

Payments

• Card payments are handled by Stripe and PayPal. Your card number goes to them, never to us.

Backups

• The database is backed up by Supabase. The application code is versioned and backed up on every release.
• Cancelling never deletes your calendar. A paid account goes back to Free and keeps everything.

Status

• A public status page is not live yet. Until it is, if something looks wrong, write to us and you will get a person.

More questions? Help has the basics.