Private preview · November 13, 2026

Your work
is personal.

Limmie Tasks is provided by Carson Kuehne. This notice covers the invited Limmie preview and its optional connections. The Microsoft organization integration described below is being prepared; it is available only after deployment, organization approval and your individual connection.

This website

The public site displays product information and invented example Limmies. It explains email-code sign-in through Supabase and lets an invited recipient verify an email code to accept a shared Limmie. The public invitation page keeps sign-in credentials in memory. The optional Microsoft workspace at /work/ displays your own tasks and shared work and keeps its Limmie session in tab session storage until sign-out or the tab session ends. Neither includes advertising, analytics scripts or tracking cookies.

Like other websites, its hosting provider processes connection information needed to deliver a page, such as an IP address and the requested address. Task-opening links contain a task identifier and may contain an account identifier. They do not contain your notes, task title, sign-in tokens or calendar credentials. Treat the link as private.

Your Limmie account and sync

If you enable account sync, Supabase provides account authentication and stores your synced task and reminder records. These include titles, dates, progress, diary entries, completion state and web references. Private tasks are restricted to their owner. When you share a task, accepted members can see its shared workflow, journal, host and the references they have verified access to. Your existing private notes are not automatically shared.

The app encrypts local task storage on Windows, Mac, iPhone and Android. Cloud sync uses encrypted transport and server access controls. It is not end-to-end encrypted: the backend must process your synced records to provide the service.

Calendars and related items

Google and Microsoft connections are optional. Calendar access follows the permissions and calendar choices you approve. Calendar-derived task content can be included in account sync when you choose to sync it.

Cloud calendar and file connections keep encrypted provider credentials in the Limmie service. The service processes calendar context and reviewed work blocks while your devices are closed. Local file paths and device appearance settings remain on the device. Linked local files are not uploaded by task sync. Web references may point to documents or emails stored by their original provider; opening one takes you to that provider.

Files you choose to upload

Choosing a local file to attach sends a copy to private Limmie storage hosted by Supabase. Each account has a 50 MB complimentary allowance, with a current limit of 50 MB per file. Cloud file and folder links use no storage allowance. Uploaded copies do not automatically update when the original changes.

Copies are private to the uploader until attached to a Shared Limmie, whose active members can download them while the uploader remains a member. Downloads require a fresh access check and use a short-lived address. This is not end-to-end encrypted storage. Manage storage in the app to delete an uploaded copy; doing so makes it unavailable to all tasks using it without deleting the original on your device. Unlinking a reference, completing a task or signing out does not delete its uploaded file.

Mobile notifications

If you enable notifications in the installed phone app, Limmie stores a device push token, time zone and your alert preferences. Expo and Apple deliver discreet reminder, sharing and handoff messages. Delivery includes account and task identifiers so tapping an alert can open the correct item; task titles, diary entries and document contents are not included. Choose each alert type in Account → Alerts on iPhone. Signing out removes this phone’s push registration.

Keeping completed work

Current Limmie apps move completed work into the archive after 30 days and remove eligible completed task content after 365 days. Private cleanup depends on the app running and syncing; shared work uses server-side retention. Reopened work is active again. These rules do not automatically delete uploaded copies, original provider files, account records or backups.

Completing, disconnecting and removing data

Completing a task records completion; it does not erase its history. Signing out stops account sync on that device, but does not delete stored tasks from your account. Disconnecting a calendar ends that app connection and does not by itself erase previously imported tasks.

Self-service account export and deletion are not ready for public release. Email [email protected] to request an export, correction or deletion. Tell us which account and what you want included; do not send passwords, sign-in codes or private task contents. We first verify control of the existing account, confirm the scope and explain effects on shared work, uploaded copies and connected calendars. We will explain any unresolved cleanup or retained records before describing a request as complete. The complete account-removal process, record retention periods and backup cleanup are still being finalized for the Microsoft release. No automatic removal deadline is promised by this preview notice.

Optional Microsoft 365 organization pilot

After your organization enables the pilot and you opt in, the Teams, Outlook and Copilot integration uses your verified Microsoft identity to access your Limmie work. Directory searches store a per-account email-to-Microsoft-identity mapping to bind invitations to the intended colleague. An Outlook capture reads the email currently open only when you choose it; reviewed content can become task notes. Original files and emails remain with Microsoft.

For meetings you explicitly enable, Limmie retrieves structured Copilot action items after the meeting and stores pending suggestions, source references and delivery state. It does not archive the meeting transcript. Suggested titles and owners can appear in the meeting chat. The assigned person must accept or edit a suggestion before it becomes their task. Limmie does not automatically list private work in group conversations. When you explicitly insert, paste or request a task or step reference, its compact title, colleague names and progress snapshot can be visible to everyone in that Teams conversation. Notes, journal entries and files stay behind their existing access checks. Posting a card does not grant task or file access, and revoking access does not retract a snapshot already posted to Teams. Pausing a meeting or disabling Teams and Copilot access stops new processing; accepted tasks and existing records remain. Email [email protected] for deletion or export requests. Disconnecting or uninstalling does not erase previously accepted work, Microsoft messages or files. Organization setup also stores capability choices, consent state and audit records to enforce access; those audit records currently have no automatic expiry.

Questions about your data

Contact Carson Kuehne at [email protected] without signing in. See support information. You can also read Supabase’s privacy information.