Legal

Privacy Policy

Updated 23 September 2026

In short: the extensions run in your browser and work on your device by default. One feature is different, and it is the one worth reading about: if you turn on the PI Labs AI engine, the text you are working on is sent to our server and passed to a model provider to answer. We do not keep it.

This policy covers the PI Labs website at pilabs.space and the browser extensions published by PI Labs (“we”, “us”, “our”):

It replaces the earlier Joelbooks extensions privacy policy for these products. Where this policy and any general Joelbooks policy differ, this one governs.

The short version. We do not sell your data and we do not use it for advertising. Your settings stay in your browser’s local storage. Extensions can, at your choice, send text you select to a third-party AI provider, or sync your data to your own Google Drive. One route does go through us: the PI Labs AI engine, which members can turn on instead of bringing an API key. Text sent that way reaches a PI Labs server, is passed to our model provider to be answered, and is not stored by us. Apart from that we hold your account, your subscription status and a record of what your energy was spent on. Each case is described below.

1. What the website collects

You can install and use every free feature without ever visiting the website or creating an account. An account exists for one reason: so premium can follow you between machines.

When you sign in with Google

We receive and store:

We use these only to recognise you when you return, to link your subscription to you, and to answer you if you contact support. We do not receive your Google password, and we cannot read anything else in your Google account.

When you use the PI Labs AI engine

This is the one feature where the text you are working on reaches us, so it is worth being exact. When an extension asks our engine for an answer, the request carries what that tool needs to answer it: for PI Fix Grammar the text you are correcting; for PI Answer the post you are replying to, up to four posts above it in the thread, and your draft.

We pass that straight to our model provider, OpenRouter, which routes it to whichever model is answering at the time, and we return the answer to your browser. We do not store the text. It is not written to our database, and we do not keep it after the request has been answered. How OpenRouter and the model provider handle it is governed by OpenRouter’s privacy policy.

What we do keep is one usage record per call, so the energy on your account adds up and you can check it on your account page: which tool asked, what kind of work it was, when, which model answered, and what it cost. Those records hold no part of your text. They are kept for 90 days and then deleted; the running totals behind your monthly allowance stay for as long as your account does.

The engine is never the only option. Every extension that offers it also runs on Chrome’s built-in on-device model or on an API key of your own, and the extension names which engine answered so you can see which applied.

When you connect an extension

Connecting an extension to your account creates a key for that extension. We store only its SHA-256 hash, along with which tool it belongs to and when it was last used, so your account page can list your connected extensions and let you disconnect any of them.

When you subscribe

Payments are handled entirely by our payment providers. We never see or store your card number, bank details, or wallet keys. What we store is your subscription status, the plan, the current period end date, and the provider’s reference for your subscription. That is enough to answer the only question the extensions ask, which is whether premium is currently active for your account.

When you send an idea or report a bug

The feedback button on every page stores what you send: the product it is about, your message, the page you were on, your browser’s user agent, and a screenshot if you attach one. If you are signed in we link it to your account so we can reply; if not, we keep an email address only if you choose to leave one. To stop spam we keep a one-way, salted hash of your IP address, never the address itself.

We use reports only to fix bugs and decide what to build. We may copy the text of a report into our private issue tracker on GitHub; the screenshot and your email are never copied there and stay in our own database. Ask us and we will delete a report.

When you just visit

The site is hosted on Vercel, which records standard server request logs (IP address, user agent, requested page) for security and reliability. We do not run advertising trackers, we do not set marketing cookies, and we do not build a profile of your browsing.

Analytics, only if you allow it

The first time you visit, we ask whether we may use Google Analytics. Its tag is on every page, but until you say yes it runs in Google’s restricted consent mode: it sets no cookies, stores no identifiers, and sends only anonymous, cookieless signals that cannot be tied to you or to a later visit. If you say yes, it sets its cookies and we use it to count visits and to see which pages are read and where visitors came from.

Your choice is remembered in your browser’s local storage for a year, and then we ask again. Signing in sets one session cookie, which is strictly necessary for your account to work and so does not need consent.

2. What the extensions collect

We do not collect, receive, or store the content you work on in the extensions. Each one keeps what it needs in your own browser using Chrome’s storage API, or, only when you choose, in your own Google Drive account.

Depending on the extension, the data held locally may include:

This information is stored on your device. Uninstalling the extension, or clearing its storage, removes it.

3. How each extension handles data

PI Prompts: optional Google sign-in to sync to your own Drive

A prompt library that inserts saved prompts into LLM websites such as ChatGPT, Claude, Gemini, Grok, DeepSeek, Mistral, Qwen and others. Your prompts are stored in your browser.

Optionally, you can sign in with Google so your library syncs across devices. Sync uses a private application folder in your own Google Drive, a hidden folder only this extension can reach. Signing in reads your basic Google profile (name and email) to identify your account.

PI Fix Grammar: on-device by default, optional cloud fallback

Corrects grammar in a text field. By default it uses Chrome’s built-in on-device AI (Gemini Nano), which runs entirely on your computer, so your text never leaves your device.

As an optional fallback you may enter your own API key for a cloud provider (Groq, OpenRouter, or Google Gemini). If you enable this, the text you correct is sent directly to the provider you configured.

The PI Labs AI engine. If you sign in and have an active plan, you can use our hosted engine instead of bringing a key. When that engine answers, the text you asked it to correct is sent to a PI Labs server at pilabs.space, which passes it straight to our model provider (OpenRouter) and returns the correction. We do not store the text, and nothing about it is written to our database. What we do record is that a correction happened: the tool, the time, the model that answered and what it cost, so your energy balance adds up. This engine is off unless you sign in and choose it.

PI Summarize: sends selected text to an AI provider you choose

Adds a right-click Summarize option. When you use it, the extension opens your chosen AI chat service (ChatGPT, Gemini or Claude) and places the text you selected into that service’s chat box.

PI Answer: on-device by default, optional cloud fallback

Drafts a reply to a post on X. Like PI Fix Grammar it uses Chrome’s built-in on-device AI first, so by default nothing leaves your computer. You may optionally supply your own key for Groq, Google Gemini or OpenRouter as a fallback.

To write a reply it reads the post you are replying to, whatever you have already typed in the reply box, and, when the post sits in a thread, up to four posts above it so the draft answers the conversation rather than one line of it. All of that is passed to the model as data, wrapped in markers, with an explicit instruction not to follow anything it says.

The PI Labs AI engine. PI Answer is a members-only tool, and its default engine is ours. When it answers, the post, the thread context above it and your draft are sent to a PI Labs server at pilabs.space, which passes them straight to our model provider (OpenRouter) and returns the draft. We do not store any of it, and nothing about it is written to our database. What we do record is that a draft happened: the tool, the time, the model that answered and what it cost, so your energy balance adds up. You can switch to Chrome’s on-device model or your own API key in Options, and then nothing goes to us at all.

Aviary: runs locally, no data sent out

Turns your own X analytics and creator-rewards figures into a daily flight progress view. It reads the figures already shown on the X pages you visit and stores your progress in your browser.

4. Summary of data flows

The only content that reaches a PI Labs server is what you send through the PI Labs AI engine, and only while it is being answered: we pass it to our model provider and return the answer without storing it. We keep a usage record for each of those calls (which tool, when, which model, what it cost) so your energy balance is auditable, and that record holds no part of your text. Everything else stays away from us: the prompts you save, the pages you summarize, your Aviary progress, and anything you send to a provider with your own key.

5. Third-party services

When you choose a feature that involves a third party, that party’s own privacy policy applies to how they handle it:

6. How we use data

The extensions use locally stored data only to provide their features to you. The website uses your account data only to sign you in, to keep your subscription working, and to contact you about that subscription. We do not:

7. Retention and deletion

Locally stored data stays in your browser until you remove it. You can:

For your PI Labs account: write to us and we will delete it. Deleting your account ends premium access. We keep the minimum billing and tax records our payment providers and the law require, and on-chain USDC transactions remain public on the blockchain regardless.

8. Your rights

If you are in the UK, EU, or another region with similar law, you have the right to ask what we hold about you, to have it corrected, to have it deleted, and to receive a copy. Because we hold so little, just your Google identity and your subscription status, these requests are quick to answer. Write to hello@pilabs.space.

9. Children

These products are not directed to children under 16, and we do not knowingly collect personal information from children.

10. Security

Data stored by the extensions is protected by your browser’s and operating system’s security. Data you send to a third-party AI provider, to Google Drive, or to us travels over encrypted (HTTPS) connections. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Changes to this policy

We may update this policy from time to time. When we do, we will revise the “Updated” date above. Material changes may also be reflected in the extensions’ store listings.

12. Contact

Questions about this policy or your data: hello@pilabs.space.

© 2026 PI Labs. This policy covers pilabs.space and the browser extensions listed above.