Production candidate · Coming soon · Purchases are not live

Responsible purchasing

Collecting should remain deliberate, informed, and controllable.

Blind-box purchasing can encourage repeat spending. ArcTrove is preparing controls that help customers set boundaries, pause activity, and understand costs before commerce is enabled.

Control principleA stop must stop.Purchasing stays blocked until an exclusion expires or is validly lifted.

Boundaries that live in the transaction path.

These controls are intended to be enforced by the backend, not left as interface suggestions that a purchase request can bypass.

01

Cooling-off periods

Temporarily suspend purchases for a defined period, with the block applied server-side.

02

Self-exclusion

Request a longer or permanent purchasing block with clear consequences and support handling.

03

Signed spending limits

Daily and monthly limits come from approved, versioned policy—not editable client values.

04

Velocity controls

Transaction frequency and behavior checks can stop activity before payment or selection.

05

Cost clarity

Price, balance type, ownership outcome, sell-back terms, and shipment options appear before purchase.

06

Support escalation

Account restrictions and spending concerns route to trained support workflows once support is operational.

Age and location rules cannot be guessed in code.

ArcTrove's intended compliance gate consumes a cryptographically signed, versioned profile approved by counsel. That profile defines allowed jurisdictions, minimum age, purchasing limits, and identity triggers for the applicable launch scope.

A missing, expired, or invalid signature must block the action. Until an approved profile is installed, purchases, sell-backs, shipments, and withdrawals remain disabled.

Questions worth asking every time.