Who we are
- Operator
- Schmade Studio (schmade.com)
- Product
- Meerkat
- Contact
- lateisha@schmade.com
- Address
- Schmade Studio, Richmond, Virginia, USA
The short version
You give Meerkat a rough ask or an existing prompt. Meerkat sends it to AI models from Anthropic, OpenAI, and Google to draft, test, and critique a better prompt, and saves the result on your shelf so you can find it again. We keep usage records to run the service and to learn what works. We do not train AI models on your prompts, we do not sell data, and we do not run advertising trackers. You can ask us for a copy of what we hold about you, and ask us to delete it.
What we collect
Account information. Your email address, and the name you give when you sign up. If you sign in with Google, our sign-in provider also keeps the name and profile picture Google shares. You can sign in with a magic link, with an email and password, or with Google. If you set a password, our sign-in provider stores it as a one-way hash; we never see it.
Your prompts and conversations. Everything you type into Meerkat, every draft it produces, and every prompt you paste for sharpening or roasting. On the web app and through the connector, each conversation is saved automatically to your shelf with its full transcript, and each change to a prompt keeps an earlier version so you can go back. Files you attach are sent to the models with your message and can be saved as part of the conversation. If you use the demo without an account, the conversation stays in your browser, not on our servers. Free accounts hold ten saved prompts at a time; archiving one makes room.
Usage records. For each action we log what happened: the type of action (build, sharpen, roast, save, search, copy), the surface (web, Claude, ChatGPT), the models used, token counts, timing, cost, and outcome signals such as whether you copied, kept, edited, reran, or preferred the original. On the web app, the record for a message also keeps a short excerpt of what you typed, up to 160 characters, with any pasted prompt replaced by a placeholder, and records keep the title of the draft Meerkat made. Connector records keep lengths and titles, not what you wrote. Where a record refers to a specific prompt, such as a preference between the original and a rewrite, it stores a cryptographic hash of the text, not the text.
Model drafts behind the scenes. When Meerkat runs its three-model panel, it keeps each model's draft next to the merged draft so we can check whether the panel is earning its cost. This applies to demo use without an account too. These are deleted after 30 days.
Test results. When Meerkat proves a draft by running it, you see the test input, each model's output, and the judge's verdict, tied to a hash of the exact prompt text tested; on the web these results are not saved on our servers. Red-team and head-to-head tests keep the prompts, inputs, outputs, and verdicts in a job record that is cleared after about an hour. When you run a prompt in the test drawer, we keep the prompt, the input, and the model's output, including for demo use without an account.
Learning about your briefs. When Meerkat critiques a prompt, it records the grade and the categories of what was missing (for example “audience” or “format”), not your text. On paid plans these patterns personalize what Meerkat checks for. This is on by default and you can turn it off (see section 10).
Roast pages. A roast creates a page at an unguessable link. Until you share it, the page is unlisted: it is not indexed or listed anywhere, but anyone who has the link can open it. Clicking share makes it public and lets search engines index it. Roasts you start on the Roast page come with a removal link that works without an account; removing a page takes it offline for everyone. Roasts made through the connector or inside the workspace have no removal link; email us and we will remove them. The prompt and the roast stay in our database after a page is removed, until you ask us to delete them.
Anonymous Roast use. The free Roast works without an account. We never store your IP address. We store a one-way hash of it with each roast to enforce limits of five roasts per hour for everyone and ten per day without an account. That hash is kept with the roast record.
Billing. If you pay, Stripe handles your card. We never see or store card numbers. We send Stripe your email address and your Meerkat account ID, and we keep your plan, subscription status, Stripe customer ID, and run-pack purchases.
Email. We keep a record of the emails we send you, such as sign-in links, plan notices, team invitations, and occasional product emails about your account, and a suppression list so that if you unsubscribe or ask us to stop, we stop.
Messages you send us. If you use the contact form, we keep your name, email address, message, the page you sent it from, and your browser's user agent.
Analytics and cookies. Page views and performance through Vercel Analytics and Speed Insights, which do not identify you. We also count visits ourselves: each visit record keeps the page, the site you came from, and a visitor ID made by hashing your IP address and browser with a value that changes every day, so it cannot follow you from one day to the next. When you are signed in, product events are linked to your account. We set one first-party cookie that groups the actions of a single browser session. No advertising pixels, no cross-site trackers.
Web lookups. When Meerkat searches the web or reads a link you give it, the search query or link goes to our search provider, Tavily.
What we do with it
- Draft, sharpen, test, and roast prompts, which is the service.
- Keep your shelf and your projects so you can find your work again. Meerkat can also file a prompt into one of your projects automatically.
- Personalize suggestions on paid plans. Meerkat notices patterns in what your briefs tend to leave out and treats them as things to check, never as facts to fill in.
- Run the service: enforce plan limits, prevent abuse, fix bugs, and understand cost.
- Improve Meerkat. We study usage records, and we review samples of stored conversations and prompts, sometimes by running them through the same AI models under the same terms, to see what makes prompts work. This never involves training a model on your prompts. We never use the text of a private prompt in public; we may link to a roast page you chose to make public.
- Bill you, if you pay.
- Answer you, if you write.
Who receives your data
We use a small number of providers. Each receives only what it needs.
- AI model providers
- Your ask, your prompt, the conversation, and the context you give Meerkat go to the models that draft, test, and judge: models from Anthropic, OpenAI, and Google, routed through Vercel's AI Gateway. More than one provider can see the same message, because Meerkat drafts with several models at once. Each processes the text under its own API terms, which do not use API inputs for training by default. We do not send your email or account details to them.
- Vercel
- Hosting, the AI Gateway, anonymous analytics, and short-lived request logs.
- Supabase
- Accounts, sign-in, and the database that holds your shelf, projects, usage records, and test results.
- Stripe
- Payments. Receives your email address and Meerkat account ID.
- Resend
- Email delivery. Receives your email address and the message.
- Tavily
- Web search and link reading, when Meerkat looks something up.
- Only if you choose to sign in with Google.
- Anthropic and OpenAI as platforms
- If you use Meerkat inside Claude or ChatGPT, that platform sees the tool calls and results as part of your conversation there, under its own privacy policy. Section 06 covers exactly what passes each way.
We do not sell personal data. We do not share it with advertisers. We share it with authorities only if legally required, and we will tell you if we are allowed to.
Meerkat inside Claude or ChatGPT
The connector uses OAuth. You sign in to Meerkat once, and Claude or ChatGPT receives a scoped token that lets it call Meerkat's tools on your behalf. To revoke it, disconnect Meerkat in Claude's or ChatGPT's connector settings, or email us and we will end every connection to your account. Signing out of the Meerkat website does not revoke it.
Meerkat receives only what the platform sends to a tool. It never receives your full conversation with Claude or ChatGPT, and it does not reconstruct chat logs from tool calls. When Chat with Meerkat or Sharpen a prompt produces a draft, Meerkat saves the messages it received for that call and its reply to your shelf.
The six tools, and what each one sends and stores:
| Tool | What Meerkat receives | What Meerkat returns | What Meerkat stores |
|---|---|---|---|
| Chat with Meerkat | The messages about the prompt that Claude or ChatGPT sends: your latest message and any earlier turns it includes | Meerkat's reply, the current draft or one clarifying question, follow-up suggestions, and a title | When a draft is produced, the messages received and the reply on your shelf, with version history; the panel's drafts for 30 days; a usage record with lengths, the draft's title, and timing |
| Sharpen a prompt | The prompt you want improved, and any notes | The sharpened prompt, a critique of what changed, follow-up suggestions, and a title | The prompt, your notes, and the reply on your shelf, with version history; the panel's drafts for 30 days; a usage record with lengths, the title, and timing |
| Roast a prompt | The prompt to roast | A verdict, what is missing or will break, a rebuilt version, and a link to the roast page | An unlisted roast page with the prompt and the roast (not indexed, not on your shelf), plus a usage record |
| Save to shelf | A prompt, and optionally a title, a project, and notes | The saved prompt's ID, title, project, and a link to it | The prompt, title, and notes on your shelf, plus a usage record with the title |
| Search shelf | Your search words, and optionally a project and a result limit | Matching prompts from your shelf, with their titles, text, and links | A usage record noting that a search ran. The search words are not saved in our database; they appear in our hosting provider's request logs, which are kept briefly |
| List projects | Nothing beyond your identity, and optionally a result limit | Your projects' IDs, names, and descriptions | A usage record |
Everything the connector saves to your shelf lives alongside your web work, under the same limits, and is deleted with your account. Roast pages and usage records are handled as described in section 08.
People whose public prompts we review
Meerkat sometimes reviews prompt files that people publish in public GitHub repositories. When it does, we store the repository and file link, the owner's GitHub username and public name, the email address on their public profile, and the review, and we may email the owner a short note with a link to the review. Sending that note publishes the review page. Every note carries a removal link for the page and an unsubscribe link; replying “stop” also works. If you received one and want your details deleted, email us. This outreach is paused at the time of writing.
How long we keep it
| Data | Kept until |
|---|---|
| Account information | Your account is deleted |
| Prompts, conversations, versions, projects | You permanently delete them (archiving keeps them) or your account is deleted |
| Roast pages | You remove the page or ask us to delete it. Removing a page takes it offline; the record stays until you ask us to delete it |
| Usage records | Kept with no automatic expiry today. When your account is deleted they are detached from it and kept without your account ID |
| Panel drafts behind the scenes | 30 days |
| Test results | Proof runs are not saved; red-team and head-to-head jobs about an hour; test drawer runs are kept and detached from your account if it is deleted |
| Anonymous Roast IP hash | Kept with the roast record |
| Hosting request logs | A short period set by our hosting provider |
| Billing records | Our copy until your account is deleted; Stripe keeps payment records as the law requires |
| Messages you send us | Kept, and detached from your account if it is deleted |
| Email suppression list | Indefinitely, so we keep honoring your request |
When we delete your account, we delete your account information, prompts, conversations, versions, projects, personalization data, and billing records within 30 days. Usage records, roast records, test drawer runs, outcome signals, and messages you sent us are kept without your account ID; if you want those deleted too, say so and we will delete them. Our database backups roll off within 7 days after that.
What you can do
- See and export. Download any conversation as a Markdown file from the chat. For a copy of everything we hold about you, email us and we will send it in a readable format within 30 days.
- Correct. Change your name in your account, or email us to change anything else.
- Delete. Archive prompts, or delete them permanently from the Archive view on your shelf. Remove roast pages with their removal link. To delete your whole account, email us and we will delete it within 30 days.
- Revoke the connector.Disconnect Meerkat in Claude's or ChatGPT's connector settings, or email us.
- Turn off personalization. Switch off Learning capture on your Progress page. Nothing new is recorded and Meerkat stops using the patterns it has.
- Stop email.Product emails and outreach carry an unsubscribe link, and replying “stop” works too. Sign-in links and billing notices are part of having an account.
- Object or complain. Email us. If you are in the EU, UK, or California, you also have the rights those laws give you, including the right to complain to your local authority.
Children
Meerkat is not for anyone under 16, and we do not knowingly collect their data. If you think we have, tell us and we will delete it.
Security
Data is encrypted in transit and at rest with our providers. Access to production data is limited to the operator, who can view stored prompts to give support, prevent abuse, and review quality. Test and reviewer accounts used for app store reviews are internal accounts and are excluded from usage metrics.
Changes
When this policy changes in a way that matters, we will update the date at the top and, if you have an account, tell you by email before it takes effect.
Contact
lateisha@schmade.com
Schmade Studio, Richmond, Virginia, USA