01
Who we are and scope
TacticSpace Tech ("TacticSpace", "we", "us") operates Lumo and is the data controller for the personal information described in this policy unless a different role is stated.
This policy covers Lumo apps, our website and account services, cloud and connected-device features, billing, transactional communications, and customer support. It does not replace the privacy terms of third-party services you independently select or visit.
02
Information we collect
The exact data depends on the product, features, account state, and device you use. We collect information you provide, information generated through use, and limited information from service providers.
Account and subscription
Email address, internal user ID, authentication and verification status, profile fields you provide, plan, entitlement, and subscription status. Stripe processes payment-card details; we receive transaction and billing status rather than full card numbers.
Device, network, and technical data
IP address when needed for delivery and security, browser, operating system, device model, app version, locale, time zone, referrer, device or browser identifiers, connection state, performance timings, and crash or error diagnostics.
Product usage and interactions
Pages and screens viewed, navigation paths, clicks, feature entry and completion, connection lifecycle, task and tool actions, permission outcomes, model and provider choice, session timing, funnels, and timestamps. Signed-in activity may be associated with your account.
Content and AI requests
Prompts, messages, documents, files, images, audio, selected context, generated output, and related request metadata when you use AI or cloud features. Content processing is explained separately below and is not the same as product analytics.
Support and communications
Your name, email, subject, message, attachments, diagnostic information you choose to provide, and our correspondence with you.
Push and connected-device data
Apple Push Notification service tokens, device registration and channel state, connection identifiers, and delivery or revocation status needed to connect Lumo across your devices.
Cookies and similar identifiers
Local storage, first-party cookies, and analytics identifiers used to remember language and privacy choices, maintain sessions, measure journeys, prevent abuse, and recognize a browser over time.
03
Product analytics and diagnostics
Enabled by default
Lumo product analytics and diagnostics are enabled by default. This helps us measure adoption, understand journeys and funnels, prioritize features, detect failures, improve performance, and protect the service. Where applicable, you can turn optional analytics off without losing core product access.
Signals may include screen and page views, navigation, clicks, feature use, task and connection milestones, permission outcomes, model or provider selection, app and OS version, device class, timestamps, latency, token and cache counts, session duration, acquisition source, crashes, and scrubbed error messages or stack traces. Some activity is pseudonymous; when you sign in, related events may be associated with your account and email to support cross-device funnels, service support, and subscription analysis.
On the website, we also use automatic interaction capture, heatmaps, and session replay. Replay can show page layout, pointer movement, scrolling, and interactions. We configure input masking and blocked elements so typed form values and sensitive fields are not recorded.
Excluded from product analytics
- Prompt and chat text
- Document and file contents
- API keys, tokens, and credentials
- Typed support-form values
- Generated image, audio, or document contents
- Payment-card numbers
This exclusion applies to product analytics. Content may still be processed separately when you ask Lumo to perform an AI or cloud task, as described next.
04
AI and cloud processing
When you ask Lumo to perform an AI task, the prompt, selected context, attachments, and related instructions are sent to the provider and infrastructure selected for that workflow. The provider returns generated content to Lumo. Local or bring-your-own-provider configurations can change which party receives the request.
Our cloud service may keep a short-lived troubleshooting copy of request and response bodies, including successful, failed, or interrupted requests, for up to 14 days. These copies help investigate reliability, abuse, billing disputes, and support cases. Request metadata such as model, provider, token counts, latency, cache use, status, and error category may be retained separately for longer operational analysis.
We do not intentionally send prompt, response, document, or file contents to PostHog, Google Analytics, or Vercel Analytics. Third-party AI providers process content under their own terms and privacy notices, so review the provider terms applicable to your configuration.
05
How and why we use data
- Provide accounts, AI features, cloud connections, synchronization, push delivery, billing, and support.
- Understand product adoption, journeys, retention, feature performance, and subscription conversion.
- Monitor availability, diagnose failures, improve speed and quality, and prevent repeated errors.
- Detect fraud, abuse, unauthorized access, and threats to users or the service.
- Communicate about verification, transactions, security, service changes, and support requests.
- Meet accounting, tax, legal, regulatory, and enforcement obligations.
Depending on the context and applicable law, we rely on performance of a contract, our legitimate interests in operating and improving Lumo, consent where required, and compliance with legal obligations. We balance legitimate interests against the impact on your rights and provide controls where appropriate.
07
Retention
We retain information for the shortest period that reasonably supports the purpose, then delete, de-identify, or aggregate it. The periods below describe current operational rules and may be shortened when data is no longer needed.
Cloud request and response troubleshooting copies
Up to 14 days
Short-lived copies are kept to investigate failed, incomplete, or disputed requests.
Usage, media, request-run telemetry, and client app logs
Generally up to 90 days
Used for reliability, security, support, metering, and product analysis.
Push registration and channel records
90 to 365 days
Inactive device tokens may remain for up to 90 days; revoked-channel security records may remain up to 365 days.
Account and user content
While the account is active
Deleted when you delete the account, subject to backups, security records, legal obligations, and third-party processing already initiated.
Analytics platform data
Configured service retention
Kept only as long as reasonably needed for trend, funnel, reliability, and security analysis, then deleted or aggregated.
Billing and support records
As required for the relationship and law
Some transaction, fraud-prevention, tax, and correspondence records may outlast an account.
08
Security and international transfers
Technical and organizational safeguards
We use HTTPS/TLS in transit, access controls, credential separation, monitoring, data minimization, and retention controls appropriate to the service. No system can guarantee absolute security.
International processing
Our providers may process data in countries other than where you live. We use provider commitments, contractual protections, and other lawful transfer mechanisms when required.
09
Your choices and rights
You can switch this website to essential-only data using Privacy choices. In Lumo for iPhone or iPad, open Settings > Privacy & Data and turn off Share Product Analytics. Other Lumo clients may offer equivalent controls in Settings. Browser-level Do Not Track is also respected by our PostHog configuration.
Depending on your location, you may have rights to request access, correction, deletion, restriction, portability, or objection; withdraw consent where processing relies on consent; and complain to a local data-protection authority. We may verify your identity before completing a request, and lawful exceptions may apply.
Deleting local content removes it from that device. Deleting an account initiates deletion of associated account data from our active systems, subject to the retention and legal exceptions described above. Third-party providers may have separate deletion procedures.
10
Children
Lumo is not directed to children under 13 or the higher minimum age required to consent to data processing where they live. We do not knowingly collect personal information from a child below that age. A parent or guardian who believes a child provided information should contact us so we can investigate and delete it where required.
11
Changes and contact
We may update this policy when our products, providers, or legal obligations change. We will update the effective date and provide additional notice in the product or by email when a change is material and notice is required.
For privacy questions or requests, contact:
TacticSpace Tech
[email protected]
This policy describes our current product and operating practices. It is not a promise that every data category is collected in every Lumo client or session.