Privacy Policy

Intent Amplifier improves the prompts you send to AI chat sites. This policy explains, in plain language and in detail, what data we handle, why, who else touches it, how long we keep it, and the choices and rights you have. It covers the Intent Amplifier browser extension, the website at intentamplifier.com, the setup pages, the dashboard, and the backend service behind them (together, the "Service"). We would rather over-explain than leave you guessing, so this page is longer than it strictly needs to be.

1. Who is responsible for your data

Intent Amplifier ("we", "us", or "our") is the party responsible for the data described here (the "data controller" under laws like the GDPR). You can reach us through the contact page for any privacy question or to exercise the rights described below.

2. The short version

• You need an account to use the amplifier in the browser extension, and you agree to this policy when you set one up. The setup pages ask you to tick one box each for this policy, the Terms of Service and the End User License Agreement. Until all three are ticked, setup goes no further and the amplifier will not write anything for you.
• Every prompt you amplify is sent to our server and to the companies that run the AI models, because that is how it gets rewritten.
• Every prompt you amplify is saved to your account's history, together with the prompt we hand back. This happens whatever the "Share anonymized data" switch says. The only way to stop it is to remove the device from your account, which also stops the amplifier working on that device.
• How long that history is kept depends on your plan. The free plan keeps seven days of it and Starter keeps thirty; Pro and Studio keep all of it. Anything past your plan's window is deleted, not just hidden. The pricing page says which window each plan has.
• "Share anonymized data" is off by default. Switching it on writes a second copy of each record to a separate store we study to improve the product. Be clear about what that means before you switch it on: that copy is kept permanently. Your plan's window does not apply to it, so it stays after your own copy has gone, and deleting your account does not delete it either. What deletion does is cut the last link between you and it. The copy carries no name, no email address and no account number, and nothing in the product depends on your switching this on.
• Memory is on unless you switch it off, on the plans that include it. It learns short facts about your situation from what you amplify. You can read, edit, or wipe it from the dashboard. On a plan that does not include Memory, your browser still builds it and still sends it with your request, but our server discards it before your prompt reaches an AI model.
• We never sell your data, and we never use your prompts to train any AI model or our expert library. No ad networks, no data brokers.
• You can download what is tied to your account, and delete your account, from the dashboard at any time.

3. Agreeing to this policy

When you set up Intent Amplifier, the setup page shows you a short summary of how your information is handled and asks you to tick one box for each of three documents: the Terms of Service, this Privacy Policy, and the End User License Agreement. All three are required. If you do not tick them, setup stops there: you cannot create an account, and the amplifier refuses to write for you. We record which version of the documents you agreed to, and when, against your account. If we change any of them in a way that matters, the amplifier asks you to agree again before it carries on.

This agreement is what lets us run the Service for you. It is separate from the optional choices in this policy (sharing anonymized data, and optional cookies on the website), which you can say no to and still use everything.

4. What the extension can access

The extension runs on the AI chat sites it supports (over 20 sites, such as Claude, ChatGPT, and Gemini) and on our own setup and dashboard pages, where it connects your browser to your account. On chat sites it reads what it needs to do its job: the text in your input box and, only if you switch on "Context scan", nearby messages in the current conversation so the amplified prompt fits the discussion. It does not read your browsing history, your other tabs, other websites, or your cookies on those sites.

When Context scan is on, the conversation text it picks up is sent to our server with your prompt, and on to the AI model companies, so the result fits the thread. We do not store that conversation text. We store only how many messages were found and which method found them.

5. The data we handle, and why

Your prompts and results. When you press Amplify, the text you wrote is sent to our server and on to the AI model companies listed in section 8, and the result comes back to you. Clarifying questions and Preview work the same way. Because the amplifier only works for an account, every amplify is saved to that account's history: the site you were on, the mode you used, the prompt you wrote, the prompt we returned, which specialism your request was routed to, the extension version, a timestamp, and whether you kept or undid the result. This is what your history page shows you.

How long we keep it. Each plan keeps a different amount of that history: seven days on the free plan, thirty days on Starter, and all of it on Pro and Studio. Records past your plan's window are deleted from our database, not merely hidden from the page, and the deleting happens when you next open your dashboard or when we run the tidy-up across all accounts. Moving to a plan with a longer window does not bring back what has already gone. If you want a copy of your history before it ages out, the dashboard's Download my data button (Settings, then Privacy) saves everything it currently holds as a file. This window governs your own history, the copy your dashboard shows you. If you switched on "Share anonymized data", the separate shared copy described below is kept permanently and none of this applies to it.

"Share anonymized data" (optional, off by default). If you switch it on in the extension, each record is also written a second time, into a separate store we look at to understand how the product is used and whether changes to it help. Three things about that second copy matter, and we would rather state them plainly than have you find them out later.

• It is kept permanently. Your own history ages out on your plan's schedule, as described just above. The shared copy is not on that clock and is not deleted when the original is. It also outlives your account: see section 11 for what deleting your account does to it.
• It carries no name, no email address, no account number and no device ID. What holds one person's shared records together is a scrambled code we work out from your account ID. The working only goes one way, so the code cannot be turned back into your account, and it is the only thing in the store that says two records came from the same person.
• "Anonymized" does not mean the text is removed. The copy still contains the prompt you wrote and the prompt we returned. If a prompt of yours holds something you would not want kept, do not switch this on, or switch it off before you write it.

Records you did not share are never copied there at all. Switching the setting off stops new copies being made; it does not reach back for copies already made, though while your account exists you can ask us to remove them (section 15).

How shared records are used. Shared records are the only prompt text we study. We use them to understand our customers better: what people bring the amplifier, what kinds of work they use it for, which AI sites they take the results to, and how that changes over time. We also use them to check whether a change to the product helped or hurt, sometimes by running them through AI models of the kind listed in section 8. A small AI model running on our own server also sorts shared records into categories, for moderation and to count what kinds of requests people make. That on-server sorting sends nothing to anyone else.

The Preview read, and your correction to it. If you use Preview, the extension shows you a sentence or two describing what it understood you to want and what it is about to ask for. That read is stored with the record, and so is your edit if you correct it. We use these to check whether the read is accurate.

Your memory. The Service can remember short, durable facts about your situation, drawn from what you amplify, so later prompts do not make you repeat yourself. How it works:

• It is on unless you switch it off in the extension settings.
• It is part of the paid plans that list it, and the pricing page says which. On a plan without it, your browser still builds it and still sends it with each request, but our server removes it before the request goes to an AI model, and the extension shows the switch as locked. It is still yours to read, edit, or wipe from the dashboard.
• Its main copy lives in your browser's extension storage. While it is on, what it holds is sent with each request, to our server and on to the AI model companies, so the result can take it into account. Summarising it into a short description of you is a separate request to an AI model.
• While your browser is connected to your account, a copy is kept on our side against your account, so it follows you to another computer.
• It is a list of facts, a few short summaries of recurring situations, and one paragraph describing you as a working persona. It is drawn from your prompts; it is not a copy of them.
• You can see every item, add one, delete one, or wipe the whole thing from the Memory tab of the dashboard. Deleting your account deletes it too.

Account details. Your email address (we send you one-time sign-in codes; there is no password), the first name you give when you sign up and your surname if you add it, a display name and profile photo if you add them, the plan you are on, a label for each browser connected to your account (such as "Chrome on Windows"), the version and date of the documents you agreed to, and anything you set up yourself: a voice, a team and its members, invites, and prompts or reactions you share with your team. If you turn on two-factor authentication, we store the secret that makes your authenticator codes work.

Setup answers. The setup pages ask how you heard about us, what you will use Intent Amplifier for, what you do for work, which AI you use most, and which plan you picked or looked at. We also record how far through setup you got and the email address you typed, even if you never entered the sign-in code. We use these answers, as counts, to decide what to work on. If you ask for our emails, we also use them to choose which emails you get, as described below.

Emails from us (optional). When you agree to these documents during setup, one more line sits beside them: "Receive emails from Lwandle", about getting better answers from AI. It starts ticked. Untick it and we send you none; nothing in the product depends on it, and agreeing to the documents does not require it. If you leave it ticked, we record that, and when, and we send Klaviyo, the service that delivers the emails, your email address, your first name and surname (so the emails can greet you by name), a topic if you picked one on an earlier version of setup, your setup answers from the lists (what you will use it for, what you do, and which AI you use most, but never anything you typed in your own words), and when you signed up. After that we tell Klaviyo three things as they happen: that the extension is installed on your account (once), that you amplified a prompt (with your plan), and that you reached your plan's limit (with the date it comes back). These never include what you typed. Which emails you get depends on these: people who have installed get emails about using it, people who have not get emails about what it is. Every email has an unsubscribe link, and unsubscribing stops the emails.

The waitlist (closed). Before Intent Amplifier was released, you could leave your email address to be told when you could create an account. Anyone can create one now, so the form is gone from the website and no new entries are being taken. We still hold the entries left while it was open: the email address, which page it was left on, and, where someone ticked the optional box for our emails, that they ticked it, when, and the topic they picked. Those addresses were also sent to Klaviyo, which asked each person to confirm before sending anything. If you left your address on the waitlist and want it removed, ask us through the contact page, or delete your account if you went on to create one, which removes it too.

Payments. Paid plans are sold by Lemon Squeezy, which acts as the seller (the "merchant of record"): it takes your card details itself, handles tax and receipts, and is the name on your card statement. We never see your full card number. When you start a checkout, we attach your account ID so the purchase goes to the right account. Lemon Squeezy then tells us about your subscription each time it changes, and we store what it sends: your billing email, your customer and subscription IDs, your plan, its status and its renewal or end date, and the full notification itself, which can include your name and the brand and last four digits of your card.

Usage counts and costs. We count how many prompts each account amplifies per day and per month, to apply your plan's limits, and we record what the AI model calls cost per account per month, in tokens and dollars. These hold counts and costs, never prompt text.

Dashboard usage. The dashboard at api.intentamplifier.com records how it is used, for everyone who uses it, so we can tell which parts of it are working. Per visit we store a random session ID, which pages and panels you opened, which elements you clicked and where on the page, how long you spent on each page, your device type, operating system, browser, screen size, and whether the device is touch-enabled. We also turn your IP address into an approximate country, region, and city through a lookup service (ipapi.co), and store the place names, not the IP address. When you are signed in, these records carry your account ID, and our staff can see them on your account's page. None of it includes anything you wrote in a prompt. The website's cookie banner does not control this; see the Cookie Policy.

The homepage demo. If you try the demo on our homepage, what you type is sent to our server and to the AI model companies to produce the result, and is not stored. It is limited per IP address to prevent abuse.

The contact form. The form on our contact page is delivered by FormSubmit (formsubmit.co), which passes your name, email, team, topic, and message to our support inbox. We keep what you send so we can help and follow up.

A random install ID and local settings. The extension stores your settings (such as your theme and toggles) and a random install ID in your browser. The ID contains nothing personal. It is how a browser is connected to your account, how fair-use limits are applied, and how a blocked install stays blocked.

Abuse prevention and moderation. If an install is used in a way that breaks the Terms of Service, we may block it. We store the install ID that was blocked, the reason, and a dated record of the decision, so a block can be reviewed and reversed rather than being a black box.

Basic technical data. Like any web service, our servers and providers process standard request information (such as IP address and browser type) as needed to deliver pages, apply rate limits, and keep the Service secure. We do not use this to track you across the web.

6. Who can see what

• You can see your own history, memory, devices, plan, and account details on the dashboard.
• Your team, if you join one, sees your email address, the prompts you deliberately share with the team, and your reactions. The team page also shows how many prompts each member amplified in the last seven days, by email, for members who share anonymized data. Teammates cannot see your history or your memory. When someone invites you to a team, your email address is stored before you have agreed to anything, so the invite can reach you.
• Our staff can open an individual account's page to support you and keep the Service safe. It shows your account details, connected devices, dashboard visits and approximate location, and your setup answers. It shows the text of your prompts only if you share anonymized data; for everyone else, the text is removed on our server before the page is sent. A moderator may read a shared prompt that was flagged for review. The separate shared store described in section 5 has no name, email or account number in it at all, so what anyone reads there is the text and not the person.

7. Our legal bases (for EEA and UK users)

Where the GDPR or UK GDPR applies, we rely on:

• Performance of a contract (the Terms of Service you agree to during setup) to run the Service you asked for: amplifying your prompts, keeping your history, running your memory, account, plan, payments, and team, and recording your agreement.
• Your consent for the three things that are genuinely optional: sharing anonymized data, our emails, and optional cookies on the website. All stay off until you turn them on, and you can turn them off at any time without losing access to anything. Withdrawing consent to data sharing stops any new record being copied to the shared store. Copies already made are kept, as section 11 explains, and while your account exists you can ask us to remove them.
• Our legitimate interests in keeping the Service secure, preventing abuse, understanding how the dashboard and setup pages are used, and deciding what to improve, balanced against your rights. You can object to these; see section 15.
• Legal obligations for payment and tax records.

8. Who else touches your data (our providers)

We use a small number of providers to run the Service. They process data to provide their part of it:

• Oracle Cloud Infrastructure hosts our backend server, which we run and administer ourselves.
• Supabase hosts our database (accounts, history, memory, teams, payment records, setup answers, dashboard usage, and moderation records) and handles email sign-in codes.
• Hugging Face runs the inference service our AI requests go through, and passes each one to one of several companies that host the AI models (for example Novita and Together AI). They receive your prompt text, and your memory and conversation context when those are on, to produce the result. We do not give them permission to use it for anything else, but each of them handles data under its own terms.
• Lemon Squeezy sells paid plans as merchant of record, processes payments, and sends us subscription updates. Its checkout window opens on our pages when you buy a plan.
• Klaviyo sends our emails to people who asked for them during setup or on the waitlist form, and holds what section 5 lists for them: email address, first name and surname, topic, setup answers, and the product moments. Never prompt text.
• Cloudflare hosts and delivers the website.
• FormSubmit delivers the contact form to our inbox.
• ipapi.co is sent the IP address of a dashboard visit, once, to turn it into an approximate country, region, and city. We store the place names it returns; we do not store the address we sent.
• Google Fonts serves the fonts the website is set in; loading a page sends a standard web request (including your IP address) as part of fetching those files.
• The email service our sign-in provider uses delivers your one-time sign-in codes.

9. What we never do

• We never sell, rent, or trade your data.
• We never use your prompts to train any AI model or our expert library.
• We never run advertising or third-party tracking on the website.
• We never read your activity on sites the extension does not support.
• We never put one person's memory into another person's prompt. The server refuses a memory sync whose stored owner does not match the signed-in account.

10. Cookies and local storage

The website sets no advertising or cross-site tracking cookies. It uses your browser's storage for practical things only: remembering your cookie choice, remembering your settings, and briefly caching content so repeat visits are faster. Optional storage runs only after you accept it in the cookie banner, and you can change that choice at any time. The dashboard keeps you signed in with a secure cookie and records its own usage as described in section 5. The full list, what each item does, and how long it lasts are on the Cookie Policy page.

11. How long we keep it

• Your prompt history is kept for as long as your plan says: seven days on the free plan, thirty on Starter, and indefinitely on Pro and Studio. Older records are deleted. All of it goes when you delete your account. This is the copy your dashboard shows you; the shared copies in the next point are separate and behave differently.
• Your memory, account details, connected devices, setup answers, dashboard usage records, and any waitlist entry left under your email address are kept while your account is open, and deleted when you delete it. A waitlist entry left by someone who never created an account is kept until they ask us to remove it.
• The shared copies, if you switched on "Share anonymized data", are kept permanently in a separate store. Your plan's window does not apply to them and deleting your account does not delete them. What deletion does is remove the code that links them to you, after which nobody, ourselves included, can work out whose they were: the code is worked out from your account ID, and once the account is gone there is nothing left to work it out from. That is also the catch worth knowing in advance. While your account still exists we can find those records, and after it is deleted we cannot. So if you want them removed, ask us through the contact page before you delete your account, not after.
• Records shared from an install that was never connected to an account cannot be deleted from the dashboard. Ask us through the contact page and we will remove them.
• Your email profile at Klaviyo, if you asked for our emails, is kept while your account is open and deleted when you delete it. If you asked on the waitlist form and never made an account, it is kept until you ask us to delete it. Unsubscribing stops the emails; to have the profile deleted without deleting your account, ask us through the contact page.
• Payment records (the subscription details and notifications from Lemon Squeezy) are kept after you delete your account, for as long as tax and accounting law requires.
• Usage counts and cost records are kept after you delete your account, as the totals we use to run the business. They never hold prompt text.
• Dashboard usage records are not deleted on a fixed schedule. Besides going with your account, we clear them in bulk from time to time.
• Moderation records are kept as long as needed to keep the Service usable, because a block that leaves no record cannot be reviewed.
• Support messages are kept only as long as needed to help you.
• Local settings and the install ID stay in your browser until you clear them or remove the extension.

All of the above is subject to short technical backups and any retention the law requires.

12. Where your data is processed

Our database is hosted in the United States. Our other providers may process data in the United States, the European Union, and elsewhere. Where data moves across borders, we rely on the providers' safeguards (such as standard contractual clauses) to protect it.

13. How we protect it

Data travels over encrypted connections (HTTPS). The database has row-level security switched on with no access policies at all, which means the public keys can read nothing; only our server, holding a service key that never leaves it, can read or write. The extension holds no passwords and no personal sign-in tokens: signing in happens on the web, and the extension is only told that a session exists. It does carry one shared access key, the same for every install, which marks requests as coming from the extension and is not tied to you. Dashboard sessions use HttpOnly cookies, so page scripts cannot read them. No system is perfectly secure, but we work to keep the attack surface small and to collect as little as possible in the first place.

14. Children's privacy

The Service is not intended for children under 13 (or under 16 in the EEA and UK), and we do not knowingly collect their data. If you believe a child has provided us data, contact us and we will remove it.

15. Your choices and rights

• Turn anonymized data sharing on or off in the extension settings. Turning it off stops new copies being written to the shared store; your prompts are still saved to your own history, which is separate and expires on your plan's schedule. Copies already shared are kept permanently; to have them removed, ask us through the contact page while your account is still open.
• Turn memory, Context scan, and Preview on or off in the same place.
• Read, edit, add to, or wipe your memory from the Memory tab of the dashboard.
• See your prompt history on the dashboard, as far back as your plan keeps it. Entries cannot be deleted one at a time; deleting your account deletes all of your own history, and anything past your plan's window is deleted for you. Anything you shared anonymously is a separate copy and is kept; see section 11.
• Remove a device from your account on the dashboard. That stops new history being recorded from it, and stops the amplifier working there. It does not delete what is already recorded.
• Download a copy of your data from the dashboard (Settings, then Privacy): your account, profile, devices, memory, and prompt history.
• Delete your account on the dashboard. This removes your profile, connected devices, prompt history, memory, shares and reactions, dashboard usage records, setup answers, waitlist entry, and your email profile at Klaviyo. Two things are not removed by it. Anything you shared through "Share anonymized data" is kept and unlinked from you rather than deleted, so ask first if you want it gone. Payment records and usage totals are kept as described in section 11.
• Unsubscribe from our emails with the link at the bottom of any of them.
• Accept, decline, or change optional website cookies through the cookie banner or the Cookie Policy.

Depending on where you live, you may also have the right to access the personal data we hold about you, to correct or delete it, to object to or restrict certain processing, to withdraw consent, and to data portability. The agreement you give during setup can be withdrawn by deleting your account; without it, the amplifier cannot be used. If you are in California, we do not sell or share your personal information as those terms are defined by the CCPA, and you can exercise your rights without being treated differently. To make any request, contact us through the contact page; we may need to verify your request. You also have the right to complain to your local data protection authority.

16. Changes and contact

If this policy changes in a way that matters, we will update the "Last updated" date above, note it on the changelog, and ask you to agree to the new version the next time you use the amplifier. Questions, or want to exercise a right? Reach us through the contact page. See also the Terms of Service, the End User License Agreement, and the Cookie Policy.