# Privacy Policy
SurfLayer (“we,” “our,” or “us”) respects your privacy and is committed to protecting user information.\
This Privacy Policy explains how we handle, use, and protect the limited data collected through your interaction with our website, application, and cross-chain protocol (collectively, the “Services”).
By using SurfLayer, you agree to this Privacy Policy and our[ Terms of Service](https://docs.surflayer.xyz/policy/term-of-service?utm_source=chatgpt.com).
### 1. Overview
SurfLayer is a non-custodial and contract-free cross-chain protocol.\
We do not request, collect, or store personally identifiable information (PII) such as names, emails, or identification documents.\
All data we handle is technical, anonymized, or publicly available on-chain data required for operating and securing the network.
### 2. Information We Collect
We collect only the minimum information necessary to operate SurfLayer safely and efficiently.\
This may include:
* Blockchain Information: Public wallet addresses, transaction hashes, source and destination networks, token details, and timestamps.
* Technical Metadata: Browser type, device type, approximate region (based on anonymized IP), session logs, and system performance data.
* Analytics Information: Aggregated, non-identifiable usage statistics collected through tools such as Google Analytics.
* Community Interaction Data: If you join our community via Discord, we may see your username or handle as provided through the Discord API.
No private keys, seed phrases, or personal wallet credentials are ever collected or stored by SurfLayer.
### 3. How We Use Information
The limited data we collect is used only for the following purposes:
* Operating and maintaining Surflayer’s cross-chain protocol.
* Monitoring system health, uptime, and performance.
* Preventing fraudulent or malicious behavior.
* Conducting aggregated analytics to improve user experience.
* Providing community support and communication through Discord.
We do not sell, rent, trade, or share data for advertising or marketing purposes.
### 4. Third-Party Services
SurfLayer relies on trusted infrastructure providers to ensure performance and reliability.\
These services process data on our behalf but do not have access to private user information.
Currently, we use:
* Cloudflare — for content delivery, DDoS protection, and load balancing.
* Google Analytics — for aggregated, anonymized usage analytics.
* Discord — for community communication and support.
* Twitter (X) — for social interaction, campaign tracking, and account verification related to SurfLayer activities.
Each provider operates under its own privacy policy:
* [Cloudflare Privacy Policy](https://www.cloudflare.com/privacypolicy/?utm_source=chatgpt.com)
* [Google Privacy Policy](https://policies.google.com/privacy)
* [Discord Privacy Policy](https://discord.com/privacy)
* [Twitter (X) Privacy Policy](https://twitter.com/en/privacy)
### 5. Data Security
We apply technical and organizational measures to safeguard information, including:
* Encryption in transit (HTTPS/TLS 1.2+).
* Log anonymization and minimal retention.
* Strict access control and internal monitoring.
Because SurfLayer never handles user custody or private keys, risks related to wallet security are fully under the user’s control.\
If a data incident occurs, we will take reasonable steps to mitigate impact and inform affected users through our public channels.
### 6. Data Retention
SurfLayer retains data only for as long as it is required to fulfill operational, security, or legal obligations:
* Technical logs are automatically rotated every 30 days.
* Aggregated analytics data is retained for up to 90 days.
* On-chain transaction data is public and permanently stored on the blockchain.
* Discord interaction data is subject to Discord’s own retention policy.
When data is no longer required, it is securely deleted or anonymized.
### 7. User Rights
Depending on your jurisdiction, you may have the right to:
* Request information about what data we hold (if any).
* Request deletion of any non-essential, off-chain data.
* Opt out of analytics or tracking through browser settings.
Since SurfLayer does not collect personal data, most data-subject rights (such as rectification or portability) are inherently satisfied by design.
To make a privacy-related request, please reach out through our official Discord support channel.
### 8. Cookies and Tracking
SurfLayer uses only essential and performance-related cookies.\
We do not use advertising, behavioral, or cross-site tracking cookies.\
You can disable cookies in your browser, though certain features may perform less efficiently.
### 9. International Data Transfers
Our infrastructure is globally distributed.\
Technical data may be processed or stored on servers located in multiple jurisdictions, including through Cloudflare and Google Analytics.\
Only non-identifiable information is transferred, and we apply reasonable security standards consistent with global data protection principles.
### 10. Changes to This Policy
We may update this Privacy Policy from time to time to reflect improvements in our services or changes in regulatory requirements.\
When updates occur, the “Last Updated” date above will change.\
Continued use of SurfLayer after the update constitutes acceptance of the revised policy.
### 11. Contact Us
If you have questions, feedback, or concerns about this Privacy Policy, please contact us via our official community channel:\
👉[ SurfLayer Discord Support](https://discord.gg/CpDAkjGSZF)
---
# 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.surflayer.xyz/policy/privacy-policy.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.