Apprentice
GuidesBenchmarkPrompt optimizationAlternativesPricingDocsStart free

Privacy policy

Last updated 19 October 2026

Contents

  • The short version
  • Which providers do you use?
  • What do you collect?
  • Does Apprentice train on my data?
  • How do you use my data?
  • Who else handles my data?
  • Do you use cookies?
  • How long do you keep my data?
  • How do I delete my data?
  • How do you protect my data?
  • Is there a minimum age?
  • Can this policy change?
  • How do I contact you?

Apprentice uses your data only to run the jobs you start. We never train models for anyone else on it and never sell it. We share it only with the providers that run your jobs, and they may use it only for that. Delete a task and its rows, jobs, models and files go with it.

The SDK can remove personal data on your machine before anything is sent. With --local, optimizing and training run on your own machine with your own model key, and that data never reaches Apprentice.

Apprentice operates runapprentice.com. This policy covers the website, the console, the API, and data the open-source plugin sends only after you agree to capture.

The plugin's own code is licensed separately, in its repository. Questions go to abhishek@runapprentice.com.

The short version#Link to this section

  • The main skill sends no code and no prompts.
  • Capture runs only after you say yes.
  • Local training keeps your rows on your machine.
  • We use no advertising or analytics trackers.
  • We do not sell your data.
  • We never use your prompts, rows, or captured calls to train a model for anyone else.

1. Which providers do you use?#Link to this section

We use a small set of providers for hosting, storage, sign-in, AI models, email and error reports. Each may use your data only to run Apprentice. Full subprocessor list available on request during security review.

2. What do you collect?#Link to this section

What you give us#Link to this section

When you create an account, we keep your email address and display name. You can sign in with a third-party account, or with a six-digit code we email you.

A task holds the name, the metric, the starting prompt, and any review instructions. Rows hold the input, any structured fields, the output, the tier, where the row came from, the model name, latency, token counts, and an error if the call failed. Feedback is a score and a note. Source files are kept as text. We also keep prompt versions, run reports, review notes, and verdicts. A verdict records the reviewer's email.

If you invite someone to review a task, we keep their email and what they are allowed to do. They see the rows and notes. They see the prompt only if you turn that on. You can see their email addresses.

When you create an API key, we show the full key once. After that we keep its name, a short prefix, and when it was created, last used, and revoked. We do not keep the full key.

The pilot form keeps your work email, a name taken from that email, the page that referred you, your browser, and the time you sent it. An application for hosted training also keeps your company name if you give one, the task type, your description of the task, the model you use now, about how many requests a month, about how many examples a person has checked, and whether your team could pay if the result meets an agreed target.

If you email us, we keep that correspondence so we can reply and follow up.

What we collect as you use the site#Link to this section

A cookie keeps you signed in. Your browser also stores the last sign-in method, your name, your avatar, and your theme. Those stay on the device after you sign out.

We use an IP address briefly to limit repeated requests to public forms and invites. We do not save it with the submission.

We store the time of the actions above, such as when a row was added or a key was used.

When error monitoring is on, a report can include your account email. It does not include the request body or the prompt.

What the plugin sends#Link to this section

The main skill does not send your code or your prompts. The capture skill sends the input and output of a call only after you give an explicit yes. The call is a line you can see in your own code, such as client.capture. Delete that line and capture stops.

If Apprentice cannot be reached, capture does not interrupt your app. That call is not recorded. If you point the SDK at another address, this policy covers only what reaches Apprentice.

Training you run on your own machine keeps the rows there. We do not receive those rows. A prompt optimization you run locally stays on your machine, and it is not added to your run history here.

Do not send passwords, payment card numbers, health details, or government ID numbers. We do not scan what you upload for those.

3. Does Apprentice train on my data?#Link to this section

  • We do not sell your data.
  • We do not use advertising or analytics trackers.
  • We do not capture a call unless you have said yes.
  • The main skill sends us nothing.
  • We never use your prompts, rows, or captured calls to train a model for anyone else.

4. How do you use my data?#Link to this section

We use what we hold to run your account and your tasks, and to show scores and history.

When you optimize a prompt or draft examples on our service, we send the prompt, the examples, or the source text to an AI model provider so it can do that work.

We email a sign-in code, a confirmation when you send a form, and an invite when you ask us to invite a reviewer. We reply when you write to us. We limit repeated requests to public forms and invites.

We use error reports to diagnose failures. Those reports leave out request bodies and prompt text. A report can include the account email.

5. Who else handles my data?#Link to this section

Companies that host the site, store the database, deliver email, monitor errors, and provide the AI models we call receive only what they need to do that work.

People you invite to a task can see its rows and notes, and the prompt if you allow it. You can see their email addresses.

We may disclose information if the law requires it. If the service is transferred, the data goes with it. We do not sell personal data, and we do not share it with advertising networks.

6. Do you use cookies?#Link to this section

We set a session cookie so you stay signed in. We do not set tracking cookies. Your browser keeps the last sign-in method, your name, your avatar, and your theme on the device after you sign out.

7. How long do you keep my data?#Link to this section

We keep what you store until you delete it, or until you ask us to delete it.

Deleting a task removes its rows, notes, verdicts, prompts, files, jobs, models, and reviewers. A revoked API key stays listed as revoked. Deleting a note clears its text. Messages you send through the public forms stay until you ask us to delete them.

8. How do I delete my data?#Link to this section

You can do most of this yourself. The rest is an email to us.

Where each kind of data lives, and how you remove it.
DataWhere you see itHow to delete
TasksIn the consoleDelete the task. That removes its rows, notes, prompts, files, and reviewers.
Dataset rowsOn the taskDelete the row. Deleting a human-verified gold row asks you to confirm. You can download the rows as a CSV first.
Review notesOn the rowThe author or the task owner can delete the note. That clears its text.
API keysAccount settingsRevoke the key. It stays marked revoked.
Reviewer accessThe task's reviewersEnd their access.
CaptureThe capture line in your codeDelete the line. Capture stops.
AccountThe consoleThere is no delete button. Email us and we will delete the account. Signing out only ends the session.
Form messagesNot shown in the consoleEmail us and we will delete them.

You can also ask for a copy of your data, or a correction. Removing the capture line withdraws consent for new calls. We may ask you to confirm it is you. We answer within the time the law requires. You can complain to the Data Protection Board of India, or to a regulator where you live.

9. How do you protect my data?#Link to this section

We use reasonable measures to protect what we hold. No transmission over the internet is perfectly secure. We show an API key in full only once, and we do not keep the full key.

10. Is there a minimum age?#Link to this section

Apprentice is for people 18 and older. We do not knowingly collect information from anyone younger. If you believe we have, write to us and we will delete it.

11. Can this policy change?#Link to this section

When we update this policy, we change the date at the top. If a change affects how we handle your data, we will tell you at least 30 days before it takes effect, by email or in the product. If you keep using Apprentice after that, you accept the change. A change does not apply to a dispute that has already started.

12. How do I contact you?#Link to this section

Apprentice. Email abhishek@runapprentice.com. The terms cover use of the service. Support is the same address.

Apprentice
abhishek@runapprentice.com
PrivacyTermsSecuritySupport