Disclaimers

DiveSuite displays mandatory disclaimers throughout the application. The disclaimer is never removed from planning screens. It may use progressive disclosure (a compact inline hint with expandable detail, or a one-time acknowledgment stored in settings), but it always stays accessible.

Mandatory Disclaimer

The following disclaimer must be displayed prominently whenever a dive plan is generated:

Disclaimer Implementation

Technical Requirements

The disclaimer is shown with every plan output and is never removed from planning screens
It may use progressive disclosure, but must remain accessible
It is a separate component (SafetyDisclaimer) so that no screen builds its own copy
Contextual safety warnings (NDL, ppO2, ICD, gas reserves) are separate from the disclaimer. They are always prominently visible and never dismissible

Display Rules

Context	Disclaimer Required	Position
Plan calculation result	Yes	Above the plan
Saved plan view	Yes	Top of screen
Plan export (PDF/share)	Yes	First page/section
Plan comparison	Yes	Once per screen
AI suggestions	Yes	With every suggestion
Engine unavailable (planned, D27)	No plan, so the “engine unavailable” card only	In place of results

Known bug: plan export

The current plan export (PlanExportSheet and the slate templates) does not include the disclaimer yet. The requirement above stands. This is a known bug and it is being fixed.

First Launch Acceptance

Users must accept the disclaimer on first launch:

Today only the acceptance time is stored. The user confirms that they are a certified diver, understand the limits of a planning tool and accept responsibility.

Storage:

Acceptance time is stored in the app settings
It stays accessible afterwards

Industry Practice

Established dive planning software shares the same elements, and DiveSuite’s disclaimer follows them:

A “not a dive computer” statement
“For planning/informational purposes only”
A recommendation to use an actual dive computer
A limitation of liability
An acknowledgment of inherent diving risks

Version Control

Planned (onboarding specification), when the disclaimer text is updated:

Bump the disclaimer version
Users must re-accept on next launch
Change documented in release notes

The text lives in the app’s translation files in English and German. Versioning with re-acceptance is planned, not built.

Legal Requirements by Region

European Union (GDPR/Consumer Protection)

Clear, unambiguous language
No buried clauses
Available in user’s language (when translations complete)
Cannot be pre-accepted (must be active action)

United States

Limitation of liability clause
Assumption of risk statement
Reference to Terms of Service

Germany (Specific)

AGB (Allgemeine Geschaftsbedingungen) compliance
No surprising clauses (“uberraschende Klauseln”)
Clear separation from marketing text

AI-Specific Disclaimers

When AI features are used, additional disclaimers apply:

+---------------------------------------------+
|  AI Suggestion                              |
|                                             |
|  Based on your description:                 |
|  - Depth: 25m                               |
|  - Bottom time: 40 minutes                  |
|                                             |
|  Warning: AI suggestions are not verified.  |
|  Please review all parameters before        |
|  proceeding with your dive plan.            |
|                                             |
|  AI cannot guarantee safety or              |
|  accuracy of suggestions.                   |
|                                             |
|  [Use Suggestion] [Enter Manually]          |
+---------------------------------------------+

AI Disclaimer Requirements

AI Feature	Additional Disclaimer
Natural language planning	“AI extracted these values - verify accuracy”
Voice-to-log	“Transcription may contain errors - review before saving”
Photo data extraction	“Extracted data may be inaccurate - verify readings”
Pattern analysis	“AI analysis is not medical advice”

Engine Unavailable (planned, D27)

The “engine unavailable” card does not exist yet (DIV-115). Today the TypeScript fallback still computes plans, within its refusal scope, and plan outputs carry the disclaimer. Once the card exists, no Rust engine means no plan, so no plan disclaimer to attach: the planner will show only the persistent card. It will say that nothing was checked and that no plan, limit or gas check was performed, and it will never be dismissible.

Planned

These items are not implemented yet and are tracked in Linear (team DIV). Do not rely on them:

Disclaimer versioning with re-acceptance on a text change (onboarding specification). Today only the acceptance time is stored
An audit log of disclaimer interactions and its retention rules
Legal review of the disclaimer text and of the regional requirements above