How Diarised handles your information

Last updated 15 November 2026.

Diarised is an AI assistant for people's time: founders, CEOs, speakers, consultants and business developers share a link, and their assistant answers questions and books meetings for them. It's run by VerdanTech (Pty) Ltd in South Africa. This page explains what we collect, why, who helps us process it and how long we keep it.

If you chat with someone's assistant

• The assistant you chat with is an AI, and the line above the chat says so. The person chooses its name and picture. Its picture always shows the AI mark. It answers only from information the person has approved and published. It can't see their calendar, email, contacts or location.
• Your messages and the replies are kept for 90 days so the person and the people who help them can review them, then deleted automatically.
• If you leave a message, it goes as a request (below): we email you a code to confirm the address, then your name, email address, organisation and message go to the person so they can reply to you.
• To limit abuse, we keep a scrambled internet address: a code made from your IP address that can't be turned back into it. We never keep the address itself.
• The page doesn't use cookies. Your browser keeps a random conversation code until you close the tab.

If you send a request

• A request (to speak at an event, for an interview, a partnership, an introduction and so on) is gathered in the chat or with the form on the person's page: your name and email address, and what that kind of request asks, such as your organisation, the event, the dates, where, the audience, a budget and anything you add. In the chat, the assistant writes a short summary of what you said; you see it before anything is sent.
• We send a 6-digit code to your email to confirm the address is yours. Until you enter it, the request is a draft that only you can continue: the person never sees it, and an unconfirmed draft is deleted after a day. The code is stored only as a one-way code and expires after 15 minutes.
• Once confirmed, the request goes to the person (and anyone who helps them on that role), and we email you an acknowledgement with when to expect an answer and a link to withdraw it.
• Holding a date. For some kinds of request, the date you asked for is held privately while the person decides, for a set time. Nothing goes in their calendar until they accept. If someone else has already asked for that date, you're told only that someone asked first, never who or why, and you're next in line for it.
• Decisions. The answer (yes, no, a fee, a question or the offer of a call) is emailed to you in the person's name, and your replies go to them. If someone who helps them made the decision, the email says so. Some requests are answered automatically by rules the person set (for example, too little notice): you get a polite email a few hours later, without the reason.
• If the person accepts, your name and email address join their network (see below); before that, you're only a suggestion they may add or dismiss. The request is kept as the person's record until they or you ask for it to be erased.
• The form on the page uses no cookies. To limit abuse, we keep a scrambled internet address (a code made from your IP address that can't be turned back into it).

If you book a meeting

• We ask for your name, your email address and an optional note, and send a 6-digit code to your email to confirm it's yours. The code is stored only as a one-way code and expires after 10 minutes.
• We email you a confirmation, a reminder before the meeting, and links to reschedule or cancel. The person you booked with is told about the booking.
• If they use Google Calendar or a Microsoft calendar, the meeting is added to a calendar Diarised created in their account, with your name and email address as a guest, and Google or Microsoft sends you the invitation. Otherwise we email you a calendar invitation.
• If you were sent a personal invitation to book, the link fills in your name and email address and stands in for the code. It works once, for 30 days. Your name and the address it was sent to are in the person's network from when it was sent.
• Once the meeting is confirmed, your name and email address are kept in the person's network on Diarised (their own list of people they know, see below), so they can invite you again. Before you confirm, you're only a suggestion they may add or dismiss.
• The booking is kept as the person's record of the meeting. If you ask them to erase your information, your name, email address and note are removed from it, and you're removed from their network and not added back.

If you use Diarised yourself

• We keep your sign-in email and name, what you do (founder, CEO, speaker, consultant or business developer, so we can suggest a starting setup), your time zone, your rules (protected time and meeting limits), and an activity log of publishing, settings and booking changes.
• Roles. You can have several roles: your own name, each business you work in, and private roles such as family. Each public role has its own page, assistant, booking links and what the assistant knows. A role's page, assistant, emails and invitations show only that role's details and never mention your other roles. A meeting in any role blocks the same time in all of them, and nobody is told why.
• Your assistant's picture. Each public role's assistant can have a picture: one of Diarised's own, or one you upload. An upload is made smaller in your browser before it's sent, so it carries no camera details such as where it was taken. The picture is kept with the role. It's shown on the role's public pages and booking pages, in the chat and, if your website's widget asks for it, on the widget's button, always with the AI mark. It isn't shown while the role is archived or your plan has ended. Removing it, or deleting your account, deletes it.
• Sign-in codes are stored only as one-way codes and expire after 10 minutes. If you turn on an authenticator app, its secret is stored encrypted.
• Helpers. If you let someone help on one of your roles (a manager or an assistant), they see that role's requests, bookings and conversations, and you see everything they did. They never see your calendars, and the rest of your time shows to them only as busy.
• Business accounts. If a business pays for you, its owner and admins see your name and whether you're set up. They don't see your pages' content, requests, bookings, conversations, calendars or network.
• Notifications on your phone. If you turn them on, your browser gives us an address its push service uses to reach that device, which we keep until you turn notifications off or the push service tells us it no longer works. A notification says only that something happened, or how many there are (for example “New meeting booked” or “2 birthdays today”), never who, what or when. You choose which ones you get in Settings, Notifications.
• Requests. Requests to your roles are kept until you or the sender ask for them to be erased; a date hold ends when you decide or when it runs out. A morning email lists what needs you: waiting requests, holds running out and tomorrow's meetings, and, from your network, the birthdays and other dates you asked to be reminded of, the people you wanted to keep in touch with (on Mondays) and promises that are due. It goes only to your own sign-in address. You choose what it includes, or switch it off, in Settings, Notifications.
• Diarised staff can't see your content unless you switch on support access for a set time, or send them a report (below). Every read under support access is listed for you.
• Reports to support. When you report a problem, or send an idea or a question, from Diarised, the report holds what you write and the kind and area you choose. It also holds a screenshot if you add one and what the form shows you before you send it: the screen you were on (the kind of screen, never its address), the app version, your device and browser, the role (a private role only as “a private role”), the time and, if you came from an error screen, the error's reference. Diarised staff read it, with your name, email address and plan, to answer you and fix the problem. They see nothing else of yours unless support access is on, from the form's tick or from Settings. A screenshot is made smaller on your device before it's sent, which removes camera details, and is kept with the report. We email you about it from Diarised support. Replies to those emails reach our team but aren't added to the report. When we plan a fix, we track it in our own work list (GitHub) in our own words, with the report's reference but never your words, name or address.

Your network

Your network is your own list of the people you know, across all your roles. It belongs to you, not to a role or a business account, and it leaves with you.

• What's kept. For each person: their name, company, job title, city and country; the email addresses, phone numbers and links you have for them; the roles you know them through; how you know each other, a relationship level, tags and notes; whether they're a VIP; and when you last met. Each contact also records where it came from (a meeting, a request, an invitation, an import or typed in) and when. You can also keep, if you choose to: dates to remember (a birthday, an anniversary, when you first met), with or without the year; family members (their relation, their first name and, if you know it, their birthday); interests and preferences; goals, gifts you've given and gift ideas; the companies they work at, own, founded, advise or sit on the board of, with their title and dates; how the people in your network are connected to each other; and promises you've made them. Each item records who added it (you, a helper or an agent you connected) and when, and can carry a note of where it came from. There are no fields for health, religion or political views. For each date, whether you want to be reminded of it; for each person you keep in touch with, when you last spoke and, if you snoozed them, until when.
• Where it comes from. Only what you give it. Added automatically, marked with the role: people with a confirmed meeting on one of your roles, people you or a helper invite to book (from when the invitation is sent), and people whose request you accept or reply to. Added by you or a helper: people typed in, and files you choose to import. Offered as suggestions only, for you to add or dismiss: people who sent a request you haven't replied to yet, and people who started a booking but didn't confirm it with their code. Diarised doesn't buy data about people and doesn't look anyone up. Dates, family, interests, companies, connections and promises are only ever typed in by you, by a helper you've given your whole network, or by an agent you connected and allowed to add them (see Agents you connect). Diarised doesn't look anyone up and doesn't fill these in from anywhere else.
• What you may keep. You decide what to record about the people you know, and you're responsible for it. Record only what they've told you or what you're otherwise entitled to keep, and no more than you need. Take particular care with children: a first name and a birthday is all Diarised lets you keep about a family member. If someone asks what you hold about them, or asks you to remove it, you must answer them.
• Who can see it. You. A manager on one of your roles sees only that role's part: the contacts marked with that role, and the notes and history made in it, never your own notes. If you give a manager your whole network (only you can, from your own session), they also see the people from your other roles, can export them all and can erase someone by email; still never your own notes. Assistants on your roles, business account owners and admins, and Diarised staff can't open it, even under support access. Nobody else can, and Diarised never tells anyone who's in it. Dates, family, interests and preferences, and promises are yours alone, like your own notes: a manager on a role doesn't see them. A manager you give your whole network sees them and can change them. A manager sees a company's people, and how people are connected, only for the people in their part, and without your notes on those connections or where anything came from. Reminders about your network, in the morning email and on your phone, go only to you, never to a helper, whatever you've given them.
• Who can introduce you, and Before you meet. Diarised can show who in your network could introduce you to someone (people you know who are connected to them, or who are or were at the same company, at most two steps away), and, before a meeting with someone in your network, a summary of what you keep about them. Both are made only from what's already in your network, nothing is looked up, and each person sees only what they could already see in Diarised: a manager only the people in their part; an assistant, nothing.
• Never the AI assistant. Diarised never sends your network to an AI model of its own. An agent you connect yourself receives only what you let it read (see Agents you connect). The assistant on your pages can't see who you know, your VIPs or your notes, so it can't mention them. That includes everything above. The assistant on your pages can't see what you keep about anyone.
• Imports. You can import your LinkedIn connections (the Connections.csv file in LinkedIn's copy of your data), your phone's contacts (a vCard file) or a spreadsheet (a CSV file), up to 10 MB and 20,000 contacts. The file is read once and not kept. You see what's new and what matches before anything is added, and you can undo an import for 7 days; contacts you've changed since stay.
• Telling the people you import. When you keep someone's details that didn't come from them, the law (POPIA) usually expects them to be told, and that duty is yours as the person who keeps the list. After an import, Diarised gives you a short note to send from your own email or messages. Diarised never contacts them for you and never sends bulk email.
• Erasing someone. You can erase a contact, or everyone with a given email address, with what you hold about them in your network and your roles' requests, conversations and bookings. Diarised then keeps only a keyed, one-way code of each of their email addresses and phone numbers, made with a secret key only our web server holds, so a later meeting or import doesn't add them back. The code can't be turned back into the address or number. What was erased stays in our encrypted backups for up to 35 days, until they're replaced; if a backup is ever restored, the erasure is made again. Erasing a contact removes everything you keep about them: their dates, family, interests, companies, promises, and their connections to other people. When you remove a single item instead, it's kept for 30 days so you can put it back, and then deleted. A record of who changed these items is kept for the same 30 days.
• Export. You can download your whole network, or a filtered list, as a vCard or CSV file. The vCard and CSV files include each person's company, job title and birthday. Notes, family, interests, connections and promises aren't in those files; they are in the file with everything that's yours (Settings, Download your data). A manager can export only with access to your whole network. Every export is listed in your activity log.

Agents you connect

You can let an AI assistant of your own, such as Claude, ChatGPT or Grok, use your network: you connect it from the assistant, and Diarised asks you, on a page in Diarised, what it may do. Only you can connect one, never someone who helps you.

• What it can read and do. You choose, for each of your roles or for all of them:
  • names and work: names, companies, job titles, cities and countries, roles, tags and how people are connected; when you added someone, last met them and were last in touch, how often you mean to keep in touch, and who is due to reconnect; what kind of detail changed recently and by whom (never the values); and a company's website, industry, size, city and country;
  • contact details: email addresses and phone numbers;
  • personal details: dates, family, interests, preferences, goals and gifts, promises (those in the roles you tick, and those in none), how you met, what you noted about how two people are connected, and notes (yours, your helpers' in the roles you tick, and other agents');
  • adding and changing: adding people and notes, adding or changing the other details (tags too), and removing single items. With it, an agent can add details you haven't let it read (for example notes, dates or how you met, or a new person's email address). It can add an email address or phone number to someone already in your network only if it may read their contact details;
  • your meetings: who and when, never your calendars;
  • how close you are: how close you are to each person (close, regular or wider), and who your VIPs are. With adding and changing for the same role too, an agent can change these and mark someone as a VIP, at most 10 a day. It's off until you tick it, and part of Pro.
  With names and work, an agent can also ask who could introduce you to someone, through the people it may see; it never ranks them by how close you are. With your meetings, it can ask for a briefing before a meeting, made only of what your other choices let it read; it says how close you are to the guest, and whether they're a VIP, only if you've ticked how close you are. On Starter an agent can read names and work, and add people and notes, and change people's details and tags; the rest is part of Pro. An agent can never delete or merge people, change your settings or rules, see your calendars, send anything to anyone, or connect another agent.
• Who receives it. Whatever you let an agent read goes to the company that makes it (for Claude, Anthropic; for ChatGPT, OpenAI; for Grok, xAI), under your agreement with them, not ours. Diarised can't control what they do with it. Connect only agents you trust, and only with what they need.
• Limits. An agent gets people 25 at a time (a person's connections too), reads up to 500 people a day on Pro (100 on Starter), and makes up to 200 changes a day (50 on Starter). Text you didn't write yourself (for example a card's wording, a visitor's name, or what a helper or another agent wrote) is marked for the agent as written by someone else, and agents are told not to follow it; an agent can still be misled, so its changes can be undone.
• What you see, and undo. Settings, Connected agents lists each agent, where it sends you back to, what it may do, how many people it read each day, and each change it made, which you can undo for 30 days unless it has changed again since. Items an agent adds say so. The morning email can tell you what your agents did the day before, and names anyone an agent marked as a VIP.
• Changing and disconnecting. You can change what an agent may do, or disconnect it, at any time; a disconnected agent stops at once. (On Starter, what's part of Pro can be turned off but not on.) It also stops if your plan ends or you delete your account.
• What's kept. For each agent: its name as it gives itself, where it sends you back to, what you allowed, when it was connected and last used, and its daily counts. If an agent signs its requests with its maker's own key, as ChatGPT can, Diarised also keeps where that maker publishes its public keys, and its connection can then only be renewed with a signed request. Its access is a random key we keep only in scrambled (hashed) form. Each renewal of its access lasts 30 days, so it keeps working as long as it's used at least once every 30 days, until you disconnect it; an agent unused for 30 days stops and must be connected again. A disconnected or stopped agent's record goes 30 days later. Your activity log records when you connect, refuse, change, undo or disconnect an agent. Items it added keep its name after it's disconnected.
• Diarised never looks anyone up for an agent. Everything an agent adds comes from it (or from you, through it), and can carry a note of where it came from. Emails and phone numbers an agent adds never count for VIP recognition, and an agent can't add back an email address or phone number of someone you erased.

If you're in someone's network

• Someone who uses Diarised may keep your details in their network: because you met or booked with them, because they typed them in, or from a file they imported, such as their LinkedIn connections or their phone's contacts. They decide why they keep them, and we process them on their behalf.
• They may also keep things they know about you that help them stay in touch: for example your birthday, the first names of your family, your interests, where you work, and who else they know that you know. They enter these themselves. Diarised doesn't look you up. You can ask them what they hold about you, and to correct or remove it. They may ask Diarised to remind them of your birthday, or to keep in touch with you. They may also let an AI assistant of their own read or add to what they keep about you; its maker then receives what they let it read.
• Only they see your details, and the people who help them see only the part they work on. They're never shown on public pages, never sold and never used for marketing, and never sent to an AI model by Diarised, except a photo of your business card if they scan it (see Reading business cards); they may let an assistant of their own read them (see Agents you connect).
• To see, correct or remove what they hold about you, ask them, or use our request page and we'll pass it on (see Asking about your information). Once you're erased, you aren't added back.

Cards and sharing details

• What a card shows. Each public role can have a card at diarised.si/c/<name>. It shows only the details its person chose for that role: their name, title, company, a line about them, a photo and logo, and the email, phone, website and LinkedIn they ticked. A phone number is hidden unless they turn it on. A card never shows their other roles or who they know. "Save contact" and the card's QR codes carry the same details and nothing more. The card page sets no cookies.
• Link previews. When a role's page, one of its booking links or its card is shared in an app such as WhatsApp, iMessage or LinkedIn, the app shows a preview made only from what that role already shows in public: its page photo or its card's logo (as its person chooses, or Diarised's own picture), its public name and title, and its address. A preview never carries an invitation, an event's name or anything else from the address that was shared. A role that's archived, or whose account isn't in service, has none. Apps keep a preview for a while, and right after a change Diarised's own can show the role's previous name or title for a short while.
• Sharing your details on someone's card. If you use "Share your details", you give your name and email (and, if you choose, a phone number, company, title and a note) to that card's person, to keep in their Diarised network. We record that you agreed, which wording you agreed to and when, and a scrambled internet address (a code made from your IP address, to stop abuse; it's deleted after 30 days). The emails we send you about it greet you without the name typed in, because anyone could have typed your address.
• Confirm or remove. We email you once, with a link to confirm it was you and a link that says "this wasn't me, remove my details". The links work once, for 30 days. If you were new to their network, you're added marked as not confirmed until you confirm; if you're never confirmed, you're deleted from it after 30 days unless they have used your details since. If they already knew you, nothing about you in their network changes until you confirm. Removing undoes only what that share added: if it added you and nothing else has happened since, you're deleted from their network and a coded form of your email and phone is remembered, so the same details can't be added again that way; if they already knew you, what they had about you stays theirs. To be removed from their network altogether, ask them, or us, at any time.
• A copy of the card. If you tick "send me a copy of this card", we send it once, after you confirm, with only the details the card shows.
• Swapping cards. When someone with Diarised saves another person's card, only what that card shows goes into their network. The other person is asked in Diarised whether to take a card back, and nothing is added for them until they say yes.
• Follow-ups sent in your name. After meeting someone, the person can send them a short "good to meet you" email they wrote, one person at a time, when they press send. It comes from them via Diarised and replies go to their own address; if someone who helps them sent it, the email says who arranged it. Diarised never sends bulk or marketing email from cards, and never emails people who shared their details about anything else.

Reading business cards

• Scanning. Someone who uses Diarised can point their phone at a QR code (a contact, a LinkedIn profile or a Diarised card) or take a photo of a paper business card, front and back. The camera is used only on the scanner screen, and only while it's open.
• Where the photo goes. To read the card, the photo is sent from our server to the AI provider chosen for reading cards (Anthropic or OpenAI, or another model maker through OpenRouter). It isn't used to train AI models. Only the photo goes; nothing else from the person's network or calendar is sent with it.
• How long it's kept. While it waits to be read, the photo is stored encrypted. It's deleted as soon as the card is read, unless the person ticks "keep the card photo", in which case it stays with that contact. If reading fails, it's deleted within an hour.
• Checked before saving. What the AI read is shown to the person, who checks and corrects every detail and chooses which of their roles to mark it with before anything is saved. Text on a card is treated only as card details, never as instructions. Details read but not saved are deleted after a day.
• Without signal. Scans made offline wait on the person's phone and are sent once it reconnects. They're removed from the phone when sent, discarded or when they sign out.

What Diarised never reads

• Your email. Diarised sends emails; it never reads your inbox.
• Your calendar events' details. Titles, descriptions, attendees and locations are never read: only when you're busy.
• LinkedIn or any other site. There's no browser extension and no scraping. LinkedIn connections arrive only in the file you download from LinkedIn and upload yourself.
• Your phone's address book. Only a contacts file you choose to upload, read once and not kept.
• Your location. Diarised never asks your phone or browser where you are.
• Your network, for the AI. The assistant on your pages, and the AI models behind it, never see who you know. Only an agent you connect yourself can, and only what you allow.

Google user data

Diarised uses Google in two places, and only when you choose to.

Sign in with Google

• We receive your Google account's email address, name and account ID (scopes openid, email and profile).
• We use them only to sign you in and to show your name in Diarised.

Connect Google Calendar

• Busy times (calendar.freebusy). We read only when you're busy, for the calendars you choose. We never see event titles, descriptions, attendees or locations. We use busy times so your booking pages don't offer times when you're already busy, in any of your roles.
• Your list of calendars (calendar.calendarlist.readonly). We read their names so you can choose which ones count as busy.
• A calendar for your bookings (calendar.app.created). We create one calendar in your account and add, change and remove the meetings booked through Diarised in it. We can't see or change any other calendar or event.
• We also record which Google account you connected (its email address), so you can see it in Diarised.

How we handle it

• The connection's access token is stored encrypted, with a key only our calendar service holds. Busy times are stored as start and end times only and refreshed every few minutes.
• Only you can connect, see or change your calendars. The people who help you, business account admins and Diarised staff can't.
• Google data is never sent to an AI model, never used to train AI models, never used for advertising and never sold. We don't share it with anyone except as needed to run the features above.
• Disconnecting (on the Calendar page) revokes Diarised's access at Google and deletes the connection, the stored busy times and your calendar list from Diarised. The calendar Diarised created stays in your Google account, for you to keep or delete. You can also remove Diarised's access at any time from your Google account's security settings.
• Diarised's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Microsoft 365 and Outlook.com calendars

• If you connect a Microsoft calendar, Microsoft asks you to allow Diarised to read and write your calendars (Calendars.ReadWrite), and to see your account's email address (User.Read, openid, email). Microsoft doesn't offer a narrower permission that lets an app create its own calendar, so the limits are ours:
• We read only the start, end and free or busy status of events in the calendars you choose. We never read event titles, descriptions, attendees or locations.
• We create one calendar, "Diarised bookings", and add, move and cancel the meetings booked through Diarised in it. Outlook sends your guest the invitation. We never change any other calendar or event.
• The connection's token is stored encrypted, with a key only our calendar service holds, and is used for nothing else. Disconnecting deletes it; you can also remove Diarised from your Microsoft account's app permissions.
• Some company accounts need their IT administrator to approve Diarised before you can connect.

Calendar feeds

• You can add a calendar's published link (an ICS or webcal address) so its busy times block bookings. Anyone with that link can read the calendar, so we store it encrypted and show only its name and website afterwards.
• We read it every 10 minutes and keep only the start and end of busy times. Removing the feed deletes the link and those times.
• If you connect only feeds, each booking is emailed to you and your guest as a calendar invitation, with your guest's name and email address in it.

Busy times you add

• You can add times you're busy yourself, once or every week, with a note. They block those times in every role's booking links and in the times the assistant offers. Nobody is told why.
• They're kept with you, not with a role. Only you see them and their notes: not the people who help you, not business account admins, not Diarised staff and not the assistant or any AI model. They're in your data download. They're deleted when you remove them or delete your account.

Payments and your plan

• New accounts start with a 14-day free trial. We don't ask for a card for it.
• PayFast (in South Africa) takes payments for plans in rands. When you choose a plan, your browser goes to PayFast's own page and you enter your card or other payment details there. Diarised never sees or stores card numbers or bank details.
• We send PayFast your name and email address, the plan and the amount. PayFast tells us whether each payment went through, with a reference for your subscription, which we keep so we can change or cancel it. We keep a record of each payment (date, amount, outcome) for our accounts; PayFast's full notification, which includes your name and email address, is deleted after 30 days.
• Billing emails (a trial ending, a payment received or failed, a plan cancelled) go to whoever pays: you, or the owner of the business account that pays for you.
• A business account that pays for you sees your name, whether you're set up and its own plan and seats. It never sees your pages, requests, meetings, network or calendars.
• We count how many assistant conversations your pages have each month, to apply your plan's limit. We count conversations, not what was said.

Downloading and deleting your data

• In Settings you can download everything that's yours: your network, roles, what your assistants know, booking links, meetings, requests, cards, your reports to support with their messages and settings, with the busy times you added. Screenshots sent with reports aren't included.
• You can delete your account in Settings. We email you a link to change your mind, and wait 7 days. Then we delete your roles and pages, what your assistants know, booking links, hours, requests, meetings, cards, network, calendar connections, busy times, helpers, reports to support (with their screenshots) and sign-in, and tell people with a meeting still to come that it's cancelled. Your plan is cancelled at PayFast. We keep only a note that an account was deleted, with counts and no names or addresses.
• If you cancel your plan, or a trial or free months end without one, nothing is deleted. Until you choose a plan, your public page and links send visitors to our home page and show nothing about you; you can still sign in, download your data and delete your account.

How long we keep things

Everything is deleted or made anonymous automatically when its time is up.

• Conversations with an assistant: 90 days, then deleted.
• Requests not yet confirmed with the emailed code: a day, then deleted. The codes themselves work for 15 minutes (10 for sign-in and booking codes).
• Requests: kept as the person's record. Once a request is declined, has expired or is withdrawn, the sender's name, email address and message are removed from it after 24 months, leaving only that a request was made.
• Booking holds never confirmed: released when they run out, and deleted with the visitor's details a week later.
• Details shared on a card and never confirmed: deleted from the person's network after 30 days (unless they've used them since). The scrambled internet address kept to stop abuse: 30 days.
• Business card photos: deleted as soon as the card is read, or within an hour if reading fails, unless the person keeps the photo with the contact. Details read but not saved: a day.
• Imports: the file is never stored. What an import added can be undone for 7 days after it's added; then only the contacts remain.
• Payments: PayFast's full notification of each payment, 30 days; the record of the payment (date, amount, outcome) is kept for our accounts.
• Deleting an account: 7 days to change your mind, then deleted as described above.
• Requests about your information (below): unconfirmed ones a day; confirmed ones 24 months from when they were made, as the record that they were answered.
• Reports to support: kept, with their messages and screenshot, until they're finished (fixed or closed), then for 2 years, then deleted. Deleting your account deletes them at once.
• Emails: what an email said is deleted once it's sent; the send log (who, which kind of email, when) is kept 90 days. Resend keeps its own copy for up to 30 days.
• Erased people: only the keyed, one-way codes of their email addresses and phone numbers, for as long as the person who erased them uses Diarised, so they aren't added back.
• Connected agents: an agent's access lasts an hour at a time and renews while it's used: each renewal lasts 30 days, so it keeps working as long as it's used at least once every 30 days, until you disconnect it; an agent unused for 30 days stops and must be connected again. Its daily counts are kept 40 days; a disconnected or stopped agent's record, 30 days. Its changes are in your network's history for 30 days, like anyone's.
• Backups: our database backups are encrypted and kept for up to 35 days. Anything deleted or erased stays in them until they're replaced, and if a backup is ever restored, everything erased since it was made is erased again.

Who processes the information

• Hosting: our own server at Hostinger, in the United Kingdom.
• AI model: chat messages are sent to the AI provider chosen for the assistant to write a reply: Anthropic or OpenAI, in the United States, or another model maker through OpenRouter, whose servers may be elsewhere. We choose the model for each job. They aren't used to train models. Calendar data and your network are never sent to them. Photos of business cards you scan go to the provider chosen for reading cards, which may be a different one, under the same terms.
• Email: Resend sends our emails. It keeps a copy of each email for up to 30 days.
• Payments: PayFast (South Africa) takes card and other payments for plans, on its own pages. We never receive card details.
• Push notifications: the push service of your phone or browser (Apple, Google or Mozilla) delivers notifications you turn on. They receive only the short message, which never names anyone.
• Google: for sign-in and calendars, if you connect them (see above).
• Microsoft: for calendars, if you connect one (see above).
• Agents you connect: the maker of an AI assistant you connect (Anthropic for Claude, OpenAI for ChatGPT, xAI for Grok, or the maker of any other assistant you connect) receives what you let it read. It acts for you, under your agreement with it, not on Diarised's behalf.

Asking about your information

If you chatted with, booked or sent a request to someone on Diarised, or shared your details with them, you can ask to see what they hold about you, or ask for it to be erased, at diarised.si/privacy/request. We email you a code to confirm the address is yours, then pass your request to the person whose page it is and to our support team, and you'll have an answer within 30 days. The page doesn't show whether anyone holds your details. You can also ask the person directly.

For anything else, including correcting information or a question about how Diarised itself uses your information, email hello@diarised.si. If you're not happy with the answer, you can complain to the Information Regulator (South Africa) at inforegulator.org.za.

If you use Diarised: what Diarised can and can't see, part by part, is in Settings.

Using Diarised is also covered by our terms of service.