Email is identity - we've used enterprise approaches from day one to protect yours.
Tack is designed so that:
[PLACEHOLDER: Data flow diagram]
A simple diagram with three boxes: Connected services → Tack processing (short-lived) → what's stored. Label: "Encrypted content", "Minimal metadata", "Deleted after handled". Keep it non-technical and readable.
Text you type is stored as a task (because you asked us to).
A rolling 30-second buffer runs locally. Nothing is saved until you press the button. Once we've processed the audio to extract tasks, the audio itself is deleted.
[PLACEHOLDER: Multipurpose "shredder" GIF]
A calm animation showing the rolling buffer process: rolling audio spool (last 30 seconds) → user presses Tack That → clip is "saved" → tasks extracted from audio, email, Teams messages, and Quick Tack notes → items appear on the tack board → shredder animation indicates the rolling buffer continues and old audio/data is overwritten / not retained unless explicitly saved. This same animation demonstrates audio task capture, quick tack, email, and teams message processing. Keep it calm, not gimmicky.
Our security whitepaper provides comprehensive technical details about encryption, key management, and data handling practices.