Why the owner of the account becomes a signer in a package using API ?

Hi, We are noticing a surprising behavior when using the REST API to create a package, compared to a package created using the UI. When we use your quick start "Create and send a package" (https://developer.esignlive.com/guides/quick-start/creating-and-sending-a-package-java/), we should have only 2 signers. But we get a third signer which is owner of the account. The thing is we don't want the owner of the account to be part of the signing process. This behavior does not exist if we create a new package from the UI directly. Is this a bug?

DocumentPackage documentPackage = newPackageNamed("Test Package Java SDK")
			.withSigner(newSignerWithEmail( "[email protected]" )
				.withCustomId( "Signer" )
			    .withFirstName( "SignerFirstName" )
			    .withLastName( "SignerLastName" ) )
			.withSigner(newSignerWithEmail( "[email protected]" )
			    .withFirstName( "YourFirstName" )
			    .withLastName( "YourLastName" ))
			.withDocument( newDocumentWithName( "sampleAgreement" )
			    .fromFile( "C:\\Users\\dly7336\\Desktop\\esignlive_requetes.docx")
			    .withSignature( signatureFor("[email protected]")
			    	.onPage( 0 )
			     	.atPosition( 175, 165 ) )
			    .withSignature( signatureFor( "[email protected]")
			        .onPage( 0 )
			        .atPosition( 550, 165 )))
			.build();
		
		PackageId packageId = eslClient.createPackage(documentPackage);

Thanks