Legal

Privacy Policy

Last updated: June 14, 2026

TropeLang is built to touch as little of your data as possible. This policy covers tropelang.com and the editor at editor.tropelang.com ("the Service"), operated by Kelvin Nishikawa ("we", "us"). It explains the little we handle and the control you keep.

Apart from the standard technical data any host processes to deliver a website, and privacy-first, cookieless analytics that holds no personal data (see "Hosting & infrastructure" and "Analytics," below), everything we handle serves exactly one of two purposes — and nothing else: (1) confirming your Pro subscription, and (2) passing your own files between your browser and your own Google Drive, at your request. We never read the content of your files. Reading your content is a red line — not a setting, and not a default we might change.

The short version

Your work stays with you. The editor's analysis — parsing, recognition, validation, coverage — runs entirely in your browser. We don't receive, store, read, or train on your .trl content. The only personal information we hold is a Pro subscriber's email address, and only to confirm the subscription. For traffic measurement we use only privacy-first, cookieless analytics that holds no personal data and never tracks you across sites; we never sell or share your data.

Your content stays with you

• Free tier — your browser. Documents and your working buffer are saved in your browser's local storage on your device. We don't receive them; clearing your browser storage deletes them.
• Local files. If your browser supports it, you can open and save .trl files directly on your own disk. Those files never touch us.
• Pro tier — your Google Drive. Documents are stored in your Drive, in your account, using the narrow drive.file permission — the editor can see only the files it created or that you explicitly pick, never the rest of your Drive. Files move directly between your browser and Google; we never receive or keep a copy.

Signing in (Pro)

Pro features are unlocked by signing in with Google. Google issues the editor a token scoped to drive.file (to read and write the files you choose) plus openid email profile (to identify you). To confirm you're a subscriber, the editor sends that token to our entitlement check — a small Cloudflare Worker — which asks Google for your verified email and looks it up in our Pro access list. We don't store the access token or keep a record of these checks. The token could technically reach the files you've granted, but on our side we use it only to resolve your email for this check — never to open or read your Drive. Your files are opened and saved by the editor in your browser, directly with Google.

What we store

As little as possible:

• A Pro subscriber's email address, kept in our access list only while the subscription is active — that's how the Service knows to unlock Pro. Cancel, and it's removed. We may email this address only about your subscription (for example, receipts, billing or renewal notices, and essential changes) — never marketing, newsletters, or any other reason.
• Nothing else. No content, no usage profiles, no advertising data.

Payments

When Pro billing launches it will run through Stripe; Stripe processes your payment details directly, and we never see or store your full card information. Stripe's handling of your data is governed by Stripe's own privacy policy. (Billing is not yet live.)

Hosting & infrastructure

The Service is delivered by hosting providers (including Cloudflare). As with any website, their servers may process standard technical information — such as your IP address — to deliver and protect the Service. We don't use this to track you or build profiles, and we don't combine it with your content.

Analytics

To understand basic, aggregate traffic — how many people visit, which pages, roughly which country, and which referrers and browsers — we use Cloudflare Web Analytics. It is privacy-first by design: it sets no cookies, stores nothing on your device, and does not fingerprint your browser or track you across sites or over time. It collects no personally identifiable information, and it never touches your .trl content. What it produces is aggregate counts only — numbers that can't be tied back to you. We use them solely to see what's working and improve the Service.

What we don't do

• No reading the content of your documents — ever.
• No training any model on your content.
• No selling, renting, or sharing your data.
• No marketing, promotional, or newsletter emails.
• No advertising, behavioral tracking, or tracking cookies — and no analytics that identifies you or follows you across sites. The only analytics we use (above) is cookieless and aggregate.

On your device

The editor uses your browser's local storage for your saved documents, your working buffer, your theme preference, and a short-lived cache of your Pro status. This stays in your browser.

Your choices

• Delete local work by removing documents in the editor or clearing your browser storage.
• Revoke Drive & sign-in access at any time from your Google Account's third-party access settings.
• Delete Drive files directly in your own Google Drive.
• Leave Pro to have your email removed from the access list.

Features not yet available

Planned Pro features — document sharing, real-time collaboration, and bring-your-own-LLM assistance — aren't live yet. They're designed to keep your data with you or with providers you choose: for bring-your-own-LLM, your API key stays in your browser and requests go directly to the provider you pick. We'll update this policy before any of them ship.

Children

The Service isn't directed to children under 13 (or the minimum age where you live), and we don't knowingly collect their information.

Changes

If our practices change, we'll update this page and the "last updated" date above.

Contact

Questions or data requests: [email protected].