Privacy

Data controller

Name

BYEN SLU

Address

12-14 Avinguda Doctor Mitjavila, Andorra la Vella, Andorra

What the tools do not send

Whatever you type, paste or drop into a calculator, a converter or a file tool is processed in your browser and is not transmitted. That is not a policy that could be changed without you noticing — it is how those tools are built, and it means there is no server-side record of your inputs to request, export or delete. A few tools are the exception and cannot be otherwise, and each says so on its own page: a DNS lookup sends the domain you asked about to our server, which asks the public resolvers of Cloudflare and Google; an IP address lookup sends the reverse-DNS name of the address you entered the same way, while the network data itself is looked up in your browser; My IP address reads the address your connection comes from in order to show it to you, and only if you click its IPv6 check does your browser contact api6.ipify.org, a third-party service that states it keeps no logs. The internet speed test exchanges blocks of empty data with Cloudflare (speed.cloudflare.com) when you start it: Cloudflare then sees your IP address, your browser and our site's address, but does not receive the result, and neither do we; Chromium-based browsers may also send it network error reports for some of those requests. For the electricity price, our server reads the public wholesale prices of the Bundesnetzagentur (SMARD.de) and of OMIE: those services see our server, never your address, and the zone you last chose stays in your browser's local storage. For the WHOIS lookup, our server queries the registry of the extension you ask about and, at most once a day, IANA's public directories: they see our server's address, never yours, and the domain you look up is neither kept nor logged. For the weather forecast, your browser sends our server the place you chose, rounded to about 1 km, and our server asks MET Norway, the Norwegian Meteorological Institute, for the forecast at that point: MET Norway sees our server and the rounded point, never your address. The last town you picked stays in your browser's local storage; your position, if you share it, is never kept there. The earthquakes page sends nothing about you: our server reads the public catalogues of the USGS, the EMSC and INGV. The weather warnings page sends the place you chose, rounded to about 1 km, together with its country code: depending on that country our server asks MeteoAlarm, the National Weather Service or Environment and Climate Change Canada, each of which sees our server, never your address. The river levels page sends the same rounded place and its country code: our server then asks Hub'Eau and Vigicrues in France, PEGELONLINE and the Länder flood portal in Germany, or the National Water Prediction Service in the United States. The active fires page sends the same rounded place: our server then downloads the NASA FIRMS satellite detection file for the surrounding region and asks GWIS, the Copernicus Global Wildfire Information System, for the fire danger index at that point. Both see our server, never your address, and neither receives anything you typed. The sea temperature page sends the same rounded place: our server asks NOAA's CoastWatch ERDDAP service for the sea-surface values around it, and NOAA sees our server, never your address. The air quality page sends the same rounded place together with its country code: in Europe our server asks the European Environment Agency for the index at that point, while in the United States, Mexico, Puerto Rico and Canada it downloads the national file of AirNow or of Environment and Climate Change Canada and finds the nearest area or station itself, so those two agencies never receive your place at all.

What is processed anyway

Five things, and this is the complete list:

• Technical request data at the host — IP address, browser, page requested, timestamp — recorded as any web server records it, to deliver pages and to resist abuse. Retention is the host's, not ours; we do not read, export or combine these logs.
• Two functional cookies, the sb-… session cookies of an account if you have one, and thirteen browser-storage keys, named one by one on the cookies page. None of them carries your civil identity. One of the thirteen is transmitted on its own: allin:sid, a random UUID drawn per browser tab and discarded when the tab closes. It is a pseudonym — derived from nothing about you, and there is no table that turns it back into a person — but it is an identifier, and calling it anything softer would be the kind of wording this page exists to avoid.
• Our own measurement of how the site is used: a page was viewed, a tool was opened, used, completed or failed, a result was copied, shared or downloaded, a suggested tool was followed, with the language, the kind of page, the country your host reports, and the per-tab identifier. A search also records the words you searched for, how many results came back and which one you opened — that is the only free text we collect, and the only way to learn which tool is missing. No account, no cookie, no address, and never the contents of anything you typed into a tool. It is not shared with anyone, and no row in it is about an identified person.
• Your email address, if you write to us — kept as long as needed to answer, and not used for anything else.
• What your account holds, if you create one: the email address you signed up with, the plan attached to it, the tools you starred or pinned, the results and projects you chose to save, and the times you opened a tool inside the workspace. It is there because you asked for it to be, it is shared with nobody, and the two sections below say exactly how it gets there and how it goes away.

What leaves your device, and when

Thirteen keys sit in your browser. Three of them can be copied to our servers, and only when three conditions hold at once: you have an account, you are signed in, and you have opened the workspace at /app. They are allin_favorites, allin_pins and allin_recents — the tools you starred, the ones you pinned in the order you arranged them, and the last two dozen you opened. They arrive as tool identifiers and timestamps, in two tables, user_tool and tool_event.

Of the other ten, one travels on its own — allin:sid, with the measurement described above — and the remaining nine never leave the browser under any condition. That includes allin_notepad, which holds whatever you type into the online notepad, and allin_tools, which holds the cities, alarms and wheels of the interactive tools: both are written to your device and read back from it, and no code path sends them anywhere.

The reason for the three is one sentence long: a library that exists in one browser only is lost when you change device or clear your data, and an account whose whole purpose is to keep it would be keeping nothing. The first synchronisation merges rather than replaces — guest favourites are added to what the account already had, guest pins are appended after the existing ones and stop at the number the plan allows, and a tool the account has already recorded is not recorded twice. It is kept for as long as the account. Removing a star or a pin deletes the row immediately, and deleting the account removes all of it.

Deleting the account

You do it yourself, from the Account page in the workspace: type the email address the account uses, confirm, and it is done. No request to write, no delay, no review.

What goes: the sign-in itself, the entitlements, the profile, the favourites and pins, the favourite collections, the saved results, the projects and what they contain, the tool history, and the administrator record if there was one. Every table that named you loses its rows with the account.

What stays, and it is deliberate: two tables keep their rows with the account column emptied instead of deleted. The usage counts — a page was viewed, a tool was opened — because they measure the product and not the person, and removing them would falsify totals nobody could correct afterwards; and the administration audit log, because a log the person it records can rewrite is not a log. Once the column is empty neither can be traced back to you.

The deletion is immediate and we keep no copy of our own. What can outlive it for a while is our database provider's own backups, which expire on their schedule and which we do not open.

Your rights

Under the GDPR you may ask for access to your personal data, its correction or erasure, a copy of it, or object to its processing. Write to us through the contact form and say which. If you have never created an account, the honest answer will usually be that we hold nothing about you, and you can verify most of that yourself by clearing this site's data in your browser. If you have one, erasure needs no letter: the Account page does it, and the section above says what it leaves.

If the answer does not satisfy you, you may lodge a complaint with the data protection authority of the country you live in.