Your account.
Everything about getting in, staying in, and finding your own numbers once you are. None of it applies to the browser tools, which work without an account and always will.
Do you even need one?
All 341 tools on the site are open to anyone, and the ones that run in your own browser are free with no limit. An account is for the things that happen on our servers.
| An account gives you | Why |
|---|---|
| A monthly credit balance | 1,000 credits a month on the free plan, for the REST API, the MCP server, AI tools and renders. |
| API keys | So your own code and your AI assistant can authenticate. |
| Saved workflows | Chains of capabilities you can run again, and their run history. |
| Usage history | 7 days on the free plan, 365 days, about 12 months on ToolForte Pro. |
| Agent memory | Values an assistant stores between sessions, kept for 30 days on the free plan and 365 days, about 12 months on ToolForte Pro. |
Signing up
Two ways in, and they end up in the same place.
With GitHub or Google
One button on the sign in page. You approve it with the provider and you are in. Nothing to confirm afterwards.
With an email address and a password
Pick Sign up, enter your address and a password of at least six characters. We then send you a confirmation link, and the account is not usable until you open it.
Confirmation links work once and expire. If yours has gone stale, or never arrived, the sign in page has a button that sends a fresh one, and the new link replaces any older one.
Forgotten passwords
No support ticket needed.
On the sign in page, choose Forgot password and enter the address you signed up with. You get an email with a link that takes you straight to the page where you set a new one. The old password stops working the moment you save the new one.
To change a password you still know, sign in and go to your account, then password. If you signed up with GitHub or Google there is no password on your account at all: you carry on signing in through them.
Where your usage and history live
Two pages, one for the summary and one for the detail.
| Your account | Plan, credits left this month, purchased credits, the date the allowance resets, your most recent API calls, your favourite tools, your API keys, and the way in to your workflows. |
| Usage | The fuller picture: what you have spent over time, by day, as far back as your plan keeps history, with what is left of the month against what it started with. |
A workflow run is recorded in two places for two reasons: the credits appear in your usage, and the run itself appears in the history under the workflow that produced it. How workflows work covers that.
Subscriptions and credits
ToolForte Pro is a subscription. Extra credits are a one-off purchase. They are separate things and you can have either without the other.
Subscribing
Start from pricing or from the plan card on your account page. Payment is handled by Stripe; we never see your card details.
Managing or cancelling
Your account page has a Manage subscription button that opens the Stripe billing portal, where you can change your payment method, download invoices, or cancel. There are no contracts: cancel whenever you like and you keep the plan until the end of the period you already paid for. After that your account carries on as a free one, and any credits you bought separately stay on it.
Buying credits
You can buy credits from your account page without subscribing to anything, and switch on an automatic top up if you would rather not think about running out. Credits and plans has the prices.
API keys
Created, shown once, revoked when you no longer trust them.
The API keys card on your account creates a key and shows it once. We store a hash rather than the key itself, so we cannot show it to you again and neither can anyone who reaches our database. Copy it into your password manager or your server configuration straight away; if you lose it, revoke it and make another.
Keys start with tf_. Use a separate one per app or server so that revoking a key that leaked does not take everything else down with it. Revoking is immediate. API and MCP shows how to use one.
Closing your account
A button on your own account page, not an email to us. It runs immediately and it cannot be undone.
Your account, then delete your account. That page lists what is on the account, counted from the database rather than described in general terms, and asks you to type your email address before the button does anything. Reading it and leaving changes nothing.
What happens, in order
If you have a subscription it is cancelled with Stripe before anything is deleted, and the deletion stops if that fails rather than leaving a subscription billing an account that no longer exists. Cancelling is immediate, so the remainder of the period you have already paid for is lost and Stripe issues no refund for it. If that matters, cancel from the billing portal first and delete the account once the period runs out. Credits you bought are forfeited in the same way.
Your data then goes in one transaction, and a check runs that looks for anything still linked to your account anywhere in the database. Only when that check comes back empty is your sign in removed. If it does not, we stop and tell you, rather than report an erasure we have not verified.
What is deleted
| Gone | Where it lived |
|---|---|
| Your email address, plan, credit balance and account settings | profiles |
| Every API key you created, and every request made with one of them | api_keys, api_usage_log |
| Everything your AI assistant stored in agent memory | agent_memory, memory_embeddings |
| Your saved workflows and their full run history, previews included | workflows, workflow_runs |
| Your favourite tools | tool_favorites |
| Your sign in credentials, including any GitHub or Google connection | auth.users |
What is kept, and why
| Kept, with your id removed | On what basis |
|---|---|
| Billing records: what you paid, what you spent it on, and when. Your user id is removed from them, so they no longer point at you. | Bookkeeping law requires a financial record to be kept for 7 years, so this is the one thing we cannot delete on request. The GDPR says the same: the right to erasure does not cover data we are legally obliged to retain. |
| Usage and traffic counts. Your user id and API key id are removed from them. | These rows never held an IP address or a browser string, and once the identifiers are gone they are aggregate numbers rather than data about you. Deleting them would corrupt historical totals without making you any more anonymous than removing the identifier already does. |
| Stripe's own record of any payment you made, including the invoices and the email address on them. | Stripe processes payments for us and keeps its own books for the same 7 year reason. We cancel your subscription and stop being able to charge you, but we cannot erase an invoice from their ledger, and we would rather say so than imply otherwise. |
The same list is on the privacy policy, because both pages render it from the same place in the code rather than describing it twice.
All 341 tools keep working afterwards, because they never needed an account in the first place. If something goes wrong halfway, the page says which step stopped and what state your account is in; write to us from the contact page and we will finish it by hand.