Privacy Policy

What information is collected

If you create a Sagacium account, we collect the name and email address you provide and your Sagacium activity, such as likes, saved posts, follows, shares, portal preferences, your My Company profile, workspaces, saved customer research, saved meeting preparation, saved analytics results, combined customer insights, growth opportunities, and account plans, and account actions.

Account authentication, password handling, email verification, and password recovery are provided by Supabase on Sagacium's behalf. Sagacium's application database does not store your password.

When you submit the contact form, we collect the name, company, email address, and message you provide so we can respond to your enquiry.

This site does not use advertising pixels or third-party behavioural tracking scripts.

How it is used

Account information is used to provide account features, remember your activity, and keep your portal work available when you return. Contact form submissions are used to assess fit and respond to enquiries. We do not sell your personal information.

Customer Intelligence and AI processing

If you use Customer Intelligence, Sagacium sends the information you submit for that research to OpenAI's API so the service can perform web research and generate the customer brief. This may include the customer name, website, your research objective, relevant information from your My Company profile, and relationship context you choose to provide.

The generated customer brief and the information you submitted for the brief are stored in your Sagacium workspace. Public web sources used by the research may also be stored with the brief.

If you use Meeting Brief, Sagacium sends the saved Customer Intelligence brief together with the meeting type, objective, attendees, and notes you choose to provide to OpenAI's API. When available in the same customer workspace, Meeting Brief may also send the saved calculated sales dashboard, current What this means synthesis, and current Growth Opportunities so the preparation can reflect both external and internal account evidence. Meeting Brief does not perform a separate web search and does not receive the raw CSV or XLSX file. The generated meeting brief and the meeting context you supplied are stored in the customer workspace and are tied to the specific evidence versions used to create them.

If you use Instant Analytics, Sagacium sends the CSV or XLSX file you upload to OpenAI's API so an AI model can read the spreadsheet and choose the dashboard's analytical ideas. Sagacium separately parses the same file on the Sagacium server and calculates the plotted chart values from the source data rather than trusting model-generated numbers.

The raw CSV or XLSX file is not stored in your Sagacium workspace after the request completes. Sagacium stores the generated chart specifications, calculated chart data, lock state, model-generation metadata, and basic file metadata so the dashboard can be reopened. If you later use Try Again after leaving the session, you must re-upload the same source file because Sagacium does not retain it.

If you use What this means, Sagacium sends the saved Customer Intelligence brief and the saved calculated customer sales dashboard to OpenAI's API so an AI model can identify evidence-backed observations across the two. This step does not perform new web research and does not require the raw CSV or XLSX file. The combined observations are stored in the customer workspace and are tied to the specific customer brief and dashboard generation used to create them.

If you use Growth Opportunities, Sagacium sends the saved Customer Intelligence brief, saved calculated sales dashboard, and current What this means synthesis to OpenAI's API so an AI model can generate commercial hypotheses such as whitespace, cross-sell, expansion, decline, concentration, retention, or timing opportunities. Growth Opportunities does not perform a new web search and does not receive the raw CSV or XLSX file. Generated opportunities are stored in the customer workspace and are tied to the exact evidence versions used to create them.

If you create an Account Plan, Sagacium assembles an editable starting point from information already stored in the customer workspace, such as the current relationship, connected insights, growth hypotheses, validation questions, recommended actions, and meeting preparation. Account Plan creation does not make an additional AI request. The plan you save, including your seller-defined objective and edits, is stored in the customer workspace together with identifiers for the evidence that originally seeded it. Sagacium also stores a compact evidence catalog for supported seeded statements, including source titles and URLs, sales-chart titles and calculation descriptions, connected-insight labels, and Growth Opportunity labels. These references remain tied to the original plan evidence even if newer account evidence is later generated. Sagacium also stores a separate evidence-review checkpoint containing the account-evidence version identifiers you have explicitly marked as reviewed and the time of that review. Updating this checkpoint does not change the Account Plan or replace its original provenance. Later changes to account evidence do not silently rewrite your saved plan.

If you use Actions & Ownership, Sagacium stores the action text, owner name or role you provide, status, optional target date, optional notes, and the Account Plan section or item you link it to. This execution layer does not make an AI request. Completing or updating an action does not automatically change the Account Plan, confirm a growth hypothesis, or rewrite customer intelligence.

Do not enter passwords, payment information, sensitive personal information, or confidential customer information that you are not authorized to provide. Sagacium does not send your Sagacium password to the AI research service.

Authentication provider

Supabase processes authentication information needed to create and secure your account, including credentials, verification messages, recovery requests, and authentication tokens. Sagacium uses those tokens only to establish and maintain your signed-in session.

Cookies

When you sign in, Sagacium sets first-party, HTTP-only authentication cookies so your account remains signed in. They are used for account authentication only and are not advertising or cross-site tracking cookies.

Account deletion

You can delete your account from the account menu. This removes your Sagacium profile, portal preferences, My Company profile, workspaces, saved customer briefs, saved meeting briefs, saved analytics results, saved combined customer insights, saved growth opportunities, saved account plans, saved account actions, likes, saves, and follow relationship and removes your authentication account. Anonymous aggregate activity, such as a share recorded without an account, is not tied to your profile.

Contact

If you have questions about how your information is handled, use the contact form on the home page.