---
title: "Privacy and security"
description: "<p>Planner separates renderer-visible content from secure credential storage."
---

> Documentation Index
> Fetch the complete documentation index at: https://planner.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy and security

<p>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.</p>
<h2>Do this</h2>
<ol>
<li>Protect the operating-system account with a strong password and device lock.</li>
<li>Use supported sign-in and provider authorization flows.</li>
<li>Review connected services and remove unused access.</li>
<li>Store exports in encrypted, access-controlled locations.</li>
<li>Send security issues to the dedicated security address.</li>
</ol>
<h2>Never store</h2>
<ul>
<li>OAuth tokens or refresh credentials</li>
<li>App passwords or API keys</li>
<li>Private signing keys or recovery codes</li>
<li>Raw webhook payloads containing personal data</li>
<li>Unredacted diagnostic bundles in ordinary notes</li>
</ul>
<h2>AI and privacy</h2>
<p>Provide agents only the context needed for the objective. Review provider and model disclosures in the relevant product settings before sending sensitive content.</p>
<h2>Logs</h2>
<p>Diagnostics should avoid customer data, private message bodies, financial credentials, and full contact databases. Review a bundle before sharing it.</p>
<h2>Good to know</h2>
<ul>
<li>Product support for Planner uses the secure contact form; security incidents use the secure contact form.</li>
<li>Legal and privacy-rights requests use the secure contact form.</li>
</ul>

Source: https://planner.helpcent.re/sync-data/privacy-and-security/index.mdx
