Skip to content

Legal

Privacy policy

What Runcrate collects when you use it, why, and the rights you keep over it.

Last updated 12 November 2026

Runcrate is operated by Aeonmind, LLC, a Delaware limited liability company, 2810 N Church St STE 91168, Wilmington, DE 19802, USA. Contact: hello@runcrate.ai.

01Introduction

At Runcrate, we take your privacy seriously. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our platform.

02Information we collect

We collect information that you provide directly to us, including:

  • Account information (name, email address, password)
  • Payment information (processed securely through Stripe)
  • Usage data (instance configurations, deployment logs)
  • Communications (support tickets, feedback)

If we emailed you at work about Runcrate, see how we find business contacts for where we got your details and how to opt out.

03How we use your information

We use the information we collect to:

  • Provide, maintain, and improve our services
  • Process your transactions and send related information
  • Send technical notices, updates, and support messages
  • Respond to your comments and questions
  • Monitor and analyze trends, usage, and activities

When you sign up with a work email, we check whether we wrote to someone at your company in the weeks before, so we can tell which outreach brought you. We do this because it is in our interest to know which outreach works. You can object at any time by writing to support@runcrate.ai, and we will stop matching you and remove the match.

04Data security

We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction. This includes encryption of data in transit and at rest, regular security audits, and strict access controls.

05Data retention

We retain your personal information for as long as necessary to provide our services and fulfill the purposes outlined in this Privacy Policy. When you delete your account, we will delete or anonymize your personal information within 30 days.

06Saved prompts and answers

We do not keep the prompts you send to the inference API or the answers it returns unless you ask us to. Calls you make from the dashboard Playground are kept for 30 days as your Playground history, separately from this setting. A workspace owner or manager can turn on "Save prompts and answers" for an environment. While it is on, we keep what each model call in that environment sent and what came back for 30 days, so members of the workspace can read it beside the request. Images, audio, video and API keys are never kept; where you sent a link to a file, we keep the link. A request sent with the header X-Runcrate-Log: off is not kept. You can delete one saved request, or everything an environment has saved, at any time, and turning the setting off stops saving straight away. We never use saved prompts or answers to train models.

07Your rights

You have the right to:

  • Access and receive a copy of your personal data
  • Correct inaccurate or incomplete data
  • Request deletion of your data
  • Object to or restrict processing of your data
  • Export your data in a portable format

08Cookies

A few cookies are needed for the site to work: they keep you signed in, protect sign-in and payment, and remember your cookie choice. Vercel also counts how many people visit each page, for everyone who has not refused analytics, without setting any cookie or keeping anything that identifies you: it gets the page's address, cut as below, your browser and device, and your country. What else we set depends on where you are. In the UK (which here includes Gibraltar, Jersey, Guernsey and the Isle of Man), the EU, Iceland, Liechtenstein, Norway and Switzerland, and wherever we cannot tell where you are, we ask before setting anything else: until you accept analytics, nothing for analytics is stored on your device. Everywhere else, analytics cookies are set from your first page and you can refuse them at any time. You can change your answer at any time from at the bottom of the site's pages, and withdrawing consent deletes the analytics cookies straight away.

Necessary

sb-…-auth-token
Keeps you signed in. Signing out removes it. Renewed while you use the site, up to 400 days.
sb-…-auth-token-code-verifier
Protects a Google, GitHub or Discord sign-in while it completes. Removed when sign-in finishes.
rc_next
Remembers the page to take you to once you sign in, also kept in your browser's storage. One hour.
rc_consent
Remembers your cookie choice. Six months, then we ask again.
rc_region
Ours: set only when you visit from outside the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland. It tells our pages which cookie rule applies to you, because a page cannot see your country on its own. It holds the word row and nothing about you. If you are in one of those places we do not set it, and delete it if you have it. 30 days.

Three cookies of ours (rc_src above, rc_ft and rc_lt below), set only when analytics is on for you, remember where you first came from, so we can tell which channels bring sign-ups. They hold no ID and nothing that identifies you or your browser. When you sign up, we also save where you first came from with your account, whatever you chose about cookies: the campaign tags in the link you followed, the name of the site that linked you, the page you landed on and the time. Your browser holds this in memory while you browse and sends it to us with your sign-up, so nothing is stored on your device for it. It holds no ID, name or email, we save it once and never change it, and we use it to see which channels bring sign-ups and payments, because it is in our interest to know which channels work. You can object at any time by writing to support@runcrate.ai. When analytics is on for you, the source from your cookies is also saved with your billing record at our payment provider, Stripe (accounts made before 6 November 2026 keep what was saved then). If you withdraw analytics consent after allowing it, we delete the source saved with your account, the one saved at sign-up included, and the one on your Stripe billing record, and we do not save another. If you refused analytics from the start, the source saved at sign-up stays on your account until you delete the account. Our analytics tools PostHog and DataFast keep their own records until you ask us to delete them, and the check against our outreach emails (above) is not undone by withdrawing consent.

First source

rc_src
Ours: set only when analytics is on for you (you allowed it, or you are outside the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland and have not refused it), when you arrive from another site or a campaign link. It holds where you first came from (the campaign tag in the link or the site that linked you, and the page you landed on) and the day. No ID, name or email. Once set it is not changed. If you refuse or withdraw analytics, it is deleted. 30 days.

If you open runcrate.ai from an email we sent you, the link carries a code that stands for you. Once the page has loaded, we note that code, the page and the time, so we know you opened the link. We do this only once you have allowed analytics, never before you choose and never after you refuse. It sets no cookie and stores nothing on your device, and the record holds neither your browser nor your IP address.

When analytics is on for you (you allowed it, or you are outside the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland and have not refused it), we use PostHog to see how the site and the dashboard are used (the pages you visit, what you click, how fast pages load, errors the site hits, your browser and device, approximate location from your IP address) and DataFast to see where visitors come from and which sources lead to sign-ups and payments. Both are reached through runcrate.ai itself, and every address we send them is cut to its page and campaign fields: sign-in links, invitations, tokens and anything else in a link never leave. Our own cookies record how you reached us, so we can tell which campaigns bring customers. Once you sign in, this activity is linked to your account and your workspace, and so are the payments you make, the instances you launch and the tools you connect (the API, the command line, an AI agent), whichever way you use Runcrate. When you top up, DataFast is also told your email so it can match the payment to your visit.

These are set only when analytics is on for you. In the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland that means after you accept; before that, none of them is set and DataFast is not loaded.

Analytics

ph_…_posthog
PostHog: a random ID for your browser, the current session and, once you sign in, your user ID and the workspace you are working in. The same record is kept in your browser's storage under the same name. One year.
ph_…_posthog_cpm
PostHog: the core of the record above (your browser's ID, the current session, and the page and referrer of your first visit), kept small so it always fits in a cookie. One year.
dmn_chk_…
PostHog: a test cookie that finds the right domain for the two above, set once when PostHog first loads. A few seconds.
datafast_visitor_id
DataFast: a random ID for your browser, so a visit that ends in a sign-up or a payment counts toward the source that brought you. One year.
datafast_visitor_first_seen_at
DataFast: when it first saw your browser. One year.
datafast_visitor_session_count
DataFast: how many visits it has counted from your browser. One year.
datafast_session_id
DataFast: the current visit. Ends after 30 minutes without activity.
rc_ft
Ours: how you first reached us (the campaign in the link, the site that sent you, the page you landed on). No name or email. 90 days.
rc_lt
Ours: the most recent campaign link you followed to us. 90 days.

DataFast also keeps datafast_pageview_state, the last page it counted, in your browser's storage until you close the tab, and PostHog keeps a note that you allowed it (__ph_opt_in_out_…) there. When you refuse or withdraw analytics while DataFast is running in your browser, we set datafast_ignore in your browser's storage, strictly a refusal flag with no ID, which stops that copy of DataFast, and any other open tab's, from sending anything; we remove it if you allow analytics again. If DataFast never ran in your browser, as in the UK, the EU, Iceland, Liechtenstein, Norway and Switzerland before you accept, we set nothing. Withdrawing also removes the link between your account's payments and PostHog.

If you are in the UK, the EU, Iceland, Liechtenstein, Norway or Switzerland and have not accepted analytics, or if you have refused analytics anywhere, we count visits to pages outside the dashboard and onboarding with PostHog in a cookieless mode: PostHog gets the page's address, cut as above, your IP address and your browser, and counts the visit under a code that changes every day. In this mode it does not work out your location from your IP address, stores nothing on your device and cannot follow you from one day to the next. We do not load DataFast for you.

Counting visits from the UK. If you are in the UK and haven't refused analytics, our server adds one to a daily total for the kind of place you came from: a search engine, a social site, another website, or direct. It works this out from the link you followed and the page that sent you, and from the country our hosting provider gives for your connection. We keep only the date, that source word and the total. We don't set a cookie, keep your IP address or browser details, or record anything about you as a person, and we don't use these totals for advertising. We don't count visitors outside the UK, anyone who has refused analytics, or browsers that send a Global Privacy Control signal. You can object at any time from . The totals include automated visits.

If you also allow session recordings, PostHog records how pages are used, using the storage above, with everything you type hidden and every piece of text in the dashboard hidden too (keys, secrets, terminal output, billing details). Once you sign in, we also record where the pointer moves and what it clicks outside the dashboard, sent to our heatmap service at 1price.co. Neither sets a cookie of its own.

If you allow marketing, we load Google Tag Manager, which loads Apollo's website tracker so we can see which companies visit. Apollo keeps a random ID (apolloAnonId) and a queue of page views in your browser's storage until you clear it; Tag Manager itself stores nothing.

If analytics is not on for you, the only thing we keep on your device is your cookie choice. When you follow one of our links to sign up, everything else (such as a link we sent you, and where you first came from) travels in the address of the sign-up page or in the sign-up request instead, and we record it with your new account. Separately, the email link described above is noted as the page loads, only if you have allowed analytics.

Two pages load a script from another company: sign-in and sign-up use Google reCAPTCHA to stop automated accounts, and pages that take payment use Stripe. Each may set its own cookies for security and fraud prevention, under Google's and Stripe's own privacy policies. If any of this changes, we will describe it here and move the date at the top of this page.

09Third-party services

We use third-party companies to run parts of our service, such as payments, email, analytics, compute and model serving. They get the information they need for that task. Prompts and outputs you send to the inference API are processed by third-party model providers, who handle them under their own terms.

10Changes to this policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date.

11Contact us

If you have any questions about this Privacy Policy, please contact us at support@runcrate.ai.