Privacy Policy

This policy covers the StellarFirm public site, the waitlist, and invite-only alpha accounts. StellarFirm gives you AI Agents, Agentic Assistants for your work. You set the goal, and an assistant does the work. Nothing is sent or published until you approve it. That approval covers sending work to a recipient and publishing. Request text may still go to a model provider before you approve it.

Who we are

The StellarFirm waitlist and alpha are run by Astro Code L.P., Athens, Greece, the controller of the data described here. Contact us at hey@stellarfirm.ai.

What we collect

Your email address, and the waitlist consent fields we store with it. We do not ask for payment details to join. When you join we record the time of your sign-up, that you accepted the terms and this policy, and the version of the waitlist wording (waitlist-consent-v3-2026-10-08). In our own logs your email appears only as a one-way hash. If you arrived through a link with a ref or utm_* parameter, that campaign label is stored with your sign-up.

Alpha accounts. An account is invite-only during this alpha. We create one only after we invite you. Assistants can read and draft, and can send the text of a request to a model provider, before your approval. They do not send that work to a recipient, or publish it, until you approve it.

Why, and on what basis. We email you about the StellarFirm waitlist, trial invites, and product updates. Joining the waitlist is how you ask for those emails. A short line under Join the waitlist links to the Privacy Policy and Terms. You can unsubscribe at any time by using the unsubscribe link in any email or by writing to hey@stellarfirm.ai. You can withdraw consent at any time the same way.

Booking a demo. When you book a call on the demo page we collect your name, email, company, team size, and, if you give them, your role and notes, with the time you picked and your time zone. We use them only to arrange and hold that call, on the basis of your request. They are emailed to our team and kept as a Resend contact that is not subscribed to product mail. Booking a demo does not add you to the waitlist. Write to hey@stellarfirm.ai to have them removed.

Who processes it for us

• Resend stores your contact details and sends our emails (email provider and processor).
• Clerk provides accounts for the invite-only alpha (processor). When you accept an invitation, Clerk stores the details needed to sign you in, such as your email and your session.
• PostHog provides product analytics (processor) for EU project 292135, on this website and in the signed-in app. It records page views, clicks (autocapture), and session recordings, and can show a short survey. All of this starts only after you accept analytics cookies in the cookie choice shown on every public page. If you reject, or have not answered yet, we do not track you: your browser sends nothing to PostHog. Our server still keeps two anonymous counts, with no cookie and nothing stored on your device: a visit that arrives from an ad link, and a waitlist sign-up. A visit carries only the campaign labels from the link (such as utm_source), whether an ad click id was present (not the id itself), the site name, and the page path. A sign-up carries the campaign labels and ad click ids from your first and latest visit, the referring site name, and the site name. Neither carries an IP address, email, name, device details, or an id that links it to you or to another event. Do Not Track turns both off. Once you have an account, our server also counts a few of its steps, with no cookie: your trial starting, an answer reaching you, and your trial ending. Usage balance, billing, and payment data are included only if and when paid plans are enabled. Each carries a code made from your account with a secret key we keep, so the steps of one account can be counted together. They never carry your email, name, account user id, IP address, or anything you asked or were told. Your choice is saved in this browser. Joining the waitlist does not turn this on. Do Not Track, and turning usage events off in the desktop app, still stop capture after an accept. The data is anonymous: we do not identify you, and we do not send your email, name, account user id, or IP address. Query strings are removed from page addresses. After you accept, a page view keeps the referrer and the campaign labels and ad click ids from the link, and a waitlist sign-up sends those labels from the first visit plus the latest visit. Secrets are stripped from events. Session recordings mask everything you type. In the signed-in app they also mask all text on screen, and they leave out your chats, code changes, terminal output, drafts waiting for approval, and the assistant's computer and files. PostHog also provides AI observability for your assistants' model calls, and stores the prompts you save in the prompt library. Those are tied to your account and are described under Your assistants' model calls below. In the signed-in app, after the same accept, PostHog also shows a Support chat. A ticket you open there is not anonymous: what you write, the email you type into the chat, the full address of the page where you started (query string included, unlike the page addresses above), and a link to that visit's session recording reach us in PostHog so we can answer you. This browser keeps the chat's own record so you can find your tickets again.
• LangSmith records your assistants' model calls so we can find and fix problems (processor, EU region). What it receives is described under Your assistants' model calls below.
• Google Analytics measures how the site is used (processor). It stays off, and its script is not loaded, until you accept analytics cookies in the cookie choice shown on every public page. Your choice is saved in this browser. Rejecting, or choosing Cookie settings and rejecting later, stops measurement and clears its cookies. Joining the waitlist does not turn it on. We keep advertising features switched off.
• TikTok provides the TikTok Pixel, which measures visits and waitlist sign-ups that come from our TikTok ads so we can improve them (processor). It stays off, and its script is not loaded, until you accept cookies in the cookie choice shown on every public page. Your choice is saved in this browser. Rejecting, or choosing Cookie settings and rejecting later, stops the pixel and clears its cookies. Joining the waitlist does not turn it on. It receives the pages you visit, clicks on the Join the waitlist buttons, the fact that you joined the waitlist, and technical details such as your browser and IP address. We never send it your email, name, or account id. TikTok also uses this data under its own privacy policy, for example to measure and deliver ads. When you join the waitlist, our server also tells TikTok about the sign-up directly (the same event id as the pixel when it ran), with your browser, IP address, the click id from a TikTok ad if one brought you here, and the page, so ads can be measured even if your browser blocks the pixel. We never send it your email. Do Not Track turns that server send off.
• Meta receives a server-side Lead when you join the waitlist, so our Meta ads can be measured (processor). The send carries the fact that you joined, your browser and IP address, the click id from a Meta ad if one brought you here, and the page. We never send it your email, name, or account id. Do Not Track turns it off. When the Meta Pixel is in use, it stays off, and its script is not loaded, until you accept cookies in the cookie choice shown on every public page. After you accept, it receives the pages you visit, and on a successful join a CompleteRegistration and a waitlist_signup, with the same event id as the server send. We never send it your email. Rejecting, or choosing Cookie settings and rejecting later, stops the pixel and clears its cookies.
• Google Ads receives a click conversion when you join the waitlist after arriving from a Google ad, so those ads can be measured (processor). We store the Google click id on your waitlist contact for that match. The send carries the fact that you joined and that click id. We never send it your email, name, or account id. Do Not Track turns it off. When the Google Ads tag is in use, it stays off, and its script is not loaded, until you accept cookies in the cookie choice. After you accept, it receives a page view, and a successful join sends a conversion with the same event id as the server send. We never send it your email. Rejecting later stops the tag and clears its cookies.
• LinkedIn provides the LinkedIn Insight Tag, which measures visits and waitlist sign-ups that come from our LinkedIn ads (processor). When it is in use, it stays off, and its script is not loaded, until you accept cookies in the cookie choice shown on every public page. After you accept, it receives the pages you visit, and on a successful join a conversion. We never send it your email, name, or account id. LinkedIn also uses this data under its own privacy policy. Rejecting, or choosing Cookie settings and rejecting later, stops the tag and clears its cookies.
• Leadsy tells us which companies visit this website, and in some cases who the visitor is, so we can follow up with businesses that show interest (processor). It stays off, and its script is not loaded, until you accept cookies in the cookie choice shown on every public page. Your choice is saved in this browser. Rejecting keeps it off. If you accepted and later choose Cookie settings and reject, the page reloads at once so its script stops. Any other page of this website where its script ran reloads too, whether it is open in this browser or you return to it with Back or Forward. After that it stays off on every page. Any cookies it already set stay until you clear them in your browser. Joining the waitlist does not turn it on. It receives the pages you visit and technical details such as your browser and IP address, and matches them with its own business contact data. We never send it your email, name, or account id.
• Dify runs Diggy, our help chat, which answers questions from our docs and guides (processor). On the public pages its script loads once you have answered the cookie choice, either way. In the signed-in app it loads only when you open Ask Diggy. What you type to Diggy goes to Dify so it can answer, and Dify may process it outside the European Economic Area. It is not analytics, and we never send it your email, name, or account id. Do not share keys, passwords, or your customers' data with it.
• Calendly provides the scheduling button and the calendar on Book a demo (processor). The button's script is not loaded until you have answered the cookie choice on a public page. It is not loaded in the signed-in app. After you choose, the button can open a calendar hosted by Calendly. What you type there (your name, email, and the time) goes to Calendly so the call can be booked. Choosing Reject still starts the button, because it schedules a call and it is not analytics. The Book a demo page, the header, and the footer still link to the same calendar without that script.
• Vercel hosts this website and the signed-in app (processor). It stores the site and the requests it receives. Vercel Web Analytics also counts page views on the public pages. It sets no cookie, and it starts only after you accept analytics cookies in the cookie choice shown on every public page. Rejecting later stops it. It receives the page address without its query string, the referring site, and your browser, operating system and country, never your email or name.
• Stripe processes payment and usage data for paid plans and for an account with a linked Stripe customer (processor). Joining the waitlist does not ask for payment details, and nothing is charged without your explicit agreement.
• Model providers act as processors when an assistant asks for an answer. They receive the text needed to write that answer. A provider may process that text outside the European Economic Area. The international transfers section below explains the safeguards.

Your assistants' model calls

Each time an assistant asks a model for an answer, we record the call in PostHog AI observability and in LangSmith, so we can fix problems and keep answers good. Unlike the website analytics above, these records are tied to your account. A hosted record always includes your account identifier, and an organization identifier only when one applies. A record from software you run yourself includes an account identifier, an organization identifier, or a workspace identifier only when that host is configured with a valid one. None of them includes your email or name. Each record also shows which assistant made the call, the model and the provider that served it, ids for the conversation and the job it belongs to, and token counts and timing. For assistants running in StellarFirm cloud it also holds the conversation text of the call: the messages, the answer, and the tool steps, with keys and passwords removed. Assistants running on your own computer send a record only when StellarFirm runs the model, and they never send the text. When a call is metered and rates are configured, the PostHog record also holds a calculated usage figure for that call. When a published rate for the model exists, the PostHog record also holds the amount that rate implies. LangSmith does not receive those figures.

You can turn this off at any time in Settings, under Privacy: switch off Share model call analytics to stop all of it, or Include conversation text to keep the words out while still sharing the rest. The change applies from the next call. It does not stop the internal usage record kept for metering, including during a free trial. A separate Stripe record of that usage is sent only when the account has a linked Stripe customer. Payment data is included only if and when paid plans are enabled. Prompts you save in the prompt library are stored in PostHog under your account identifier. A shared prompt is also stored under your workspace identifier, and it keeps the account identifier of the person who saved it. When you delete one we archive it there; write to hey@stellarfirm.ai to have it erased.

The model provider that writes the answer acts only as a processor for that request. This policy does not name those providers, and it does not claim that every answer is produced in one country or region.

Cookies

Analytics and advertising cookies stay off until you accept them in the cookie choice on every public page. Your choice is saved in this browser. Rejecting, or choosing Cookie settings and rejecting later, stops the tags and clears the cookies those tags set, as each processor above describes.

PostHog product analytics, and the ad tags for Meta, Google, and LinkedIn, are loaded only after you accept cookies. The same rule applies to the other tags named above when they are in use. Joining the waitlist does not turn them on.

We honor Do Not Track where it is implemented. A browser that sends Do Not Track stops the product analytics and the ad measurement we control, including after you have accepted cookies.

We do not sell your data. When you join the waitlist, our server may tell Meta, TikTok, and Google Ads that a sign-up happened, with the technical details above and never your email, so we can measure our ads. Do Not Track turns those sends off. The TikTok Pixel runs only if you accept cookies. When the Meta Pixel, the Google Ads tag, or the LinkedIn Insight Tag is in use, each of those runs only if you accept cookies in a choice that names it. An earlier accept that did not name it is asked again before that tag runs.

How long we keep it

We keep your waitlist details until you unsubscribe or ask us to delete them, and consent records for as long as needed to show that consent was given. We keep an alpha account while it is open. After you ask us to erase it, or after the account is closed, we delete or anonymize the personal data unless the law requires us to keep it longer. PostHog keeps the conversation text of a model call for 30 days. LangSmith keeps calls for the retention period set on our account.

International transfers

Some of these providers, including model providers, may process personal data outside the European Economic Area. Where they do, we use standard contractual clauses (SCCs) or an equivalent safeguard.

Your rights

You can ask for access, rectification, erasure, and portability of your personal data. You can object to a use of your data, and you can withdraw consent at any time. Withdrawing consent does not affect a use that was lawful before you withdrew it. You can also complain to the Hellenic Data Protection Authority (Hellenic DPA). Write to hey@stellarfirm.ai to use any of these rights.

Children

StellarFirm is not for children under 16. Do not join the waitlist or use an account if you are under 16. We do not knowingly collect personal data from children under 16. If you believe we have, write to hey@stellarfirm.ai and we will delete it.

This site is the public page, the waitlist form, and the signed-in app. It never stores your API keys or your connected account secrets. See also our Terms of Service.