This policy explains how AAVESwap handles information used to create, execute and support an exchange. It covers service records separately from public blockchain information that the service cannot rewrite.
An exchange requires information that identifies its payment and receiving instructions. Support and security functions can generate additional records when you use the website or contact us.
| Category | Examples |
|---|---|
| Order information | Assets, networks, amounts, quote conditions, status and relevant times |
| Blockchain identifiers | Deposit, receiving or refund addresses and transaction references |
| Support correspondence | Messages and evidence supplied for a request |
| Technical records | Limited IP, device, request and error information for security and diagnosis |
| Review evidence | Information relevant to a transaction review, where requested |
Do not provide a recovery phrase or private spend key. Those secrets are not required to create an exchange or identify a public transaction.
We use the relevant information to calculate and execute an order, identify payments, arrange payouts, investigate errors, respond to support and address transaction risks. We minimise information collected for a request and restrict access according to the task.
Service providers may support hosting, security, quotes or liquidity, payouts, screening and support communications. They receive information needed for those functions under the arrangements applicable to the service; we do not publish private order records as a public trading profile.
The website's operating model uses essential session and security storage. Advertising tracking cookies are not part of that model, and introducing a different tracking purpose requires an appropriate change to the site's disclosures and controls.
Records are kept for the periods assigned to their purpose and then deleted or minimised when no further justified retention applies. A documented dispute, security incident or applicable obligation can require a relevant subset to be retained longer.
| Record | Ordinary retention |
|---|---|
| Closed exchange records | 150 days after order closure |
| Technical security and diagnostic logs | 21 days |
| Support correspondence | 180 days after the request closes |
| Verification attachments | 30 days after the review closes, unless a specific retention reason applies |
Deleting a support message does not necessarily remove the order record needed for its separate purpose. We assess a request against the relevant categories rather than treating all information as one undifferentiated record.
We use HTTPS, restricted access and private order links as part of handling service information. Keep your order link confidential because someone with it may be able to see details relevant to that exchange.
Blockchain addresses and transaction records can remain visible according to the network's design even after our own records are removed. A private website status link does not make a public-chain transfer invisible, and network participants or receiving platforms can maintain their own records.
Send a request to [email protected] and identify the order or correspondence concerned. Our response target is 21 days; we may need limited information to verify that you are entitled to the requested access or action.
You can ask about access, correction, deletion or handling of your information. The available response depends on the relevant record, retention purpose and applicable requirements, and does not include editing another party's blockchain records.
Use the privacy contact instructions to send a focused request. For information collected during a transaction investigation, the transaction review policy explains that separate process.
Identify the record and action concerned when asking about data. Website records and information maintained by blockchain participants are handled separately.
No. Public blockchain information is held by the network and other participants, not only by this website. We can assess our own records, but cannot erase a confirmed transaction from the chain.
Yes. Identify the conversation and the action you want, so we can assess it against its purpose and retention rules. A related order or documented dispute may require a separate record to be kept even when some correspondence can be removed.
No. We verify a privacy request without asking for unrestricted wallet access. Do not send a recovery phrase or private spend key in correspondence or an attachment.