Privacy Policy

Last updated 3 August 2026. Applies to the Daily Brief app for Jira Cloud.

The short version. Daily Brief runs entirely inside Atlassian's own infrastructure. It declares no external permissions, so it cannot send your data anywhere outside Atlassian. We do not receive, see, sell, or store your Jira data on our own servers, because we do not operate any servers for this app.

Who is responsible

This app is provided by Abdullah Khalfi (Ranzo Apps), Freiburg im Breisgau, Germany. For any privacy question or request, write to support@clientportal-platform.com. For your Jira data, your organisation is the data controller and we act as a processor limited to what is described below.

Where the app runs

Daily Brief is an Atlassian Forge app. Its code executes on infrastructure operated by Atlassian, and its storage is Atlassian's app storage, inside your Atlassian site's own data residency arrangements. The app's manifest contains no external permissions block, which means the platform itself blocks it from making requests to any domain outside Atlassian.

What the app reads

The app requests the minimum Jira scopes it needs to produce a brief:

Scope	Why it is needed
`read:jira-work`	To find your open issues and their due dates, status, last update time, and issue links, so the brief can tell you what is overdue, going stale, or blocking a teammate.
`read:jira-user`	To show the display name of a teammate who is blocked by your work, and to read your profile timezone so the brief arrives in your morning, not someone else's.
`storage:app`	To save your own settings and reminders (see below).

The app never requests write access to your issues. It cannot edit, transition, comment on, or delete anything in Jira.

What the app stores

Your settings: delivery hour, chosen weekdays, pause switch, and your stale and due-soon thresholds.
Your reminders: the note you typed, the date you chose, an optional issue key, and who the reminder is for.
Your latest brief: the rendered text of your most recent brief, so the page can show it without recomputing.
An activation list: the Atlassian account IDs of people who have opened the app, so the scheduler knows whose brief to prepare.

Issue data is not copied into storage beyond the short summary lines that appear in your own rendered brief. Everything above is stored in Atlassian Forge storage, scoped to your installation.

What the app never does

No data is sent to us or to any third party. The app has no network egress.
No analytics, telemetry, advertising, profiling, or tracking of any kind.
No AI or machine-learning processing of your issues, and no training on your data.
No selling or sharing of personal data. We never receive it in the first place.
No email is sent by the app. Everything is delivered inside Jira.

Who can see what

Your personal brief is yours. The team view runs queries as the person viewing it, so Jira's own permission checks decide what appears; the app cannot reveal an issue a viewer could not already open in Jira. A reminder that one person sets for another is visible to that other person, which is the point of the feature.

Retention and deletion

Data is kept only while the app is installed. When an administrator uninstalls Daily Brief, Atlassian removes the app's storage for that installation, and all settings, reminders and stored briefs go with it. You can clear your own reminders at any time from the Reminders tab, and pause the brief entirely from Settings.

Your rights

Under the GDPR and similar laws you may request access to, correction of, or deletion of personal data, and may object to processing. Because all data lives inside your own Atlassian site, the fastest route is usually your Jira administrator. You can also write to support@clientportal-platform.com and we will respond within 30 days.

Sub-processors

Atlassian Pty Ltd, as the operator of the Forge platform and the storage the app uses. There are no others.

Security

The app holds no credentials of its own and stores nothing outside Atlassian, which removes most of the ways an app like this can leak data. Access to Jira is mediated by the Forge platform under the scopes listed above. If you believe you have found a security issue, please write to support@clientportal-platform.com and allow us a reasonable window to fix it before disclosing it publicly.

Changes

If this policy changes in a way that affects what the app reads or stores, the updated date above will change and the new version will be published here before the change takes effect.