Refund and Cancellation Policy

Applies to service orders, package payments, cancellations, revisions, refunds, disputes, and operator/admin overrides.

Draft policy for cancellation windows, refund review, revision paths, payment mode limits, and non-guaranteed outcomes.

Cancellation eligibility may depend on whether work has started, whether deliverables have been generated, and whether the request remains within package scope.

Operators may review workspace events, intake details, payment events, generated files, and buyer messages before deciding an action.

Refund decisions should consider package scope, accepted milestones, revision opportunities, dispute notes, payment provider state, and any applicable law.

The current beta implementation uses mock/local payment mode unless explicitly configured otherwise, so beta refund records may be operational records rather than live money movement.

Mock/local payment mode records provider-style events without moving live funds.

Stripe/live payment behavior is not enabled unless configured and validated.

Do not claim escrow protection unless a compliant payment arrangement is legally and technically approved.

Live provider refund behavior requires provider configuration and counsel review.

Public refund windows and statutory cancellation rights need jurisdictional review.