Dainvo
Log inSign up

Privacy Policy

Last updated: August 30, 2026

Dainvo is a calendar, task, and planning application for desktop and mobile devices, operated by Intagri Technologies LLC. This Privacy Policy explains how Dainvo collects, uses, stores, shares, and protects information when you use our websites, desktop applications, mobile applications for iOS and Android, connected integrations, support channels, account features, billing features, and related services.

Dainvo is a local-first product. That means much of your calendar, task, planning, and settings data is stored on your own device. Some information may still be processed by Dainvo, by service providers, by app stores, or by integrations you choose to connect, as described below.

1. Who We Are

Dainvo is an Intagri Technologies LLC company.

Company: Intagri Technologies LLC
Mailing address: 131 Continental Dr Ste 305, Newark, DE 19713-4324, United States
Privacy contact: contact form
Support contact: support form

2. Scope of This Policy

This Privacy Policy applies to:

  • the Dainvo websites, including dainvo.com and the users.dainvo.com account site, and pages hosted on WordPress or other web-hosting services;
  • Dainvo desktop applications for Windows, macOS, and Linux;
  • Dainvo mobile applications for iOS, iPadOS, and Android, whether you use them alongside the desktop app or on their own;
  • Dainvo builds distributed directly, through the Apple App Store, through Google Play, through the Mac App Store, through the Microsoft Store, or through other approved distribution channels;
  • Dainvo account, licensing, billing, update, support, and diagnostic features;
  • integrations you choose to connect to Dainvo, including calendar, task, meeting, communication, authentication, and productivity providers.

This Policy does not control the privacy practices of third-party services that you connect to Dainvo or that Dainvo features rely on, such as Google, Microsoft, Todoist, TickTick, Zoom, Webex, Apple, OpenAI, Anthropic, Stripe, Supabase, Cloudflare, Open-Meteo, or CalDAV providers. Those services process information under their own privacy policies and terms.

3. Information We Collect

3.1 Information You Provide Directly

We may collect information that you choose to provide, including:

  • name;
  • email address;
  • account signup, login, or authentication information;
  • support requests, feedback, bug reports, and messages you send to us;
  • billing, subscription, license, or entitlement information;
  • diagnostic files, screenshots, logs, or other troubleshooting materials you choose to send to us.

Please do not send us passwords, recovery codes, OAuth tokens, app passwords, payment card numbers, private keys, confidential documents, or sensitive calendar exports unless we specifically request a safe diagnostic artifact for support.

3.2 Local App Data on Your Devices

Dainvo desktop and mobile apps store application data locally on your device. Depending on your platform, version, settings, and connected integrations, local app data may include:

  • calendar accounts and calendar metadata;
  • calendar events, titles, descriptions, locations, links, attendees, reminders, availability, recurrence data, and sync status;
  • tasks, task descriptions, due dates, deadlines, labels, priorities, completion status, reminders, task blocks, and provider metadata;
  • buckets, scheduled work blocks, bucket tasks, file-link references, and related planning metadata;
  • Projects, subprojects, Project task membership, Project blocks, local Project Notes, and Project file-link references;
  • local Markdown Daily Notes and other Dainvo note files when you enable those features;
  • local settings, preferences, interface settings, calendar visibility settings, and sync preferences;
  • import/export metadata, sync cursors, safe sync errors, and diagnostic notes;
  • local file or folder path references that you intentionally attach to buckets or planning items.

Local file-link features store references to file or folder paths. Dainvo does not copy, upload, delete, rename, move, or read the contents of those linked files merely because you create a file link.

3.3 Mobile App Data (iOS and Android)

The Dainvo mobile apps for iPhone, iPad, and Android require a Dainvo account sign-in. They can be used alongside the Dainvo desktop app or on their own. In addition to the local app data described above, the mobile apps process:

  • Locally cached content: calendars, events, tasks, planning items, connected-account summaries, license status, and sync state are cached in a local database on your device so the app works quickly and offline.
  • Secure credential storage: your Dainvo sign-in session and connected-provider tokens are stored using platform secure storage backed by the iOS Keychain or Android Keystore. Microsoft sign-in tokens are held in Microsoft's authentication library cache on your device. Token payloads are not stored in the app's regular local database.
  • Device registration: to manage the devices signed in to your account and apply license limits, the mobile app sends Dainvo a randomly generated, app-created device identifier (not a hardware identifier and not an advertising identifier), together with the device platform, operating-system name and version, and app version.
  • Optional announcement notifications: if you explicitly enable notifications in the signed-in mobile app, Google Firebase Cloud Messaging (FCM) and, on Apple devices, Apple Push Notification service (APNs) process a notification registration token and delivery requests. Dainvo stores the FCM registration token with your Dainvo account-device record, platform, locale, app version, license tier, notification-permission status, and supported announcement capabilities so that it can target and deliver the announcements you are eligible to receive.

The current Dainvo mobile apps request internet and network-state access and, only when you choose to enable optional announcements, notification permission. They do not request device permissions for the camera, microphone, photos, contacts, device location, or the device's built-in calendar database; calendar and task sync happens through the provider accounts you connect, not by reading the device calendar. Notification permission is not requested automatically on first launch, and refusing or withdrawing permission does not prevent in-app announcements.

Dainvo records privacy-preserving daily aggregate counts for announcement impressions, dismissals, action clicks, notification opens, and requests accepted by FCM. These reports are grouped by campaign, platform, locale, and action and do not retain user-level engagement history. Temporary per-installation delivery and deduplication records are used for retries and operational diagnosis and expire after 30 days.

The current Dainvo mobile apps do not include third-party advertising, analytics, or crash-reporting SDKs, do not use advertising identifiers, and do not track you across other companies' apps and websites. If a future version adds diagnostics or crash reporting, we will update this Policy and the app-store privacy disclosures first.

3.4 Dainvo Account Sync Data

If you sign in with a Dainvo account and use Dainvo-hosted features, some content is stored on Dainvo servers so it can stay in sync across your active devices. Depending on the features you use, Dainvo-hosted sync data may include:

  • Dainvo tasks and task projects, including titles, descriptions, labels, due dates, deadlines, priorities, recurrence rules, completion status, reminders, scheduling blocks, and attachment or link metadata such as a display name, type, URI, MIME type, and size; Dainvo Account sync does not upload the contents of a linked local file;
  • Dainvo-owned planning data for connected-provider tasks, including privacy-minimized provider references, My Day dates, multi-block preferences, and task-block times, without provider task titles, descriptions, completion state, passwords, or OAuth tokens;
  • paid Bucket sync data, including Bucket titles, descriptions, time ranges, status, display mode, task membership, and exact provider calendar projection identifiers; linked local file paths and provider Event content stay device-local;
  • paid Project sync data, including Project names, descriptions, colors, workflow status, deadlines, hierarchy, task membership, scheduled blocks, and exact assigned or projection calendar identifiers; Project Notes, linked local file paths, and provider Event content stay device-local;
  • Account classification settings, supported Account and Calendar bindings, priority ranks, and Standard hours when your plan includes those features;
  • the encrypted source URL and safe sync bookkeeping for each calendar subscription you choose to sync across devices; subscription Event content and display settings stay device-local;
  • Dainvo Calendar and Event content only for local Dainvo Calendars that an eligible user explicitly enrolls in cross-device sync;
  • Obsidian task-relay data, such as task titles, note paths, note titles, headings, labels, and due dates, if you enable the Obsidian mobile relay;
  • profile information such as display name and avatar image, account settings, and sync bookkeeping records.

Current Dainvo Account sync does not upload Dainvo Daily Notes, Project Notes, note bodies, or local file paths linked to Buckets or Projects. Mobile Daily Notes editing and cross-device Daily Notes sync are in development and are not available in the current release.

Dainvo-hosted sync data is protected by per-user access controls so that each account can access only its own records. Calendar events and tasks that live in a connected provider account, such as Google or Microsoft, continue to sync directly between your devices and that provider. Connecting a provider does not upload that provider's Event or task content to Dainvo servers. This provider boundary does not apply to Dainvo-owned tasks, Dainvo-owned planning metadata, or Dainvo Calendars that you explicitly enroll in Dainvo Account sync.

3.5 Connected Provider Data

If you connect a third-party service, Dainvo may access and process the information needed to provide the features you enable. Depending on the integration, this may include:

  • account identifiers, account email addresses, profile names, and connection status;
  • OAuth authorization responses, access tokens, refresh tokens, token expiration data, and similar credential data;
  • CalDAV server URLs, usernames, app passwords, or credentials you enter for CalDAV sync;
  • calendar lists, calendar colors, event data, meeting metadata, attendees, links, reminders, recurrence data, and availability data;
  • task lists, projects, sections, labels, task titles, descriptions, due dates, reminders, completion status, and provider task IDs;
  • meeting data used to create, read, update, or delete meetings when a meeting provider integration is enabled;
  • provider sync tokens, delta links, page tokens, etags, and other technical sync metadata.

Dainvo may support or prepare support for integrations such as Google Calendar, Google Tasks, Google Sign-In, Microsoft 365, Outlook Calendar, Microsoft To Do, CalDAV providers, Todoist, TickTick, Zoom, Webex, Supabase, Stripe, Apple services, Microsoft Store services, and update or release-hosting providers. Not every Dainvo build includes every integration, and not every user enables every integration.

3.6 Account, Authentication, and Billing Information

If Dainvo account login, licensing, subscriptions, or paid access features are enabled, we may process:

  • account email address and account identifier;
  • authentication session status and login timestamps;
  • subscription, purchase, license, entitlement, or access status;
  • billing customer identifiers and transaction identifiers;
  • registered device records for the desktop and mobile devices signed in to your account, as described in this Policy;
  • app-store receipt, purchase, or entitlement information where needed to confirm access.

Payment card details are processed by payment processors or app stores, such as Stripe, Apple, Google, or Microsoft. Dainvo does not need to store full payment card numbers to provide subscription or license access.

3.7 Website, Email, and Support Data

When you visit our website, contact us, join a waitlist, request support, or communicate with us by email, we may collect:

  • your email address and message content;
  • your name, company, or role if you provide it;
  • ordinary email metadata;
  • IP address, browser type, device type, operating system, referring pages, pages visited, and timestamps;
  • cookie, WordPress, hosting, security, analytics, or spam-prevention data, depending on the website configuration.

If our WordPress site uses cookies, analytics tools, embedded content, forms, anti-spam tools, or security plugins, those tools may process technical information needed to provide, secure, measure, or improve the website.

3.8 Updates, Diagnostics, and Crash Information

Dainvo may check for software updates or release metadata. Update checks may reveal technical information such as app version, operating system, platform, architecture, IP address, request time, and user agent to Dainvo or to the service hosting the update feed.

Dainvo desktop crash diagnostics are enabled by default and can be disabled immediately in Settings > Sync & Privacy. When enabled, diagnostic data may include app version, operating system, device type, error messages, stack traces, feature area, timestamps, and sanitized technical logs. Turning the setting off closes active diagnostic clients and prevents new automatic reports; it can be turned on again without restarting the app.

Dainvo desktop builds may use a crash- and error-reporting service, currently Sentry, to receive sanitized crash and error reports. Screenshots and Sentry's default collection of personally identifiable information are disabled. Payloads are filtered to remove tokens, credentials, file paths, calendar or task content, and user-interface interaction or navigation breadcrumbs before they are sent.

Manual feedback is sent only when you choose to open and submit the feedback form. The manual feedback form is unavailable while crash diagnostics are disabled. The current Dainvo mobile apps do not include a crash-reporting service, as described in the mobile section above.

4. How We Collect Information

We collect information in the following ways:

  • directly from you when you create an account, contact us, request support, submit feedback, or enter information into Dainvo;
  • from your device when Dainvo stores local application data or reads local app settings;
  • from integrations you connect after you authorize Dainvo to access them;
  • from app stores, payment processors, and licensing systems when needed to confirm purchases, subscriptions, or entitlements;
  • from website hosting, WordPress, email, analytics, anti-spam, security, and diagnostic tools.

5. How We Use Information

We use information to:

  • provide, operate, maintain, and improve Dainvo;
  • create, display, edit, import, export, and sync calendars, events, tasks, reminders, meetings, buckets, and planning items, including syncing Dainvo-hosted content across the desktop and mobile devices signed in to your account;
  • register and manage the devices signed in to your Dainvo account and apply plan or license limits;
  • connect to third-party integrations that you choose to authorize;
  • authenticate users and maintain account sessions;
  • process subscriptions, licenses, purchases, billing status, refunds, and access entitlements;
  • send service messages, support replies, security notices, product updates, and administrative communications;
  • deliver optional localized in-app and mobile notification campaigns that you are eligible to receive and measure their performance using aggregate reporting;
  • troubleshoot errors, investigate bugs, verify update delivery, and improve reliability;
  • protect the security and integrity of Dainvo, users, integrations, and our systems;
  • comply with legal obligations and enforce our rights, agreements, and policies.

We do not sell your calendar, task, meeting, bucket, or connected-provider content. We do not use that content for targeted advertising. We do not use that content to train generalized AI models.

6. Connected Integrations

6.1 General Integration Rules

Integrations are optional unless a feature clearly requires a connected provider. When you connect an integration, Dainvo requests the permissions needed to provide the relevant user-facing feature. Integration data is used to provide or improve the feature you enabled, maintain sync, process user-requested actions, troubleshoot errors, secure the service, and comply with law.

You can disconnect integrations in Dainvo where controls are available. You may also revoke Dainvo's access from the third-party provider's account settings. Disconnecting an integration may stop future sync, but it may not automatically delete local data already stored on your device or data retained by the provider.

6.2 Google APIs

Google integrations are optional. Dainvo requests Google permissions only when you choose to connect a Google account or enable a Google-powered feature. Current releases may request Google Sign-In profile permissions, Google Calendar access, or Google Tasks access. Dainvo should not request Gmail or Google Drive access unless a later release implements the relevant feature and you separately authorize that access.

The current Dainvo desktop app requests these Google OAuth scopes: openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile, https://www.googleapis.com/auth/calendar, and https://www.googleapis.com/auth/tasks. Dainvo uses these scopes only for the Google-connected features described in this section.

The current Dainvo mobile apps request a narrower set of Google permissions: sign-in profile information (openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile), Google Calendar (https://www.googleapis.com/auth/calendar), and Google Tasks (https://www.googleapis.com/auth/tasks). The mobile apps do not request Gmail access.

When you connect Google, Dainvo may process Google account identity data, including your Google account identifier, email address, display name, OAuth authorization response, access token, refresh token, token expiration time, approved scopes, and related connection status. Dainvo uses this information to identify the connected account, keep the same Google account matched to the same Dainvo connection, refresh access that you authorized, show connection status, and disconnect access when requested.

For Google Calendar and Google Meet features, Dainvo may access, store locally, and sync Google Calendar data such as calendar lists, calendar IDs, calendar names, colors, time zones, access roles, conference capabilities, events, event IDs, event titles, descriptions, locations, start and end times, recurrence rules, availability status, attendees, attendee response status, reminders, meeting links, Google Meet conference data, etags, sync tokens, page tokens, and related metadata. Dainvo uses this data to display your calendars, sync events, create events, update events, delete events, move events between calendars, preserve event metadata, create or add Google Meet links when you ask, update Google Meet-backed calendar events, and troubleshoot sync or connection errors.

For Google Tasks features, Dainvo may access, store locally, and sync Google Tasks data such as task lists, list IDs, list titles, task IDs, task titles, notes, due dates, completion status, completed timestamps, deleted or hidden status, parent task references, ordering positions, task links, etags, page tokens, and sync metadata. Dainvo uses this data to display task lists, sync tasks, create tasks, edit tasks, complete or reopen tasks, delete tasks, organize tasks, and schedule Dainvo task blocks for planning.

The Gmail connection and starred-email task workflow are paused and are not available in the current Dainvo release. Current builds do not request Gmail access. If Dainvo reintroduces a Gmail feature, we will update this disclosure where necessary and request the relevant authorization before access.

Dainvo stores Google integration data primarily on your local device. Local storage may include Google account summaries, cached calendar, Event, and task metadata, provider IDs, sync state, pending sync operations, and encrypted OAuth token payloads. Provider tokens are intended to be stored by the desktop app using encrypted operating-system-backed storage where supported, and sensitive provider operations are intended to run in the Electron main process rather than being exposed to the renderer interface.

Dainvo uses Google user data only to provide, maintain, secure, troubleshoot, and improve user-facing Dainvo features that you request and that are visible in the app, including account connection, calendar sync, Event management, Google Meet scheduling, Google Tasks sync, task planning, support, abuse prevention, and security. Dainvo does not use Google user data to train generalized AI models.

Dainvo's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Dainvo does not sell Google user data, use Google user data for advertising or retargeting, transfer Google user data to advertising platforms, data brokers, or information resellers, or use Google user data to determine creditworthiness or lending eligibility.

Dainvo does not allow humans to read your Google user data unless you first ask for support and affirmatively provide or authorize access to the specific information needed, access is necessary for security or abuse investigation, access is necessary to comply with applicable law, or the information is aggregated and used for internal operations in accordance with applicable privacy laws.

Dainvo does not transfer Google user data except as needed to provide or improve the Google-connected features you request with your consent, to maintain security, to comply with applicable law, or as part of a merger, acquisition, or sale of assets after obtaining explicit prior consent where required by Google's Limited Use requirements.

You can disconnect a Google account in Dainvo where controls are available. Disconnecting removes locally stored OAuth tokens and stops future Google API access from Dainvo for that account. You can also revoke Dainvo's Google access from your Google Account security settings. Disconnecting or revoking access may not automatically delete calendar Events, tasks, or other data already stored by Google, and may not automatically remove local cached app data that remains on your device until you delete it, use available deletion controls, remove the connected account, or uninstall and delete Dainvo's local app data.

If Dainvo changes the way it accesses, uses, stores, shares, or transfers Google user data, we will update this Privacy Policy and, where required, provide in-product notice or request renewed consent before using Google user data for a new purpose.

6.3 Microsoft Services

If you connect Microsoft services, Dainvo may access Microsoft account identifiers, Outlook Calendar data, Microsoft 365 calendar data, Microsoft To Do data, events, attendees, reminders, tasks, lists, due dates, and sync metadata, depending on the permissions you approve.

On mobile, Microsoft sign-in uses Microsoft's authentication library (MSAL), and Microsoft sign-in tokens are held in that library's secure cache on your device. The current Dainvo mobile apps request Microsoft Graph permissions limited to calendars (Calendars.ReadWrite), tasks (Tasks.ReadWrite), and basic profile information (User.Read).

Dainvo Outlook Email features, including the Outlook add-in, are in development and are not available in the current release. If you are invited to test an unreleased Outlook add-in build, Dainvo processes only the email you explicitly choose to capture as a task. The add-in sends the title you approve and, when Outlook provides them, the sender name, sender address, and received date. It also sends the mailbox address and internet message ID, or an Outlook item ID fallback, only as transient inputs to a user- and account-scoped HMAC duplicate-prevention fingerprint. Dainvo does not store or log those raw identifiers.

The Outlook add-in does not read or send the message body, message preview, recipients, thread, attachments, or Microsoft credentials. It does not request Microsoft Graph Mail permission for email capture, and it does not edit, move, flag, or delete the original Outlook message. The resulting Dainvo task and privacy-minimized email-source metadata sync to your signed-in Dainvo desktop and mobile devices through Dainvo's normal task snapshot and delta service.

The Outlook add-in connects to your Dainvo account through a public OAuth client using authorization code with PKCE and no client secret. You can review and revoke recognized Outlook add-in grants from the Connections page at users.dainvo.com. Revoking a grant stops future captures by that client but does not delete tasks already created or affect the original Outlook message.

6.4 CalDAV

If you connect a CalDAV account, Dainvo may process the server URL, username, app password or credential, calendar metadata, event data, and sync metadata needed to connect and sync with that CalDAV server. You are responsible for ensuring that you have permission to connect the account and that any credentials you enter are valid for that provider.

6.5 Zoom

Zoom integrations are optional. If you connect Zoom, Dainvo may request Zoom OAuth permissions needed for scheduled meeting workflows, such as reading your Zoom user profile and creating, reading, updating, or deleting Zoom meetings that Dainvo manages for user-facing calendar events.

When you connect Zoom, Dainvo may process Zoom account identity data such as your Zoom user ID, account email address, display name, OAuth authorization response, access token, refresh token, token expiration time, approved scopes, Zoom API URL, and connection status. Dainvo uses this data to identify the connected Zoom account, verify that the account has the required meeting permissions, refresh access that you authorized, show connection status, and disconnect access when requested.

For Zoom meeting features, Dainvo may send Zoom meeting details to Zoom, including meeting topic, agenda or description, start time, duration, time zone, waiting-room setting, join-before-host setting, mute-upon-entry setting, approval type, and default passcode setting. Dainvo may receive and store Zoom meeting metadata such as meeting ID, meeting UUID, host ID, topic, start time, duration, time zone, status, attendee-safe join URL, web URL, conference ID, and related provider metadata. Dainvo uses this data to create Zoom meetings from calendar-event workflows, add Zoom meetings to existing provider-backed calendar events, update Zoom meetings when event details change, delete Zoom meetings when you cancel them through Dainvo, and show safe join links in the app and in calendar invitations.

Dainvo is not designed to access Zoom cloud recordings, meeting transcripts, in-meeting audio, video, chat messages, participant reports, webinar data, phone data, or account-wide admin data for the Zoom meeting-link workflow described here. Dainvo does not request Zoom admin scopes for this workflow unless a future feature separately explains and requests that access.

Dainvo stores Zoom integration data primarily on your local device. Local storage may include Zoom account summaries, meeting IDs, attendee-safe join links, cached meeting metadata, provider IDs, and encrypted OAuth token payloads. Provider tokens are intended to be stored by the desktop app using encrypted operating-system-backed storage where supported, and sensitive provider operations are intended to run in the Electron main process rather than being exposed to the renderer interface.

Dainvo uses Zoom data only to provide, maintain, secure, troubleshoot, and improve the Zoom-connected features you request, including account connection, meeting creation, meeting updates, meeting cancellation, calendar invite coordination, support, abuse prevention, and security. Dainvo does not sell Zoom user data, use Zoom user data for advertising or retargeting, transfer Zoom user data to advertising platforms or data brokers, or use Zoom user data to train generalized AI models.

You can disconnect a Zoom account in Dainvo where controls are available. Disconnecting removes locally stored OAuth tokens and stops future Zoom API access from Dainvo for that account. You can also remove Dainvo from the Zoom App Marketplace by signing in to the Zoom App Marketplace, opening Manage, selecting Added Apps, finding Dainvo, and removing the app. Disconnecting or removing Zoom access may not automatically delete Zoom meetings already created in Zoom or local cached app data that remains on your device until you delete it, use available deletion controls, remove the connected account, or uninstall and delete Dainvo's local app data.

6.6 Task, Meeting, and Productivity Providers

If you connect task, meeting, or productivity integrations such as Todoist, TickTick, Zoom, or Webex, Dainvo may process account identifiers, OAuth tokens, tasks, task lists, projects, sections, labels, reminders, meeting information, meeting links, attendees, and sync metadata needed to provide the connected feature.

For some of these integrations, Dainvo servers briefly broker the OAuth token exchange so that confidential integration secrets stay off your device. The broker returns the resulting tokens to your device for secure local storage and does not retain provider tokens on Dainvo servers. Provider data calls then flow directly between your device and the provider.

6.7 OpenAI, Codex, and Claude MCP Connections

External AI connections are optional and disabled by default. If you enable OpenAI, Codex, or Claude under Dainvo AI settings, you select which Dainvo data categories that provider may access. Primary Dainvo calendar, task, bucket, rule, and settings data remains on the desktop; the connection does not upload or convert the desktop database into a cloud-hosted Dainvo database.

To route a user-requested MCP tool call to the active signed-in desktop, Dainvo stores request and result envelopes transiently in Supabase. Those envelopes are encrypted before storage. Cloudflare and Supabase process the requests, but Dainvo configures the gateway, relay, and content-free audit events not to log authorization headers, OAuth tokens, tool arguments, tool results, or error text.

The AI provider you select receives the tool inputs and results required to perform and answer your request. OpenAI or Anthropic processes that information under its own terms and privacy policy. Dainvo does not send selected desktop data to either provider while its connection is off, and disconnecting the provider disables the desktop route and revokes recognized Dainvo OAuth grants for that provider.

6.8 Weather Features (Open-Meteo)

Where weather features are available and you use them, Dainvo retrieves forecasts from Open-Meteo, a third-party weather data service. When you search for a weather location, the place-search text you type is sent to Open-Meteo's geocoding service, and the latitude, longitude, and timezone of the place you select are sent to Open-Meteo to retrieve forecast data.

Weather locations are chosen by you. Dainvo's mobile apps do not request device-location permissions, and weather features do not read your device's GPS position. Open-Meteo processes weather requests under its own terms and privacy policy.

7. OAuth Tokens, Credentials, and Local Security

On desktop, Dainvo is designed so that sensitive provider operations run in the Electron main process rather than in the renderer interface. Provider tokens, refresh tokens, CalDAV credentials, and similar credential payloads are intended to be stored through encrypted main-process credential storage where supported by the operating system.

On mobile, Dainvo stores session and provider tokens using platform secure storage backed by the iOS Keychain or Android Keystore, and Microsoft sign-in tokens are held in Microsoft's authentication library cache on the device, as described in the mobile section above.

The app interface should receive safe account summaries, connection status, and sanitized data needed for display. It should not receive raw provider tokens, refresh tokens, client secrets, authorization headers, database handles, or raw provider credential payloads.

Dainvo apps are designed to communicate with Dainvo servers and connected providers over encrypted connections, such as HTTPS/TLS.

No method of transmission or storage is completely secure. We use reasonable administrative, technical, and organizational measures designed to protect information, but we cannot guarantee absolute security.

8. When We Share Information

We may share information with the following categories of recipients:

  • Connected providers: when you authorize an integration and Dainvo needs to read, write, update, delete, or sync information with that provider.
  • Service providers: companies that help us operate hosting, website services, email, support, diagnostics, security, billing, authentication, analytics, update delivery, infrastructure, and business operations. For optional mobile notifications, this includes Google/Firebase for FCM and Apple for APNs delivery to Apple devices.
  • Payment processors and app stores: such as Stripe, Apple, Microsoft, or other storefronts, when needed for purchases, subscriptions, billing, refunds, tax, fraud prevention, receipt validation, or entitlement management.
  • Professional advisors: lawyers, accountants, auditors, insurers, and similar advisors where reasonably necessary.
  • Authorities or legal recipients: when we believe disclosure is required by law, legal process, security needs, user safety, fraud prevention, or protection of rights.
  • Business transaction recipients: if we are involved in a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, subject to appropriate protections.
  • With your direction or consent: when you ask us to share information or enable a feature that requires sharing.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not sell calendar, task, meeting, bucket, or connected-provider content.

9. App Stores, Direct Downloads, and Linux Builds

Dainvo may be distributed through direct downloads, the Apple App Store, Google Play, the Mac App Store, the Microsoft Store, and Linux package builds. The store or distribution channel you use may collect information such as account identifiers, purchase records, device information, crash reports, installation records, refund records, review information, and update information under that store's own privacy policy.

Direct-download versions may use update feeds or release-hosting services to check for new versions. Linux builds may be distributed as packages or artifacts and may rely on the distribution method selected by the user or administrator for installation and updates.

10. Cookies and Website Technologies

Our website uses cookies and similar browser technologies to operate the site, remember privacy choices, protect forms from spam, improve security, measure traffic, understand usage, and support optional support chat.

Strictly necessary storage is used to remember your cookie choice and keep the website working. Optional analytics and support chat technologies are off unless you consent through the cookie banner or Cookie settings.

If you consent to analytics, Dainvo may use Google Analytics to understand page views, referrals, device/browser information, and general website usage so we can improve the website.

If you consent to support chat, Dainvo may use Intercom Messenger. Intercom may use cookies and browser storage to identify the browser, maintain Messenger sessions, remember Messenger state, and prevent abuse.

Dainvo may use Cloudflare Turnstile when you submit website forms to help detect abuse and spam. Turnstile may process technical information such as IP address, browser data, device signals, and interaction signals under Cloudflare's Turnstile Privacy Policy.

You can manage website cookie choices through the Cookie Policy, the Cookie settings control in the website footer, or your browser settings. Blocking cookies may affect some website features.

11. Retention

We retain information for as long as reasonably necessary to provide Dainvo, maintain accounts, provide support, comply with legal obligations, resolve disputes, enforce agreements, prevent abuse, and maintain business records.

Local Dainvo app data generally remains on your device until you delete it, change app settings, disconnect an account where applicable, uninstall the app, delete the local application data folder or app storage, or use deletion controls that may be available in the app.

Dainvo-hosted sync data is retained while your Dainvo account is active. Some sync records are cleaned up automatically, such as expired completed-task history and relay records that are purged on a schedule. If you delete your Dainvo account, active Dainvo-hosted account records are deleted as described in the account deletion section below, and limited records, such as deletion-request logs and billing, tax, security, dispute, or other legally required business records, may be retained for as long as reasonably necessary for those purposes.

Notification registrations are deleted when you turn notifications off in Dainvo, sign out, withdraw operating-system notification permission and the app detects that change, revoke the associated Dainvo account device, delete your account, or when FCM reports that the specific registration token is no longer registered. Temporary notification delivery and event-deduplication records expire after 30 days. Aggregate announcement counts contain no user or device identifier and may be retained for product and operational reporting.

For a completed Outlook-captured task, Dainvo freezes the eligible active desktop and mobile device set and retains task and email-source content until every remaining target has committed and acknowledged that completed version. An offline device delays purge; explicitly revoking that device removes its requirement, and reopening the task before purge cancels deletion. After convergence, Dainvo writes a content-free task tombstone and deletes the active task and email-source content. The normal tombstone is retained for 365 days for cross-device convergence, and the content-free HMAC duplicate-prevention record is retained for 30 days after content purge.

Deleted active records may remain inaccessible in encrypted managed database backups or point-in-time recovery copies until the configured backup or recovery window expires. Those copies are restricted to disaster recovery and are not used to keep a deleted account active.

Connected providers may retain information under their own policies. App stores, payment processors, email providers, hosting providers, and other service providers may also retain records under their own legal and operational requirements.

12. Your Choices and Controls

Depending on your location, your app version, and the feature involved, you may have choices such as:

  • editing or deleting Dainvo Calendar entries, Dainvo Tasks, events, buckets, reminders, and settings in the app;
  • disconnecting connected provider accounts in Dainvo where supported;
  • revoking Dainvo access through the connected provider's security or account settings;
  • reviewing or revoking recognized Outlook add-in grants from the Dainvo Account Connections page;
  • deleting local app data from your device;
  • turning optional announcement notifications on or off in the mobile app under Settings > Notifications and managing notification permission in your operating-system settings;
  • uninstalling Dainvo;
  • deleting your Dainvo account, as described below;
  • opting out of non-essential marketing emails by using unsubscribe instructions or contacting us;
  • requesting access, correction, deletion, portability, restriction, or objection where applicable law provides those rights.

To make a privacy request, contact us at contact form. For support-related requests, contact support form. We may need to verify your identity before fulfilling certain requests.

12.1 Deleting Your Dainvo Account and Data

You can delete your Dainvo account and the Dainvo-hosted data associated with it:

  • In the apps: current Dainvo desktop and mobile app versions include an account deletion control in Settings under the Dainvo account section. The app asks you to confirm, then requests server-side deletion and signs the device out.
  • In the account portal: sign in at users.dainvo.com, open the Account page, and use the Danger Zone account deletion control. This works from any web browser, including on devices where Dainvo is not installed.
  • By request: you can request deletion at any time, including after uninstalling the app, through our account and data deletion page or the contact form. We may need to verify that you own the account.

When account deletion completes, Dainvo deletes the active Dainvo-hosted records associated with the account, including the Dainvo login and sessions, profile information, registered devices, license and access links, Dainvo-hosted tasks and related sync data, Outlook email-capture source rows, content-free capture fingerprints, completion-device targets, and recognized Dainvo Outlook OAuth grants.

Account deletion is permanent and cannot be undone. If you have an active subscription billed directly through Dainvo, you may need to cancel it before deletion can complete. Subscriptions or purchases managed by an app store must be cancelled or managed in that store; deleting your Dainvo account does not cancel a store-managed subscription.

Account deletion does not delete content held in your connected provider accounts, such as Google, Microsoft, Todoist, or TickTick, does not remotely erase local app data still stored on your devices, and does not remove records that app stores, payment processors, or providers keep under their own policies. Limited records, such as the deletion request itself and legally required billing or security records, may be retained as described in the Retention section. Details of what is deleted, what may remain, and how to remove remaining local data from each device are described on the account and data deletion page.

13. Privacy Rights by Region

13.1 United States State Privacy Rights

Depending on your state of residence, you may have rights to request access, correction, deletion, portability, or information about certain disclosures of personal information. You may also have the right to opt out of certain sales, sharing, targeted advertising, or profiling. Dainvo does not sell personal information and does not share personal information for cross-context behavioral advertising.

13.2 EEA, UK, and Similar Jurisdictions

If applicable privacy laws such as the GDPR or UK GDPR apply to your information, our legal bases may include:

  • contract: to provide Dainvo and features you request;
  • consent: when you authorize an integration, subscribe to communications, or provide optional information;
  • legitimate interests: to secure, maintain, improve, and troubleshoot Dainvo, communicate with users, and prevent abuse;
  • legal obligations: to comply with applicable law, tax, accounting, consumer protection, and legal process requirements.

You may have rights to access, correct, delete, restrict, object to processing, request portability, or withdraw consent. You may also have the right to lodge a complaint with your local data protection authority.

13.3 Canada and Other Regions

Depending on your location, you may have additional rights under applicable privacy laws. We will respond to privacy requests as required by applicable law.

14. Children's Privacy

Dainvo is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, please contact us at contact form so we can take appropriate action.

15. Sensitive Information

Dainvo is a calendar, task, and planning app. You may choose to enter information that could reveal sensitive details, such as health appointments, financial deadlines, legal matters, religious events, union activities, or personal relationships. We do not require you to enter sensitive information, and you should avoid entering sensitive information unless you are comfortable storing it in the app and, where applicable, syncing it with your chosen providers.

We do not use sensitive personal information to infer characteristics for advertising or to sell such information.

16. International Processing

Intagri Technologies LLC is located in the United States. If you use Dainvo from outside the United States, your information may be processed in the United States and in other countries where we, our service providers, app stores, payment processors, or connected providers operate. Those countries may have privacy laws different from the laws where you live.

17. Third-Party Links and Services

Dainvo may contain links to third-party websites, provider authorization pages, app stores, support tools, payment pages, documentation, or other services. We are not responsible for the privacy practices of third-party services. Review their privacy policies before providing information or connecting accounts.

18. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last updated" date above. If we make material changes, we may provide additional notice where required by law or where reasonably appropriate.

Your continued use of Dainvo after an updated Privacy Policy becomes effective means that you acknowledge the updated Policy, to the extent permitted by law.

19. Contact Us

If you have questions about this Privacy Policy or Dainvo's privacy practices, contact us:

Dainvo / Intagri Technologies LLC
131 Continental Dr Ste 305
Newark, DE 19713-4324
United States

Privacy: contact form
Support: support form