Aries Labs LLC, a Wyoming limited liability company
Privacy
Last updated 20 November 2026
This document is published in English. The English version governs; any translation is provided for convenience only.
1. Who we are, and what this policy covers
This Privacy Policy explains what personal data Aries Labs LLC, a Wyoming limited liability company (“Aries Labs”, “we”, “us”) collects when you use alkanes.dev, the builder registry, the Alkanes Buildathon sign-up, the forum and our related services (the “Services”), why we collect it, what we do with it, and what rights you have. Aries Labs is the controller of that data.
Last updated 20 November 2026. This policy is published in English. The English version governs; any translation is provided for convenience only.
What this policy does not cover. It does not cover the practices of third parties whose services you reach through ours — including SUBFROST, Telegram, X, GitHub, wallet extensions, block explorers and RPC providers — each of which has its own policy. It also does not cover data recorded on a public blockchain, which nobody controls; see section 6. Nor does it cover AlkaFrost, the open-source MCP server we publish: you run it on your own machine, we do not operate it, and nothing it does is sent to this site.
2. What we collect, and why
We collect as little as the Services can work with. In detail:
a. X (Twitter) profile data, for builder registration. If you register as a builder, you sign in with X. Through that sign-in X tells us your X user ID and handle, and the address of your avatar where your settings on X make it available. We store your X user ID and handle, the avatar’s address and a copy of the avatar image, and the time we last saw them. We use them to create and display your builder record and to let you manage it. We do not receive your X password, your direct messages, or your follower graph, and we do not request them.
b. Bitcoin wallet addresses. If you bind a wallet to your builder record, we store the address, the signature that proves control of it and the exact message that was signed. We use them to verify that the person controlling the record controls the address, and to let you rotate it.
Wallet addresses are stored, and are never publicly displayed
We do not display wallet addresses on any public surface of the Services — not on a builder profile, not in the registry listing, not in the forum, and not in any API response available without authentication. They are held in our own database for verification and rotation only. We treat a wallet address as personal data where it can be linked to you, which — because we link addresses to X identities at registration — is the case here.
c. Your Alkanes Buildathon entry. If you enter the Buildathon, we store, under your X user ID: what you plan to build (up to 500 characters), your GitHub username, your Telegram handle if you give one (stored without the “@”), whether you chose to be listed on the public builders page, the version of the Terms of Service you accepted, and the times the entry was created and last changed. We use them to run the sign-up and so the event’s hosts know who is building what. What is public, and how to change or delete the entry, is in section 4.
d. Server logs. The web server in front of the Services writes an access-log line for each request: your IP address, the time, the method and path, the response status, the user agent, the referrer and the other request headers, with cookie and authorization headers redacted. The application writes its own operational log of errors and events. We use logs to operate and secure the Services, to diagnose faults, and to detect and prevent abuse.
e. Rate-limit counters. To stop abuse, the Services count requests to the routes that write: registering, checking and rotating a wallet, the Buildathon entry, and forum posts. Each counter is stored in our cache under your IP address, your X user ID or, for forum posts, your wallet address, and holds nothing but the count. It expires on its own after one hour or 24 hours, depending on the route.
f. Content you deliberately submit. Forum posts, builder-record fields, your Buildathon entry and anything else you choose to send us. Some of this is published by design — see section 4.
We do not knowingly collect special-category data, and you should not send it to us.
3. Purposes and legal bases
Where the EU or UK General Data Protection Regulation applies, our legal bases are:
- Performance of a contract (Art. 6(1)(b)) — operating your builder record and your Buildathon entry, and publishing what you post.
- Legitimate interests (Art. 6(1)(f)) — keeping the Services secure and available, preventing abuse and fraud, diagnosing faults, and understanding how the Services are used in aggregate. Where we rely on legitimate interests we have balanced them against your rights and interests, and you may object (see section 11).
- Consent (Art. 6(1)(a)) — listing your Buildathon entry on the public builders page, which you choose with its own checkbox. You may withdraw consent at any time by unticking it or deleting the entry, which stops future publication but does not undo publication already carried out.
- Legal obligation (Art. 6(1)(c)) — where we must retain or disclose data to comply with the law.
4. Your Buildathon entry — what is public, and how to change or delete it
What is public. The number of Buildathon entries is public. If, and only if, you tick “List me on the public builders page”, these fields of your entry are published on the Community page and through the site’s public entries endpoint: your X handle, what you plan to build, your GitHub username, and your Telegram handle if you gave one. Nothing else about an entry is published. An entry you did not choose to list is counted and is otherwise not shown to anyone. Your wallet address, your signature and your X user ID are never part of an entry and are never published. The builder directory continues to show the fields it already shows for every registered builder.
Who receives it. This site sends your entry to no one. Listed fields are public to everyone; the rest is held in our own database.
Changing or deleting it. You can change your entry, or delete it, at any time from the register page while signed in with X. Deleting removes the entry from our database; it is not merely hidden. To have your builder registry record itself removed, see section 11.
Do not put secrets or personal data in anything you submit
Never submit private keys, seed phrases, API keys, passwords, tokens, personal data beyond what a field asks for, hostnames, local file paths, or anything confidential — in a Buildathon entry, a forum post, or anything else you send us. If you believe you have submitted something you should not have, contact privacy@arieslabs.org and we will remove it as quickly as we can.
5. We do not sell your personal data, and we do not advertise
We do not sell your personal data, and we do not share it for cross-context behavioural advertising, as those terms are defined under applicable United States state privacy laws. We have not done so in the preceding twelve months. We run no advertising on the Services, and we do not use your data to profile you for advertising purposes anywhere.
We honour opt-out preference signals, including Global Privacy Control, where applicable law requires it.
6. On-chain data is public and permanent — and what that does not mean
Data recorded on the Bitcoin blockchain, including data written by the Alkanes Protocol, is public and permanent. Anyone can read it using a block explorer or a node. It cannot be altered or removed once confirmed. Aries Labs does not control that data and cannot delete or modify it — including at your request. Your right to erasure under applicable data protection law therefore cannot be fully enforced against data that is already on the blockchain, by us or by anyone else.
This limit applies only to the blockchain
It does not apply to the information we hold in our own systems. Your X profile data, your Buildathon entry (including any Telegram handle), the wallet addresses you register with us, your forum posts and your server-log entries are held off-chain, in our own database, and we can and will delete them on request, as described in section 11. The permanence of the blockchain is not a reason for us to refuse a deletion request about anything else, and we do not treat it as one.
By design, we do not publish personal data to any blockchain. Registration data stays in our own systems.
7. Who we share data with
We do not sell your data. We share it only in these cases:
- Service providers acting on our instructions — our hosting and infrastructure provider. They process data only to provide those services to us, under contract.
- Where you have asked us to — for example, X receives an authentication request because that is how you sign in.
- Publication you chose — forum posts, builder-record fields intended for display, and the Buildathon entry fields you chose to list.
- Legal and safety — where we are required by law, or where we believe in good faith that disclosure is necessary to investigate or prevent fraud, abuse or a security incident, or to protect the rights or safety of any person.
- Corporate transaction — in a merger, acquisition or sale of assets, subject to this policy continuing to apply.
8. Cookies
We set only cookies that are strictly necessary to operate the Services: a sign-in cookie that keeps you signed in with X and lasts 12 hours; three cookies used only while you sign in with X — a verifier, a state value that protects against cross-site request forgery, and the page to return you to — which last 10 minutes and are cleared when sign-in completes; and a language cookie that remembers the language you chose and expires when you close your browser. We set no advertising cookies, no cross-site tracking cookies, and no third-party analytics cookies.
9. How long we keep things
- Builder registry records — for as long as your record is active, and deleted when you ask us to delete it.
- Wallet addresses and rotation history — for as long as the associated builder record exists; rotation history is kept while the record is active so a change of address is auditable, and is deleted with the record.
- Buildathon entry — until you delete it from the register page, which removes it, or ask us to delete it.
- Web-server access logs — kept in the server’s system journal, which is limited by size, not by age: 500 MB for all of the server’s logs together, with the oldest entries deleted as new ones are written. How long a given line survives therefore depends on how busy the server is. We do not currently delete access logs on a fixed schedule.
- Application logs — at most three files of 10 MB each, with the oldest deleted as new ones are written.
- Rate-limit counters — one hour or 24 hours, depending on the route, after which they expire automatically.
- Forum posts — until you or we delete them.
- Blockchain data — permanently recorded on-chain, outside our control (see section 6).
10. Security
We take reasonable technical and organisational measures to protect personal data, including transport encryption, access controls, and credential handling that keeps secrets out of source control and logs. No method of transmission over the internet and no method of electronic storage is completely secure, and we cannot guarantee absolute security. We do not promise that the Services or our systems will never be compromised. If a breach affects your personal data and applicable law requires notification, we will notify you and the relevant supervisory authority within the time the law requires.
11. Your rights, and how to exercise them
Depending on where you live, you may have rights to access the personal data we hold about you, correct it, delete it, obtain a portable copy, object to or restrict certain processing, withdraw consent, and opt out of any sale or sharing (we do neither). You will not be discriminated against for exercising any of them.
To exercise a right, email privacy@arieslabs.org. Tell us what you are asking for and give us enough information to identify your records — the X handle or wallet address you use with the Services. We may ask you to verify control of the relevant identifier, because acting on an unverified deletion request would itself be a security failure. We respond within the period applicable law requires, and within 30 days where no other period applies.
Your Buildathon entry you can change or delete yourself, at any time, from the register page; you do not need to ask us. Your builder registry record is removed on request: email privacy@arieslabs.org from an address you can receive at, name your X handle, and we will ask you to prove control of the X account or the wallet before we remove it.
Appeals. If we decline your request, we will tell you why, and you may appeal by replying to our response. If you are in the EEA or the UK you may also complain to your local supervisory authority. If you are in a United States state with an applicable privacy law you may contact your state Attorney General.
The one limit we cannot work around is data already recorded on a public blockchain — see section 6, including what that limit does not cover.
12. Children
The Services are not directed to, and are not for use by, anyone under 18 years old. We do not knowingly collect personal data from anyone under 18. If you believe a person under 18 has given us personal data, contact privacy@arieslabs.org and we will delete it.
13. International transfers
We are established in the United States and our infrastructure is operated there and in Europe. If you are in the EEA or the UK, your personal data may be transferred to and processed in the United States, which has not received an adequacy decision applicable to us. Where we make such a transfer we rely on appropriate safeguards — the European Commission’s Standard Contractual Clauses, and the UK International Data Transfer Addendum where applicable — together with additional measures where they are needed. You may request a copy of the safeguards we rely on by emailing privacy@arieslabs.org.
14. Changes to this policy
We may update this policy. When we do, we will change the date at the top of this document, and for material changes we will give reasonable advance notice on the Services. Changes are prospective. Your continued use of the Services after a change takes effect is your acceptance of the updated policy.
15. Contact
Aries Labs LLC, a Wyoming limited liability company. Privacy questions and rights requests: privacy@arieslabs.org. Other legal questions: legal@arieslabs.org.
Contact details for questions about this document are in its final section. The route to this page is /privacy.