Privacy Policy

Last updated: 12 October 2026

Days2Go ("we", "us", or "our") helps you visualise upcoming events from your Google Calendar as countdowns. This Privacy Policy explains what we collect, how we use it, and your choices.

1. Who we are

Days2Go is operated by Lunami Labs. You can contact us at leon.tex610@gmail.com for any privacy questions or account deletion requests.

2. Information we collect

When you sign in with Google, we receive:

• Your name, email address, and profile picture (Google OpenID Connect).
• A Google OAuth access token + refresh token that we use to read your calendars and tasks.

We also store your in-app preferences:

• Which event colours you've chosen to monitor.
• Which calendars you've selected.
• Your Pro subscription status, if you have purchased one.
• Your manually created countdowns and their notification preferences (stored only on your device).

For Pro purchases we use Google Play Billing (via RevenueCat). Google Play handles your payment details directly — we never see or store your card number. We only receive a purchase confirmation and a subscription entitlement.

3. Google User Data — what we access

Days2Go accesses the following Google user data only after you sign in and grant consent to the specific OAuth scopes at the Google consent screen. We request the narrowest scopes technically available for our functionality.

• Google Calendar — calendar list (https://www.googleapis.com/auth/calendar.calendarlist.readonly) — read-only access to the list of calendars you own or subscribe to (calendar ID, display name, background colour). This lets you pick which calendars you want to surface in Days2Go.
• Google Calendar — event data (https://www.googleapis.com/auth/calendar.events.readonly) — read-only access to upcoming events (title, start date/time, end date/time, colour, calendar ID) within approximately the next 400 days. This is used solely to display your events as countdowns inside Days2Go.
• Google Tasks (https://www.googleapis.com/auth/tasks.readonly) — optional read-only access to your task lists and tasks with due dates, used solely to display your upcoming tasks as countdowns inside Days2Go. This scope is requested incrementally — only after you explicitly enable "Show Google Tasks" in Settings. Users who never turn Tasks on never grant this scope.
• Basic profile (openid, email, profile) — your name, email address, and profile picture URL, used to identify your account inside the app.

We deliberately do not request the broader calendar.readonly scope. We request only the narrow calendar.calendarlist.readonly and calendar.events.readonly scopes so we can read exactly what is needed and nothing more.

We do not request write access to your Google Calendar or Google Tasks, and we do not modify, create, or delete any of your events or tasks.

Google Calendar events and Google Tasks that we retrieve are held only in memory on our server for the duration of your request and are not stored in our database. Only the OAuth tokens and your basic profile are persisted, so we can re-fetch your events when you re-open the app.

4. Sharing, Transfer and Disclosure of Google User Data

This section directly answers Google's question: with whom does Days2Go share, transfer or disclose Google user data?

Who receives or processes Google user data:

• You. Google user data flows to your own Days2Go app instance (mobile or web) so it can be rendered as countdowns.
• Google itself. All Google user data is retrieved from Google's own APIs (Google Calendar API, Google Tasks API, Google OAuth) over HTTPS/TLS.
• Days2Go's cloud hosting provider (Emergent). The Days2Go backend runs on managed Kubernetes infrastructure operated by Emergent (emergent.sh). This provider hosts the application server that mediates each Google API request and may technically transit Google user data in memory while a request is being served. Emergent processes this data only as a hosting sub-processor on our behalf and is contractually restricted to that role.
• Days2Go's database provider (MongoDB). Your OAuth tokens, basic profile fields (name, email, profile picture URL), your calendar/colour selection preferences, and your Pro-subscription status are stored in a MongoDB database. Google Calendar events and Google Tasks themselves are not persisted to this database — only the credentials needed to re-fetch them from Google. The database provider acts strictly as a storage sub-processor.

Who does NOT receive Google user data:

• Our AI provider (Anthropic Claude via Emergent's LLM proxy). Days2Go includes an optional AI assistant that helps you create manual countdowns from natural-language text you type or dictate yourself. Only that text you explicitly type/dictate is sent to the AI provider. Your Google Calendar events, Google Tasks, calendar list, and Google profile fields are never sent to the AI provider. Google user data is never used to develop, improve, or train generalized or non-personalized AI or machine-learning models.
• Payments (Google Play Billing / RevenueCat). Payment processing receives only the fields necessary for billing (e.g. purchase identifiers, plan). Google Calendar / Tasks / profile data is not sent to any payment processor.
• Analytics (Firebase Analytics). Analytics events contain no Google Calendar or Google Tasks data. They log anonymised app-usage metrics (screen views, feature toggles, subscription events) and do not include event titles, task names, or personally identifying content from Google.
• Advertising networks / data brokers / information resellers. None. Days2Go does not integrate with any advertising SDK, retargeting network, data broker, or information reseller.

Explicit commitments about Google user data:

• Days2Go does not sell Google user data.
• Days2Go does not rent Google user data.
• Days2Go does not provide Google user data to data brokers.
• Days2Go does not provide Google user data to information resellers.
• Days2Go does not use Google user data for targeted, personalised, retargeted, or interest-based advertising.
• Days2Go does not use Google user data to develop, improve or train generalized or non-personalized AI or machine-learning models.
• Days2Go does not disclose Google user data to third parties for any purpose unrelated to providing, maintaining, securing, or supporting the Days2Go service.
• Days2Go does not allow humans (including our own staff) to read Google user data except (a) with your affirmative agreement for a specific support case, (b) as necessary for security investigations, or (c) where required by law.

The infrastructure and database providers listed above are sub-processors that provide the hosting and storage layers required to operate Days2Go. They may process Google user data only as necessary to provide, maintain, secure, or support the Days2Go service, and only under contractual confidentiality obligations. Beyond these operational sub-processors, Days2Go does not share, transfer, or disclose Google user data to any third party.

5. Google API Limited Use

Days2Go's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements. In particular:

• We use Google user data only to provide or improve user-facing features that are prominent in the Days2Go user interface (the countdown display of your Google Calendar events and, optionally, Google Tasks), and for necessary security, reliability, and legal-compliance purposes.
• We do not transfer Google user data to others unless necessary to provide or improve those features, comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users.
• We do not use Google user data to serve advertisements, including retargeting, personalised, or interest-based advertising.
• We do not allow humans to read Google user data unless we have your affirmative agreement for specific data, it is necessary for security (such as investigating abuse), to comply with applicable law, or the data has been aggregated and anonymised for internal operations.
• AI/ML models. Google Workspace / Calendar / Tasks data is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models. Google user data is never sent to an AI or machine-learning model for generalized model training. The Days2Go AI assistant, when used, only receives natural-language text you yourself type or dictate to create manual countdowns — it never receives your Google Calendar events, Google Tasks, calendar list, or Google profile fields.

6. What we do not collect

• We do not read or store the description, location, attendees, or attachments of your Google Calendar events.
• We do not store the notes or subtasks of your Google Tasks.
• We do not store your Google password.
• We do not include any advertising SDKs.
• We do not share, sell, or transfer your data to third parties.

7. Security

We use industry-standard controls appropriate to the sensitivity of the data we process:

• All traffic between your device and our servers, and between our servers and Google's APIs, is transported over HTTPS/TLS.
• Your Google OAuth access token and refresh token are stored server-side in our MongoDB database. Database connections use TLS.
• Your Days2Go session token is stored on your device using the platform's secure key store (iOS Keychain or Android Keystore) — never in plaintext AsyncStorage.
• Google Calendar events and Google Tasks are held only in memory during the request that fetches them; they are not written to any long-term store on our infrastructure.
• Access to production systems is restricted to authorised personnel with principle-of-least-privilege controls.

No system is perfectly secure. We continue to review and improve our security practices, and will notify affected users of any material security incident as required by applicable law.

8. Data Retention and Deletion

What Google-related data we retain server-side:

• Your Google OAuth access token and refresh token — retained until you disconnect Google in Days2Go or revoke access at Google, then deleted.
• Your Google basic profile fields (name, email, profile picture URL) — retained while your Days2Go account exists.
• Your selection preferences (which calendars and colours you chose to display, whether Tasks is enabled) — retained while your Days2Go account exists.

What we do NOT retain: Google Calendar events, Google Tasks, and any content of your events (description, location, attendees, attachments, task notes, or subtasks) are never written to our database. They are fetched from Google on demand and dropped from memory after each request.

What happens when you disconnect or revoke Google access:

• Disconnect in Days2Go (Settings → Disconnect Google): we immediately delete your stored Google OAuth access token and refresh token from our database. Days2Go can no longer contact Google on your behalf.
• Revoke at Google ( myaccount.google.com/permissions ): Google immediately invalidates our tokens. Next time Days2Go tries to fetch your events, the call will fail and we will discard the stale tokens on our side.

Requesting deletion of your Days2Go account: email leon.tex610@gmail.com with the subject "Delete my Days2Go account" from the address associated with your account. We will confirm and permanently delete your account record, OAuth tokens, and preferences within 7 days. Anonymous payment records held by our payment provider (Google Play) are retained by them as required by tax and fraud-prevention laws; these records contain no Google user data.

See also our Account Deletion page for step-by-step instructions.

9. Your choices and rights

• Disconnect Google: open Days2Go → Settings → Disconnect Google. This deletes your stored Google OAuth tokens.
• Revoke at Google: at any time, you can revoke our access at myaccount.google.com/permissions .
• Delete your account: email leon.tex610@gmail.com with the subject "Delete my account" — we will remove your account, preferences, and OAuth tokens within 7 days.

10. Children

Days2Go is not directed at children under 13. We do not knowingly collect data from children under 13.

11. Changes to this policy

If we materially change this policy, we will update the "Last updated" date and, for significant changes, notify active users in-app.

12. Contact

Email: leon.tex610@gmail.com