Skip to content

Privacy and security

Updated View as Markdown

Planner separates renderer-visible content from secure credential storage. Refresh credentials and provider secrets belong in native or hosted secure boundaries, not notes, logs, or browser storage.

Do this

  1. Protect the operating-system account with a strong password and device lock.
  2. Use supported sign-in and provider authorization flows.
  3. Review connected services and remove unused access.
  4. Store exports in encrypted, access-controlled locations.
  5. Send security issues to the dedicated security address.

Never store

  • OAuth tokens or refresh credentials
  • App passwords or API keys
  • Private signing keys or recovery codes
  • Raw webhook payloads containing personal data
  • Unredacted diagnostic bundles in ordinary notes

AI and privacy

Provide agents only the context needed for the objective. Review provider and model disclosures in the relevant product settings before sending sensitive content.

Logs

Diagnostics should avoid customer data, private message bodies, financial credentials, and full contact databases. Review a bundle before sharing it.

Good to know

  • Product support for Planner uses the secure contact form; security incidents use the secure contact form.
  • Legal and privacy-rights requests use the secure contact form.
Planner.li
Help and documentation for Planner.li.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close