AI disclosure for DueKit

If AI assist opens later, it should remain optional, explicitly triggered, reviewable, and easy to reverse before any client-facing content is treated as final.

• No AI assist surface is live on the current public routes.
• If an AI action opens later, sender-provided inputs should only be processed after the user explicitly triggers the approved AI action on that specific surface.
• Any AI output should appear as assistive draft material rather than hidden automation that silently changes client-facing content.

• AI-assisted draft and review output should always be reviewed before use, export, share, or send.
• The sender remains responsible for final wording, scope, dates, pricing, payment terms, and any other client-facing business content.
• If the AI assist fails, the manual workflow should still remain usable so AI never becomes a hard blocker for completion.

• Any pricing, checkout, upgrade, or AI credit surface should keep this disclosure directly reachable before a charge or credit consume occurs.
• Critical notice copy should not be weakened or hidden behind locale, theme, or lower-visibility UI treatment on AI-related surfaces.
• If the AI provider, data flow, or paid posture changes materially, this page should update before the new behavior goes live.

• This page does not promise autonomous completion, legal review, accounting advice, or guaranteed correctness from AI-assisted output.
• It describes only the current live posture and any future AI touchpoints that are explicitly opened and disclosed at that time.
• Future AI expansion should preserve explicit triggering, editable output, and direct disclosure reachability.