Privacy policy

01Who we are

Plansmith is a planning agent operated by BrainGrid AI, Inc., 1111B S Governors Ave STE 29316, Dover, DE 19904, USA ("BrainGrid", "we", "us"). This policy describes what we collect when you use Plansmith, how we use it, and the choices you have.

For your account, usage, and billing data, we decide how the data is processed and act as the data controller. For the Plan content and Context you and your Team put into Plansmith — Projects, Plans, Specs, planning conversations, and the sources you connect — we act as a processor on your behalf: you decide what goes in, and we store and process it to run the service for you. If you use Plansmith through an organization, that organization controls its content.

02Information we collect

Account information

When you sign in, we store your email address and a unique user identifier, and the Team you belong to. Sign-in and identity are handled by Supabase Auth. You can sign in with an email address and password, or with BrainGrid, our own identity service, which fronts Google sign-in. If you use a password, it is hashed by Supabase Auth and we never store it in readable form. If you sign in with Google, we never see a password at all. Where Google shares your name or avatar, we store those too.

Plan content

Plansmith stores the planning work you and your teammates create: Projects, Plans, and the Specs within them, together with the planning conversations that shape them, the readiness and effort scores the agent assigns, and any prototypes and comments you generate. This content is private to your Team and is not public — unless you choose to share it, for example by publishing a plan as a prototype with a shareable link, which anyone holding the link can open.

Context you connect

Context is the material you attach so the agent can ground your plans: documents, pasted text, links, and read-only access to the code repositories you authorize. We collect it only when you add it, and we use it only to plan.

Usage and technical data

To operate and secure the service we record technical data such as the IP address a request comes from and request metadata like timing, status, and errors.

Product analytics

We use PostHog to understand how Plansmith is used and where it can be better. We record milestone events — such as creating your first Plan or pushing a plan to your tracker — tied to your organization and user identifiers. We do not send your Plan content, Context, or raw personal information into analytics.

Session recordings and errors

To diagnose problems and improve the product, we also record how the app is used: page navigation, clicks, and errors the app hits in your browser. Everything you type is masked before it leaves your browser, and all other on-screen text is masked too. Your plans, specs and planning conversations go further than masking: those parts of the screen are left out of the recording entirely, so nothing about them is captured. A recording shows where you clicked, never what your content says. Pages opened from a share or invite link are never recorded at all. These recordings follow the same cookie choice and the same opt-out described in Cookies below.

Marketing site visitors

On our public marketing pages only, we run a visitor identification tag from Leadsy (vTag), which loads Instantly’s RB2B pixel. It uses your IP address and browsing signals to work out which company you visit from, and in some cases which person. We use it to see which companies are interested in Plansmith so we can reach out. Where the law requires consent, including the European Economic Area and the United Kingdom, it does not run until you accept. Elsewhere it runs when you arrive, and you can turn it off in Cookies below, taking effect from your next page load. It never runs on a signed-in page, and it never runs if your browser sends a Global Privacy Control signal.

On the same pages we run the LinkedIn Insight Tag. It tells LinkedIn that you visited, which lets us see which of our LinkedIn ads bring people here and lets us show ads on LinkedIn to people who have visited. LinkedIn sets its own cookies to do this and acts as an independent controller of what it collects. Where the law requires consent, including the European Economic Area and the United Kingdom, it does not run until you accept. Elsewhere it runs when you arrive, and you can turn it off in Cookies below, taking effect from your next page load. It never runs on a signed-in page, and it never runs if your browser sends a Global Privacy Control signal.

Separately from that tag, when a Team buys a paid plan we send LinkedIn one conversion event so we can measure whether our LinkedIn ads lead to customers. It contains the purchase amount, the buyer’s email address in hashed form (a one-way fingerprint; we do not send the address itself), and, if the buyer arrived from one of our LinkedIn ads, the click identifier LinkedIn stored in their browser. LinkedIn uses these only to match the purchase to an ad it showed. This sends nothing about how you use Plansmith.

Connector credentials

When you connect an issue tracker or a code host, we store the access token encrypted. Code access is read only: the agent reads the code you authorize to ground the plan, and it never changes a line. If you connect a code host, we also store repository metadata for the repositories you authorize.

To let the planning agent search a linked repository quickly, we keep a copy of its text files at the two most recent commits of the linked branch, encrypted at rest and readable only by your Team's planning agent. While a conversation searches it, the server answering holds a working copy that is removed as it ages out. We delete every stored copy when no Project links the repository any more. This applies to repositories reached through the private-network connector too: the connector builds the copy inside your network and uploads it to us.

Billing data

If your Team is on a paid plan, we store Stripe customer and subscription identifiers, your seat count, and subscription status. Card numbers and full payment details go directly to Stripe and are never received or stored by us.

03How we use information

We use the data above to:

• provide and operate the service, including storing and syncing your Plan content;
• authenticate you and secure your account and Team;
• run the planning agent — generate, refine, and score your Specs (see the next section);
• process payments and account for seats;
• send transactional email, such as Team invitations;
• understand product usage and improve Plansmith;
• detect and prevent abuse and fraud;
• respond to support requests and comply with legal obligations.

We may create aggregated or de-identified statistics that do not identify you and use them to operate and improve the service. We do not send marketing email by default, and we do not use your data for advertising.

04AI and your content

Plansmith is a planning agent, so making your plans better means sending your content to AI models. To generate and refine your Specs, we send the relevant Plan content, planning conversations, and connected Context to the third-party large language model providers we use to run the planning agent. This processing takes place in the United States.

We send this content to the models only to run the service for you (inference). Your content is not used to train or improve AI models — not by us, and not by our model providers. It is never sold.

Because these features rely on AI, the plans and Specs they produce can be incomplete or wrong. They are a starting point, not a substitute for your judgment — review your Specs before you hand them off.

05How we share information

We share data only with the service providers that run Plansmith ("subprocessors") and as required by law. We do not sell your Plan content or the Context you connect. We do use analytics cookies, a visitor identification tag, and an advertising tag on our marketing pages (see Cookies); under some laws, such as the California Consumer Privacy Act, that use can count as "selling" or "sharing" personal information. You have the right to opt out of that sharing at any time.

We process opt-out preference signals, including Global Privacy Control, in a frictionless manner: if your browser sends one, we treat it as an opt-out for that browser automatically. There is no fee, no reduction in the service you get, and nothing for you to click. You can also opt out yourself with the cookie controls described in Cookies below.

We may disclose information if required by law, regulation, or valid legal process, or to protect the rights, safety, or property of BrainGrid, our users, or others. If BrainGrid is involved in a merger, acquisition, or sale of assets, your data may be transferred as part of that transaction; this policy would continue to apply to it.

06Cookies

We use cookies and similar technologies to run the service, understand how it is used, and support our marketing. They fall into three groups:

Essential cookies

Required to provide the service — for example, the session cookies from our authentication provider that keep you signed in. These are always on.

Analytics cookies

Set by PostHog to measure how Plansmith is used so we can improve it.

Marketing and advertising cookies

Set by the Leadsy (vTag) visitor identification tag and by the LinkedIn Insight Tag, on our public marketing pages only. We use them to see which companies are interested in Plansmith, to measure which of our LinkedIn ads bring people here, and to show ads on LinkedIn to people who have visited. Neither tag runs on a signed-in page, and neither runs before you accept in the regions where consent is required.

You can control non-essential cookies through your browser settings, and where the law requires it, for example in the European Economic Area and the United Kingdom, we ask for your consent before setting analytics or marketing cookies.

Outside those regions we do not interrupt you with a banner: analytics and marketing cookies are set when you arrive, and the control below turns them off for this browser. Tags already loaded on the page you are reading stop at your next page load. We also honor Global Privacy Control, so if your browser sends that signal we treat it as an opt-out and set no analytics or marketing cookies at all, wherever you are. If you want to send it, you can turn on Global Privacy Control in a browser or extension that supports it; globalprivacycontrol.org lists them.

07Data retention

We keep your account records and Plan content while your account and Team are active. We do not run a fixed deletion schedule — you can delete your Projects, Plans, and Specs, or export and delete your data, at any time. When you delete content, we remove it; deleting your Team removes its content.

Revoked connector and API credentials are deactivated immediately; their records may be retained for audit purposes.

Copies of linked repositories are deleted within minutes of the last Project unlinking the repository, and older commits are deleted as newer ones replace them.

08Security

Traffic to the app and API is encrypted in transit with TLS. Your data is isolated by Team — organization identity is the primary isolation key, enforced on every read and write — and realtime data is additionally protected with database row-level security. Connector and code-host tokens are encrypted at rest. Access to production data is restricted. That said, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.

09Your rights and choices

You can request access to, correction of, export of, or deletion of your personal data by emailing hello@braingrid.ai. Depending on where you live, you may have additional statutory rights — for example, under the GDPR or the California Consumer Privacy Act — including rights to access, correct, delete, and port your data, to object to certain processing, and to be free from discrimination for exercising them. We will honor valid requests as required by applicable law.

Where we process Plan content on behalf of an organization, that organization is the controller, and we will refer your request to it.

10Plan content and other people

Content in a Team may include personal data about teammates or third parties — for example, names in a planning conversation, or the authors of code the agent reads. The Team and its organization are responsible for having a lawful basis to put that content into Plansmith and for honoring the rights of the people it concerns. If your personal information appears in a Team and you want it addressed, contact that organization, or email us at hello@braingrid.ai and we will route the request appropriately.

11Children's privacy

Plansmith is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, contact us and we will delete it.

12International data transfers

Plansmith is operated from the United States, and data is processed and stored in the United States. If you use the service from outside the US, you understand that your data is transferred to and processed in the US.

13Changes to this policy

We may update this policy from time to time. The "Last updated" date above reflects the latest revision, and material changes will be announced through the site or the app.

14Contact

Privacy questions and requests can be sent to hello@braingrid.ai or by mail to BrainGrid AI, Inc., 1111B S Governors Ave STE 29316, Dover, DE 19904, USA.