Privacy Policy

Last updated: September 2026

Scope

This policy covers the three ways to use Transmify: the web converter, the free REST API, and the browser extension. It doesn't cover third-party sites linked from the project (like GitHub), which have their own privacy practices.

Who operates this

Transmify is sponsored by Scriptimiz Insight LLP (scriptimiz.com). Source code is public on GitHub, though being open source describes the code, not the operational data practices — this page describes those separately.

1. The web converter (the main site)

Every conversion you run at the main URL happens entirely inside your browser tab, using JavaScript running on your own device. The converter does not make a request to our backend containing your input data — under the current implementation, we do not receive or process the content you paste, drop, or upload. Closing or refreshing the tab discards everything; nothing is saved between visits.

We do not intentionally use cookies, analytics services, advertising trackers, or behavioral tracking scripts on this site — we checked the actual source code to confirm this rather than just asserting it, and there is currently no analytics, tracking, or third-party script of any kind loaded anywhere on the site.

2. Third-party services

Fonts. This site loads its typefaces (Space Grotesk, Inter, IBM Plex Mono) from Google Fonts. Because of that, your browser connects directly to Google's servers to retrieve those files, which — like any web request — may expose information such as your IP address and browser/network information to Google, handled according to Google's own privacy practices. We don't control or see that data ourselves.

Infrastructure. This site is hosted on Cloudflare. Cloudflare, as our infrastructure provider, may process limited technical information associated with requests to our service — such as IP addresses and other request metadata — for security, reliability, and abuse-prevention purposes, according to its own policies. We do not intentionally send or store your converter input as part of that, but we haven't independently audited Cloudflare's full infrastructure-level configuration, so we describe this as "we don't intentionally log it" rather than an absolute guarantee about every layer of the stack.

The interactive API docs at /docs/ use Swagger UI, hosted directly on this site (not loaded from a third-party CDN).

3. The free REST API

Unlike the web app, the REST API (/api/convert/...) is a server-side endpoint — by definition, whatever you send it has to reach our server (a Cloudflare Worker) to be converted and sent back. We do not intentionally log, store, or retain the request body or converted content in our application code; conversion happens in memory and the result is returned directly. API requests necessarily include your IP address and other standard request metadata as part of normal internet communication, which our infrastructure provider may process as described above.

If your data is sensitive or confidential, we recommend using the browser-based converter rather than the API, since API requests travel over the internet to our infrastructure by design. Please don't use the API to transmit information you aren't permitted to send to a third-party service.

4. The browser extension

The extension runs locally in your browser and only reads a table's content (or a raw JSON page) when you take a specific action — clicking "Extract table," or navigating to a page the JSON viewer activates on. It doesn't scan or transmit page content automatically in the background. Copying or previewing extracted data (CSV/JSON/Markdown) all happens locally.

If you click "Open in converter," the extracted data is encoded into the URL used to pre-fill the web app in a new tab — specifically, into the URL fragment (the part after #), not a query parameter. That distinction matters: a URL fragment is never sent to any server as part of the request — browsers keep it entirely client-side — whereas a query parameter is technically part of the request and can end up in server or CDN access logs even when our own application code never reads it. We do not intentionally transmit or store that data as a result of this action either way. That said, URLs — fragment included — can still be retained by your own browser or other software: browsing history, bookmarks, sync services, or other installed extensions. For highly sensitive information, we'd recommend copying the data manually into the converter instead of using "Open in converter."

5. Data retention

We do not intentionally retain the content submitted to the browser converter or processed through the API after a conversion completes. Standard infrastructure and security logs may be retained by our hosting provider for a limited period, according to its own policies.

6. Security

We use reasonable technical measures aimed at protecting the service and the information that passes through it. No internet transmission or storage system can be guaranteed to be completely secure, and we can't promise otherwise.

7. International data processing

Our infrastructure provider may process limited technical information (like the request metadata described above) in countries other than your own, including wherever its infrastructure operates. That processing is subject to the provider's own applicable privacy and data-protection obligations, which we haven't independently certified.

8. Accounts and authentication

There are currently no user accounts, logins, or saved preferences anywhere in this project. That doesn't mean zero technical data exists anywhere — your browser and third-party infrastructure providers may still maintain standard network-level logs, as described above. If accounts are added in the future (see the optional-authentication section of our product spec), this policy will be updated accordingly before it ships.

9. Your rights and requests

Because converter input stays in your browser and isn't transmitted to us, we generally don't have access to that content, and so can't provide, correct, or delete it from our systems — there isn't a copy of it to act on. For anything that isn't covered by that (for example, a question about how the API or infrastructure logging works), contact us using the details below and we'll do our best to help. This section is not a substitute for legal advice about your rights under GDPR, India's DPDP Act, or any other applicable law — we're a small open-source project, not a law firm, and haven't had this policy reviewed by one.

10. Children

This service isn't directed at children, and we don't knowingly collect personal information from children, consistent with the rest of this policy — the web converter doesn't collect input data from anyone, regardless of age.

11. Changes to this policy

If how this project handles data changes — new features, a paid API tier, accounts, analytics — this page will be updated to reflect that honestly, and the "Last updated" date above will change.

12. Contact

For privacy-specific questions or requests, reach us at support@scriptimiz.com. General questions, bugs, and technical issues are welcome via GitHub Issues instead — GitHub Issues are public, so please don't include personal or sensitive information in one. See the contact page for all the ways to reach us.