Begin of the insertion### User Story

**As an** app userEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I want to** Begin of the insertionopt in or out of sharing crash reports (including a Firebase installation ID)End of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so Begin of the insertionthat I** can control what diagnostic data is collected about my app usage.End of the insertion Begin of the deletion that** \[enter desired result\]End of the deletion

Begin of the insertion### Acceptance CriteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionOn app launch after updating to a version that introduces or changes crash report collection, the app shows an opt-in modal titled **“Help us improve app stability”**.

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionThe modal body explains that crash reports are collected to fix bugsEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertionimprove performance.

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionThe modal explicitly states that the Firebase installation IDEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionused only to understand how many users are affected.End of the insertion Begin of the deletion this feature visible?_End of the deletion

* Begin of the insertionThe modal explicitly states that only an anonymous statisticEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertionused as the outcome of crash counting.

* The modal contains a single checkbox with the label **“I agree to share crash reports to help improve the app.”**

* The checkbox is **unchecked by default**.

* The modal contains a **Privacy Policy** link, styled as a link and tappable.

* Tapping the **Privacy Policy** link opens the privacy policy content in an in-app browser or system browser.

* The modal contains two actions:

* **Close** (secondary)

* **Done** (primary)

* Tapping **Close** dismisses the modal without changing the previously stored crash-report consent value.

* Tapping **Done** stores the crash-report consent value based on the checkbox state:

* Checked means consent is set to “opted in”.

* Unchecked means consent is set to “opted out”.

* After tapping **Done**, the modal dismisses.

* If the user closes the modal via the close icon (X), the behavior matches **Close** (no consent value change).

* The consent choice is persisted locally and restored on next app launch.

* The app applies the stored consent choice on startup before any crash reporting is initialized or enabled.

* Crash report collection is disabled when the stored consent is “opted out”.

* Crash report collection is enabled when the stored consent is “opted in”.

* The modal can be re-opened at any time from **Settings → Crash reports opt-in**.

* Re-opening the modal from Settings pre-fills the checkbox to reflect the currently stored consent value.

* If the user changes the checkbox and taps **Done** when opened from Settings, the new consent value is stored and takes effect immediately for subsequent crash events.

* If there is no stored consent value (first run after update), the Settings entry still opens the modal and shows the checkbox unchecked.

* The Settings screen includes a visible entry **“Crash reports opt-in”** (or equivalent) andEnd of the insertion it Begin of the insertionis accessible without requiring authentication beyond the app’s normal access.

* The modal layout supports small screens without clipping content, with scroll behavior if needed.

* <br>

* The app doesEnd of the insertion not Begin of the insertionprompt again automatically after the user has explicitly set a consent value, unless a future app version introduces a materially new purpose or data category requiring renewed consent.End of the insertion Begin of the deletion visible?_End of the deletion


Begin of the insertion### Technical NotesEnd of the insertion Begin of the deletion **Translation considerations**End of the deletion

* Begin of the insertionAssumptions:

* Crash reporting is implemented using Firebase Crashlytics (or equivalent Firebase crash reporting tooling).

* The referenced “Firebase installation ID” corresponds to the Firebase Installation ID (FID), not an advertising identifier.

* Data model implications:

* Persist a single boolean or enum value, e.g. `crashReportsConsent = opted_in | opted_out | unknown`.

* Persist a timestampEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertionapp version when consent was last set, e.g. `crashReportsConsentUpdatedAt`, `crashReportsConsentSetInVersion` (optional but recommended for audits and future re-consent logic).

* Backend vs frontend responsibilities:

* Mobile app is responsible for rendering the modal, storing consent, and enabling or disabling crash reporting SDK initialization/collection.

* No backend changes required unless the app also forwards crash logs to a proprietary backend.

* SDK behavior considerations:

* Ensure crash reporting is disabled by default until consent is explicitly optedEnd of the insertion Begin of the deletion phrasesEnd of the deletion in Begin of the insertion(when consent is `unknown` treat as `opted_out` for collection).

* Apply consent as early as possible at app startup, before crash SDK starts sending reports.

* IfEnd of the insertion the Begin of the insertionSDK supports runtime toggling, apply changes immediately on **Done** from Settings.

End of the insertion Begin of the deletion key languages_&nbsp;


**Out of scope**

End of the deletion * Begin of the insertionPrivacy policy link:

* Use a single immutable URL per environment: `https://www.openproject.org/legal/privacy/`

* Consider locale-aware URL routing if privacy policy is localized.

* Caching, state, and performance:

* Consent read shouldEnd of the insertion Begin of the deletion <br>


_Set the_ **ToEnd of the deletion be Begin of the insertionsynchronous or near-instant (local storage).

* Avoid any network callsEnd of the insertion Begin of the deletion informed/consulted teams** _fieldEnd of the deletion to Begin of the insertiondetermine whether to show the modal.

* Risks and constraints:

* Some crash SDKs may collect minimal device/app metadata even when disabled unless explicitly configured. Confirm the exact “disabled” behavior and ensure it meets legal requirements.

* If the app crashes before the user sets consent, crash reports must not be uploaded when consent is unknown.

* If the modal is shown as an overlay on Settings (as in the mockups), ensure it is accessible and does not trap navigation.


### Permissions and Visibility Considerations

* All users must see at least once the opt-in modal

* The Settings entry to re-open the modal is visible toEnd of the insertion Begin of the deletion includeEnd of the deletion all Begin of the insertionusers

* If the app supports multiple accounts on a single device:

* Crash report consent is an account-level consent

* The modal is always accessible through Settings, regardless of current consent states


### 5\. Translation Considerations

* Strings requiring localisation:

* “Help us improve app stability”

* Modal body text describing crash report collection, crash type/time, Firebase installation ID usage, and anonymous statistic statement

* “I agreeEnd of the insertion Begin of the deletion teams necessaryEnd of the deletion to Begin of the insertionshare crash reports to help improve the app.”

* “You can change this choice at any time in your account settings.”

* “Learn more in our Privacy Policy.”

* Settings labels: “Crash reports opt-in”

* Must NOTEnd of the insertion be Begin of the insertiontranslated:

* “Firebase”

* “Firebase installation ID”

* Any URLs (privacy policy URL)

* Any internal keys/identifiers used in code (e.g. `crashReportsConsent`)


### 6\. OutEnd of the insertion Begin of the deletion informedEnd of the deletion of Begin of the insertionScope

* ChangingEnd of the insertion the Begin of the insertioncontent of the privacy policy itself.

* Implementing a full consent management centre beyond the crash reports opt-in.

* Adding additional analytics or marketing tracking consent flows.End of the insertion Begin of the deletion changes._End of the deletion