Last updated: July 30, 2026
Granite has no accounts, analytics, telemetry, advertising, or user database. Wallet secrets stay on your device. Network providers still receive the minimum public and network data needed to serve requests.
Granite is Arweave wallet software. The hosted interface is watch-only; the desktop and iOS apps provide native self-custody. The source code is currently maintained privately during security validation and is intended to be published under the MIT License.
The Granite application does not operate a personal-data collection pipeline. Specifically:
Modern browsers can send Content Security Policy violation reports when a script is blocked by our policy. We accept these reports at /.well-known/csp-reports on the same origin you're already loading the app from - never a third-party endpoint. Our server returns HTTP 204 and does not persist the report body. The fact that a violation happened may appear in standard hosting access logs (URL + timestamp + IP); we use this only to detect attempted exploits, not to identify users. No tracking IDs, no cookies, no cross-request correlation.
Granite stores wallet data only on the device running the app:
Private keys are encrypted before storage. Granite has no server-side copy, recovery database, or reset capability.
Granite can create a link or QR code that copies a watch-only portfolio to another device. The payload contains public wallet addresses, display labels, and the selected wallet only. It never contains private keys, passwords, contacts, transaction notes, activity history, or signing authority.
The portfolio payload is placed in the URL fragment (the part after #), which browsers do not send to Granite's web server during a normal page request. However, anyone who receives the link or QR code can read the included public addresses and view their public on-chain balances and activity. Treat a portfolio link as public information and share it only with intended recipients.
Granite communicates with the following external services to function as a wallet. These are not ours - they are public Arweave infrastructure:
These services may see your IP address and, for blockchain queries, public wallet addresses or transaction data. Granite does not receive, store, or aggregate that information. These requests never contain your private keys, password, seed phrase, or recovery material.
As Granite is developed further with the Arweave community and ecosystem, we intend to move suitable query, coordination, and application-service workloads toward permaweb infrastructure using Arweave and AO Computer, including HyperBEAM where its security and privacy properties have been reviewed for the specific workload. Community-operated infrastructure may take a greater role over time. This is a roadmap direction, not the architecture currently deployed.
Arweave and AO data may be public and permanent. A future permaweb migration will not be used to publish private keys, passwords, recovery material, or plaintext private user data. We will update this policy before any migration materially changes what data leaves a device, where it is processed, or how long it is retained.
Granite cannot recover your wallet. Your keyfile is encrypted with a password only you know, on a device only you control. Without the password and a usable backup or recovery share set, access to the funds may be permanently lost.
Keep an exported encrypted keyfile or the recovery method you chose in a separate, secure location.
Granite does not knowingly collect data from anyone, including children under 13. Since we collect nothing from anyone, we are compliant with COPPA in the most literal way possible.
Granite's landing page and hosted watch-only wallet currently run on Railway. Railway and upstream network providers may process IP addresses, request paths, timestamps, and ordinary transport metadata to deliver and secure the service. Granite does not add tracking identifiers or operate an account, analytics, crash-telemetry, or user-profile database.
Our longer-term intention is to transition suitable parts of Granite toward a permaweb architecture running through Arweave and AO Computer, including HyperBEAM-backed services where appropriate, with the community and ecosystem taking an increasing role in operating and evolving that infrastructure. That transition has not yet occurred. Railway remains the current host until a reviewed migration is deployed and independently verifiable.
If we ever change this policy, we will update this page and the "Last updated" date above. Given that our policy is essentially "we collect nothing," changes would likely mean we started collecting something - and we'd be upfront about why.
Granite's source code is intended to be published under the MIT License after the current security-validation period. Until then, this policy describes the behavior of the hosted preview and will be updated if that behavior changes.
Questions, concerns, or compliments about this policy can be directed to our GitHub Issues. We read everything.