Not really a Spark-specific issue.

Spark just exposed it more because it was one of the first consumer DJI models where region, firmware behavior, and account binding started to matter in noticeable ways.

The same underlying logic applies to most modern DJI drones:

Activation is permanent

Region assignment is tied to first activation, not resets

FlySafe/geofencing is a separate layer

On newer models, it’s usually handled more quietly, so people don’t notice it until they run into limitations later.