Legal

This page covers the terms of using Retired Today, what data the platform collects, and how those rules stay current as the platform changes. It's deliberately short. If a section becomes more complicated than necessary, we've gotten something wrong.

Terms of use

Who runs this. Retired Today is operated by an individual sole-proprietor based in Bali, Indonesia. There is no company entity, no investors, no third-party operations team. Every line of code on this platform is written or directly reviewed by the operator.

What you get. Free accounts have access to the public surfaces — blog posts, tools, the changelog, the docs, the trade log, the portfolio tracker (Holdr), and the dashboard's read-only views. The trading-signal feed and swap alerts are paid features. Paid access is bought outright in 6-month or 12-month windows. There is no recurring billing, no card on file, and no auto-renewal. When your access window ends, it stops; renewing is a fresh purchase.

What you should know about the trading content. The site shows historical results from a backtested strategy and live results from the operator's own automated bot account. Past results, simulated or live, do not predict future results. Crypto futures are high-risk products that can lose more than the amount risked per trade if exchanges fail to execute stop-losses. Nothing on this site is financial advice. Trading signals are setups for you to consider; you decide whether and how to act on them; the platform does not place trades on your behalf, and your account on whatever exchange you use is yours alone.

What you can do. Sign up, browse, use the tools, read the blog, log your trades, track your portfolio. Comment, share, link to anything you find here. Standard expectations apply: don't try to break the platform, don't scrape it at industrial volumes, don't try to recreate the trading-signal logic from public surfaces (it's protected; the homepage's "Recent signals" list strips the reasoning server-side specifically so the rules can't be reconstructed from a curl).

What we can do. Add features, change features, remove features. The changelog at /changelog is the canonical record. Suspend or remove an account that's abusing the platform. Decline a signup that looks fake. Update these terms — when we do, the version number on this page changes and signed-in users see a single-line notice in the app the next time they open it.

Liability. As a small product run by one person, the platform is provided "as is" with no warranty. The operator's maximum liability for any claim related to use of this site is capped at the amount you've paid for the service in the last twelve months. If you've paid for an access window, that cap is the actual amount you paid. If you haven't paid anything, the cap is zero.

Refunds. Crypto payments are final. There is no refund mechanism — we don't accept the chargeback risk a refund flow would introduce. If the platform stops delivering signals for any reason during your access window (exchange outage, planned downtime, strategy review), the unused portion of your access is paused on the calendar and resumes when service resumes; you always receive the full delivery period you paid for.

Jurisdiction. Disputes are governed by the laws of Indonesia, where the operator resides. If a dispute can't be resolved directly, it goes to the courts of jurisdiction at the operator's residence. Practically: send a polite email first; almost everything resolves there.

How to reach us. The contact email is on the homepage and in the menu. The operator reads every email. There is no support ticketing system; small platform.

Privacy

Short version. The platform does not run third-party tracking, advertising, or behavioral analytics. The only personal data we hold is your email address (if you've signed up) and a handful of opaque session IDs stored in your browser. The only cookie we set is the one that keeps you signed in.

What gets collected.

• Account email + password. Used to log you in and to push platform notifications. Passwords are stored as scrypt hashes — the actual password isn't recoverable even by us. Emails are kept until you ask us to delete the account.
• Anonymous page views. When you visit a page, the server records the path, a 30-day-rolling session ID, a per-tab session ID, your country (resolved from your IP via an offline geoip database — the IP itself is never stored), and a coarse device class (mobile / tablet / desktop) and browser family (Chrome / Safari / Firefox / etc) extracted from your User-Agent header. The raw IP and the raw User-Agent are discarded the moment the lookup finishes. No fingerprinting.
• First-touch attribution. On the first page-view of a session we also note utm_source / utm_medium / utm_campaign from the URL if present, your browser's navigator.language, and your viewport size. Used for understanding where visitors come from in aggregate; never linked to you personally.
• In-app data. If you use the Trade Log, your logged trades + cycles are stored on our server keyed to your account. Same for the Portfolio Tracker (Holdr), the Tasks app, the Gym app, and your blog read-progress. None of this is shared, sold, or used for advertising.
• Conversion events. When you sign up, complete the waitlist form, click the Phemex referral link, reach the checkout page, or complete a payment, the platform records a small event tied to your session's view history. This lets the operator see which page someone was on when they took the action — useful for understanding what content actually helps. Email is included only on the signup event itself (because that is the action); other events are session-id-only.
• Tool interactions. The /tools section records aggregate counts per tool: views, interactions, shares. These are tool-level totals, not per-person traces.
• Payments. When you buy access, the platform creates an invoice tied to your account email, a unique-per-invoice USDT amount, and a single shared Tron deposit address. When the on-chain transfer matches, the platform records the matched transaction hash, the amount received, and the time. We do not collect your wallet address; that information arrives implicitly with the transfer and is stored only as it appears on the blockchain (which is already public).

What does NOT get collected.

• No third-party advertising or analytics SDKs. No Google Analytics, no Meta pixel, no Mixpanel, no Segment, no Hotjar, no Sentry, no Datadog, none of it. The only analytics is the in-house anonymous event log described above.
• No tracking pixels in emails. We don't send marketing emails; the only emails sent at all are direct admin pushes when something on your account changes.
• No browser fingerprinting, no canvas hashing, no WebRTC IP leak collection, no font enumeration.
• No selling or sharing of your data to anyone for any purpose. There is nobody to sell it to — there is no commercial data partnership of any kind.

Cookies. The platform sets exactly one cookie: a session cookie named rt_session, used to keep you signed in. It is HttpOnly, Secure, SameSite=Lax. It is a "strictly necessary" cookie under GDPR — without it the login flow can't function — so no consent banner is required and we don't show one. The cookie expires when you sign out or after 30 days of inactivity. There are no tracking cookies, no advertising cookies, no analytics cookies.

localStorage. A handful of small entries are kept in your browser's localStorage to remember things across visits without round-tripping the server: a 30-day-rolling session ID for traffic counting, a per-tab session ID, blog reading-progress per post (also synced to the server when you're signed in), a one-time welcome flag for new signups, and a marker for the version of this legal page you've already seen. None of these contain your email or any personal information. Clearing your browser data removes them.

Third-party services we depend on.

Server-side (your data is not sent to these unless explicitly noted):

• Railway hosts the platform's servers and persistent data volume. The application currently runs in Railway's europe-west4 region (Amsterdam, Netherlands). Railway sees the same anonymous request metadata any host would see (IP, request paths). They don't see our application's stored data unless we share it.
• Fastly is the CDN edge in front of Railway. Fastly sees request IPs and paths in transit; the specific edge node serving you depends on where you are on the planet. They don't store request bodies.
• TronGrid (api.trongrid.io) is the public Tron blockchain API the payment watcher polls every 30 seconds to spot incoming USDT transfers to our deposit address. We send TronGrid only our own wallet address; no buyer information leaves the platform.
• Phemex is the exchange where the operator's own trading bot account runs and where price data for the strategy is sourced. It's not connected to your data; you don't have a Phemex account through us.
• Anthropic's Claude API is used by the operator to draft blog posts, tools, and this legal page. Your data is not sent to Claude. Claude only sees prompts the operator types in.
• Pushover delivers push notifications to the operator's phone for things like new signups, payment events, and bot alerts. Your email may appear in those notifications because the operator needs to know who joined or paid. Nothing about your activity beyond signup / waitlist / payment events is sent to Pushover.
• Binance, CoinGecko, and Coinbase public APIs are queried by the server as fallback price sources for backtests and the BTC daily cache. No user data is sent; these are read-only price queries.
• IndexNow (api.indexnow.org) is pinged by the platform when new content publishes so search engines can crawl faster. Only public content URLs are sent.

Client-side (loads in your browser):

• Google Fonts (fonts.googleapis.com) serves the Victor Mono webfont used across the site. Loading the font causes your browser to make a request to Google's font-CDN, which means Google sees your IP at request time. We use Google Fonts because the alternative — self-hosting the font — adds load time on every page. If your privacy posture is incompatible with this, the site is still legible without the webfont (it falls back to your system monospace).

Where the data lives. A persistent volume on Railway in the europe-west4 (Amsterdam, Netherlands) region. Daily backups are kept on the same volume. Nothing is exported off-platform. Because the data is stored inside the EU, the platform falls within direct GDPR scope, which is the right framework for the protections we've described above.

Your rights. You can ask us, by email, to:

• Tell you what we hold about you. We'll dump your account record + your in-app data and email it to you.
• Delete your account and all associated data. The next backup cycle clears it from backup state too.
• Correct anything that's wrong.

We aim to action these requests inside 14 days. If we ever stop responding, we've shut down — sorry in advance.

Children. This is not a service for under-18s. If you're under 18 you can read the blog, but please don't sign up.

About this page

This legal page is AI-generated. It's drafted by Claude, the same AI that drafts blog posts and tools on the platform, with a prompt that re-reads the platform's actual code and current state — what data it captures, what services it depends on, what payments it accepts — before regenerating. The page is then committed and deployed like any other piece of content. The version number and last-updated date in the page metadata reflect the regeneration moment.

This is intentional. A traditional terms-and-privacy page is written once by a lawyer and immediately starts drifting from reality. By the time the platform adds a feature six months later, the legal page describes a platform that no longer exists. AI-generation makes regeneration cheap; the platform stays one prompt away from a current legal page at all times.

What this is not. It's not a substitute for actual legal advice if you have a specific dispute. The operator is not a lawyer. If you're considering legal action against the platform, get your own counsel.

How "current" really stays current. The /creator dashboard has a "Refresh legal" prompt that the operator runs whenever a material change ships — a new payment provider, a new third-party integration, a new field captured in the event log. The prompt re-audits the codebase and rewrites this page if anything material has changed. When the version bumps, signed-in users see a single-line notice in the app the next time they open it.

One-version-old archive. Older versions of this page aren't currently archived publicly. If you want a copy of an earlier version (e.g. the version that was live when you signed up), email and we'll send the rendered text from git history.

Last verified accurate against the codebase: version 3 · 2026-04-28.

If anything on this page seems wrong — missing, misleading, internally inconsistent — please email. The whole point of the regeneration model is that mistakes can be fixed in the next prompt cycle, not the next legal review.