Last updated September 30, 2026
How YakoPlan handles your information
You can plan locally without an account. Local-only planner content stays in your browser or app. If you choose cloud features, Yakoru AB processes the information needed for accounts, planning, collaboration, reminders, security, and support. YakoPlan does not sell personal information or use advertising trackers.
Information processed for your account
Registration and sign-in process your email address, authentication provider identifiers, display name, profile image when supplied, session records, language, time zone, working hours, reminder choices, theme, and accessibility preferences. Supabase Auth and configured identity providers process authentication data. YakoPlan never asks you to enter a Google, Microsoft, or Apple password into a Yakoru AB form.
Information you put in the planner
Planner content can include task and event titles, descriptions, dates, times, deadlines, labels, notes, locations, links, assignees, reminders, local focus-session history, and activity records. Shared-workspace members can see content according to their role and the calendar or workspace you share. Public links expose only the fields selected by an authorized owner.
Local plans and account synchronization
Local-only plans stay in this browser or app and are not uploaded when you sign in. Clear them in Settings or by clearing browser or app data. Account planners keep a separate offline cache and queued changes for sync. Signing out or deleting an account clears its local cache, not the separate local planner. Native apps protect authentication tokens with secure operating-system storage.
Reminders and connected calendars
YakoPlan processes notification preferences, delivery status, reminder metadata, and registered-device information. Email, browser push, APNs, and FCM delivery operate only when the corresponding production adapters, credentials, device permissions, and account settings are configured. Reminder privacy is on by default. If you turn it off, phone reminders can display task or event titles, including on the lock screen, and remote reminders send these titles through Apple or Google notification services. Browser push remains generic. Connected Google, Microsoft, or iCalendar calendars process selected calendars, events, provider identifiers, synchronization cursors, and encrypted provider credentials. Those credentials are not available to normal browser or mobile queries.
Profile images and attachments
Supabase Storage holds profile images and permitted collaboration attachments in private buckets protected by membership and ownership policies. File records can include type, size, object path, uploader, and attachment target.
Security and operational records
We process limited technical information needed to prevent abuse and keep the service reliable, such as application version, device registration, job status, delivery failures, synchronization errors, rate-limit events, authentication security events, and request identifiers. Administrator diagnostics avoid planner content. No advertising or invasive analytics SDK is included.
Retention and deletion
Active account information is retained while the account is used. Soft-deleted planner records can remain marked for deletion so changes synchronize across devices, until account deletion or an administrator-operated retention process removes them. Operational records use limited retention appropriate to security and reliability. An account-deletion request is queued for verified cleanup; access can remain available until cleanup begins. Owned shared workspaces follow the deterministic transfer-or-delete rule described on the account-deletion page.
Your choices and rights
You can change profile and planner settings, disconnect configured external calendars, revoke public links, export a selected date range, and request account deletion inside every YakoPlan app. Depending on applicable law, you may also ask for access, correction, restriction, portability, or objection through the support flow.
International processing and service providers
YakoPlan uses Supabase for database, authentication, realtime, storage, and server functions. Identity, email, notification, calendar, and hosting providers are used only when configured for the production environment. Their processing locations and contractual safeguards are documented with the production deployment and reflected in the applicable store disclosures.
Privacy questions
Use the YakoPlan support page to reach Yakoru AB through the authenticated support channel. This policy will be updated if processing, providers, or legal requirements materially change.