1. Our Local-First Privacy Principle
Luci is designed so that your private workspace information is primarily processed and stored on devices you control.
In ordinary use, Divine Automation does not receive or maintain a centralized copy of your private emails, messages, conversations, calendar contents, documents, voice transcripts, notes, tasks, contacts, relationship information, or other personal workspace content merely because you use Luci.
Luci may connect directly from your device to services you authorize, such as Google, Microsoft, Apple, LinkedIn, or other services. Those connections may cause information to travel between the applicable provider and your device without that information passing through or being stored by Divine Automation.
Where Luci must communicate with Divine Automation infrastructure for functions such as licensing, activation, software updates, security, or explicitly requested diagnostics, those systems are designed not to receive your private workspace content unless you deliberately submit specific information for support or diagnostics.
2. Information Luci May Process on Your Device
Depending on the features you enable and permissions you grant, Luci may locally process the following categories of information.
Communications
- Email messages and associated metadata.
- Authorized LinkedIn information.
- Messages from supported communication platforms.
- Senders and recipients.
- Message dates and times.
- Subjects and conversation topics.
- Attachments that you choose to make available.
- Follow-up status.
- Commitments, requests, and action items identified from communications.
Luci may analyze this information to help you understand conversations, identify relevant people, prepare responses, create tasks, identify commitments, organize follow-ups, and maintain useful context.
People and Organizations
Luci may maintain a local People and relationship system containing information such as names, organizations, job titles, contact information, relationships, meetings, communications, notes, projects, commitments, follow-ups, user-entered information, and context derived from sources that Luci is authorized and permitted to process.
Luci may associate information from multiple user-authorized sources with a person or organization when doing so is permitted by the terms governing those sources.
Calendar and Scheduling Information
If you authorize calendar access, Luci may process event titles, dates and times, locations, attendees, event descriptions, meeting links, recurrence information, availability, and related tasks, projects, people, notes, and commitments.
Luci may use this information for scheduling assistance, Today views, meeting preparation, reminders, conflict identification, and contextual recommendations.
Contacts
If you authorize contacts access, Luci may process contact information such as names, phone numbers, email addresses, organizations, and other contact fields made available through the operating system or connected provider.
Notes, Tasks, Commitments, Projects, Goals, and Decisions
Information you create in Luci may be locally stored and connected to other relevant information so Luci can maintain continuity across conversations and over time.
Documents and Files
If you authorize Luci to access specific files, folders, document repositories, or other data sources, Luci may process the contents and metadata of those resources for the feature you requested. Luci does not obtain permission to unrelated files merely because you authorize access to a particular file, folder, repository, or source.
Voice, Microphone, and Listening Information
When you enable voice or listening features, Luci may locally process microphone input for speech recognition, transcription, voice commands, wake-word detection, conversation organization, speaker differentiation where supported, notes, tasks, commitments, and meeting context.
Listening functionality is subject to the permissions and controls made available through Luci and the operating system. Where wake-word functionality is enabled, temporary on-device audio processing may occur for the purpose of identifying the wake phrase. Such processing is not intended to create a permanent recording unless a feature specifically allows recording and the user chooses to use that feature.
Raw audio is not transmitted to Divine Automation merely because Luci performs local voice processing.
Users are responsible for obtaining any consent required by applicable law before recording, transcribing, or analyzing conversations involving other people.
Screen, Browser, and Workflow Context
If you explicitly enable workflow observation, screen-related features, browser integrations, accessibility features, or similar capabilities, Luci may process information necessary to provide those features. This may include information about the application or website currently being used, workflow steps, selected content, or other user-authorized context.
Luci is designed to provide visible controls for enabling, pausing, or disabling observation features. Luci does not use these capabilities for advertising or covert surveillance.
Camera and QR Pairing
Luci may use your device camera when you request features such as QR-code scanning, device pairing, document capture, or another camera-based feature. Camera access does not authorize Divine Automation to remotely access your camera. Camera information used solely for scanning a QR code does not need to be retained as a photograph.
Device and Local Network Information
For device pairing, synchronization, security, and connectivity, Luci may locally process technical information such as device identifiers generated for Luci, device public keys or fingerprints, device names, network addresses, local network discovery information, connection state, synchronization state, application version, and operating-system information.
3. Artificial Intelligence Processing
Luci is designed to use artificial intelligence to understand information and provide user-facing assistance. This may include categorization, semantic search, entity recognition, relationship identification, conversation continuity, summarization, draft generation, task identification, commitment identification, meeting preparation, recommendations, contextual question answering, and workflow assistance.
Private Workspace Data is not used by Divine Automation to train a shared or general-purpose artificial intelligence model merely because you use Luci.
Luci does not sell your private information for AI training.
Where Luci's local AI capabilities are used, processing occurs on hardware controlled by the user. If Luci ever offers an optional feature that sends private information to an external AI provider, that feature must identify the external processing before transmission and obtain any consent required for that use. Enabling such an optional feature does not authorize unrelated transmission of other Luci information.
4. Connected Accounts and OAuth
Luci may allow you to connect third-party services using OAuth, operating-system authorization, or another provider-approved authorization mechanism.
Luci does not require you to provide your third-party account password directly to Divine Automation when OAuth or another provider authorization system is used.
Authorization credentials, access tokens, refresh tokens, or equivalent credentials are stored using appropriate secure storage mechanisms available on the relevant device or operating system where supported.
Luci requests access only to permissions reasonably necessary for the features being enabled.
Disconnecting an integration removes Luci's authority to continue accessing that account through the disconnected authorization. You may also be able to revoke Luci directly through the applicable provider's account-security or connected-app settings.
5. Google and Google Workspace Data
If you connect a Google account, Luci may access only the Google information authorized by the permissions you approve.
Depending on the features you enable, this may include authorized Gmail, Calendar, Contacts, Drive, or other Google Workspace information.
Google information may be processed to provide features such as email intelligence, search, draft assistance, follow-up identification, meeting preparation, calendar assistance, contact and People context, task and commitment identification, and user-requested actions.
Luci's use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Google user data will not be sold, used for advertising, provided to data brokers, used for surveillance, used to determine creditworthiness or lending eligibility, or used to train or improve a generalized AI model unrelated to the individual user's Luci experience.
Divine Automation employees, contractors, or other humans do not routinely read users' Google Workspace content.
A user may explicitly submit specific information to Divine Automation for troubleshooting or support. When that occurs, Divine Automation will process only the information voluntarily provided for the relevant purpose.
6. LinkedIn Data
If Luci offers a LinkedIn integration, it will access LinkedIn information only through interfaces, APIs, permissions, and programs authorized by LinkedIn and made available to Luci.
Luci will not request or collect your LinkedIn password.
Before Luci accesses LinkedIn information, you will be informed of the relevant access and asked to authorize the connection.
Depending on the specific LinkedIn APIs and permissions approved for Luci, authorized information may include member identifiers, profile information, account information, communications or messaging information where specifically authorized and available, and other information available through an approved LinkedIn API.
Where permitted, Luci may locally analyze authorized LinkedIn information to assist with People context, relationship context, conversation categorization, topics, follow-ups, tasks, commitments, meeting preparation, and user-requested drafting or responses.
Luci will not scrape LinkedIn or use unofficial methods to obtain LinkedIn content.
Luci will not persist, combine, transform, or derive information from LinkedIn content beyond what LinkedIn's applicable API terms, approved program, permissions, and any applicable additional terms expressly permit.
Where LinkedIn permits information to be stored, Luci will maintain that information in a manner that allows it to be identified and deleted as required.
When you revoke Luci's LinkedIn access, request deletion of LinkedIn-derived information, close your Luci account where applicable, or another deletion requirement under the applicable LinkedIn terms is triggered, LinkedIn information and authorization credentials will be removed as required by those terms and applicable law.
LinkedIn information will not be sold, rented, provided to data brokers, used for advertising, or used for surveillance.
7. Microsoft Data
If you connect a Microsoft account or organization, Luci may use Microsoft's authorized identity and API mechanisms to access only permissions that you or your organization approve.
Depending on the authorized features, Luci may process information from services such as Outlook email, calendars, contacts, Microsoft 365, or other Microsoft resources. The information is used to provide the Luci features for which access was granted.
Luci does not require Divine Automation to receive your Microsoft password.
8. Apple Data and Platform Permissions
On Apple devices, Luci may request operating-system permissions for features such as calendar, contacts, microphone, speech recognition, camera, local network, notifications, files, Bluetooth or nearby-device functionality where required, and location when a feature specifically requires location and you choose to enable it.
A permission is requested only when required by a relevant feature.
You can manage these permissions through Luci and/or your device's operating-system settings.
Information made available through an Apple permission remains subject to the scope and controls of that permission.
9. Cross-Device Synchronization
Luci may allow authorized devices to share approved context.
Synchronization may use technologies such as local-network communication, direct encrypted device connections, or other user-authorized networking methods.
Devices must be authorized before participating in a Luci private workspace. Pairing may involve QR codes, one-time pairing codes, cryptographic keys, device fingerprints, and explicit approval.
Device authorization is designed to prevent an unknown device from silently joining a private workspace.
Removing a device revokes its authorization to participate in future synchronization.
Data already present on a removed device should be deleted from that device through Luci's deletion controls or device-management process when appropriate.
10. Information Divine Automation May Receive
Although Luci's Private Workspace Data is designed to remain local, Divine Automation may receive limited information in specific situations.
Licensing, Activation, and Updates
Where a Luci build uses Divine Automation infrastructure for licensing, activation, entitlement validation, security, or software updates, limited technical information may be processed for those purposes.
Such information may include Luci version, platform, license or entitlement identifier, activation state, update state, security-related request information, and a pseudonymous installation or device identifier where required.
These systems are not intended to receive your private workspace contents.
Diagnostics and Support
If you explicitly create or submit a diagnostic report, crash report, screenshot, log, or other support material, Divine Automation receives the information you choose to submit.
Luci should provide the user an opportunity to review diagnostic information where technically feasible before intentionally submitting private diagnostic material.
Diagnostic information is used for support, debugging, reliability, security, and product improvement.
Submitting diagnostics does not authorize Divine Automation to independently browse your Luci workspace.
Communications With Divine Automation
If you contact Divine Automation directly, we may receive information you provide, including your name, email address, message, support request, and attachments.
11. Information We Do Not Sell or Use for Advertising
Divine Automation does not sell your Private Workspace Data.
Divine Automation does not rent your Private Workspace Data.
Divine Automation does not provide your Private Workspace Data to data brokers.
Divine Automation does not use your emails, private messages, documents, voice conversations, People relationships, tasks, calendar data, or other Private Workspace Data for targeted advertising.
Luci is not designed to build an advertising profile about you.
13. User Approval for Actions
Luci may offer the ability to take actions on your behalf.
Depending on the action and your settings, actions may require user approval before execution.
Examples may include sending communications, creating or changing appointments, modifying files, performing external workflows, sharing information, connecting services, and executing higher-risk actions.
Luci's privacy architecture is intended to preserve meaningful user control over external actions.
14. Automated Categorization and Recommendations
Luci may automatically classify information into categories such as People, Organizations, Conversations, Projects, Tasks, Commitments, Goals, Decisions, Meetings, Notes, Follow-ups, Topics, Documents, and Workflow observations.
These classifications are intended to assist the user and may be inaccurate.
Users may review, correct, remove, or reorganize information where the applicable feature permits.
Luci's categorization is not intended to make legally significant decisions about another person's eligibility for employment, credit, insurance, housing, or other regulated opportunities unless an expressly authorized feature and applicable law permit such use.
15. Data Security
Luci uses administrative and technical safeguards appropriate to its local-first design.
Depending on platform capabilities, these safeguards may include encryption of locally stored sensitive information, operating-system secure credential storage, encryption for network communications, cryptographic device pairing, device authorization, authentication tokens rather than account passwords, access controls, user approval mechanisms, isolation of private workspaces, and restricted diagnostic submission.
OAuth tokens and similar sensitive credentials should be stored using secure platform credential-storage mechanisms and encrypted where appropriate.
No software or security system can guarantee absolute security.
Users should protect their devices using operating-system security features such as passwords, passcodes, biometrics, encryption, updates, and appropriate physical security.
16. Retention
Private Workspace Data stored by Luci is generally retained on the user's authorized devices until the user deletes it, changes applicable retention settings, the related account or integration is disconnected and deletion is required, the Luci workspace is deleted, the device is securely reset or data is otherwise removed, or a source-specific contractual requirement requires earlier deletion.
Luci will not retain third-party integration information longer than the applicable provider's terms permit.
Information submitted directly to Divine Automation for support or diagnostics will be retained only for as long as reasonably necessary to resolve the request, protect the service, satisfy legal obligations, or maintain appropriate business records, after which it will be deleted or de-identified where appropriate.
Deletion from Luci does not necessarily delete the original information from the third-party service from which it came.
For example, deleting a local reference to an email does not automatically delete the original message from the user's email account unless the user specifically instructs and authorizes Luci to perform that action.
Information contained in device backups controlled by the user or operating-system provider may remain until those backups expire or are deleted according to the applicable backup system.
17. Your Privacy Controls
Luci is designed to give users control over their information.
Depending on platform and version, available controls may include viewing stored information, correcting information, exporting information, deleting information, removing People records, removing conversations, disconnecting integrations, revoking OAuth access, pausing observation, stopping listening, managing microphone permission, managing camera permission, managing calendar access, managing contact access, managing file access, managing connected devices, removing a paired device, reviewing synchronization state, reviewing diagnostic information, and deleting the private workspace.
You can also use operating-system settings and third-party provider settings to revoke permissions.
18. Privacy Requests to Divine Automation
You may contact Divine Automation to request information about personal information that Divine Automation itself maintains about you.
Depending on applicable law, you may have rights to request access, correction, deletion, or a portable copy; object to or restrict certain processing; withdraw consent; appeal certain privacy decisions; or obtain information about disclosure practices.
Because Private Workspace Data generally remains on your own devices, Divine Automation may not possess the information you are requesting. Where that occurs, we will explain that the data is locally controlled and direct you to available Luci controls when possible.
Divine Automation does not discriminate against users for exercising applicable privacy rights.
19. Disconnecting an Integration
You may disconnect a connected account through Luci where supported or revoke the application through the provider.
When an integration is disconnected, Luci will stop using the revoked authorization for future access, associated OAuth credentials will be deleted as required, locally retained provider information will be deleted where required by the provider's rules, the user's request, or applicable law, and information independently created by the user may remain where legally and contractually permitted.
20. Deleting Your Luci Data
Luci is designed to provide controls for deleting locally stored private information.
A deletion request made within Luci applies to Luci's copy of the information and does not automatically erase information independently held by Google, Microsoft, LinkedIn, Apple, another provider, another person, or a user-controlled backup.
For information held directly by Divine Automation, deletion requests may be submitted using the contact information below.
We may retain limited information when required by law, necessary to establish or defend legal claims, necessary for security, or otherwise permitted by applicable law.
21. Enterprise and Business Use
Organizations may deploy Luci for employees, contractors, or other authorized users.
Where Luci is provided through an organization, the organization may establish policies governing devices, integrations, information access, retention, and use.
The organization may independently have privacy obligations to its employees, customers, contacts, or other individuals whose information is processed through Luci.
Enterprise agreements may further define data-processing roles and responsibilities.
An organization does not receive private user information from Divine Automation merely because it licenses Luci unless the applicable configuration, agreement, and user authorization provide otherwise.
22. Information About Other People
Luci may process information concerning people other than the primary user because emails, messages, meetings, contacts, recordings, and documents naturally contain information about other individuals.
Users are responsible for ensuring that their use of Luci complies with applicable laws, agreements, workplace policies, confidentiality obligations, intellectual-property rights, recording-consent requirements, and privacy rights applicable to those individuals.
Luci should not be used to unlawfully surveil another person.
23. Children
Luci is a productivity and professional-assistant product and is not directed to children under 13.
We do not knowingly design Luci to collect personal information from children under 13 through a Divine Automation account service.
Where local law requires a higher age for independent consent, users below that age should use Luci only with authorization from a parent, guardian, school, organization, or other party legally permitted to provide that authorization.
24. International Users
Luci may be used in multiple jurisdictions.
Because its private workspace architecture is primarily local, Divine Automation generally does not centrally transfer users' Private Workspace Data merely because they use Luci.
Third-party providers you connect may process information in other countries according to their own infrastructure, terms, and privacy policies.
Where Divine Automation itself processes personal information subject to international privacy laws, it will process that information according to applicable legal requirements.
Where required by applicable law, the lawful basis for Divine Automation's processing may include performance of a contract, user consent, compliance with legal obligations, protection of security and legitimate interests, or another basis recognized by applicable law.
25. No Sale or Cross-Context Behavioral Advertising
Divine Automation does not sell Private Workspace Data.
Divine Automation does not share Private Workspace Data for cross-context behavioral advertising.
If applicable privacy law provides a right to opt out of sale or advertising-related sharing, Divine Automation's current local-first business model is designed so that Private Workspace Data is not used for those activities in the first place.
26. Security Incidents
If Divine Automation becomes aware of unauthorized access to information actually held by Divine Automation, we will investigate and take appropriate steps consistent with applicable law and contractual obligations.
Where legally required, affected users, regulators, integration providers, or other relevant parties will be notified.
A compromise limited to a user's own device may require action by the user because Divine Automation may not have access to or knowledge of local device activity.
Users should promptly remove unknown paired devices, revoke compromised integrations, and change affected account credentials when compromise is suspected.
27. Third-Party Services
Third-party services connected to Luci are independently operated.
Their privacy policies and terms govern their own processing of information.
Luci's Privacy Policy does not replace the privacy terms of Google, Microsoft, Apple, LinkedIn, telecommunications providers, operating-system providers, user-selected networking providers, or other services the user chooses to connect.
Connecting a provider authorizes only the access presented through the corresponding permission or authorization process.
28. Changes to This Privacy Policy
We may update this Privacy Policy as Luci evolves, laws change, integrations change, or privacy practices change.
The "Last Updated" date will identify the current version.
If a change materially expands how Divine Automation or Luci uses information, users will receive notice when required by applicable law or provider policy.
Where new consent is required before using Google, LinkedIn, or other third-party information for a materially different purpose, Luci will obtain that consent before beginning the new use.
Continued availability of an integration does not override a user's right to revoke authorization.
29. Contact Divine Automation
For questions, privacy requests, data deletion requests, access requests, complaints, or concerns regarding Luci or this Privacy Policy, contact:
Divine Automation LLC is a home-based business and does not publish a public residential street address for privacy and security reasons.
Privacy requests may be submitted electronically using the email address above.
For requests concerning information maintained independently by Google, Microsoft, Apple, LinkedIn, or another connected provider, you may also need to exercise your privacy rights directly with that provider.
30. Summary of Luci's Privacy Commitments
Luci is built around the principle that an AI assistant should work with a user's private information without requiring the developer of that assistant to possess that information.
- Your private workspace is designed to remain under your control.
- Private content is processed locally whenever Luci's local functionality supports it.
- Divine Automation does not routinely receive your private workspace content.
- Your private workspace information is not sold.
- Your private workspace information is not used for advertising.
- Your private workspace information is not provided to data brokers.
- Your private workspace information is not used to train a shared general-purpose AI model.
- Connected accounts require authorization.
- Luci requests only access needed for enabled functionality.
- High-impact external actions may require user approval.
- Users can disconnect integrations.
- Users can remove authorized devices.
- Users can delete locally stored information.
- Optional external processing must be disclosed when required.
- Third-party data is handled subject to the rules governing the applicable source.
- Users remain in control of whether Luci observes, listens, connects, synchronizes, or acts on their behalf.
Your data should serve you. Luci is designed so that Divine Automation does not need to own it, sell it, or centrally possess it in order to help you use it.