← Back to home

DailyPulse Privacy Policy

This Privacy Policy explains how DailyPulse (the "app"), provided by lghdeveloper, collects, uses and protects your information.

Who we are

DailyPulse is developed and operated by lghdeveloper. If you have any question about this policy or your data, contact us at the email address in the Contact section below.

Data we collect

We collect the following data, all of it provided by you or generated by your use of the app:

  • Account data: email, name and authentication provider ID, obtained when you sign in with Google Sign-In or Sign in with Apple.
  • Check-in data: energy (1–5), mood (1–5), deep work hours, number of meetings, and, optionally, a note, a work location (home, cafe, coworking, office or other) and a day tag (vacation, sick or travel).
  • Onboarding answers: your role, meetings per day, what drains you and your goal.
  • Preferences: your timezone and reminder preferences, and the push notification token (Expo push token) of your device.
  • Usage data: which screens and features you use (for example finishing onboarding, viewing the paywall, starting a trial, saving a check-in or connecting your calendar), with device and app version, linked to your account ID. It never includes your check-in values, notes, email or any Google Calendar data.
  • Google Calendar data (optional, Pro): see the next section.

Google user data

Connecting Google Calendar is optional and available with a Pro subscription. If you connect it, the app requests a single scope, https://www.googleapis.com/auth/calendar.events.readonly (read-only access to your calendar).

We read only your primary calendar, for a window from the last 7 days to the next 30 days. All-day, cancelled, free and declined events are ignored.

For each event we store only: the Google event ID, the start and end time, whether it is a meeting, the number of other attendees (a count only, with no names or emails) and whether it is recurring.

We do NOT store event titles, descriptions, locations or attendee identities.

Your Google OAuth tokens (access and refresh) are stored server-side in our backend database. They can be read only by backend functions, never by the app on your device, and are used only to read your calendar on your behalf.

How we use data

We use your data only to provide the app's features to you: computing your own energy score (Pulse), patterns, 7-day forecast, recommendations and reminders, and weekly recap.

We do not use your data for advertising, we do not sell it, and we do not use it (including Google user data) to train artificial intelligence or machine learning models. No human reads your data, except when needed for security or legal reasons, or for support with your consent.

Google API Services User Data Policy (Limited Use)

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

Google API Services User Data Policy

Sharing and processors

We do not sell your data. We share it only with the service providers (processors) needed to run the app:

  • Supabase: database, authentication and backend functions. Data is hosted in the EU (West EU – Paris).
  • Google: Google Sign-In and the Google Calendar API.
  • Apple: Sign in with Apple.
  • RevenueCat: subscription management.
  • Expo: push notifications.
  • PostHog: product analytics (usage data described above). Data is hosted in the EU.

The app does not include advertising SDKs, and no data is used for advertising or tracking across other apps.

Retention and deletion

  • Disconnecting Google Calendar in Settings deletes your stored calendar events and your Google tokens.
  • You can also revoke DailyPulse's access at any time from your Google Account permissions page (myaccount.google.com/permissions).
  • Deleting your account in the app deletes all your data.
  • You can export your data as a CSV file from the app.

Security

Data is encrypted in transit. Access to data is controlled with access controls and row-level security, so each user can access only their own data. Google tokens are not accessible to the app client; only backend functions can read them.

Children

These Services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13. If we discover that a child under 13 has provided us with personal information, we immediately delete it from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us so that we can take the necessary actions.

Subscriptions

Subscriptions (annual with a 7-day free trial, monthly and lifetime) are processed by Apple or Google. RevenueCat receives your purchase status to manage your access; we and RevenueCat do not receive your card data.

Changes to this policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

This privacy policy is effective as of 2026-10-18.

Contact

If you have any question or suggestion about this Privacy Policy, contact us at lghdeveloper@gmail.com.

← Back to home