Privacy Policy

Effective September 15, 2026

This describes what Adi Astra actually collects and does with it. It’s written to be read rather than to be technically unfalsifiable, so if anything here is unclear, ask and we’ll answer plainly.

What changed in this version: the previous version (effective July 29, 2026) said that this site set no cookies and used no advertising or social trackers, that your assessment answers reached us only if you chose to submit them, that the providers we use processed your information only to provide their service to us, and that we didn’t share it for cross-context behavioral advertising. None of that is accurate now, and it was not accurate while those tools were running. The site uses PostHog analytics, which sets cookies and receives your assessment answers as you go, whether or not you submit your details. Since September 1, 2026 it has used Meta’s Pixel, and since September 4, 2026 Meta’s Conversions API, which give Meta information about your visits that it can use to show our ads to people who visited this site and for its own purposes. This version corrects those statements and describes everything the site collects, including our own site log and the AI chat assistant.

Who we are

Adi Astra is an AI automation consulting practice operating in South Florida. For anything in this policy, contact us at koladi1@gmail.com or (561) 757-9339.

What we collect

Information you give us

Contact form: your name, email address, company name if you give it, and your message.
Assessment results: when you enter your details to see your results, your name and email address, and your company and industry if you give them.
Tips and updates sign-up: if you sign up on the results page, your email address, so we can send them. Ask us at any time and we’ll stop.
Chat assistant: if you give the assistant your email address, it saves that email along with your name, company, and industry if you mentioned them, and a short summary of what you discussed. If you use the chat’s “Prefer email?” form instead, we save the name and email address you enter and your most recent chat message.

Campaign and assessment records

When campaign attribution is enabled, we keep a minimal record of the campaign and creative, assessment start and completion, contact-save receipt, and clicks to request a consultation. These records do not include assessment answers or scores. A consultation click does not establish that a meeting was booked. If your contact details are saved, we link that assessment run to your enquiry for authorized staff.

Campaign context and pending activity are kept in this tab for up to 24 hours. Unsaved contact details stay in memory and are discarded on reload or when the tab closes. Results remain available when a contact save fails; the page shows whether the save succeeded and offers a retry. A saved contact receipt does not mean a report was emailed.

Your assessment answers

The self-assessment asks how your business works: which tasks your team still does by hand, roughly how many hours and people those tasks take, what an hour of that work costs, how often errors slow it down, your team size and how it handles change, the software you use and its pain points, your goals, when you want results, and your budget.

As you finish each part of the assessment, your answers are sent to our product analytics provider, PostHog — even if you stop before the end or never give us your email address. When you enter your details to see your results, the results calculated from your answers (your score, estimated savings, insights, and recommendations) are sent to PostHog as well, and your earlier answers are linked to the name, email address, company, and industry you entered. The enquiry we save in our own database holds those contact details and the page you came from, but not your answers or your score.

Some of this is commercially sensitive. We treat it as confidential, use it only to understand how people use the assessment and to prepare for a conversation with you, and don’t share it with anyone outside the providers listed below.

Chat conversations

If you use the chat assistant, your messages are sent to a third-party AI model provider to generate the replies. Each message and reply is logged together with the same random session identifier our site log uses (see below), your browser’s user-agent string, and the page you were on, so we can see what people ask and improve the answers.

Information collected automatically

When you submit a form we record the page you submitted it from, the referring page that sent you to us, and any campaign tags in the link you followed. For the contact form and the tips sign-up we also record your browser’s user-agent string.

Our own site log. The site keeps a technical log in our database, hosted by Supabase. It records each page you view, with its full web address (including any campaign tags or ad-click identifiers in the link), some actions such as moving through the assessment or clicking to book a call, and any technical errors, together with your browser’s user-agent string and a random identifier kept in your browser’s session storage for that tab. When you submit a form, the log also records your email address, which can link that tab’s page views, and any chat messages sent from the same tab, to you.

Hosting statistics. Our host, Vercel, collects aggregate page-view statistics that do not identify you individually.

Product analytics (PostHog). PostHog records the pages you view, how long you stay and how far you scroll, which buttons and links you click (including the answer choices you pick in the assessment), the assessment answers and results described above, the full page address including any campaign tags or ad-click identifiers, the site that referred you, and technical details about your browser and device. It may also receive your IP address and estimate an approximate location from it. It keeps an identifier in a first-party cookie (named ph_…_posthog, which can last up to a year) and in your browser’s local storage so that repeat visits can be recognized. That identifier starts as a random value; once you submit a form or give your email address to the chat assistant, it becomes your email address, and local storage also keeps the name, company, and industry you provided. Session recording is switched off: we do not use PostHog to record your screen or replay your session.

Advertising measurement (Meta Pixel and Conversions API). The Meta Pixel, from Meta Platforms, loads on every page of this site. It tells Meta when a page is viewed and when you start the assessment, complete a step, view your results, submit your details, or click to book a call. Each Pixel request also carries the address of the page, the page that referred you, your IP address, your browser’s user-agent string, and, depending on your browser, cookies Meta has set for its own sites. The Pixel sets a first-party cookie (_fbp) and may store a click identifier (_fbc) if you arrived from a Meta ad. We have turned off the Pixel’s automatic collection of button text and page metadata. Meta may use this information to measure our ads and to show our ads to people who have visited this site, and it also uses it under its own terms for its own purposes. Automatic advanced matching is switched on in our Meta settings, so the Pixel may also send Meta a hashed (scrambled) copy of contact details you type into forms on this site, such as your email address, so Meta can match your visit to a Meta account.

We also send Meta a server-side copy of the assessment, results, contact-details, and book-a-call events (not ordinary page views) from our own server, using Meta’s Conversions API. That copy includes the event, the address of the page, the Meta cookie identifiers described above, your IP address, and your browser’s user-agent string. This server-side copy is sent even if your browser blocks the Meta Pixel.

Cookies and similar technologies

Adi Astra: a session-storage entry (log_session_id) holding a random identifier for the current tab, cleared when the tab closes
PostHog: a first-party cookie (ph_…_posthog) and a local-storage entry holding an identifier that starts as a random value and becomes your email address after you submit a form or give it to the chat assistant, plus the name, company, and industry you provided; and session-storage entries that identify the current browser window
Meta: the _fbp cookie, and the _fbc cookie if you arrived from a Meta ad

PostHog data is sent through this site’s own web address, and the Meta events described above are also sent from our server. Both are set up that way so that ad and tracker blockers don’t stop them. Blocking or deleting cookies and site storage stops these tools from recognizing you on later visits, and a tracker blocker can stop the Meta Pixel from loading in your browser. Neither stops your assessment answers, results, or contact details from reaching PostHog, or stops the server-side copy of the assessment, results, contact-details, and book-a-call events from reaching Meta.

What we don’t do

We do not sell or rent personal information for money. We do use Meta’s advertising tools as described above, which means Meta receives information about your visits to this site.
We don’t record your screen or replay your sessions.
We don’t buy contact lists or add you to a mailing list because you took the assessment. You only get tips and updates if you sign up for them.

Why we use it

To send you the assessment results you asked for
To respond to your enquiry and arrange a conversation
To answer your questions through the chat assistant
To send you tips and updates if you signed up for them
To prepare for and deliver work you engage us for
To understand how people use the site and the assessment, and which pages and channels bring them to it
To measure which of our ads lead to enquiries, and to show our ads to people who have visited this site
To keep the site working and fix errors
To meet legal, accounting, and tax obligations

Who processes it for us

We use a small number of service providers:

Supabase — the database where enquiries, chat logs, and our site log are stored, and the servers that run the chat assistant and send events to Meta
Vercel — website hosting and aggregate statistics
PostHog — product analytics, including assessment answers and results
Meta Platforms — advertising measurement through the Meta Pixel and Conversions API. Meta also uses this information under its own terms and privacy policy.
An AI model provider — generates the chat assistant’s replies from the messages you send it
SendGrid — transactional email
Google — the calendar used to book calls, if you book one
Stripe — payment processing, if you pay us. Stripe handles card details directly; we never see or store your card number.

How long we keep it

We keep enquiry, chat, and site-log information for as long as we need it to respond to you, run any engagement that follows, and keep the site working, plus whatever period our tax and accounting obligations require for records relating to paid work. PostHog and Meta keep the data they receive according to their own retention settings and policies.

You can ask us to delete it at any time and we will, other than records we’re legally required to retain.

A daily cleanup removes campaign records older than 30 days when they are not linked to an enquiry, and older than 12 months when they are linked. Enquiry records follow the policy above. Deleting an enquiry removes its link to assessment runs.

Your choices

Email koladi1@gmail.com and we will, within a reasonable time and at no charge:

Tell you what we hold about you
Correct anything that’s wrong
Delete it
Send you a copy

You do not need to cite a statute or use particular wording. Just ask.

Browser settings and tracker blockers won’t fully stop this collection (see “Cookies and similar technologies” above), and the site doesn’t yet offer an in-page opt-out. Page views reach PostHog as soon as you visit, and reach Meta too unless a tracker blocker stops the Pixel from loading. If you don’t want your answers or details collected, don’t use the assessment, the chat assistant, or the site’s forms, and email us to have what we already hold deleted from our systems and from PostHog. You can also change the settings in your Meta account for activity from other websites and apps. This site does not currently respond to browser “Do Not Track” or Global Privacy Control signals.

Security

The site is served over HTTPS. Form submissions are written through a restricted database function, the site log accepts new entries but can’t be read back from the browser, and access to stored information requires an authenticated administrator account with database-level access rules enforcing it. No system is perfectly secure.

Children

This is a business-to-business site and is not directed at anyone under 18. We don’t knowingly collect information from children.

Changes

If this policy changes we’ll update the effective date above. Material changes affecting information we already hold will be communicated directly to the people affected.

Contact

koladi1@gmail.com · (561) 757-9339 · South Florida