Cookie Policy
How ERP•AI uses cookies, browser storage and similar technologies on its websites and apps, and how you control them.
On this page
Who we are and what this policy covers
This policy is published by ERP•AI US Inc., 2 Embarcadero Center, San Francisco, CA 94111, USA (“ERP•AI”, “we”, “us”). It covers:
- www.erp.ai (erp.ai redirects there), including its contact form at hi.erp.ai, and erpai.studio, our staging copy of www.erp.ai;
- protoagent.ai and proto.erp.ai, the websites for Proto;
- apps.erp.ai, the web app of the ERP•AI platform, including the cookies ERP•AI sets in Published Apps; and
- build.host, including the script build.host adds to the sites it hosts.
It does not cover the Proto desktop app, cookies and tools that Customers add to their own Published Apps or Hosted Content, our status page at status.erp.ai (run by Better Stack), or third-party websites. Our Privacy Policy covers the Proto app and explains how we use the data, international transfers and your rights. Capitalized terms such as Customer, Published App and Hosted Content have the meanings in our Terms of Service.
What these technologies are
Cookies are small files a website stores in your browser. Local storage keeps data until it is deleted; session storage ends when you close the tab. Tags and pixels are scripts that send details of your visit to us or a vendor. Lifetimes below run from when an item is last set or renewed.
Server logs. Our servers also log each request (IP address, browser, page, referring page and time) to run and secure the sites and apps, and our in-house tools produce traffic statistics from the logs of www.erp.ai, apps.erp.ai and build.host. This uses no cookies or browser storage and does not depend on your cookie choices.
Categories and consent
| Category | What it does | Your choice |
|---|---|---|
| Essential | Security, sign-in, remembering your cookie choice and settings, and features you ask for | Always on |
| Enhanced Features | Remembers preferences on our marketing sites, such as your theme | Optional |
| Performance & Analytics (“Analytics Cookies” on proto.erp.ai) | Measures visits and use so we can improve the sites | Optional |
| Personalized Advertising (loads a tool only on www.erp.ai) | Lets X measure our ads and use your visit to choose the ads it shows you on X | Optional |
| Third-party content | Images, fonts, forms, videos and file viewers fetched from another company, which receives your IP address and browser details; video players may set their own cookies | No switch; listed below with when each loads |
Banners and defaults. On www.erp.ai, erpai.studio, protoagent.ai and proto.erp.ai, every visitor sees a banner with Reject, Customize Settings and Accept All, and each site keeps its own choice. On www.erp.ai and erpai.studio, optional categories stay off until you turn them on. On protoagent.ai and proto.erp.ai, Customize Settings shows Enhanced Features switched on, and saving keeps it on unless you switch it off. Reject turns every optional category off. apps.erp.ai and build.host show no banner, because they set only Essential cookies and storage of their own.
Legal basis. Optional categories rely on your consent. We set Essential items without asking, because they are needed to run or secure the site, to remember a choice or setting, or to provide something you ask for; a setting you choose inside apps.erp.ai or build.host, such as a theme, is Essential. For third-party content we rely on our legitimate interest in showing the page, or on your request when you open the content.
How long data is kept. The data a tool collects is kept apart from its cookies. Google Analytics and PostHog keep event data for the retention period we set in each service, chosen by how long we need to compare traffic over time, and then delete it. X keeps what it receives under its own privacy policy. Server logs are kept as the Privacy Policy explains.
ERP•AI website and staging site
Before you choose, www.erp.ai and erpai.studio set no cookies of their own, Google Consent Mode is set to “denied” for analytics and advertising, and Google Tag Manager, PostHog and the X Pixel are not loaded. Only the Essential items marked “Yes” below are stored before a choice. The contact form, images and Cloudflare also load before a choice.
| Name or vendor | Purpose | Category | Before consent? | Lifetime |
|---|---|---|---|---|
cookie_consent (cookie) |
Remembers your choice | Essential | Set when you choose | 365 days |
erpai-proto-film-popup:v1 (local storage) |
Records that the Proto popup was shown or minimized, so it does not open on every page; holds no identifier and is not sent to us | Essential | Yes: when the popup first opens by itself on a large screen, or when you minimize it | Until cleared |
erpai-proto-install-session (session storage) |
Remembers the state of the Proto installer prompt | Essential | Yes, when you use it | Until the tab closes |
proto-download:<system>:<platform> (session storage) and a download code |
When you ask to download Proto for an app on our site, our download service puts a random code in the installer’s file name or in a link that opens Proto, so Proto can set up that app, and logs your IP address and browser | Essential | Only when you ask for a download | Session storage until the tab closes; the code for a limited setup period |
erpai-theme, erpai-theme-dark-at (cookie and local storage) |
Remember your theme; an explicit dark choice lapses after 6 hours. Without consent, a theme change lasts only for the page | Enhanced Features | No | Cookie 365 days; storage until cleared |
Google Tag Manager (GTM-M3XZN5RC) and Google Analytics 4 (Google), _ga, _ga_<ID> |
Tag Manager loads the Google Analytics tag, which counts visits and measures pages and clicks | Performance & Analytics | No | 2 years from your last visit |
PostHog (PostHog, Inc., US Cloud), ph_<project key>_posthog (cookie and local storage) |
Product analytics: records the conversion clicks we define (such as sign-up and download links) and script errors and, depending on our PostHog settings, may also record other interactions automatically and how you move through a page | Performance & Analytics | No | Cookie up to 1 year; storage until cleared |
X Pixel (X Corp.; in the EU, the EFTA States and the UK, the X company named in X’s privacy policy), _twpid, _twclid, _twsid and cookies on X’s domains |
Sends X the pages you visit, your IP address and X cookie identifiers so X can measure visits and sign-ups from our ads. X can link this to your X account and uses it under its own privacy policy, including to choose which ads it shows you | Personalized Advertising | No | Set by X; see How cookies are used on X |
| Tally form at hi.erp.ai, on www.erp.ai/contact | The contact form. Tally and the services it uses receive your IP address and browser details: Google Fonts, the Sentry error-monitoring service, and GitHub, which hosts email-domain lists the form checks | Third-party content | Loads with the contact page | Under Tally’s policy |
hi.erp.ai form opened in its own tab: erpai_tally_analytics_v1 (local storage) and Google Analytics cookies prefixed tally_direct |
The first stores your analytics choice for that page; the others measure use of it | Essential; Performance & Analytics | Choice when you make it; analytics only if you allow it there | 180 days; 2 years from your last visit |
| Unsplash | Serves images on our pages | Third-party content | Loads with the page; sets no cookie | Not applicable |
| Cloudflare | Delivers and protects the sites, and asks your browser to report failed connections to Cloudflare (Network Error Logging) | Essential | Yes. Cloudflare may also set a security cookie such as __cf_bm to detect automated traffic |
Error-reporting instruction 7 days; __cf_bm 30 minutes |
Google Analytics and PostHog cookies may be set for all of erp.ai, so your browser may also send them to other erp.ai addresses.
Proto setup steps. If you download Proto from an app page on our site, Proto sends us the download code with your setup steps (such as sign-in completed and first task completed), so we can measure which pages lead to installs. The cookie banner does not control this, because it happens in the Proto app. We rely on our legitimate interests, you can object as the Privacy Policy explains, and we keep these records only as long as that measurement needs them.
Google Tag Manager. On our sites, Google Tag Manager runs only the Google Analytics tag.
Who is responsible for the X Pixel. ERP•AI and X are jointly responsible under the GDPR for collecting data through the X Pixel on www.erp.ai and sending it to X. We are responsible for asking your consent and for this notice; X is responsible for what it does with the data afterwards, as its privacy policy explains. You can exercise your rights with either of us.
erpai.studio works the same way, except that it loads no X Pixel, its contact page does not embed the Tally form, its security policy blocks a Cloudflare Web Analytics beacon, and its CRM implementation starter saves what you type in local storage as erpai.crm-implementation-draft.v1 (Essential, until you clear or replace it).
Proto websites
protoagent.ai and proto.erp.ai have their own banner and consent cookie, and set no cookies or browser storage of their own before you choose. protoagent.ai loads no analytics tools. proto.erp.ai loads Google Analytics and PostHog only after you turn on “Analytics Cookies”.
| Name or vendor | Purpose | Category | Before consent? | Lifetime |
|---|---|---|---|---|
web_proto_cookie_consent (cookie) |
Remembers your choice | Essential | Set when you choose | 365 days |
erpai-theme, erpai-theme-dark-at (cookie and local storage) |
Remember your theme | Enhanced Features | No | Cookie 365 days; storage until cleared |
proto-hero-video (local storage) |
Avoids repeating the same homepage clip | Enhanced Features | No | Until cleared |
Google Analytics 4 (Google), proto_ga, proto_ga_<ID> (proto.erp.ai only) |
Counts visits and measures use. Set only for proto.erp.ai, with Google signals and ad personalization turned off | Performance & Analytics | No | 2 years from your last visit |
PostHog (PostHog, Inc., US Cloud), ph_<project key>_posthog in local storage (proto.erp.ai only) |
Product analytics; automatic click capture, session recording and surveys are off | Performance & Analytics | No | Until you withdraw consent or clear it |
| Tally (Contact sales form) | protoagent.ai loads Tally’s embed script on pages with the Contact sales button, and the form when you open it. proto.erp.ai loads the full form, with Google Fonts, Sentry and GitHub, when its home page opens | Third-party content | Yes, as described | Under Tally’s policy |
| Cloudflare | As for www.erp.ai | Essential | Yes | As for www.erp.ai |
ERP•AI platform
The platform web app at apps.erp.ai loads no analytics or advertising tools.
| Name or vendor | Purpose | Category | When set | Lifetime |
|---|---|---|---|---|
Session cookies better-auth.session_token and better-auth.session_data (which may carry a __Secure- prefix) |
Keep you signed in; the second briefly caches session details | Essential | When you sign in | Up to 30 days, extended as you use the app (your organization may set a shorter limit); cache 5 minutes |
| Sign-in state cookie | Protects sign-in with Google or your company’s single sign-on against forged requests | Essential | When you start such a sign-in | Up to 15 minutes |
| Two-factor and passkey cookies | Hold a challenge during two-factor or passkey sign-in and, where offered, remember a trusted device | Essential | Only when you use them | Minutes; a trusted device for the limited period our sign-in service sets |
| Local and session storage | For example theme and layout preferences, unsent drafts, checkout and connector sign-in state, and notices such as a sign-out after inactivity | Essential | While you use the app | Local storage until cleared; session storage until the tab closes |
| Tally (Contact sales in Billing) | Sends what you enter, and the page you sent it from, to Tally (through hi.erp.ai if Tally cannot be reached directly), with a random respondent ID kept in local storage (erpai:contact-sales-respondent) that groups your repeat requests |
Essential | When you submit the form | Respondent ID until cleared |
| Google sign-in | “Continue with Google” sends you to Google, which uses its own cookies | Essential | Only if you use it | Set by Google |
Stripe (Stripe.js), cookies such as __stripe_mid and __stripe_sid |
Processes Credit purchases and saved cards for auto top-up, and helps prevent fraud; Stripe also uses this data as its own controller for fraud prevention (stripe.com/privacy) | Essential | When you open checkout or add a card | About 1 year; 30 minutes |
| Google Fonts | Loads fonts for app themes and the page editor | Third-party content | When a page uses one of these fonts; sets no cookie | Not applicable |
| Videos, web pages and Office files added to a knowledge base | Shown in a frame from the source: the YouTube, Vimeo or Loom player, the linked website, or, for Excel and PowerPoint files, Microsoft’s Office viewer, which receives a link to the file and fetches it | Third-party content | Only when you open such an item | Set by the provider |
| Cloudflare | As for www.erp.ai | Essential | Yes | As for www.erp.ai |
Published Apps. People who sign in to a Customer’s Published App get Essential session cookies from the same sign-in service, set on the app’s domain until they sign out or the session expires. Published App sign-in pages may use hCaptcha bot checks, which receive browser signals and your IP address, and apps served from build.host’s shared servers may carry the build.host script described below. Customers are responsible for the cookies and tools that their own code or embedded content adds.
build.host
build.host loads no analytics or advertising tools.
| Name or vendor | Purpose | Category | When set | Lifetime |
|---|---|---|---|---|
| Session cookies from the ERP•AI sign-in service, relayed through build.host | Keep you signed in | Essential | When you sign in | Until you sign out or the session expires |
bh_console_sess (cookie) |
Session for a landing-page console the site no longer shows. If the console is used, what you type is sent to an AI model provider (OpenRouter) | Essential | Only if the console is used | 30 minutes |
Local and session storage keys starting build-host. or bh- |
Remember your theme, save your design work on your device, prevent a reload loop after a release and keep a design launch in progress | Essential | When you use these features, or when needed | Local storage until cleared; session storage until the tab closes |
| Cloudflare Turnstile | Checks that sign-ins come from a person; Cloudflare receives your IP address and browser signals | Essential | When you sign in by email | Set by Cloudflare |
| Google Fonts | Loads fonts | Third-party content | With every page; sets no cookie | Not applicable |
| Cloudflare | Delivers build.host itself (not hosted sites) and asks your browser to report failed connections | Essential | With every page | As for www.erp.ai |
Sites hosted on build.host. Sites on *.build.host and custom domains are Hosted Content: the Customer that deploys a site decides its cookies and is responsible for its notices and consent. build.host adds its own script, /__build_host/attribution/v2/proto-attribution.js, to every HTML page of every hosted site, whether or not the badge is on, and Customers cannot remove it. The script sets no cookies and no local or session storage, and it does not collect or send identifiers, events or page content. If the site’s “Made with PROTO” badge is on, it shows the badge, which links to proto.erp.ai with campaign (UTM) parameters. Loading the script reveals your IP address, browser details and the site’s address to our servers, which log those requests. Every site uploaded from Proto also loads a copy of the script from build.host through Cloudflare, from a tag in its index.html, and that copy asks build.host for the badge setting, so Cloudflare and build.host also receive the site’s hostname and your IP address. Customers can turn the badge off, for example through the build.host API.
Your choices
Change or withdraw consent with the cookie settings in the site footer (“Cookie Preferences” on www.erp.ai and erpai.studio, “Cookie preferences” on protoagent.ai, “Cookie settings” on proto.erp.ai). Withdrawing is as easy as consenting and does not affect earlier use. When you turn a category off, we delete the Google Analytics, PostHog and X cookies and storage we can reach and reload the page; cookies on Google’s or X’s own domains can be deleted only in your browser. On the hi.erp.ai form page, use “Analytics preferences” below the form.
Browser and vendor controls. You can block or delete cookies in your browser; blocking Essential cookies breaks sign-in. Google offers a Google Analytics opt-out browser add-on. To stop X using your activity on other websites to personalize ads, turn off “Personalized ads” in your X Ads preferences (X’s instructions).
Global Privacy Control, Do Not Track and US state laws
Global Privacy Control (GPC). If your browser sends a GPC signal, www.erp.ai, erpai.studio, protoagent.ai and proto.erp.ai treat it as a refusal of Personalized Advertising for that browser, even if you allowed it before. On www.erp.ai this means the X Pixel does not load. protoagent.ai and proto.erp.ai have no advertising category, and apps.erp.ai and build.host load no advertising tools. GPC does not change your other cookie choices.
Do Not Track. There is no common standard for Do Not Track signals, so we do not respond to them; we honor GPC instead.
California and other US states. When Personalized Advertising is on, giving data to X through the X Pixel may count as a “sale” and as “sharing” for cross-context behavioral advertising under California law, so we treat it as both. One opt-out covers both, and also covers targeted advertising under other US state laws. Personalized Advertising is off unless you turn it on, and you can opt out at any time in the footer cookie settings, with GPC, or by emailing legal@erp.ai. The X Pixel is the only advertising tool that runs on our sites. We do not sell or share personal information linked to ERP•AI accounts, and we do not sell personal information for money.
Changes to this policy
We update this policy and its date when our cookies, storage or vendors change, and we list any new tool here before we use it. Before we add a vendor or a purpose to an optional category, we will ask for your consent again.
Contact
Write to legal@erp.ai, or ERP•AI US Inc., Attn: Legal, 2 Embarcadero Center, San Francisco, CA 94111, USA. Account help: care@erp.ai.