Privacy
Last updated 27 August 2026
BABA and DIDA are self-hosted software. There is no service behind them and no server of mine that your installation talks to: what they read stays on the machine you run them on. This page is about the one Google integration DIDA offers, because Google requires a policy to be published for it.
What DIDA reads from Google
With your permission, and only after you grant it, DIDA reads two things from the Google account you connect:
- — Contacts (
contacts.readonly): names and birth dates, so the household knows who its people are and whose birthday it is. - — Calendar (
calendar.readonly): events and their dates, so a photograph taken years ago can be offered the name of the occasion it belongs to.
Both are read-only. Nothing is ever written back to your Google account, and no other Google data is requested.
Where it goes
Into the database of your own DIDA installation, on your own hardware. It is not sent anywhere else — no third party, no analytics, no advertising, no model training. I have no access to it: I do not run your installation and there is nothing for it to phone home to.
How long it is kept
Until you disconnect. Disconnecting deletes the stored Google token from your installation and the daily read stops. You can also revoke DIDA's access at any time from your own Google account, at myaccount.google.com/permissions, which has the same effect from the other side. The names and birth dates already read remain in your database until you remove them, the same as any other data you put there.
This website
boskovic.biz is a static page. It sets no cookies, runs no analytics, and collects nothing about you.
Contact
Ivo Bošković — [email protected]