Last updated: 18 October 2026. This policy explains exactly what happens to the data you type into Layerbit's tools, what the site collects about your visit, and which third parties are involved. We have tried to be specific rather than reassuring — where a guarantee is strong we say why, and where it is weaker we say that too.
Almost every tool on this site processes your input entirely inside your own browser. Nothing you paste into the JSON validator, the JWT decoder, the SQL formatter or any other local tool is transmitted to us or to anyone else, because there is no endpoint receiving it. The site does serve advertising and runs an anonymous visitor counter, both of which set cookies, and a consent notice appears before that happens.
The following tools run as client-side JavaScript in the page you have open: JSON Validator & Formatter, Universal SQL Formatter, JWT Decoder & Verifier, QR / Barcode Generator, Base64 Encode / Decode, JSON Table Viewer, Text Diff Checker, CSV ↔ JSON Converter, YAML ↔ JSON Converter, Cron Expression Generator, URL Encoder / Decoder, Log Analyzer, Regex Tester, HTML Escape / Unescape, CIDR & Subnet Calculator, Hash & HMAC Generator, UUID & ULID Generator, Unix Timestamp Converter, XML Formatter & XPath Tester, Unicode Inspector, and the UAE PINT-AE Compliance Checker.
For all of these, the text, code or files you provide are read, processed and displayed by your own browser. They are not uploaded, not logged, and not retained by us — we never receive them in the first place. You do not have to take this on trust: open your browser's developer tools, switch to the Network tab, and use any of these tools; nothing leaves. You can also load a tool, disconnect from the internet, and continue using it normally.
Because we never receive this data, we cannot disclose it, sell it, lose it in a breach, or hand it over on request. That is a property of how the site is built rather than a promise about our intentions.
LayerLink screen sharing is badged Cloud API on the homepage because it cannot work purely locally — two browsers have no way to find each other without help. It uses WebRTC, which means:
Anyone holding a session identifier can attempt to join a live session, so treat a LayerLink link like a temporary password and share it only over a channel you trust.
This page covers the website. If you are using the LayerLink Android app, its data handling is different — it captures your screen through Android's MediaProjection API and runs a foreground service to do so, neither of which applies here — and it has its own policy: LayerLink app privacy policy.
We do not operate an application server, a user database, or any account system. There is no sign-up and no login anywhere on Layerbit, so there is no profile associated with you. The data that is collected comes from four places:
_ga family to tell one visit apart from the next. GA4 does not store your full IP address, and we have not enabled any feature that would let us identify an individual reader — we look at totals, not at people. We added it for a plain reason: without it we cannot tell which guides are worth writing more of.Google acts as our processor for the analytics data and as a controller in its own right for the advertising data, which is why an advertising request has to go to Google rather than to us. Both are covered by Google's privacy policy. Beyond these four, nothing else on the site collects anything: no heatmap tool, no session recorder, no third-party tag manager, and no advertising network other than AdSense.
On your first visit a notice asks whether you allow non-essential cookies, which on this site means advertising (Google AdSense) and analytics (Google Analytics). Accept all allows both; Reject non-essential refuses both, and the tools work exactly the same either way because none of them needs a cookie. Your answer is stored as a single flag in your browser's local storage, never sent to us, and you can change it at any time with the Your privacy choices link in the footer of every page.
The choice is passed to Google through Google Consent Mode before any Google script runs. If you reject, or if you are in the European Economic Area, the United Kingdom or Switzerland and have not yet chosen, advertising and analytics storage are switched off: Google may still show ads, but they are not personalised and no advertising or analytics cookies are set. Visitors in those regions may instead see Google's own consent message, provided by Google as a certified consent management platform under the IAB Transparency and Consent Framework; when it appears it replaces our notice and records your choice in the same way.
Two other things are stored on your device, and only there. Run history: some tools can keep your recent inputs in your browser's own IndexedDB database so you can restore them later; nothing is recorded unless a tool offers it, the data never leaves the browser, and the command palette (Ctrl+K) has a "Clear local history" action that deletes all of it. Offline copies: a service worker caches the pages and scripts you have visited so the tools keep working without a connection; it stores only the site's own files, never your input, and your browser's "clear site data" removes it. Share links encode your input into the URL fragment, the part after the #, which browsers do not send to any server — a share link is a container for your work, not a copy of it with us.
You have several independent controls:
Depending on where you live, data protection law may give you rights to access, correct, delete or restrict processing of your personal data, to object to processing, and to receive a copy of it. We support all of these — and in practice the answer is usually short, because there is very little to act on.
For the local tools there is nothing to request, access or delete: we hold none of it. For correspondence you have sent us, email ceo@layerbit.co.in and we will provide a copy or delete it. For data held by Google in connection with advertising, requests need to go to Google, since they are the controller for that processing and we have no ability to access or delete it on your behalf.
Every page is served over HTTPS. The site is entirely static — pre-rendered HTML with no application server and no database — which removes most of the categories of vulnerability that lead to data disclosure, for the simple reason that the systems which would be attacked do not exist. The correspondence we do hold is kept in a standard email account protected by multi-factor authentication.
Layerbit is a developer tools site intended for a professional and technical audience. It is not directed at children, and we do not knowingly collect personal information from anyone under 13 (or the equivalent minimum age in your jurisdiction). If you believe a child has sent us personal information, contact us and we will delete it.
When this policy changes we update the date at the top. Material changes — a new third-party service, a new category of data collected — will be reflected here before the change is deployed, not afterwards. In September 2026 we removed three tools that queried third-party APIs for breach data, URL reputation and IP geolocation; this policy no longer references them, and no data from those tools was retained. In the same month we added Google Analytics 4, which is disclosed above and was added to this policy in the same change that deployed it. In October 2026 we replaced the accept-only cookie notice with an accept-or-reject choice wired to Google Consent Mode, so that advertising and analytics cookies are off until you allow them in the regions where consent is required.
Questions about this policy, requests about your data, or anything you think is inaccurate here: ceo@layerbit.co.in. If something in this document does not match what the site actually does, we would genuinely like to know — please tell us and we will correct it.