Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

fix(privacy): scroll the data table inside its own box so a phone stops scrolling the whole policy sideways

nirholas404653f6be01
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6f52e6d98..0001a94cf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -94,6 +94,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The paid Market Data API stops blaming buyers for a data provider's rate limit**: When an upstream data provider throttled us, the paid market endpoints (sectors, exchanges, derivatives, chains, DeFi, DEX volumes, fees) passed that straight back as a 429 rate-limit error, which read as if the caller had exceeded a limit on three.ws. These endpoints have no per-IP rate limit, so that was never true, and the error text also repeated the provider's name and our internal request path. A provider outage or throttle now comes back as the documented, retryable 503 data_unavailable and nothing else, so an agent's retry logic backs off for the right reason. Separately, market-fees used to quietly serve the fees table when asked for a mistyped type, charging for a dataset the caller did not ask for; an unrecognized type is now rejected before payment settles, so the call is free and the mistake is visible. (`/docs/market-data-api`) `[fix]`
- **The paid Market Heatmap stops going dark when its data provider throttles a busy minute**: The Market Heatmap endpoint asked CoinGecko for the board over the keyless public tier, ignoring the account key and the cached last-good copy every other market surface on the platform reads through. A throttled minute therefore dropped it straight onto its backup provider, whose free allowance is sixty requests an hour shared across the whole deployment, so a paid call could come back as a temporary outage while fresh data was already sitting in the platform's own cache. It now reads through that shared client: the key raises the ceiling, a rejected key is retried without it, and a throttle is answered with the last good board instead of a refusal. As before, a call that cannot be served is refused before payment settles, so a buyer is never charged for one. (`/docs/market-data-api`) `[fix, improvement]`
- **The payment-outcome board no longer reports itself healthy while it is blind**: One of the internal boards we watch payments with is built from three independent panels: payments arriving, settlements going out, and the fee wallet that pays for them. If a panel could not be read, the board swapped in an error for that panel but still answered with a plain success, so a read where all three had failed looked identical to a read where everything was fine. It now names every panel it could not see and answers with a partial-success status instead, which is what our alerting keys on. Separately, all three ops boards were spending the same strict per-address budget that guards sign-in attempts, so simply watching a dashboard could lock an operator out of logging in from that address. The boards now use the generous read budget the rest of the signed-in read surface uses. `[fix, infra]`
+- **The privacy policy's data table no longer pushes the page sideways on a phone**: The privacy policy lists what three.ws collects in a three-column table: the category, an example, and why we hold it. On a narrow phone screen that table was wider than the screen, and because it sat in the normal flow of the page it dragged the entire document sideways with it, so every paragraph and heading in the policy scrolled left and right too. The table now scrolls on its own inside a box the width of the screen, and the rest of the page stays put. The box is reachable with the keyboard and announced to screen readers, so the table can be read across without a mouse. Checked at phone, tablet, and desktop widths. (`/legal/privacy`) `[fix]`
- **The public custody page is switched off until its on-chain anchor works again**: The /integrity page invited anyone to verify our custodial wallets against a Merkle root anchored on Solana. The snapshot half of that has been running correctly all along: every six hours the platform reads each wallet's live mainnet balance, builds the tree, and records the root. The anchoring half has not. No epoch has been committed on-chain since the feature launched on 23 June, so the page was headlining custody you can verify above a history table where every row read anchor_failed, and telling readers the latest root would be anchored shortly when in fact nothing had been. A trust page that overstates what it can prove is worse than no trust page, so we have taken it down rather than leave it up making a promise the data does not support. Nothing else changes: snapshots keep running and keep accruing, the public API behind the page (/api/custody/integrity and /api/custody/anchor) is untouched and still reports every epoch along with an honest epochs_anchored count, and wallet owners can still recompute their own inclusion proof. The page comes back when anchoring is fixed, not before. (`/proof`) `[fix, security]`
- **The Reputation Staking Market is live: back an agent and earn from what it actually did**: Stake SOL behind an agent you believe in and earn a share of a daily reward pool, sized by that agent's signed on-chain record: accepted tasks, passed validations and real reviews pay, while failed validations, disputes and revocations cost double what work earns. The market page had shipped without the code that drives it, so it rendered empty no matter what was staked; it now loads live, ranks agents by the conviction escrowed behind them, shows any wallet's positions with earnings that update as they accrue, and settles a withdrawal back to the staker who signed the stake. Your principal is never slashed and can be withdrawn at any time: bad conviction earns nothing, it never costs you your stake. Every number is re-derivable from the chain, the exact formula runs identically in your browser and on our servers, and the whole cycle is provable on devnet with one command. Devnet is open to everyone; mainnet stays owner-gated. (`/reputation/market`) `[feature, fix]`
- **The security headers every three.ws page serves are now checked against the live site, not just the config**: Every page three.ws serves carries a set of browser security rules: which scripts are allowed to run, that the connection must stay encrypted, that browsers must not second-guess a file's type, how much of the current address is passed on when you follow a link, and who is allowed to put a three.ws page inside a frame. Those rules are written in one config file, but until now nothing checked that the site actually answered with them. The sweep that loads real pages in a real browser now also compares each response against that config, and it can be pointed at the live site to check the whole catalogue in about a minute. Running it against production found no gap: all 25 of the most script-heavy pages, and the rest of the catalogue with them, serve exactly the rules the config declares. Two fixes came out of building it. Files that are not web pages, like robots.txt and the machine-readable service descriptions, were being reported as wrong when they were correct. And a page whose file changed while the server was running could be sent with the script rules of the previous version, which would have blocked its own scripts and shown a blank page; the server now notices the change and recomputes them. `[security, infra]`
diff --git a/data/changelog.json b/data/changelog.json
index 1ae5f8d03..37f2407b8 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,15 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-14",
+ "title": "The privacy policy's data table no longer pushes the page sideways on a phone",
+ "summary": "The privacy policy lists what three.ws collects in a three-column table: the category, an example, and why we hold it. On a narrow phone screen that table was wider than the screen, and because it sat in the normal flow of the page it dragged the entire document sideways with it, so every paragraph and heading in the policy scrolled left and right too. The table now scrolls on its own inside a box the width of the screen, and the rest of the page stays put. The box is reachable with the keyboard and announced to screen readers, so the table can be read across without a mouse. Checked at phone, tablet, and desktop widths.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/legal/privacy"
+ },
{
"date": "2026-08-14",
"title": "Eleven links that led nowhere now land where they promise",
diff --git a/public/changelog.json b/public/changelog.json
index f45641a61..5e2e55f34 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-14T20:51:25.884Z",
+ "generated_at": "2026-08-14T21:10:59.178Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -958,6 +958,16 @@
"infra"
]
},
+ {
+ "date": "2026-08-14",
+ "type": "update",
+ "title": "The privacy policy's data table no longer pushes the page sideways on a phone",
+ "summary": "The privacy policy lists what three.ws collects in a three-column table: the category, an example, and why we hold it. On a narrow phone screen that table was wider than the screen, and because it sat in the normal flow of the page it dragged the entire document sideways with it, so every paragraph and heading in the policy scrolled left and right too. The table now scrolls on its own inside a box the width of the screen, and the rest of the page stays put. The box is reachable with the keyboard and announced to screen readers, so the table can be read across without a mouse. Checked at phone, tablet, and desktop widths.",
+ "link": "/legal/privacy",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-08-14",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index e5d903591..6f248b9d6 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -710,6 +710,14 @@
<category>fix</category>
<description>One of the internal boards we watch payments with is built from three independent panels: payments arriving, settlements going out, and the fee wallet that pays for them. If a panel could not be read, the board swapped in an error for that panel but still answered with a plain success, so a read where all three had failed looked identical to a read where everything was fine. It now names every panel it could not see and answers with a partial-success status instead, which is what our alerting keys on. Separately, all three ops boards were spending the same strict per-address budget that guards sign-in attempts, so simply watching a dashboard could lock an operator out of logging in from that address. The boards now use the generous read budget the rest of the signed-in read surface uses.</description>
</item>
+ <item>
+ <title>The privacy policy's data table no longer pushes the page sideways on a phone</title>
+ <link>https://three.ws/legal/privacy</link>
+ <guid isPermaLink="false">2026-08-14:The privacy policy's data table no longer pushes the page sideways on a phone</guid>
+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The privacy policy lists what three.ws collects in a three-column table: the category, an example, and why we hold it. On a narrow phone screen that table was wider than the screen, and because it sat in the normal flow of the page it dragged the entire document sideways with it, so every paragraph and heading in the policy scrolled left and right too. The table now scrolls on its own inside a box the width of the screen, and the rest of the page stays put. The box is reachable with the keyboard and announced to screen readers, so the table can be read across without a mouse. Checked at phone, tablet, and desktop widths.</description>
+ </item>
<item>
<title>The public custody page is switched off until its on-chain anchor works again</title>
<link>https://three.ws/proof</link>
diff --git a/public/features.json b/public/features.json
index 150fe0ac6..3b2c87b17 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-14T20:51:25.737Z",
+ "generated_at": "2026-08-14T21:10:58.792Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/public/legal/privacy.html b/public/legal/privacy.html
index dd5a1faaa..1a08615af 100644
--- a/public/legal/privacy.html
+++ b/public/legal/privacy.html
@@ -26,9 +26,14 @@
ul { padding-left: 20px; }
li { margin-bottom: 6px; }
a { color: var(--ink-bright); }
- table { width: 100%; border-collapse: collapse; margin: 16px 0; font-size: 14px; }
+ table { width: 100%; border-collapse: collapse; margin: 0; font-size: 14px; min-width: 420px; }
th { text-align: left; color: var(--ink-bright); padding: 8px 12px; border-bottom: 1px solid var(--stroke-strong); }
td { padding: 8px 12px; border-bottom: 1px solid var(--hairline); color: var(--ink); vertical-align: top; }
+ /* The data table's shortest readable width is wider than a 320px phone,
+ so it scrolls inside its own box rather than pushing the whole page
+ sideways. Focusable and labelled, so it is reachable by keyboard. */
+ .table-scroll { overflow-x: auto; margin: 16px 0; }
+ .table-scroll:focus-visible { outline: var(--focus-ring-width) solid var(--focus-ring-color); outline-offset: var(--focus-ring-offset); }
hr { border: none; border-top: 1px solid var(--stroke); margin: 48px 0; }
.foot { color: var(--ink-faint); font-size: 13px; }
</style>
@@ -64,6 +69,7 @@
<p data-i18n="legal_privacy.this_privacy_policy_explains_how_three_ws">This Privacy Policy explains how three.ws ("we", "us", "our") collects, uses, and shares information about you when you use three.ws (the "Service"). We take your privacy seriously and collect only what we need to operate.</p>
<h2 data-i18n="legal_privacy.1_information_we_collect">1. Information We Collect</h2>
+ <div class="table-scroll" role="region" tabindex="0" aria-label="Information we collect" data-i18n-attr="aria-label:legal_privacy.table_information_we_collect_label">
<table>
<tr><th data-i18n="legal_privacy.category">Category</th><th data-i18n="legal_privacy.examples">Examples</th><th data-i18n="legal_privacy.why">Why</th></tr>
<tr><td data-i18n="legal_privacy.account_identifiers">Account identifiers</td><td data-i18n="legal_privacy.wallet_address_email_optional_username_displ">Wallet address, email (optional), username, display name</td><td data-i18n="legal_privacy.authentication_account_management">Authentication &amp; account management</td></tr>
@@ -74,6 +80,7 @@
<tr><td data-i18n="legal_privacy.legal_acceptance_records">Legal acceptance records</td><td data-i18n="legal_privacy.terms_of_service_version_accepted_risk_discl">Terms of Service version accepted, Risk Disclosure version accepted, timestamp, IP address, user agent, which flow recorded it</td><td data-i18n="legal_privacy.proof_of_agreement_legal_compliance">Proof of agreement, legal compliance</td></tr>
<tr><td data-i18n="legal_privacy.email_if_provided">Email (if provided)</td><td data-i18n="legal_privacy.email_address_for_transactional_messages">Email address for transactional messages</td><td data-i18n="legal_privacy.account_notices_subscription_receipts">Account notices, subscription receipts</td></tr>
</table>
+ </div>
<p data-i18n-html="legal_privacy.we_do_not_collect_advertising_identifiers_us">We do <strong>not</strong> collect advertising identifiers, use third-party tracking pixels, or sell personal data to any third party.</p>
<h2 data-i18n="legal_privacy.2_how_we_use_your_information">2. How We Use Your Information</h2>
diff --git a/public/locales/en.json b/public/locales/en.json
index f5f3b2184..d44ea92c3 100644
--- a/public/locales/en.json
+++ b/public/locales/en.json
@@ -10556,7 +10556,8 @@
"what_we_return_a_public_url_to": "<strong>What we return:</strong> a public URL to the generated GLB model (hosted on our CDN) and a link to view it. The response contains no account identifiers or personal data. Generated model files are served from public URLs so you can download and share them; treat a model URL as public.",
"why": "Why",
"you_have_the_right_to_lodge_a": "You have the right to lodge a complaint with your local supervisory authority. You may also contact us first at <a href=\"mailto:[email protected]\">[email protected]</a>; we would welcome the chance to resolve your concern directly.",
- "you_have_the_rights_to_know_access": "You have the rights to know, access, correct, delete, and port your personal information, and to not be discriminated against for exercising them. Exercise them via <a href=\"mailto:[email protected]\">[email protected]</a> (Section 6). We verify requests using your signed-in session, your account email, or a message signed by your wallet. An authorized agent may act for you with written permission."
+ "you_have_the_rights_to_know_access": "You have the rights to know, access, correct, delete, and port your personal information, and to not be discriminated against for exercising them. Exercise them via <a href=\"mailto:[email protected]\">[email protected]</a> (Section 6). We verify requests using your signed-in session, your account email, or a message signed by your wallet. An authorized agent may act for you with written permission.",
+ "table_information_we_collect_label": "Information we collect"
},
"legal_risk": {
"10_contact": "10. Contact",