Privacy notice
How Lunume processes account information, workspace content and connected calendars.
On this page
01Who operates Lunume
Lunume is operated by Колупаев Константин Вячеславович (Konstantin Vyacheslavovich Kolupaev), an individual. Contact [email protected] for support and personal-data requests. Lunume is not currently operated by a registered company named Lunume LTD. This notice describes the current early-access service and applies from 25 October 2026.
02Account and service information
We process your email address, display name, password hash or linked sign-in identifier, language, time zone, session identifiers and device information to provide and protect your account. Security and operational records can include IP addresses, timestamps, request errors and changes to access permissions. We do not ask you to send passwords, recovery codes or payment-card details to support.
03Content you choose to store
Lunume stores the notes, tasks, files, comments, revisions, dates, tags and sharing choices you submit. Content is used to provide the workspace functions you request. Some supported files have text extracted for search. Other workspace participants can access content only through applicable permissions. A public sharing link makes the selected material accessible to people holding that link; they may retain copies after the link is revoked.
04Why we process information
We use account and content data to provide requested service features, and operational information to keep the service secure, diagnose faults and respond to support requests. Contractual necessity applies to requested account services; legitimate interests apply to proportionate security and support activities; legal obligations apply where retention or disclosure is required by law. Optional Google Calendar access is initiated by you and can be withdrawn.
05Google account and calendar access
Google sign-in uses your account identifier, email address and basic profile to sign you in to Lunume. Calendar access is optional and requested separately. When you connect Google Calendar, Lunume reads your calendar list so you can choose which calendars to display. It reads events only from the calendars you enable, including event titles, descriptions, locations, dates, times and links. The connection does not create, change or delete events in Google Calendar.
06Use and storage of Google Calendar data
Lunume uses the selected calendar data to show your schedule alongside your notes and tasks and keep that schedule updated. Imported events are private to your Lunume account and are not published to workspace members or public note links. Access and refresh tokens are encrypted on the server. Event data is cached on the server for the previous three months and the next twelve months. Calendar data is not automatically sent to AI providers or used to train AI models, sold, or used for advertising. Lunume’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
07Disconnecting Google Calendar
You can disable an individual calendar or disconnect the account in Settings → Connections. Disabling a calendar deletes its cached events from the active service database; disconnecting removes the connection, its stored tokens, calendars and cached events. It does not change the original events in Google. You can also revoke Lunume’s permission in your Google Account’s third-party connections settings. Backup copies follow the service’s applicable retention schedule and are not used to continue synchronization after disconnection.
08AI actions and other connections
An AI action you request sends its prompt and selected context to the AI service configured for that feature. Review the material you select before sending it. Connected Google Calendar data is not automatically included in AI requests. Other integrations are optional and process the information needed for the action you enable. Their services also have their own privacy notices.
09Service providers and disclosure
The service uses hosting, database, object-storage and email infrastructure to operate. Cloudflare provides network delivery and object storage in the current deployment. Infrastructure providers process the data required for those functions. Operational access is limited to running, securing and supporting the service. We do not sell account or Google user data. Information may be disclosed when required by law or necessary to establish or defend legal claims. Contact support for information about the providers and transfer safeguards relevant to your account.
10Retention and deletion
Account and workspace information is kept while it is needed to provide your account and requested content. Trashed notes remain recoverable until permanently deleted. Permanent deletion removes the live note and its linked history; a file still referenced elsewhere is retained for that reference. Google Calendar deletion controls are described above. Backups, security records and records subject to legal obligations may persist beyond deletion from the live service, and are not used to restore a disconnected calendar for normal use. You can request account deletion and information about remaining retention at [email protected].
11Browser storage and devices
Authentication cookies maintain your session. Browser storage also remembers interface preferences and can preserve unsent drafts for recovery. Clear site data on shared devices after saving needed work. Signing out does not erase files you downloaded or copies already shared with others. The public landing demonstration uses fictional examples.
12Operational account administration
When the Control Room integration is enabled, Lunume synchronizes your account identifier and, where available, your account email and display name with its operational administration service at control.secretcandies.com. Account-linked operational events can describe app openings, feature categories, created record types and counts, sign-in outcomes and methods, platform and application version. These event payloads do not include document titles, document text, file contents or calendar-event contents. Sign-in failure events do not send the email or credentials entered in the failed attempt.
13Public website analytics
Public marketing pages load the controlled analytics SDK from control.secretcandies.com. It measures page views, scrolling, engagement and download or support clicks using approved public paths without query strings or fragments. The default uses no analytics cookies or visitor identifier. Explicit consent permits a random session-scoped identifier; an explicit opt-out stops tracking, clears queued events and removes that identifier. Do Not Track and Global Privacy Control prevent optional analytics events. The public SDK does not load on account, workspace or shared-note routes, and does not collect document titles or bodies.
14Support conversations
Messages you choose to send through public website chat or in-app support go to the operational support service so designated staff can read and reply. Public website chat uses a project- and origin-specific visitor token in localStorage; reset or expiry ends that token’s use. Authenticated in-app support binds each conversation to your account. Replies appear in the conversation and are not automatically emailed. Message text is supplied by you; avoid passwords, payment details and unrelated private documents.
15Ideas and voluntary support
When you send an idea, we store its title, description, product category and optional contact email so designated operators can review and process it. Do not include passwords or unrelated private documents. The separate Lunume support and download interaction records use a random browser-session identifier, platform, source and assigned delay to compare requested actions; these records expire on Lunume’s server after 90 days. Browser Do Not Track and Global Privacy Control disable optional client interaction events. Download completion and payment are not inferred from a button click. The support page and app can display the official embedded Ko-fi form. In download dialogs it loads only after you choose to open it. The form loads resources from Ko-fi, where you choose the real amount and payment method under its own privacy notice; you can also open that form separately. Lunume does not infer a payment or its amount from loading or interacting with the embedded form. A verified payment webhook records transaction identifiers, amount, currency, type and time; donor name, email, message and shipping details are not retained by this integration.
16Your choices and rights
You can review account sessions, change sharing permissions, disconnect integrations and request access, correction, deletion or portability of your personal data. Where applicable, you may restrict processing, object to processing based on legitimate interests, or withdraw consent without affecting earlier lawful processing. Send requests to [email protected], preferably from your account email. We may need proportionate verification to protect your data. Where the GDPR applies, requests are normally answered within one month, subject to its permitted extensions and exceptions. You may complain to your competent data-protection authority.
17Security and changes
Controls include password hashing, authenticated sessions, access checks, encrypted calendar credentials and HTTPS connections. Ordinary workspace content is not end-to-end encrypted. Password-protected records encrypt supported record content separately; their visible title and other metadata remain visible as indicated in the app. No system can guarantee complete security. We update this notice when relevant processing changes and provide additional notice where required.