Confidentiality and data handling

1. 1.1

   Name, email address and optional profile information.

2. 1.2

   Research briefs, submitted documents and support messages.

3. 1.3

   Order, payment status and security session records.

1. 2.1

   Staff permissions and customer ownership are checked by the API.

2. 2.2

   Passwords are hashed. Session revocation is stored durably.

3. 2.3

   Operators must configure HTTPS, private storage and tested backups before launch.

1. 3.1

   Submitted manuscripts are accessible to their owner and authorized staff.

2. 3.2

   Purchased files require an active paid entitlement.

3. 3.3

   Issued download links expire and stop working after a refund. Keep links private.

1. 4.1

   Update profile information and preferences from your account.

2. 4.2

   Request account deletion from settings. Purchase records remain pending retention review.

3. 4.3

   Contact support for a data access or correction request.

1. 5.1

   Payment and email providers must be selected and disclosed before live activation.

2. 5.2

   No payment provider is connected in the local test environment.

Send your request through the contact form and follow replies in Messages.