Privacy Policy
Last Updated: 7 November 2026
At Lucius AI Systems, Inc. ("Lucius AI", "we", "our", or "us"), we are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Forensic Tender Audit services (the "Service"). Please read this Privacy Policy carefully. If you do not agree with the terms of this Privacy Policy, please do not access the Service.
1. Information We Collect
1.1 Personal Information
We collect information that you provide directly to us, including:
- Name, email address, and contact information when you create an account
- Payment information processed through Stripe (we do not store credit card details)
- Company information, including name, industry, and tender preferences
- Communications with us, including support requests and feedback
- Your email address, if you sign up for our monthly newsletter, with where and when you signed up and when you confirmed.
1.2 Tender Documents
When you upload tender documents for analysis, we process these documents to provide our services. This includes:
- PDF files containing tender specifications and requirements
- Metadata associated with uploaded files (file names, sizes, upload dates)
- Analysis results and compliance matrices generated from your documents
1.3 Automatically Collected Information
We automatically collect certain information when you use our Service:
- Device information (IP address, browser type, operating system)
- Usage data (pages visited, features used, time spent)
- Cookies and similar tracking technologies
2. How We Use Your Information
We use the information we collect to:
- Provide, maintain, and improve our Service
- Process and analyze tender documents you upload
- Process payments and manage subscriptions
- Send you technical notices, updates, and support messages
- Respond to your comments, questions, and requests
- Monitor and analyze usage patterns and trends
- Detect, prevent, and address technical issues and security threats
- Send you our monthly newsletter, The tender market this month, only if you asked for it and confirmed your email address. We rely on your consent, and you can withdraw it at any time with the one-click unsubscribe link in every issue or in Settings.
3. Data Security & AI Processing
How We Handle Your Tender Documents
Your tender documents are stored securely in your workspace. We do not use your private data to train our AI models (LLMs). Your documents are:
- Encrypted in transit using TLS/SSL protocols
- Encrypted at rest using industry-standard encryption
- Kept in your workspace until you delete them (a document you try without an account is deleted after 7 days unless you save it to one)
- Stored on Google Cloud in the EU, encrypted at rest, with each workspace's data kept separate and access limited by role
- Never used to train or improve AI models without explicit consent
Our staff open a workspace's documents, analyses or assistant conversations only to provide support you ask for or to investigate and fix a problem with the Service, and only for as long as that takes.
4. Data Sharing and Disclosure
We do not sell, trade, or rent your personal information to third parties. We may share your information in the following circumstances:
- Service Providers: We may share information with third-party service providers who perform services on our behalf (e.g., cloud hosting, payment processing, email delivery)
- Legal Requirements: We may disclose information if required by law or in response to valid requests by public authorities
- Business Transfers: In the event of a merger, acquisition, or sale of assets, your information may be transferred
- With Your Consent: We may share information with your explicit consent
5. Your Rights (GDPR Compliance)
If you are located in the European Economic Area (EEA) or United Kingdom, you have certain data protection rights:
- Right to Access: Request copies of your personal data
- Right to Rectification: Request correction of inaccurate or incomplete data
- Right to Erasure: Request deletion of your personal data ("right to be forgotten")
- Right to Restrict Processing: Request restriction of processing your personal data
- Right to Data Portability: Request transfer of your data to another service
- Right to Object: Object to processing of your personal data
- Right to Withdraw Consent: Withdraw consent at any time where we rely on consent
To exercise these rights, please contact us at contact@ailucius.com.
6. Data Retention
We retain your personal information for as long as necessary to provide our Service and fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law.
Tender documents you upload to your account stay in your workspace until you delete the tender or your account. Deleting a tender removes its document and our AI provider's cached copy of it straight away; our storage can still recover a deleted file for 7 days, after which it is gone. Separately, Google may keep recent AI requests in its own cache for up to 24 hours to speed up repeat analysis; that copy is encrypted, kept per project, and never used to train Google's models. A workspace admin can also set a retention period of 30 to 3,650 days, after which older tenders are deleted automatically every night. A document you try without an account is deleted after 7 days unless you save it to an account.
If you unsubscribe from the newsletter we keep only your email address and the date, so that we do not email you again. Deleting your account deletes your newsletter record.
7. Cookies and Analytics
Signing in sets one cookie that keeps you signed in. If you are not signed in, nothing else is set until you choose on the cookie banner; what applies to a signed-in account is described at the end of this section.
Every visit is counted by PostHog without cookies and without storing anything in your browser: the pages you view, how quickly they load and what you click, under a code that PostHog's servers work out from your IP address and browser and change every day, so a visit is not linked to you or followed from one day to the next. PostHog does not keep the IP address. This happens whatever you choose on the banner; session replays and everything described next run only if you accept, or, for a signed-in account, as described at the end of this section.
If you accept, we use two analytics tools in full. PostHog keeps an identifier in your browser so it can follow how the product is used across visits, and records session replays in which the text of your tender documents, your drafts, every form field and the page title are masked before they leave your browser. Google Analytics runs through Google's own tag, which your browser loads only after you accept: it records page views, how you arrived (for example from a search engine or a link) and the events we send it, under an identifier kept in a cookie on our site for up to 13 months so that a return visit counts once. The tag sets no advertising cookies. Google receives your IP address with each request so it can work out your approximate location; Google Analytics does not store it. If your browser blocks Google's tag, page views and events reach Google Analytics through our own server instead, with an identifier kept in your browser, and our server passes your IP address on for the same purpose. Before you choose, nothing is sent to Google Analytics: our server only notes that the cookie banner was shown and what you chose, with the page you arrived on, the site that sent you and your browser type, but no analytics identifier.
We also use Sentry to find errors in the app. When something breaks, Sentry receives a technical report: the page, the browser and the error. It sets no cookies. Under the same choice as PostHog, Sentry also keeps a short replay of the session, with all text masked and all images and media blocked, so we can see what went wrong.
If you arrive through a link that carries a referral code (a web address ending in ?ref= and a code), we pass that code along when you create an account, so the person or partner who shared the link is credited for your signup. The code identifies whoever shared the link, not you. If you accept, we keep it in your browser in a cookie called lucius_ref for up to 60 days, so the credit still applies if you sign up on a later visit. If you decline or do not choose, nothing is stored: the code is kept only while the page is open.
When you create an account, we keep with it where your visit came from: the path of the page you first arrived on, the name of the site that sent you (for example www.google.com, never the full address of the page), the campaign tags in the link you followed (its utm_ values), whether you came from a paid search ad (only yes or no, never the ad's click code), the kind of visit (for example a search, a link from another site, or typing our address) and when it happened. We use this to learn which pages and searches lead to signups and payments. It is sent when you create an account unless you declined analytics on the banner, and our server keeps it only for a new account. The same details, with where your most recent visit came from, are attached to the signup event in PostHog and, if you accepted, in Google Analytics, and our server adds what it kept with your account to its own signup and payment records in PostHog.
Before you choose, these details are kept only while the page is open. If you sign in with Google or Microsoft before choosing, they travel inside the sign-in request (in its state value) to Google or Microsoft and come back to us with the sign-in, because that round trip reloads the page; a referral code travels the same way, and an ad's click code never does. If you accept, we keep them in your browser under lucius_first_touch for up to 60 days from your first visit. If you decline, they are deleted from your browser and nothing is sent. They are also deleted from your browser when you sign in to an account you already have.
If you arrive from a Google ad, the link carries Google's click code (gclid, gbraid or wbraid). If you create an account, we send that code to our server so that the signup can be reported to Google Ads as coming from that ad. Before you choose, the code is kept only while the page is open. If you accept, we keep it in your browser under _ads_click for up to 90 days, and _ads_click_sent once our server has it. If you decline, both are deleted and the code is not sent.
After a payment, so that the same payment is not counted twice in our analytics, your browser keeps a short code made from the checkout under lucius_reported_checkouts, for your last 20 payments. Stripe's reference for the payment cannot be read back from it, and our analytics receive the same short code instead of that reference. This is kept for a signed-in account that has not declined; after a decline nothing is kept.
If you decline, no analytics cookie is set: PostHog only counts the visit as described above, Sentry's replay does not run and nothing is sent to Google Analytics. Sentry's error reports still run, because they are how we keep the Service working. Accounts are covered by the Terms accepted at signup: for a signed-in user who has not chosen, PostHog keeps its identifier in the browser, links what they do in the product to their account and records masked session replays, and Sentry keeps its masked replay, unless they decline on the banner or under Cookie preferences in the account menu. Google Analytics is not part of this: it runs only after you accept, signed in or not. Your choice is kept for a year in your browser and can be changed by clearing the site's cookies.
8. Children's Privacy
Our Service is not intended for individuals under the age of 18. We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal information, please contact us immediately.
9. International Data Transfers
Your information may be transferred to and maintained on computers located outside of your state, province, country, or other governmental jurisdiction where data protection laws may differ. By using our Service, you consent to the transfer of your information to our facilities and those third parties with whom we share it as described in this Privacy Policy.
10. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date. You are advised to review this Privacy Policy periodically for any changes.
11. Contact Us
If you have any questions about this Privacy Policy, please contact us:
- Email: contact@ailucius.com
- General Inquiries: contact@ailucius.com