$29 a month for Pro. Free is where your account lands.

Every new account starts on a 14-day Pro trial with no card — nothing to enter, nothing to cancel. After it lapses, the account lands on the permanently free tier (one database source plus Google Sheets, three dashboards, unlimited reports and exports), so nothing gets locked away. You do need your own AI provider key on every plan, including during the trial; a Google Gemini key is free to create.

Tax is added on top. $29 is the price before tax, so if sales tax or VAT applies where you live, your card is charged more than $29. We would rather you heard that from us than from your statement. Here is how we know, so you can check it yourself: Lemon Squeezy stores this as a single switch per shop, and our live checkout reports it off — which in Lemon Squeezy's own worked example means “the price of your product will be $15 plus tax” (docs.lemonsqueezy.com/help/payments/sales-tax-vat, read 1 September 2026). What we cannot give you is the rate. Lemon Squeezy works it out from your billing address and does not publish a country-by-country table — we looked through all 145 pages of their documentation on 1 September 2026 and there is no rate list, not even for Malaysia, where we are registered. So we are not going to invent a number. If you want the exact figure before you commit anything, email contact@intellrise.com with your country and we will get it and write back. None of this touches the trial: 14 days of Pro costs nothing and asks for no card, and tax cannot apply to a charge that is not made.

Yes, and Pro does not charge per database. Pro has no cap on data sources, so three clients' Postgres databases run on one $29/month account rather than three; Free is one database plus Google Sheets, and Sheets never counts toward that limit. The condition sits with you, not with us: our Terms say you are responsible for having the right to connect and query the data sources you add. Two things to know before you commit. Everything you connect lives in one workspace — each question's schema context lists the tables and columns of every connected source, and a query can join across them. That is deliberate, because cross-source questions are the point, but it means there is no wall between one client and the next inside a single account; a client who needs strict separation needs a separate account. What that costs, since we are the ones who sent you down that road: a second account is another $29/month — there is no multi-account or agency bundle in our plans today, so two isolated clients are $58 and three are $87, and each account needs its own login and its own AI key. And we do not publish a data processing agreement today — that is true whoever the data belongs to, so if your own company's review asks for one, the answer is the same: talk to us before you connect.

Yes — all plans are bring-your-own-key (BYOK). That puts the AI bill between you and your provider: we never meter it, mark it up or resell it, and we never train on your data. What it does not do is put a ceiling on it — how far a ceiling actually holds is answered under “How much can the AI half cost me?” below. We guide you through adding a key on your first sign-in.

Intellrise never bills you for AI usage — we are not in that path at all. The question is what your provider can bill you, and for the free Gemini key we point new users at, the honest answer has a hole in it, so here is the whole thing rather than a reassuring sentence. A key has no billing of its own: Google's billing page says keys "have no independent billing settings; they inherit the tier limits and billing status of the project", and a project you create from scratch starts on the free tier — "New accounts begin on the Free Tier". Moving off it is something you have to do on purpose: "Upgrading from the Free Tier to the Paid Tier means linking a billing account and prepaying to add a minimum of $10". Run past the free limits and the rate-limit page says "exceeding any of them will trigger a rate limit error" — an error, not an invoice. All read 28 August 2026. The hole: Google does not print the sentence you actually want, which would read something like "a project with no billing account can never be charged". We looked on the pricing, billing and rate-limit pages and did not find one, so we are not going to put it in Google's mouth. And if you do enable billing and want a ceiling, know that Google has two things with confusingly similar names: an ordinary budget only emails you — "Setting an alerts-only budget doesn't automatically cap Google Cloud or Google Maps Platform usage or spending" — while a spend cap budget does stop the service, and Gemini API is on its eligible list, though the feature is in Preview. AI Studio separately offers per-project spend caps, which Google labels Experimental and warns you can overrun: long-running tasks "may incur overages beyond your project spend cap". So the truthful summary is that the ceiling is real but not guaranteed, it is set in your provider's console rather than in ours, and whatever it turns out to be, it is billed to you by them and never by us. The step-by-step guide has both branches in full.

Google AI Studio gives you a Gemini key for free, and creating one does not ask for a card. Go to aistudio.google.com/api-keys, sign in with your Google account, click "Create API key", then paste the key into Intellrise under Settings → AI Keys. If you have never used Google Cloud, that is the whole of it; if you already have a Cloud account, AI Studio asks you to import an existing project first, which adds about a minute.

We do not quote a free-tier allowance here, because Google no longer publishes one — its rate-limit page says the limits "can be viewed in Google AI Studio" (read 28 August 2026). Yours are shown in AI Studio itself.

One thing to settle before you point a free key at confidential data, because on the free tier it is your provider's terms that apply rather than ours: Google's Gemini API terms (effective 23 March 2026, read 28 August 2026) say that for Unpaid Services "Google uses the content you submit to the Services and any generated responses to provide, improve, and develop Google products and services and machine learning technologies", and the same page says "Do not submit sensitive, confidential, or personal information to the Unpaid Services." Between those two sentences Google's terms carry a third that a vendor review will ask about and that we had left out: "To help with quality and improve our products, human reviewers may read, annotate, and process your API input and output." Google says it takes steps first — "disconnecting this data from your Google Account, API key, and Cloud project before reviewers see or annotate it" — which unlinks who sent it, not what it says, so your table and column names are still in what a reviewer would read. A key on a Cloud project with an active billing account is a Paid Service, and there Google says it "doesn't use your prompts ... or responses to improve our products". The paid branch has a cost of its own, and it belongs next to the recommendation rather than in a footnote: the same terms say "For Paid Services, Google logs prompts and responses for a limited period of time", for abuse detection and any legally required disclosure. And if you are in the European Economic Area, Switzerland or the United Kingdom, Google says those paid terms apply to all Services "including Google AI Studio and unpaid quota in the Gemini API, even though they are offered free of charge" — so the free-tier caveat above does not apply to you. The same terms carry a second sentence about the EEA, in a different section, and it points the other way: under "Use Restrictions", Google says "You may use only Paid Services when making API Clients available to users in the European Economic Area, Switzerland, or the United Kingdom" (read 31 August 2026). Whether that binds a bring-your-own-key setup like this one — where the key and the Google Cloud project are yours, and our software calls Google with them — we do not have a settled answer, and we are not going to invent one. Both sentences sit in the same document at ai.google.dev/gemini-api/terms; if you are in one of those three places, read that one yourself and have whoever signs off on your vendors read it too. We never train on your data either way — this is about your provider, not us. The step-by-step guide has the sourced detail and both branches in full.

We never use your business data to train our AI models. The analysis runs on your own provider key, though, so the other half of that answer belongs to your provider: its terms decide what it does with what it receives, and free tiers often do allow training — the free AI key page quotes Google's wording for both tiers. We keep no standing copy of what you connect: PostgreSQL, MySQL and Redshift sources are attached read-only and queried in place; SQL Server, Snowflake, BigQuery and Databricks are read into memory for the session instead, and a Google Sheet is re-read from the Sheets API each session — but the rows an answer returns are saved with that message in your chat history, and again in any report or dashboard you save. Files you upload are kept in full, because a file has nowhere else to live. All of that sits in your account and you can delete it anytime. Beyond that we keep your account and your connection settings + AI key, with credentials encrypted at rest (AES-256-GCM — that is the name of the encryption standard; the point for you is that the stored password is not sitting there as readable text). Storage is only half the question, so the other half is answered plainly too: what actually reaches your AI provider is your question, your table and column names, and the SQL — not your query results. There are two exceptions: AI Semantic Schema Learning on Pro (the Pro feature that works out once what your columns actually hold, so you stop re-explaining them), which sends up to three sample rows per table when you connect or refresh a source, and a Gemini-only retry that carries up to ten rows of a result it already has. The connect guide lists every case. One caveat you should hear from us rather than work out later: names are part of what leaves, so if your tab is called "Acme Corp 2026 orders" or a column header is a client's name, then for you the names are the data. We cannot strip them, because the model needs them to write the SQL, and renaming the tab only helps if the name stays out of your questions as well, since your question text is sent too. What we send to your AI provider lists every case and what to do instead.

Yes. You keep paid access until the end of your billing period, then your account moves to the Free plan. Your saved content stays, subject to Free-plan limits.