Trust & Privacy at Lumenfolk

Overview

We aim to collect the minimum useful data needed to make the product work, improve the experience, and respect user choices. Lumenfolk is currently in beta, and our public policy center is being updated as products move from prototype to public beta.

Privacy laws vary by location. This page is designed to help users understand and manage privacy choices. It is not a substitute for legal review.

Privacy choices

Essential functions always work. Analytics and personalization stay off until you turn them on.

Data we may collect

Categories below describe what may apply across Lumenfolk products. Not every product collects every category.

• Account data

  Required

  Identifiers needed to sign in and keep your account working.

• Usage data

  OptionalPersonalization

  Coarse signals like pages viewed and features used. No raw content.

• Consent preferences

  Required

  Your privacy choices, stored so we can respect them.

• Product inputs

  OptionalMay be sensitivePersonalization

  Things you type, select, upload, or paste into a product.

• Profile signals

  OptionalPersonalizationCross-product with consent

  Structured facts a product learns about your taste, fit, or context.

• Feedback & corrections

  Optional

  When you mark something wrong, suppress, or correct a signal.

• Recommendation interactions

  OptionalPersonalization

  What you opened, saved, dismissed, or asked to see less of.

• Contribution requests

  Optional

  Resources, sources, or examples you share back to improve products.

• Payment or inquiry intent

  OptionalPlanned / not currently collected

  When you start a checkout, demo, or inquiry flow.

How we use data

• To deliver core product functionality you asked for.
• To improve products with coarse, sanitized analytics — only with your consent.
• To personalize a product to your context — only with your consent.
• To respond to feedback, support, and inquiry requests.
• To meet security, fraud-prevention, and operational needs.

Analytics & personalization

We avoid sending raw private content or sensitive profile details to analytics. Analytics events use coarse categories, reason codes, counts, and consent-safe properties. Names, emails, phone numbers, uploaded content, and sensitive details are not sent.

Sensitive data

Sensitive context is optional unless required for the product to function. We aim to use the minimum information needed and avoid exposing sensitive details unnecessarily. We treat the following as sensitive by default: health, legal, financial hardship, child/family, precise location, identity/community, sexuality/gender/race/ethnicity/religion, biometric or ID-verification data, raw uploads, free-text private notes, mental health, employment vulnerability, and immigration/citizenship context.

User rights & requests

You can request to access, correct, delete, export, suppress, or restrict cross-product use of your data, opt out of sale/share/targeted advertising where applicable, limit sensitive data use where applicable, or ask a privacy question.

AI & automated assistance

Some product experiences may use AI or automated systems to summarize, rank, classify, parse, recommend, or generate drafts. AI-assisted outputs may be incomplete or wrong. Important outputs should be reviewed before relying on them.

• Not medical advice, diagnosis, or treatment.
• Not legal advice.
• Not financial advice.
• Not identity verification.
• Not a guarantee of outcomes.

Product profiles & CanonIQ

Product-specific profiles (Taste, Resource Fit, Work, Style, etc.) help a single product work better. They are not the same as the full CanonIQ. Full CanonIQ is a deeper personal context profile. No user receives the full CanonIQ output unless they purchase or are granted access to the full CanonIQ product. CanonIQ is not biometric authentication, legal identity verification, or a mental health diagnosis.

Contributions & user content

When you share feedback, sources, examples, or corrections, you help us improve products. We do not expose your private contributions publicly, and contributions are reviewed before they shape shared outputs.

Regional privacy readiness

We design our data systems around privacy-by-default principles, data minimization, consent controls, user correction, deletion/export request paths, sensitivity labeling, and regional privacy-readiness — including California, the European Union / EEA, South Korea, and Brazil.

Data processing and storage locations may vary by vendor and product.

Contact

For privacy questions or data requests, use the inquiry form.