1. The short version
This is a static website. It has no accounts, no forms, no cookies, no analytics, and no third-party scripts. We do not build a profile of you and we have nothing to sell.
One thing is worth stating exactly. The web server that answers your request keeps no access log for this site, so an ordinary visit leaves no record of your IP address or of what you read. The one exception is a fault on our side, described in section 4. Claiming that nothing is ever recorded would be false.
2. Who we are
This site is operated by Aries Labs LLC, a Wyoming limited liability company ("Aries Labs", "we", "us", "our"). This policy covers this website only. It does not cover our products, which live on their own domains and carry their own terms and policies, and it does not cover any third-party property we link to.
3. What we do not collect
We do not:
- set cookies, or use local storage or session storage to identify you
- run analytics, tracking pixels, fingerprinting, or session recording
- load fonts, scripts, images, styles, embeds, or frames from any third-party network
- operate accounts, logins, newsletters, contact forms, or comment fields
- ask for your name, email address, postal address, telephone number, or payment details
- ask for, receive, or store any wallet address, key, seed phrase, or signature
- sell, rent, or share personal data with data brokers or advertisers
- serve advertising of any kind
- take part in cross-site or cross-device tracking
Every asset this site loads is served from this site. When you open a page here, your browser talks to our server and to nobody else.
4. Server logs
Neither our reverse proxy nor the server behind it keeps an access log for this site, so an ordinary request is not recorded. If a request fails because our own server is faulty or unreachable, the reverse proxy writes that failed request to its error log, which is kept in the server's system journal and copied to its system log; section 5 says how each is kept. Such an entry records the IP address the request came from, the requested path, the User-Agent string your browser sends and the response status code. The details an entry can include are:
- the IP address the request came from
- the date and time of the request
- the HTTP method and the requested path
- the response status code and response size
- the User-Agent string your browser sends
- the Referer header, where your browser sends one
- the protocol and TLS version used
We use these logs only to operate and secure the service: to see that the site is up, to diagnose faults, to detect and block abuse and automated attacks, and to satisfy legal obligations if they arise. We do not use them to profile visitors, and we do not combine them with data from any other source.
Where the law requires a stated basis for this processing, ours is our legitimate interest in running a secure, available website. Where consent would instead be required for a given practice, we do not carry out that practice.
5. How long logs are kept
Because no access log is written, there is nothing to keep for an ordinary visit. Error entries are kept in the server's system journal, which is capped by size, not by time: no retention period is configured for it. A copy is written to the server's system log, which is rotated weekly with four rotated files kept. Backups of system state may hold log fragments beyond that until they expire on their own schedule.
6. Who can see log data
Error log entries are readable by the small number of people who operate our infrastructure, and by the hosting provider that runs the underlying servers, in its capacity as our service provider.
We disclose log data outside that circle only where we are legally compelled to do so, or where it is necessary to investigate abuse of the service or to protect our rights, our users, or the public. We do not sell it, and we do not transfer it for anyone else's advertising.
7. How log data is protected
The site is served over encrypted transport. Access to the servers that hold logs is restricted to the people who operate them, over authenticated connections, and log data is not exported to any analytics, advertising or business-intelligence system, because none is in use.
We describe only controls that are configured. If a control is not in place, it is not claimed here.
8. If something goes wrong
If we become aware of a breach affecting personal data held from this site, we will notify the people affected and the relevant supervisory authorities where the law requires it, within the time the applicable law allows, and we will say what happened on this page rather than stay silent about it.
9. Where processing happens
The server answering this site is operated in a single jurisdiction, which may not be the one you are reading from. Using the site means your request reaches that server; it is recorded there only in the fault case described in section 4. If you are in a region with rules on international transfers, treat this as notice that such a transfer occurs.
10. Links to other sites
This site links out to properties we do not control, including source code hosts, social platforms, messaging services, and our own product domains.
We do not control what those sites collect. Following a link takes you under their privacy practices, not ours. Read them where it matters to you. This policy stops at the edge of this site.
11. Public blockchain data
Our work involves public blockchains. Data written to a public blockchain is visible to anyone, is permanent, and cannot be deleted, amended, or withdrawn by us, by you, or by anyone else. Addresses and transactions can often be linked together and, with outside information, to real identities.
This site does not write anything to any chain and does not read your wallet. But if you interact with our products elsewhere, understand that what a chain records, it records for good.
12. Children
This site is not directed to people under 18, and we do not knowingly collect personal data from them. If you believe a child's personal data has reached us, contact us through the channel in section 15 and we will delete what we hold.
13. Your rights
Depending on where you live, you may have rights to access, correct, delete, or restrict the processing of personal data about you, to object to processing, to receive a copy in a portable form, and to complain to a supervisory authority.
In practice we hold no personal data from an ordinary visit to this site. The only exception is an error log entry from a failed request, which we can search for a given IP address for as long as section 5 describes. We will not be able to identify you across time, and we may need enough detail to locate the relevant entries. We do not sell personal data and do not carry out automated decision-making or profiling.
Our public contact route is a source repository, so anything written in an issue there is public. Do not put personal data into a public issue. Ask there for a private channel instead, as section 15 describes; your request counts from the moment you ask, not from the moment you disclose anything.
14. Changes to this policy
We may revise this policy. The revised version takes effect when posted, and the version line at the top of this page changes with it. If a change is material, we will say so on this page rather than change it quietly.
15. Contact
Reach us through our public source repository organisation:
https://github.com/Aries-Labs-HQ
Open an issue or a discussion there for privacy questions and rights requests, asking only for a private channel if the matter needs one. We will supply a private route, and we do not publish a contact address on this site.
16. Language
This policy is published in English. The English version governs. Any translation is provided for convenience only, and in the event of a conflict the English text controls.