Privacy

Last updated 3 September 2026. The short version first. The text you paste into the converter is processed entirely in your browser and is never sent to our servers. Everything else we touch is listed below, plainly.

Who is responsible for this

The site is operated by JINO LABS (OPC) PRIVATE LIMITED, a One Person Company registered in India and trading as JINO LABS. Its registered place of business is 3rd Floor, 25-2-200/103 SF-304, Revenue Ward 52, Kanithi, Visakhapatnam, Andhra Pradesh 530044, India. That company is the data controller for everything described on this page, which means it decides what is collected and why, and it is who to contact about any of it. Reach us through the contact page, which is the fastest route and goes to a person rather than a queue.

Your pasted text

Conversion runs on your device. The words you paste, type or copy out of the converter never leave your browser. The free tier limits how long a text can be, and that check also happens in your browser without sending the text anywhere. The optional Humanize toggle, which rewrites em dashes and strips filler, also runs entirely in your browser and never sends your text anywhere.

Accounts and the lifetime unlock

You can use the free tier with no account. If you buy a paid plan, monthly or lifetime, you sign in with Google, and we store the basics of that account on our servers, meaning your name, email address, avatar, a session token and the Google sign-in tokens that link your account. When you sign in we also register your name and email with Dodo Payments, our payment provider, so a purchase can be linked to your account. Payment itself is handled by Dodo as merchant of record. Your card details go to them, never to us. We store only the fact that a payment for your account succeeded or was refunded, and for the monthly plan your subscription status, so the unlock follows your account. Subscriptions renew through Dodo and can be cancelled any time from Manage billing in the account menu. Sessions record the IP address and browser they were created from.

Analytics

We use PostHog and Google Analytics to understand how the product is used, and neither runs until you accept analytics cookies. Both record metadata only, for example which conversion pair was picked or which button was pressed, never the text itself. The input box and the converted output are explicitly excluded from analytics capture, and session recording is off. Google Analytics runs under consent mode with analytics storage and every advertising signal denied by default, so no analytics cookie is set until you say yes, and advertising signals stay denied even then.

We also keep our own counts on our servers. Every one of them measures the shape or the size of the work and never its content, and every one is a running total rather than a record of a single conversion. Examples are which conversion pairs are used, which source formats we detect, whether output is rich text or symbols, and how many conversions, words and characters go through each day. Because they are only ever totals, there is no record of an individual conversion, nothing is tied to you or to your session, and no part of what you paste is sent or kept. To stop abuse we also count requests per address. A count covers a minute at a time, or at most a day for things like the request form and new API keys. Those counts are tied to the address and not to anything you convert, they stop counting when the window ends, and the rows are cleared out by later traffic.

Server logs

Our servers write ordinary diagnostic logs as requests arrive. Two things are true of everything in them. The text you paste is never among it, and none of it is analysed or used to build a profile of you. What can appear is the sort of detail a server records to debug itself, for example the address a request came from, the page a browser was on when it reported a content-security-policy problem, and the payment or subscription identifiers our payment provider sends us. Cloudflare runs our servers and keeps these logs for up to seven days before deleting them, and we do not copy them anywhere else.

Cookies and your choice

Analytics cookies are off until you agree. On your first visit a small card in the corner asks, and nothing is stored on your device for analytics until you accept, apart from a note of your answer so we do not ask you again. Declining is a single click in the same card, the same size as accepting, and the converter behaves identically either way. If you accept, Google Analytics sets a first-party cookie and PostHog keeps an anonymous identifier in your browser storage, both used only for the metadata described above.

You can change your mind here at any time, and it takes effect immediately.

Two cookies do not wait for a choice, because neither is used to learn anything about you. If you sign in, a session cookie keeps you signed in, which is the thing you asked for by signing in. And a short-lived record of your address supports the abuse limits described further down. Clearing your browser data removes anything stored on this device, including your answer to the card, so it will ask again.

Advertising on the free tier

The free tier is ad supported. When ads are enabled they are served by Google AdSense, which may use cookies. In the European Economic Area, the United Kingdom and Switzerland a Google certified consent tool will ask for your choice before any personalised ads load. Paid accounts never load the advertising script at all.

Feature requests

If you use the request-an-app widget, what you type there, including the email you provide so we can reply, is delivered to us by FormSubmit and also stored on our servers so requests can be tracked. Requests are kept until we action them or you ask via the contact page to have one removed.

The developer API

Unlike the web tool, the optional developer API processes the text you send to it on the server, converts it and returns the result. It is stateless and stores neither the input nor the output.Usage counters record which conversions happen and through which interface, never the content and never how much of it there was, and issuing an API key records the requesting address to enforce the daily key limit.

Why we are allowed to hold each thing

If you are in the UK or the European Economic Area, the law asks us to name a reason for each kind of data rather than a single blanket one, so here they are. Your account details and payment records exist because we cannot give you a paid plan without them, which is performance of our contract with you. Analytics cookies rest on your consent, which is why they are off until you give it and stop when you take it back. The abuse limits and the server logs rest on our legitimate interest in keeping a free tool from being abused, and both are narrow and short-lived for that reason. A feature request you send rests on your consent, given by choosing to send it.

How long each thing is kept

Account and payment records are kept while your account exists, and payment records for as long afterwards as tax and accounting rules require, which is our payment provider's obligation as much as ours. Server logs are kept by Cloudflare for up to seven days. The per-address abuse counts last a minute in most cases and at most a day, then are cleared. The anonymous usage and volume counts are daily totals kept for ninety days, plus all-time running totals that contain no dates and no identifiers. Feature requests are kept until we action them or you ask us to remove one.

Who else handles it

We do not sell anything to anyone, and nobody buys data from us. The companies that process something on our behalf are Cloudflare, which runs the site and the database, Dodo Payments, our merchant of record for payments, Google, for sign-in and analytics, PostHog, for product analytics, and FormSubmit, which relays the feature-request form to our inbox. Google and PostHog only receive anything if you accept analytics cookies. Some of these companies are based in the United States or process data there, so using this site involves your data being handled outside the UK and the EEA under the transfer terms each provider offers.

Your rights over this

You can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, ask for it in a portable form, or object to a use that rests on our legitimate interest. Where something rests on your consent you can withdraw it, and the analytics control above does that for cookies without asking anyone. To exercise any of the others, or if you are unhappy with how we have handled a request, reach us through the contact page below. If you are in the UK or the EEA you also have the right to complain to your data protection regulator.

Two limits worth stating plainly rather than leaving you to discover them. We cannot give you a copy of the text you have converted, because we never had it. And we cannot single out your share of the anonymous totals, because nothing in them is tied to you, which is the same property that makes them harmless.

Children

This is a text formatting tool with nothing in it aimed at children, and we do not knowingly collect anything from anyone under 13. If you believe a child has given us something, tell us through the contact page and we will remove it.

Changes to this policy

The date at the top changes whenever this page does. If a change means we start collecting something new that rests on your consent, we will ask again rather than treat an old answer as covering it.

Data removal and questions

To delete your account data, exercise any of the rights above, or ask anything about this policy, write to JINO LABS (OPC) PRIVATE LIMITED through the contact page.