Lucid Keeper

Privacy Policy

Effective date: September 15, 2026

This Privacy Policy describes how the Lucid Keeper Alexa skill, provided by Lumina Lucid, accesses, uses, stores, and shares Google user data.

Google data the skill accesses

After a user links a Google account, Lucid Keeper uses the Google Tasks API to access task lists and tasks. This can include task-list identifiers and titles, task identifiers and titles, task status, and other response data required by the Google Tasks API to complete the requested operation.

How Google user data is used

Google user data is used only to provide user-requested Lucid Keeper features, including adding a task, reading pending tasks, listing task lists, and selecting the list used for new tasks.

When the skill reads a task or list title, that information is returned to Alexa so it can be spoken or shown to the user. When the user adds a task, the task title is sent to Google Tasks.

Data stored by the skill backend

The Lucid Keeper backend does not persist Google OAuth access tokens or Google task contents such as task titles or notes.

To remember the user's selected task list, the backend stores the selected Google Tasks list identifier and list title associated with a one-way hash of the Alexa user identifier.

To reduce accidental duplicate task creation, the backend temporarily stores a one-way request fingerprint and request receipt state. These duplicate-protection records expire after approximately 24 hours. They do not store the task body in readable form.

Sharing and sale of data

Lucid Keeper does not sell Google user data. It does not share Google user data with advertisers or unrelated third parties. Data is transmitted to Google to perform Google Tasks operations and to Amazon Alexa as necessary to process the user's voice request and deliver the response. Google and Amazon process information under their own applicable terms and privacy policies.

Security

Google account access uses OAuth authorization. The skill backend receives an access token through Alexa account linking for the current request and uses it to call the Google Tasks API. The backend is designed not to write access tokens, task text, or full request payloads to application logs.

Data retention and deletion

Selected-list preferences remain stored until they are replaced or the skill's stored backend data is removed. Temporary duplicate-protection records expire after approximately 24 hours.

A user can revoke Google access for Lucid Keeper through the Google Account permissions interface and can disable or unlink the skill through Alexa. To request deletion of Lucid Keeper backend preference data, contact the address below.

Limited use

Lucid Keeper' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Changes to this policy

This policy may be updated if the skill's functionality or data practices change. The effective date above will be updated when material changes are published.

Contact

For privacy questions or data-deletion requests, contact paisleyartmachine@gmail.com.