Privacy Policy
This policy explains what AllTools.Solutions collects, what it doesn't, and why. It's written by Ken Ozawa, an individual based in Australia who operates this Site (“we,” “us,” or “our”) — there's no larger company behind it.
The short version
What you type into a tool — numbers, text, a resume, a job posting — is not kept once your result is produced, with one short exception for tools that hold your input briefly, explained below. We don't build a profile of you or keep a history of what you've used. Separately, and honestly: this Site runs on Google Analytics and Google AdSense to stay free, and those set standard tracking cookies once you accept them. Those two facts aren't in tension — they're about different things, and both are explained below.
Cookie consent
On your first visit, a banner asks whether you're okay with Google Analytics and AdSense cookies. Until you accept, neither script loads — no analytics pageview is recorded, and no ad request is made. If you decline, we remember that choice (in your browser's local storage, not a server-side record tied to you) and won't ask again on that device. You can change your mind at any time by clearing your browser's local storage for this Site.
What tool inputs we collect — and what we do with them
Free tools (calculators, converters, generators, developer tools) run entirely in your browser. What you type is used to compute a result on your own device and is never sent to our servers at all, unless a specific tool says otherwise on its own page.
Some AI-powered and paid-data tools do send what you enter to our server, because they can't work otherwise. Depending on the tool, that can include text you paste or upload (such as a resume or job posting), keywords, or choices you make (such as an age range, supplies, or a theme). We pass this information to the outside services that do the work, only to produce the result you asked for. That means Vercel, our hosting provider, and the AI and data providers listed under “Other services we rely on” below. We don't sell it, and we don't use it for anything else.
By default we don't save what you enter or the result you get back, and once your result is returned we don't keep a copy. A few tools need to hold your input briefly so a request can finish or so the same lookup isn't repeated and paid for twice. When that applies, it is kept for no more than 24 hours and then deleted automatically. After that we keep only anonymous counts, such as how many times a tool was used.
To prevent abuse, some tools record a scrambled (hashed) version of your IP address for about a day, to limit how often one person can use a free allowance. We can't turn it back into your address.
Tools aimed at parents and carers (for example, activity or experiment ideas for children) ask for an age range only to suit the activity. We don't ask for, and don't collect, a child's name, photo or any information that identifies a child.
Redemption codes — the one thing we do keep
If you buy credits (usable on any AllTools.Solutions tool that accepts them) we generate an anonymous redemption code and store it along with its starting and remaining credit counts, hosted on Upstash (a Redis database provider). That stored record is just a code and a number — no name, no email, no resume content, nothing that identifies you. Credits don't expire. When a credit is spent we also add one to a per-tool counter (a tool name and a total, nothing about you) so we can see which tools get used.
For each purchase we also keep a record of when it happened, which pack was bought and the amount, next to Stripe's payment reference. It contains no name and no email. An unlock is stored against your code with its end time, and disappears when it ends.
Stripe collects your email as part of processing payment. We use it once, at the moment of purchase, to automatically send your code to you by email via Resend (our transactional email provider) — purely as a convenience so you have a backup copy. We don't store that email ourselves. We do store Stripe's reference for your payment next to the code (it contains no name or email), so we can show you the same code if you reload the page after paying and can handle a refund request. There's no account system and we can't look a code up by email address on our own — if you lose the code and didn't keep the email, contact us and we'll try to match your purchase through Stripe's payment record, but we can't guarantee we'll be able to.
Payments
All payments are handled by Stripe, our payment provider and Merchant of Record (through Stripe Managed Payments). Stripe collects and processes your payment details (card number, billing address, etc.) directly — we never see or store that information. See Stripe's own privacy policy for how they handle it.
Analytics and advertising cookies
Once accepted, this Site uses:
- Google Analytics — measures overall traffic and usage patterns (which pages get visited, roughly where from, what device). This is aggregate usage data about visits to the Site, not the content you type into a tool.
- Google AdSense— shows the ads that keep free tools free, and may use cookies to personalize which ads you see based on general browsing interest signals from Google's ad network.
You can opt out of personalized advertising directly through Google's Ads Settings, independent of the cookie banner on this Site.
We also use Vercel Analytics, a privacy-friendly page-view counter. It doesn't use cookies or track you across sites, and it runs regardless of the cookie banner.
Other services we rely on
Vercel hosts the Site and runs its servers. Upstash hosts the redemption-code database. Anthropic's Claude AI writes the results for our AI-powered tools. DataForSEO supplies search data for tools that need it. Stripe processes payments. Resend sends the one-off redemption-code email. None of these providers receive more than what's needed to do their specific job.
Children's privacy
This Site isn't directed at children, and we don't knowingly collect data from them. Some tools are designed for parents and carers to use with their children. They ask for an age range only to suit the activity, and nothing that identifies a child.
Changes to this policy
We may update this policy as the Site changes — for example, if a new paid tool is added. We'll update the “Last updated” date above when we do.
Contact
Questions about this policy, or a request related to your data? Reach out at mmoz.ai@outlook.com. See also our Terms of Service and Refund Policy.