Privacy policy
Last updated: September 5, 2026 · Effective: August 28, 2026
This policy covers everything LifQ operates: the lifq.ai website, the beta waitlist, and the LifQ application itself, meaning the documents you upload, the information we draw from them, and the household features built on them. One policy, the whole service. Short notices inside the app explain things at the moment they matter. They summarize this policy and never replace it.
Some of what we handle is consumer health data, which carries extra protections under Washington and Nevada law and additional rights in California. Our consumer health data privacy policy explains what we treat as health data and the specific rights that attach to it. During the private beta, LifQ is available to residents of Nevada, Texas, Virginia, New Jersey and Pennsylvania. Where laws differ, we build to the strictest standard that applies to us, today that is Nevada’s SB 370, and we extend those protections to everyone who uses LifQ. In places this policy goes further than any single state requires, and where it does, the commitment here is what binds us.
1. Who this service is for
LifQ is for adults 18 and over. During the private beta, access is by invitation and is limited to residents of Nevada, Texas, Virginia, New Jersey and Pennsylvania. Parents and legal guardians may add documents relating to their dependents. Adding documents about another adult works differently, see section 10.
2. What we collect
When you apply for the beta. Your first and last name, and your email address. That is everything the waitlist collects.
When you use the LifQ application. Your account details (name, email, password handled by our authentication provider), the documents you choose to submit through enabled LifQ features, the information LifQ extracts from those documents (coverage details, dates, amounts, benefit descriptions), the household members you invite and the permissions you set, your questions to the LifQ Assistant, and records of account activity, including access logs that show who in your household viewed or changed what.
When you browse the website. Standard web analytics: pages viewed, approximate location from IP address, device and browser type, and how you arrived. Our hosting provider keeps short-lived server logs that include IP addresses.
What we deliberately do not collect. Bank logins, card numbers, or account credentials for any of your providers, ever. The free tools on the website run entirely in your browser; nothing you enter there is sent to us. We do not load third-party analytics or session recording on the beta application, the tools pages, or inside the LifQ application.
3. How we use it
We use your information to provide the service you asked for: storing your documents securely, producing plain-language summaries, showing your household’s coverage side by side, sending the reminders you enable, and operating household sharing. We use beta applications to manage the waitlist and contact you, and website analytics to understand which pages are useful. In aggregate, de-identified form (section 12), we use data to understand how LifQ is used and to report honestly about the product. That is the complete list. We do not use your information for advertising or profiling, and we do not use it for any purpose incompatible with the ones described here without asking you first.
4. How AI processing works
LifQ uses large language models to read the documents you submit and restate them in plain language. Here is exactly how that works, including the limits.
- A PDF that already carries readable text is parsed on our own systems. Nothing about it goes to an outside text-extraction provider.
- A photo you take goes to Google Cloud Vision to have its text extracted. So does a PDF that turns out to be a scan rather than text, or that our own parser cannot read: Vision receives it as an image, a scanned PDF one rendered page at a time. Vision extracts text and does nothing else with it.
- The extracted text is then processed by Anthropic and OpenAI to produce your summaries.
- Each of those three providers is bound by contract to process only on our instructions, and is prohibited from using your content for its own purposes.
- Your documents are not used to train general-purpose AI models, ours or anyone’s, without your separate, affirmative opt-in. No such training happens by default, and declining costs you nothing.
- We treat what we extract from your documents, and everything derived from it, as consumer health data, and we do not claim anything is de-identified unless it meets the law’s strict de-identification standard.
5. Household sharing
An account holder can invite up to six household members and set what each can see, change that at any time, and revoke access entirely. Two commitments come with this.
- Every adult controls their own data. An invited adult must accept the invitation, and the privacy terms, before documents about them are read or shared. One adult cannot consent on behalf of another adult, full stop. Guardians may act for their dependents where the law permits.
- Sharing is auditable. Household members can see who accessed which shared documents and when access was granted or revoked. Nothing moves silently.
LifQ does not currently offer emergency, incapacity, or after-death access mechanisms. If we build one, it will require explicit advance designation by you, document-level scoping, verification, and audit logging, and this policy will be updated before it launches.
6. Who else touches your data
We use a small number of service providers, each handling data only on our instructions and each bound by contract to the commitments in this policy: Supabase (application data and document storage), Vercel (website hosting and server logs), Resend (transactional email), Cloudflare Turnstile (form abuse prevention), CookieYes (cookie consent, section 15), our AI processing providers (Anthropic and OpenAI for summaries, and Google Cloud Vision for extracting text from photos and scanned PDFs, section 4), and website-only analytics providers (PostHog, Google Analytics, Microsoft Clarity, Vercel Analytics), none of which run on the application or tools pages. We update this list before adding a provider that will touch customer content.
If LifQ is ever acquired or merges, your information may transfer to the successor, who will be bound by this policy’s commitments, and we will notify you directly before the transfer takes effect, with a real opportunity to delete your data first.
We disclose personal information in response to legal process only when legally required, we notify you before doing so unless the law prohibits it, and we push back on overbroad requests.
7. What we never do
We do not sell your personal information or your documents. We do not share them with insurers, brokers, agents, quote services, data brokers, or advertisers. LifQ has no business relationship with any insurance carrier and receives no commissions or referral fees. Our only revenue is the subscription you pay, which is deliberate: it means no one else is paying for access to you. We do not run advertising pixels or remarketing. We do not use dark patterns to obtain consent: no pre-ticked boxes, no consent bundled into terms-of-service acceptance, no design that nudges you toward sharing more than you intend. And because we never sell or share data for advertising, opt-out preference signals like Global Privacy Control are honored automatically. There is nothing for them to switch off, and we treat them as a formal opt-out anyway.
8. Consent for health-related data
Documents like health insurance policies and explanations of benefits are consumer health data under Washington and Nevada law. Before LifQ first processes a health-related document of yours, we ask for your affirmative consent in a separate, plainly worded step, not buried in sign-up. You can withdraw that consent at any time, and withdrawal stops further processing without affecting anything else in your account. The consumer health data privacy policy covers this in detail, including the additional rights Washington, Nevada, and California residents hold.
9. Security
Application data is stored with row-level security, so every record is scoped to the household it belongs to, and is encrypted in transit and at rest. Documents are held in encrypted storage. Section 4 names every provider that receives document content and says what each one does with it. Access within LifQ is limited to the people who need it to operate the service, and internal access to customer content is logged.
LifQ is not a HIPAA-covered entity and does not claim to be. HIPAA governs healthcare providers, health plans, and their business associates. It does not apply to a tool you use on your own information. The protections described here are the ones that actually apply.
If a security incident affects your information, we will notify you without unreasonable delay, consistent with applicable law, and tell you plainly what happened, what was involved, and what we are doing about it. We do not disclaim that responsibility, in this policy or anywhere else.
10. Retention and deletion
- Active data. When you close your account or ask us to delete your data, your uploaded documents and the information extracted from them are deleted within 30 days, and our processors are instructed to delete their copies concurrently.
- Backups. Encrypted backups expire on a rolling schedule and are fully purged within 90 days at most. Our internal target is faster. Backups are restored only for disaster recovery, and anything restored that should have been deleted is re-deleted.
- What we keep. Only narrow records we genuinely need: billing records for tax and accounting, security logs for fraud prevention, and records the law requires, each kept only as long as its purpose requires, then deleted.
- Beta applications. Kept while the waitlist is open and for a reasonable period afterwards. Ask and we delete yours, including from our email records.
We do not retain your personal information indefinitely after you leave, and we take no license to your documents beyond what operating the service requires.
11. Your rights, and how they actually work
Wherever you live, you can ask us to show you what we hold about you, correct it, delete it, or give you a copy, and you can withdraw consent for health-data processing at any time. Email privacy@lifq.ai and we will respond within the timeline your state’s law sets, and within 45 days everywhere else. We verify requests to protect you (typically by confirming control of the account email; we may ask for more for sensitive requests), and you may use an authorized agent, whose authority we will verify. If we refuse a request, we will explain why, and you have the right to appeal. Reply to our refusal and a different reviewer will decide. If the appeal fails, we will point you to your state attorney general. We will never treat you differently for exercising any of these rights.
12. De-identified and aggregate data
When we talk about usage in aggregate, “how many households found a forgotten benefit,” for instance, we use data that has been de-identified so it cannot reasonably be linked back to you or your household. We commit to never attempting to re-identify de-identified data, and we require the same of anyone we share it with.
13. Children
LifQ is not intended for anyone under 18, and we do not knowingly collect information from children. Guardians may store documents relating to their dependents within their own account. If you believe a child has submitted information directly, email us and we will delete it.
14. Changes
If we change this policy, we will update the date above. For changes that affect how we handle information you have already given us, we will contact users and applicants directly and, where the change involves a new use of existing data, ask rather than tell. New collection channels or materially new uses are added to this policy before they launch, not after.
15. Cookies and similar technologies
We use a consent manager, CookieYes, to ask before any non-essential cookie is set and to keep a record of what you chose. It blocks the scripts in question until you answer, so declining is not a preference we honor afterwards, it is a script that never runs. Your choice is stored in a first-party cookie so we can tell, on your next visit, what you already decided.
Strictly necessary cookies are exempt from that prompt and always set: they carry your session, your consent record itself, and the abuse prevention on our forms. Nothing in that category is used to profile you. CookieYes receives your IP address and consent state in order to do this job, and nothing else. It never runs on the free tools, whose inputs stay in your browser.
You can change your mind at any time, and separately from anything else in your account.
16. Contact
LifQ is operated by Pakal Systems LLC. For privacy questions or to exercise any right: privacy@lifq.ai. Washington and Nevada residents can also find their state-specific contacts and appeal routes in the consumer health data privacy policy.
Pakal Systems LLC9101 W Sahara Ave, Suite 105 PMB 1513Las Vegas, NV 89117United States