Dikidaki · MB \"The Mykolas\" · 2026-10-20
About Dikidaki
Dikidaki is a classroom communication service for adult parents and guardians. An adult can create a class and invite others. Children do not have independent accounts. The class owner manages the paid plan and can close the class, but does not approve or refuse other people's personal-data rights.
Data we handle
We store your email, account identifier, sign-in records, language and optional profile name, phone number or photo. Class data includes announcements, questions, replies, polls, participation responses, photos, invitations and memberships. Child records include names, guardian relationships and participation responses. We also process acceptance of rules and terms, data requests, optional device notifications and technical security information. Purchases record amounts, dates, accepted terms and payment-provider identifiers; Stripe handles card details.
Signing in with Google and Apple
Google sign-in and Apple sign-in, on the web and in the iOS app, are optional; the email code remains available, and each method works on its own. Google provides a verified email address, an account identifier and your Google profile name. If your Dikidaki profile has no name yet, we use that name as its starting display name; we never replace a name you already have. Apple shares your name only the first time you sign in with it, and we use it the same way. If your profile has no photo, the iOS app may also add your Google profile photo as a normal upload to your account; our server never downloads photos from Google. You can change or remove your name and photo in your profile at any time. Apple provides an account identifier and a verified email address, which may be a Hide My Email relay address. Your first Apple sign-in creates its own Dikidaki account under that address once you confirm the terms or hold an invitation; we never attach an Apple identity to an existing account only because the addresses match. If that address already belongs to an account, or you want to use Apple with an account under another email, you confirm that account once with an email code. Later sign-ins use the same Apple identifier, not the address Apple returns. Our server keeps only the linked provider identifier and link date, not Google or Apple access, refresh or identity tokens. Your iOS device also remembers the Apple identifier to check whether access was revoked. Your data export shows the provider and link date; the link is erased with your account. After deleting your account, also revoke Dikidaki access in your Apple Account settings: we keep no provider tokens and cannot revoke it automatically. Providers' own privacy policies apply to their accounts and sign-in screens.
Optional AI connections
A class administrator can give a chosen AI agent time-limited permission to create news, polls and questions in one class. Posts publish immediately as that administrator and families receive normal notifications. The agent cannot read chats, the roster or class funds. We receive the content and options you give the agent to publish; we do not connect to your AI provider account. Your conversation with the agent is subject to that provider’s separate privacy policy. If the app requests your verified account email, this is disclosed before authorization and shared only with your consent. The app may check its domain against its workspace rules. We store connection and app names, administrator and class identifiers, permissions, expiry, revocation and usage dates, and cryptographic token hashes. To prevent duplicate posts, we retain the request identifier, payload hash and created record identifier, rather than another copy of its text. Class administrators can see connections and metadata for successful publications. Revoke access at any time under AI connections; losing administrator rights also revokes it. Expiry or revocation does not delete earlier publications. Connection and retry-prevention records are deleted with the authorizing account or class; published content follows the ordinary retention and deletion rules.
Website usage statistics
We use Plausible on our own server to count visits and aggregate sign-in steps so we can spot difficulties. Measurements contain only a general page area, sign-in method, funnel outcome, app version and approved public campaign labels. We do not send email addresses, account or class identifiers, codes, tokens, form-field values or private content. Private parts of invitation and other links are removed. Public campaign and ad-version labels are retained in this browser tab for up to 24 hours to measure new registrations, class creation and invitation sharing. Test visits are marked separately. For a new account, we keep its signup campaign labels privately with the account for up to 90 days to attribute its first confirmed web class payment, including after the trial. Plausible receives only the public labels and a paid-customer event, without account, class, email or payment identifiers. Test payments are separated. No tracking cookies are set. We respect browser Do Not Track and Global Privacy Control preferences.
Safety reports and blocking
Reports about members, live chat messages, questions and replies can be reviewed by administrators of that class. They can see the reporter's name, reason, details and the reported content they are permitted to access. The Dikidaki service operator can also review safety reports across the service, including other content reports, and remove content that breaks the rules. Resolved reports are kept for 90 days; unresolved reports remain for review. Your own reports and personal block preferences are included in your personal export. Personal blocking hides a user's posts and related notifications for you in the selected class; it does not change membership or parent links. Class-administrator blocking suspends a member's access to that class while preserving their membership role and parent links; unblocking restores access if the class's state allows it. Removing a member from the class is a separate action.
Help and feedback
When signed in, you can report a problem or suggest an idea. We store your message, its type and status, and only the details shown to you before sending: platform, app version, page and error code. The message is linked to your account so we can reply by email, but not to a class, and class members cannot see it. We do not automatically attach screenshots, logs or class content. Only the Dikidaki service operator reads feedback; the email alert about a new message contains only its reference. Messages are deleted 12 months after they arrive or together with your account, and they are included in your personal export. Page guides you hide are remembered only on that device or browser; choices saved by older app versions are stored with your account and deleted with it.
Class fund
All current class members can see the fund's money records: the contributions and expenses members added, who added each one, optional receipt screenshots, the remaining balance and earlier reviewed records. Any member can add a contribution or an expense; only the person who added it or a class administrator can change its amount or delete it, and these changes are kept in the fund's history. This is manual bookkeeping: Dikidaki does not transfer these funds or connect your bank account. Members can download the visible fund data as CSV. Deleting a child's record removes its individual contribution and correction rows, retaining only an aggregate amount no longer linked to the child or family to preserve the balance. Deleting an adult's account removes their attribution; the amounts they recorded stay so the balance remains correct. Fund data and receipts are deleted with the class. Do not put unnecessary personal or bank details in descriptions or receipt screenshots.
How data is used
Account and purchase information is used to perform the service contract. Security and abuse-prevention processing serves the legitimate interest of protecting the service; required financial records meet legal obligations. Class content is used for classroom communication and organisation. Organisers must have lawful authority to supply children's and other people's data; payment alone does not provide that authority. Do not upload health details, national identifiers or other sensitive information unnecessary for class communication. Additional profile details and device notifications are optional. We do not use advertising trackers.
Who can access data
Class members can see shared content, child names and guardian relationships, participation lists and parent-directory profiles. Owners and administrators manage membership. The app checks current authority when serving files; your profile photo may be visible in your other classes. We cannot recall copies already downloaded or emails already received by other people. Use only fictional information in the demo. Necessary hosting, storage, email and payment providers may process data, including Cloudflare R2, Resend and Stripe. If you enable device notifications, device push identifiers and notification content are processed for delivery by Apple Push Notification service (APNs) on iOS, Google Firebase Cloud Messaging (FCM) on Android or your browser's push provider on the web. We do not use Firebase for accounts or the class database. External websites have their own privacy practices.
Class retention and closure
Each account gets one free class with a 30-day trial. Every additional class needs its own paid plan before use. A trial includes 30 posts, 30 polls, 30 chat threads and 100 MB; reaching any one limit requires upgrading for new activity. Deleting posts, polls or chats does not reset their counts. Reaching a limit does not shorten the trial. Seven days before the trial ends, we warn the owner that the unpaid class and its data will be deleted after the full 30 days. Existing unpaid trials get at least seven days of deletion notice when this policy takes effect. New paid school-year plans end on August 31; the exact date is shown before payment. Remaining trial time is preserved and previously purchased access is not shortened. After paid access ends, members have 30 days of read-only access, export and renewal before the class is deleted. Owner-requested closure removes access to class content immediately. We prepare one private JSON copy without uploaded files, then delete the source class data and files without a seven-day wait. Members present at closure receive the private download link by email. The copy expires seven days after closure and may be removed sooner to fulfil an erasure request. If preparing the copy fails, we notify members and continue deletion. This is not a class-restoration period. Previously scheduled closures keep their original deletion date. Purging removes class memberships, child records, content and files, while shared adult accounts and other classes remain. Existing legacy classes do not automatically start a trial.
Leaving, accounts and child data
Download your data from Data and privacy in Settings. Leave a class from class management, and unlink yourself from a child or initiate child deletion from the child's management menu in Members. Account deletion is available in profile settings. Leaving revokes access but does not itself erase shared content. A child linked to another guardian is not deleted solely because you leave or erase your account. Shared conversations, photos and conflicting guardian claims receive individual review. Your rights request does not require the class owner's permission. Owners need to transfer or close a class before ordinary departure, but we still accept their erasure requests.
Exports and separately retained records
Download my data provides a JSON copy. File references do not provide public access and stop working when files are deleted or your access changes. Separately prepared personal ZIP archives require sign-in, expire after 24 hours and check access again at download. Closed-class JSON exports use the seven-day period described above. Personal exports exclude other people's private ballots and sign-in details. Resolved data-request records are removed after 90 days. Legally required financial records can remain separately from a deleted class. Backups, security records, legal retention grounds and provider copies are assessed during a request; we explain what was deleted and what is still lawfully retained. Changing a name alone is not treated as erasure.
Your rights and contact
You can request access, correction, erasure, restriction, object to processing and request portability where applicable. Use the app's download and deletion actions or the email below, including after leaving a class. We verify identity and, where needed, authority to act for a child. We normally respond within one month and explain any lawful extension in time. You may also complain to Lithuania's State Data Protection Inspectorate (vdai.lrv.lt).