Privacy Policy

Lucy is operated by Archworks Technologies Pte Ltd, a company incorporated in Singapore (UEN 202552318N).

Lucy is a voice-first Excel add-in with a companion website, Lucy Hub. It processes spoken instructions to update records in the workbook you have open. This policy describes the desktop Excel implementation being prepared for release and the website; it does not claim Marketplace approval or public add-in availability. Excel web and native Google Sheets are not currently offered.

For privacy questions or requests, contact our Data Protection Officer at colin@arcworkstech.com. Microsoft, Google and other services you use separately also have their own privacy notices.

• Account information. Microsoft or Google provides a sign-in identifier, name, email address and available email-verification information. Lucy stores linked identity details, account settings, access entitlements and session records to sign you in and manage your account. Lucy also records the Terms version you accept and when that acceptance is recorded after sign-in. Lucy does not receive your Microsoft or Google password.
• Microphone audio. When you explicitly start listening and grant microphone permission, audio travels through Lucy’s backend to Microsoft Azure Speech for live transcription. This includes silent intervals and any background voices picked up by your microphone. Stop listening when you do not want audio processed. Lucy’s application does not save raw audio recordings.
• Transcripts and worksheet context. Lucy processes recognized speech, worksheet headers, record identifiers, row and column positions, and identifiers used to bind a session to its worksheet. The add-in also inspects worksheet structure and editability. OpenAI receives the instruction text, field names and up to 20 example record identifiers to interpret the requested changes. Lucy’s backend resolves the exact targets and checks the result before the add-in applies changes.
• Commands and outcomes. Lucy processes requested values, target references, timestamps and applied, skipped, failed or uncertain outcomes. If you enable previous-value capture, the add-in may also read and send the previous cell value. This preference is off by default and does not provide undo.
• Usage and technical information. Lucy records the current daily listening allowance, session ownership and timing needed to enforce it. Operational logs include request identifiers, route names, status codes, error information, counts and durations. Hosting and analytics services also process connection and device information such as IP addresses and browser details.
• Messages and forms. If you contact Lucy or submit a beta-access form, the information you choose to send is processed to respond to your request. The website links to a form hosted by Youform. Beta-access submissions are used only to respond about beta access, not for newsletters or other marketing. Avoid including workbook contents, credentials or other sensitive information in support messages.

Microsoft and Google sign-in identify you to Lucy. They do not give Lucy permission to browse OneDrive or Google Drive, access closed workbooks, or edit spreadsheets through those providers’ server APIs. The Excel add-in reads and writes through Excel’s permissions for your open workbook.

Keeping a workbook locally does not keep all processing on your device: the audio, instruction and worksheet context described above are sent to Lucy and its processing providers. Lucy requires an internet connection. Only use data you are authorized to send to these services.

Information is used to authenticate you, provide and troubleshoot voice updates, show command outcomes, remember configuration and privacy preferences, enforce access and usage limits, prevent duplicate writes and misuse, protect the service, respond to requests, and understand website use.

Where applicable law requires a legal basis, providing the service you request, legitimate interests in security and service operation, legal obligations, and consent where required are the relevant bases. Consent can be withdrawn where processing depends on it; withdrawing permission needed for a feature may prevent that feature from working. A privacy notice does not itself replace any consent required by law.

Lucy uses the following providers for the purposes described here:

• Microsoft and Google for identity-only sign-in.
• Microsoft Azure Speech for live speech recognition.
• OpenAI’s API for interpreting instructions with limited worksheet context.
• Vercel for the website and Fly.io for the backend.
• Supabase for account and application records; Fly.io-hosted Redis for temporary operational state.
• PostHog for website analytics, and Youform when you use the linked beta-access form.

Microsoft’s speech privacy documentation describes real-time audio processing in memory without storage at rest. Lucy has not enabled Azure audio logging. OpenAI’s API data controls state that API data is not used for training by default unless the customer opts in, and that abuse monitoring logs may retain content for up to 30 days, or longer where legally required. These are provider terms, not a zero-retention guarantee for Lucy. Lucy has not enabled OpenAI data sharing for training.

Providers may process information outside your country. This policy makes no promise that processing stays in Singapore, Switzerland, the European Union or any other single region. Deployment regions, provider settings and applicable transfer arrangements remain subject to verification.

Information may also need to be disclosed to meet a legal requirement or address fraud, security incidents or legal claims, subject to applicable law. This notice does not authorize unrelated uses of workbook data.

Lucy Hub uses the lucy_session cookie for sign-in and lucy_csrf to protect requests. Both have a configured 24-hour lifetime. The Excel pane uses separate local credential storage to restore sign-in; restoring sign-in does not automatically start listening. Configuration hints may also be saved in the workbook and Lucy’s database.

Lucy uses PostHog to understand website visits and template downloads. The existing website integration starts automatically when configured and can run on website and Hub pages; it is not limited to the homepage. Manual page-view events include the visited URL and its query parameters. PostHog may also process browser and device information, identifiers, interaction events and person profiles, and use cookies or local storage according to its configuration.

Session replay is disabled in the live PostHog project according to the operator. Other project capture and retention settings still require verification. The website does not display analytics acceptance, rejection or withdrawal controls. Contact our Data Protection Officer about analytics-related privacy requests.

You can control cookies and storage through your browser, although blocking essential storage may prevent sign-in. The spoken-history preference in Hub controls a separate feature. See PostHog’s privacy information.

Raw audio is streamed rather than saved by Lucy’s application. Transcripts, worksheet context, command values and outcomes are processed temporarily in memory and operational storage. Relevant Redis records use 30-minute expiry periods, which can refresh during activity or state updates. Stopping listening therefore does not mean all processing records disappear immediately.

A separate database journal contains execution identifiers, timing and outcome metadata without transcripts or cell values. Entries expire for execution recovery after 24 hours and become eligible for scheduled cleanup; this is not a guarantee of deletion from every storage layer at exactly 24 hours.

Persistent spoken history is off by default and requires both an eligible Pro entitlement and your explicit preference. Initial free Starter access does not include this history or its export. When enabled for an eligible account, saved history can contain transcripts, interpreted commands, record identifiers, target fields, new values and outcomes, plus previous values if separately enabled. Turning history off does not delete existing history. Enabling it does not recreate earlier sessions.

Daily allowance accounting keeps one current-state record per Lucy account, including the usage day, time reserved or used and active-session metadata, rather than a historical daily ledger. A day’s reset does not delete the account record. Operational logs and optional history have their own lifecycles.

Account records, Terms acceptance records, preferences and any saved history or export records remain in persistent storage. There is currently no automatic age-based cleanup for saved history or exports. Final retention, account-deletion procedures, platform-log retention and backup handling are still under review; this policy does not establish new retention periods or promise immediate deletion from backups. Copies in your workbook or exports you download remain under your control.

Stop listening to stop microphone capture, revoke microphone permission in your device or browser, and review eligible history and previous-value preferences in Hub privacy settings. Signing out, removing the add-in, or disconnecting a sign-in method does not itself delete your account or saved history.

Contact colin@arcworkstech.com about access, correction, deletion, consent withdrawal or other privacy requests. Our Data Protection Officer handles these requests manually on behalf of Archworks Technologies Pte Ltd. Lucy has no self-service account-deletion button. Identity verification may be needed to protect your information; do not send passwords or access tokens. Rights and lawful exceptions depend on your location, and may include objection, restriction or portability. You may also raise a concern with your local data-protection authority, including Singapore’s Personal Data Protection Commission.

Lucy uses authentication, access checks and separate Hub and add-in credentials. Application request logging omits request bodies, cookies and query strings; command-content logging is not part of the intended operational logging flow. These controls do not make internet services risk-free or establish a regulatory certification.

Be mindful of other people’s voices and personal information in worksheet identifiers or commands. Obtain the permissions needed for your use. The Terms of Service require legal capacity to agree and any consent required by applicable law. Do not treat a successful Microsoft or Google sign-in as proof that any required parental consent has been obtained.

Material changes should be brought to your attention as required by applicable law. This policy does not replace any existing rights.