Last updated: 14 August 2026

This page describes the current technical data handling of Timed Highlight for Confluence.

Data handling

Timed Highlight currently:

  • requests no Atlassian OAuth or product scopes;
  • calls no Atlassian REST APIs;
  • uses no Forge Storage;
  • uses no external database;
  • has no remote backend;
  • performs no external network egress;
  • uses no analytics, advertising or user tracking; and
  • does not operate an external customer-data datastore.

The text and expiry date entered into Timed Highlight are stored as Confluence macro configuration within Atlassian’s platform. Caffeine and Cashflow does not receive that content through an external service.

Confluence permissions and page history can affect who can access current or earlier macro configuration. Users should not deliberately store passwords, tokens, private keys or other secrets or sensitive information in Timed Highlight configuration.

Contact

For privacy questions, email [email protected]. For product help, see Support.

This technical policy does not claim GDPR, ISO, SOC, HIPAA or PCI certification, and it is not a formal legal opinion.