Dailify

Privacy Policy

Last updated 13 November 2026 · Applies to dailify.co.za and app.dailify.co.za

Dailify places outbound calls on behalf of South African financial advisers, and books verified appointments into their calendars. This policy describes what personal information we handle, why, and what we do not do with it.

The short version. We read when you are busy, not what you are busy with. We write only the meetings we book. We never sell personal information, never use calendar data for advertising, and never use it to train machine-learning models.

Who we are

Dailify is operated by Dailify (Pty) Ltd (registration 2026/452962/07, 64 Jan K Marais, Malanshof, Randburg, 1792) ("we", "us"), the responsible party for the purposes of the Protection of Personal Information Act 4 of 2013 (POPIA).

Information OfficerGarth White (director) — garth@dailify.co.za
Contactgarth@dailify.co.za
Service addresshttps://dailify.co.za

Two groups of people

Dailify handles information about two distinct groups, and the rules differ for each.

Brokers — our customers

Financial advisers and their staff who sign in to Dailify. We are the responsible party for their account information.

Prospects — the people we call

Consumers Dailify sources itself and holds consent records for. Dailify is the responsible party for that data. Brokers do not supply leads, and Dailify does not call a broker's own contacts. Where a prospect agrees to a meeting, we pass the details needed for it to the broker they are booked with.

Broker information we hold

WhatWhy
Name, work email, mobile numberTo create and secure the account
Brokerage name, FSP licence number, VAT numberRegulatory identification and invoicing
Business address of the brokerage (street, unit or building, suburb, city or town, province, postal code)To know who and where our customer is, and to print on invoices.
Calendar connection and the email address of the connected accountTo read availability and book meetings
Wallet balance and ledger entriesBilling for verified appointments
Audit records of actions taken in the portalAccountability, and dispute resolution

Calendar data — Google and Microsoft

Connecting a calendar is optional, and Dailify cannot book meetings without one. When you connect one, this is exactly what we ask for and what we do with it.

Google account data

ScopeWhat it lets us do
userinfo.emailRead the email address of the account you connected, so the portal can show you which calendar is attached.
calendar.events.freebusyRead busy blocks only — start and end times. This returns no event titles, no attendees, no descriptions and no locations.
calendar.events.ownedCreate and cancel only the meetings Dailify books, in your own calendar. We do not read, edit or delete events created by anyone else, and we never touch calendars other people share with you.

We deliberately do not request the broader auth/calendar scope, which would grant full read and write access to every event on every calendar, nor calendar.events, which reaches calendars other people share with you as well as your own. The two narrower scopes above do everything the product needs.

Microsoft 365 account data

The Microsoft integration uses User.Read, Calendars.ReadWrite and OnlineMeetings.ReadWrite, with offline_access so the connection survives without asking you to sign in before every booking. Free/busy is read through Microsoft Graph's getSchedule, which likewise returns busy intervals and no event content.

Limited use

Dailify's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically, we do not:

AI services and your calendar data

Dailify's calls are made by an AI assistant. The only thing it learns from your Google calendar is which times you are free: Dailify works those out from the busy blocks above and gives the assistant a short list of free times, so it can offer the client two of them and book the one they choose. Those times reach:

Nothing else from Google reaches any AI service: no busy blocks, no event titles, attendees, descriptions or locations, and not the event Dailify creates, its ID or its Google Meet link. Neither provider may train its models on this data: OpenAI does not train on data sent through its API, and Inworld's terms (section 4(f)) bar training its generally available models on customer material that is not public. Dailify does not train or fine-tune any AI model, on calendar data or anything else. No other AI service, aggregator or model hub receives Google user data.

The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

How the connection is stored

The refresh token that keeps your calendar connected is encrypted with AES-256-GCM before it is written to our database, and decrypted only in memory for the duration of a single API call. It is never logged and never displayed.

Withdrawing access

You can disconnect a calendar in the Dailify portal, or revoke access directly in your Google Account or Microsoft account, at any time. Revocation takes effect immediately. Campaigns that depend on that calendar pause rather than book blindly, and the stored token is discarded.

Calls and recordings

Where the data lives

Some processors necessarily receive data outside South Africa, including Google and Microsoft, when you connect a calendar of theirs, and only the calendar data described above; and, during a call, the AI services that run it: OpenAI for speech recognition, the conversation and the voice, or Inworld AI for the voice where a South African one was chosen. Their own terms govern that processing.

Who else sees it

We do not sell personal information. We share it only with service providers who are necessary to run Dailify — hosting, telephony, email delivery and payments — each bound to process it only on our instruction. We disclose information to a regulator or a court only where the law requires it.

How long we keep it

Recordings and transcriptsAnonymised after 180 days
Appointment and billing recordsFive years, as required by financial-services record-keeping rules
Calendar tokensUntil you disconnect or revoke; discarded immediately on either
Account informationFor the life of the account, then deleted or anonymised

Your rights under POPIA

You may ask us what personal information we hold about you, ask us to correct or delete it, object to processing, or complain to the Information Regulator. Write to garth@dailify.co.za and we will respond within 30 days.

The Information Regulator of South Africa can be reached at complaints.IR@justice.gov.za.

Security

Changes

If we change this policy we will update the date at the top, and tell account holders by email where the change is material.