Privacy
What Enablement Studio collects, what it does not sell, and how to ask us to delete it.
Last updated 15 November 2026.
What we collect
- Email — only if you create an account. We use it to send one-time sign-in links (the first one also confirms a new account), a welcome note once the account is ready, and, if you ask, a password reset link.
- Password — only if you set one; signing in by email link or Google needs none. We store a slow hash of it, never the password itself.
- Google sign-in — only if you choose Continue with Google. Google tells us your email address, that Google has verified it, and the Google account number behind it. We use them only to sign you in, to link that Google account to your Studio account, and to send one welcome note. We never see your Google password, contacts, or files, and we do not share or sell what Google sends.
- Kits saved to your account — when you are signed in with a confirmed address: each kit’s source text (your paste, or the text of the files and links you added), the drafts, your edits, and the conversations with the studio’s agents; your Settings (name and workspace notes); for each model call, its tokens and what it cost, which is how your plan’s allowance is measured; and a short activity list (kit made, renamed, moved to the trash). They are stored in Cloudflare’s database, which runs the studio, and kept until you delete them. Kits in the trash are deleted for good after 30 days.
- Payments — only if you choose Plus or Pro. Stripe takes the payment on its own pages; we never see or store your card number. We keep the Stripe customer and subscription ids, your plan, its status, and its billing period, so the studio can apply your plan. Stripe’s privacy policy covers what it keeps.
- Visitor kit cookie
es_sid— an HttpOnly cookie so this browser can keep its own kits for about an hour when you are not signed in. The client never mints it. - Optional account cookie
es_aid— set after you open a sign-in link, sign in with a password, or sign in with Google, so this browser stays signed in for 30 days. With each sign-in we keep which browser and system it was (for example, Chrome on macOS) and the country Cloudflare saw, never the IP address, so Settings → Account can show where you are signed in and sign any of them out. We keep only a hash of it. - Practice answers — only when someone shares a kit’s quiz as a practice link. For each learner we keep which option they chose on their first try, tied to a random cookie
es_lrn: no name, no email, no account. A practice link and its answers are deleted 90 days after it was shared. - Online lesson answers — only when someone shares an online lesson as a link. For each learner we keep their first answer to each activity and whether they reached the end, tied to the same random cookie
es_lrn: no name, no email, no account. A lesson link and its answers are deleted 180 days after it was shared. What a learner writes in the lesson, and their progress, stay in their own browser.
What we do not do
We do not sell your email, pastes, or kits. We do not run ads against them. We do not put a learner portal or a learning-platform login on this host, and nothing here tracks a named learner. A practice link or a lesson link is one anonymous page: no sign-in, and it never records who answered.
Cookies
Only essential, first-party cookies, unless you accept more: es_sid keeps this browser’s kits for an hour, es_aid keeps you signed in for 30 days, es_lrn marks a learner on a practice or lesson link, and es_gst lives ten minutes while you sign in with Google. They are HttpOnly, SameSite=Lax, and Secure on the public host. One more, es_in, only says this browser is signed in, so the home page can offer Open the studio; it holds no account data, the page's own script reads it, and it comes and goes with es_aid. Your appearance and cookie choices stay in this browser’s localStorage, and so does a draft you start on the home page or in a door, for up to 30 minutes, so it is waiting after you sign up. It is not sent anywhere until you run it.
The newsletter form on the home page is run by MailerLite. Only if you choose Accept all in the cookie notice does MailerLite’s script load; it then keeps its own identifier (ml_guid) and a cookie that remembers it showed you the form. With Essential only it never loads.
Google Analytics, through Google Tag Manager, is the other optional one. Only if you choose Accept all does Google’s script load, and then only on the public pages (the home page, Pricing, Examples, Contact, Creator, and these policies). It sets _ga and _ga_<id>, which Google Analytics keeps for up to two years. With Essential only it never loads and neither cookie is set. Change your choice any time with Cookie settings at the bottom of the home page. If you switch to Essential only, Google’s script stops loading from the next page you open; _ga cookies it already set stay until you clear them in your browser.
The try box on the home page
When you sort your own words in the try box, our server runs the studio’s offline rules on them and sends the sorted brief back. The words are not stored, not logged, and not sent to OpenAI. Page analytics record only that a sort happened, which example or your own words, and how many actions it found.
The checks under the Role composer
The five checks under the Role composer (who, what they should do, what they do now, why, and the number to watch) run in your browser: what you write is not sent anywhere until you run it. Page analytics record only which check you tapped for a sentence starter, and when you run, how many of the five your words named.
Page analytics
We use PostHog for anonymous, cookieless page analytics. PostHog runs in the US cloud. There is no cookie and no local storage for analytics. We do not record sessions. Page text and form values are masked and never sent. We honor Do Not Track. We do not identify you, and we do not build a profile. Practice and lesson links and their results pages load no analytics at all.
On the public pages (the home page, Pricing, Examples, Contact, and these policies), Cloudflare, which already serves this site, also measures how each page loads with Cloudflare Web Analytics: the page's address, the page that sent you there, your browser and system version, and load timings. It sets no cookie and stores nothing in your browser, and Cloudflare says it discards the IP address and does not log query strings. It does not run on sign-in pages, in your account, or in the Studio.
Separately, and only if you choose Accept all in the cookie notice, the public pages load Google Analytics through Google Tag Manager (container GTM-NC8N4NQC). Google then receives the page you view, the page that sent you, your browser and device, and an approximate location from your IP address, under the _ga cookies listed above. It never loads on sign-in, confirm, reset, account, kit, practice, lesson, or results pages, nor with Essential only.
When your paste is drafted
You do not need an account to look around: the example kits and the sample data labeled EXAMPLE DATA open and run without one, and kits you make that way stay in this browser for about an hour. To run your own paste you need an account with a confirmed address. If you run a paste that is not labeled EXAMPLE DATA, the draft is sent to OpenAI so the model can write the kit. EXAMPLE DATA, Keep / Drop choices, and exports of what is already in the session never use that path. When you ask one of the studio’s agents about a kit, the kit, the text it was made from, your workspace notes, and the conversation so far are sent to OpenAI with the question, and when you ask the model to write an online lesson, the kit is sent with that request. Signed in, a draft runs in the background so closing the tab does not lose it: the request waits in Cloudflare’s database until the draft finishes, then it is deleted.
What OpenAI may do with it
Our OpenAI account shares API inputs and outputs with OpenAI, and OpenAI may use them to improve its models. That covers everything this page says is sent to OpenAI: a paste you run, a kit and the question you ask an agent about it, a page read from a scan, and a lesson the model writes. The one exception is what an AI app sends for you: see AI apps below. Do not paste anything you are not free to share. Take names, customers, and other confidential details out of anything you do paste. Drafts made with the Studio’s own rules are never sent to OpenAI: EXAMPLE DATA, a Run once your plan’s monthly model allowance is used up, or a Run when the studio drafts with its own offline rules because its AI budget for the day is spent.
Web research, only if you turn it on
Web research is off for every kit. If you turn it on for a kit (in its Sources panel), three of the studio’s agents, the Performance Consultant, the Assessment Writer, and the Practice Designer, may look up public guidance on the kind of work the kit trains before they answer: standards and the mistakes people commonly make. The model writes the searches from the kit’s role and objectives and is told never to include names or other details from your source. OpenAI’s web search tool runs them on a fixed list of public sites (government agencies, standards bodies, professional associations, and universities) and returns public pages. We keep each page’s title and link on the kit, and show them with the answer, marked “From outside your source”. Turning research off clears what it found; answers already given keep their links.
Files and links
Files you add are read on our server. We keep the text they contain with the kit, not the files themselves. A link is fetched from our server; for job boards and Google files we read the posting or the export behind the page. A scanned PDF or a picture of text has no text to read, so after you confirm the address it is sent to OpenAI to be transcribed, and the kit marks that source as read from the page images.
AI apps
You can connect an AI app, such as Claude, ChatGPT, Cursor, or Grok, to your account (the AI apps guide says how). Once you allow it, the app can see your plan and how much of your allowance is left, read your projects and kits, start Role, Call, and Critic runs, and ask a kit’s specialists a question. It cannot apply or reject changes, rename, move, or delete anything, or reach your account, billing, or sign-in settings.
What an app sends us is handled like what you paste on the site: a kit it starts is saved to your library and kept until you delete it. When it asks a kit’s specialist a question, the question and the answer are kept with that kit, as yours are, marked with the app’s name. Only if you tick the box when you connect are the words for a run, and a question for a specialist with the kit, the text it was made from, your workspace notes, and the conversation so far, sent to OpenAI. What an AI app sends goes through a separate OpenAI project of ours that does not share it with OpenAI to improve its models, so “What OpenAI may do with it” above does not apply to it. Without the tick, nothing an app sends goes to OpenAI, and the app can only read. When an app reads a kit, it receives everything in that kit, including the quiz answers with their explanations and any names in a transcript you pasted.
For each connection we keep the app’s name, when you connected it, when it was last used, whether you allowed sharing with OpenAI and when, and the country Cloudflare saw when it gives one, never the IP address. The keys the app holds are stored only as hashes. A connection ends after 30 days without use, and at most 180 days after you allowed it. At most ten apps can be connected at once; connecting one more ends the oldest.
To disconnect an app, open Settings → AI apps and choose Disconnect, or end it under Where you are signed in. Delete account ends every connection. Each AI app is made by a separate company, under its own terms and privacy policy: what you write in the app, and what it receives from us, is handled under those.
Your data
Signed in, open Settings: Export my data downloads every kit, your settings, and your activity as one file, and Delete account deletes your account, every kit in your library, your settings, your activity, and the practice and lesson links you shared, right away. One thing is kept until the end of that month: how much of the month's AI allowance was used, with a scrambled form of your email address that can only be matched to the same address signing up again. It stops deleting and signing up again from starting a new allowance. If you sign up again that month, the scrambled address is deleted and the amount moves to your new account. Otherwise both are deleted within a day of the month ending. A plan that still renews is cancelled in Plan & billing first, so Stripe does not charge an account that is gone.
Deletion
You can also write Contact or login@enablementstudio.app and ask us to delete the account on that email. Visitor kits die with the es_sid cookie. Practice links and their answers are deleted 90 days after they were shared, lesson links after 180 days; write to us to delete one sooner.
The app
The iPhone, iPad, and Mac app signs in to the same account as the website. An app sign-in lasts 60 days from the last time you use it. For each one we keep a hash of it, the kind of device (for example, "Enablement Studio on iPhone"), and the country Cloudflare saw, never the IP address, so Settings → Account can show where you're signed in and sign any of them out.
On your device, the app keeps its sign-in in the keychain, plus a copy of your Library and the kits you opened. Signing out, deleting your account, or another account signing in on that device clears them.
The app has no ads, no analytics, and no third-party SDK. It doesn't ask for your photos, contacts, location, camera, or microphone. Nothing is sold in the app: plans and billing are on the website, through Stripe.
When you ask one of the studio's agents a question in the app, we send OpenAI your question, the conversation so far, the kit and the text it was made from, and your workspace notes. That's the same as on the web, and "What OpenAI may do with it" above covers it. Before the first question on each account, on each device, the app asks "Share this with OpenAI?" Nothing is sent until you choose Allow and ask. Not now sends nothing and keeps your question in the box. The app remembers your answer on that device until you sign out, delete the account, or someone else signs in.
Deleting your account from the app
In the app, open Account and choose Delete account…. On iPad and Mac, open Manage account at the foot of the sidebar first. Type the account's email to confirm.
It deletes what Delete account on the web deletes (see "Your data" above, and the one thing it keeps until the end of that month), right away: your account, every kit, your drafts, edits, conversations, projects, settings, and activity, and the practice and lesson links you shared. It signs you out everywhere, in browsers and in the app, and clears the sign-in and your Library from the device. It can't be undone, so use Export my data on the web first if you want a copy.
If your plan still renews, the app tells you and deletes nothing. Open Plan & billing takes you to the web page where you cancel it. Then delete the account. Stripe keeps its own payment records (see "Payments" above).