# Signing
Just like the key generation procedure, logged-in users receive a token that grants access to the storage where the encrypted key is stored, and they request the Wepin server along with the transaction that requires signing. The server uses the user's token to retrieve the encrypted private key and then decrypts it using the PIN number submitted by the user. After signing the transaction with the decrypted key, the private key is securely encrypted again and stored in the cloud.
The operations for signing are also executed exclusively within a Trusted Execution Environment (TEE). Therefore, the private key loaded into memory during the creation of the signature is inaccessible to the Wepin server, meaning the server cannot know the private key information. The server merely performs the role of executing operations; the private key information remains undisclosed, and interactions throughout the entire protocol of signing a transaction occur in an encrypted form.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.wepin.io/en/wepin/architecture/sign.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
