Privacy policy

Last updated: 26 October 2026

This page explains what getsolved.net collects, what happens to the business problems and inputs you type in, how accounts and credit payments work, and how to reach us.

Who we are and how to contact us

GetSolved (getsolved.net) is a library of AI solutions for everyday business problems. It was founded by Bach Vu and Minh Hoang, is developed by Autana.ca, and is based in Burnaby, British Columbia, Canada.

To reach us with questions about this policy, or to ask to access, correct or delete information, including asking us to remove a solution, use our contact page: https://autana.ca/contact/.

What we collect and why

You can search and browse solutions without an account. To run solutions you sign in with your email address and buy credits. What we handle:

Your email address, when you sign in. We use it to send your sign-in link, to identify your account and credit balance, and as the receipt address for your card payments. We don't send marketing email.
Your credit balance and history: each top-up (amount, currency, time and Square's payment ID), and for each step you run, the time, the solution's ID, the AI model used, how many tokens it used and the credits charged. We don't keep what you typed or the results.
The business problem you describe when you ask Claude to build a new solution. We send it to Anthropic to generate the solution, and we keep a copy, with the time and the solution it produced, so we can review new solutions and learn which problems visitors want solved. It is stored without your IP address, email address or account, and only our site administrators can see it.
The generated solution, which we save as a pending submission. It is not public: we review it, and it joins the public solution library only if we approve it. So we know there is something to review, its title and short description are sent to us in a Telegram message; the problem text you typed and your IP address are not included.
Your IP address, briefly, when you build a solution. We use it to limit how many solutions one visitor can build, as described under Build limits.
Server request logs. Our web server records each request: your IP address, your browser's user agent, the address requested, the referring page and the time. We use these logs to operate and troubleshoot the site.
Application error messages. When a request causes an error, the message can include the address that was requested.
Engagement analytics from the homepage, described under Analytics.
A sign-in cookie for visitors who sign in, and an admin session cookie for site administrators, described under Cookies.

Content you submit, accounts and payments

Building a solution

When no solution matches your search and you choose to build one, the problem you typed is sent from our server to Anthropic's Claude, which designs the solution. We keep the problem text for 12 months, separately from the solution, for our administrators only: it is never shown in the public library or returned by our site API, even if the solution is approved. We also keep the solution Claude generates: its title, description, tags, keywords, instructions, input fields and steps, and the time it was built. Claude may repeat details from your problem in that solution, so please don't include personal or confidential information. To have a problem you typed deleted, send us the time you built it or the solution's title through our contact page.

New solutions are reviewed before they become public. The solution appears on your screen straight away, so you can run it immediately. It is saved as pending: pending solutions are not shown in the public library, in search results or on the homepage, and our site API doesn't return them. Only our site administrators can see them. We review each one, and either approve it, which adds it to the public library where any visitor can find and run it, or delete it. Solutions aren't linked to a name or account. To have a solution removed, whether pending or public, send us its title through our contact page.

Build limits

Building a solution uses our own Claude access, so we limit how many can be built: a few per visitor per hour, and a fixed number across all visitors per day. When a limit is reached, the site tells you when you can try again. To count your builds, our server keeps your IP address, with the times of your recent builds, in memory for up to an hour. It is not written to disk or linked to the solutions you build, and it is cleared whenever the server restarts.

Running a solution or a Builder flow

When you run a solution or a flow you wrote in the Builder, your browser sends your inputs to our server. Our server sends them, with each step's prompt, to Anthropic's Claude using our own access, and returns the result to your browser. We don't store or log your inputs or the results. We record only the usage needed to charge credits, as listed above.

Signing in

There is no password. You enter your email address and we email you a one-time link that expires after 30 minutes. Sign-in emails are sent from our own mail server.

Buying credits

Card payments are processed by Square. You type your card details into a form that Square provides, and they go directly to Square: our server never sees or stores your card number, expiry date or security code. Square gives us a one-time payment token, which we use to charge the amount you chose, and we keep Square's payment ID, the amount and the time. Square's handling of your payment is covered by Square's privacy notice.

AI providers

Anthropic, through its Claude models, is the only AI provider that receives what you type on GetSolved. It gets your input in two ways:

Building a solution: our server sends your problem description to Claude using our own access.
Running a solution or flow: our server sends your inputs and the step's prompt to Claude using our own access.

Anthropic's handling of that data is covered by Anthropic's privacy policy.

Cookies and local storage

We set no cookies for visitors who don't sign in, and the site doesn't use your browser's local storage or session storage.

gs_user is set when you sign in, and keeps you signed in. It lasts 90 days or until you sign out. gs_session is set only when a site administrator signs in to the admin page. It lasts 30 days or until they log out. The Square card form, which loads only when you open the top-up window, may set its own cookies for fraud prevention.

Analytics

The homepage loads a small engagement beacon called Klimb from autana.ca. When the tab is hidden or closed, it sends the page path (never the query string), how far you scrolled, how long the page was visible, whether you arrived from a Google results page, and whether you left quickly. It goes to our analytics service at autana.ca. It sets no cookies and stores nothing on your device. It uses a random ID for each page view. We don't store your IP address or user agent with this data, and we keep raw page views for 90 days. The beacon does nothing when your browser sends Do Not Track or Global Privacy Control.

We don't use any other analytics or advertising tools.

Service providers

Anthropic generates new solutions and runs solution steps, as described above.
Square processes card payments for credits, as described above.
Telegram. When a new solution is waiting for review, we receive a Telegram message with its title and short description, so it can be reviewed promptly. Telegram's handling of that message is covered by Telegram's privacy policy.
Google Fonts. Our pages load their fonts from Google (fonts.googleapis.com and fonts.gstatic.com). Like any web request, this means Google sees your IP address and browser details. See Google's privacy policy.
Autana.ca develops GetSolved and operates the Klimb analytics service.

How long we keep it

Approved (public) solutions: until they are removed.
Pending solutions: until we approve or delete them.
IP address used for build limits: in memory for up to an hour, and cleared when the server restarts.
Problem text for a new solution: 12 months from when you built it, then deleted automatically. You can ask us to delete it sooner.
Solution inputs and results: passed through our server to Anthropic, and not stored by us.
Your email address, credit balance, payments and usage records: while your account exists, and afterwards as long as the law requires us to keep payment records. Ask us to close your account through our contact page.
Sign-in links: expire after 30 minutes; we delete them within a day.
Sign-in cookie: 90 days, or until you sign out.
Server request logs: about 14 days. They rotate daily and older files are deleted.
Klimb raw page views: 90 days.
Admin session cookie: 30 days, or until the administrator logs out.
Application error messages: as long as needed for the purpose they were collected for.

Your choices and rights

Leave personal and confidential information out of the problems you ask Claude to build, because the resulting solution can become public once it is approved.
Turn on Do Not Track or Global Privacy Control in your browser to stop the Klimb beacon.
Ask us to access, correct or delete information we hold about you, or to remove a pending or public solution, through our contact page.
Ask us to close your account and delete your email address, through our contact page.

If you are not satisfied with our response, you can complain to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia.

Changes to this policy

If our practices change, we will update this page and the "Last updated" date at the top.

Last updated: 14 September 2026