Privacy Policy

Last updated: February 4, 2026

This Privacy Policy explains what information TaskSense collects, why we collect it, how it's used, and the choices you have. We've kept this plain-English and practical.

1) Who this policy applies to

This policy applies to TaskSense on:

• the TaskSense website (web app),
• the iOS app,
• the Android app.

"TaskSense," "we," "us" refers to the company/individual operating TaskSense.

Contact: hello@tasksense.me
Website: https://tasksense.me

2) What we collect

A) Account information (authentication)

When you create an account or sign in, we collect and process:

• email address,
• display name (either provided by you or derived from your email),
• profile photo URL (if available from Google/Apple or if you set one),
• authentication identifiers (like your Firebase user ID).

How login works in TaskSense:

• Email + password sign-in is supported.
• Google Sign-In is supported.
• Apple Sign-In is supported.
• If you sign up with email + password, we require email verification before granting full access.
• Passwords are not stored by TaskSense — they're handled by Firebase Authentication (Google).

B) Profile details you optionally add

In your profile, you can optionally provide:

• company, position (and "custom" position),
• industry (and "custom" industry),
• organization size,
• country.

We also use country in the product (e.g., timezone detection for reminders and optional targeting for announcements).

C) Your TaskSense content

TaskSense is a productivity app, so the main thing we store is the content you create, such as:

• workspaces,
• lists,
• tasks (title, completion status, starred status),
• due dates and optional time-of-day,
• priority,
• notes,
• subtasks,
• recurrence settings,
• reminders settings,
• visibility settings (private/public within a shared context),
• activity history (e.g., edits, completion, assignments),
• comments and related metadata (e.g., mentions, reactions, reply threading).

D) Collaboration information

If you collaborate with others, we store data needed to make that work:

• workspace membership (roles like owner/admin/member, status),
• invitations (workspace and list invitations),
• "shared with" lists (user IDs who have access),
• basic identity needed in shared contexts (like display name, email, and photo if available).

E) Notifications and preferences

We store:

• in-app notifications you receive (and their status: unread/read/archived),
• notification preferences (like which types you want),
• reminder settings and "quiet hours" preferences,
• timezone (used for reminders and quiet hours calculations).

F) App activity / presence signals (lightweight)

To make notifications smarter (for example: don't send a push if you're actively using the app), TaskSense updates:

• last active time (timestamp),
• online/in-foreground state.

G) Device + technical data (depends on platform)

Depending on platform and your settings, we may process:

• device and app info (basic runtime info),
• IP address and general network info (typical for web + APIs),
• diagnostic data.

Mobile push notifications (iOS/Android): If you enable push notifications, OneSignal processes:

• push token (APNs/FCM token),
• OneSignal device identifiers,

and we map your TaskSense user ID to OneSignal (so the right device gets the right notifications).

Web: Push notifications are disabled in the web build (web uses in-app notifications).

H) Analytics and error monitoring (only if enabled)

• Firebase Analytics may be enabled in production on web (only if supported by the browser and configured).
• PostHog product analytics and session replay may be enabled in production if configured.

These tools generally collect technical event data (e.g., page/app actions, crash traces, device/browser info). We use them to improve stability and performance — not to sell ads.

3) How we use your information

Provide the service

• Create and manage your account
• Sync your tasks/lists/workspaces across devices
• Enable collaboration features and invitations

Run reminders and notifications

• Create in-app notifications
• Send push notifications on mobile (if enabled)
• Schedule reminders using server-side jobs for accurate timing

Keep things secure

• Detect abuse or suspicious behavior
• Enforce access controls (e.g., only workspace members can access workspace data)

Improve the product

• Debug issues, fix crashes, and understand performance bottlenecks (e.g., via PostHog)
• Understand feature usage trends (e.g., via Firebase Analytics, if enabled)

Communicate important updates

• Send service announcements (in-app and/or push), for example about new features or critical changes

4) Where your data is stored

TaskSense uses Firebase (Google) as its primary backend, including:

• Firebase Authentication
• Cloud Firestore database
• Cloud Functions / Cloud Tasks (for reminders, announcements, cleanup jobs)
• Firebase Hosting (for the web app)

Your data is stored and processed on Google's infrastructure. Data location can depend on your Firebase project configuration.

5) How we share information

We share information only as needed to run TaskSense:

A) With service providers (processors)

We use trusted vendors to operate the app:

• Google Firebase (authentication, database, cloud functions/tasks, hosting, analytics if enabled)
• Apple and Google (only when you choose Apple/Google sign-in)
• OneSignal (mobile push notifications)
• PostHog (product analytics and session replay, if enabled)

These providers process data under their own terms and security standards.

B) With other users (when you collaborate)

If you join shared workspaces/lists or send/receive invitations, other users may see:

• your display name,
• your email,
• your profile photo (if available),
• and shared content you collaborate on (tasks, comments, activity).

C) For legal and safety reasons

We may disclose information if we believe it's reasonably necessary to:

• comply with law or legal process,
• protect users, prevent fraud/abuse,
• enforce our terms or respond to safety/security issues.

D) Business transfers

If TaskSense is involved in a merger, acquisition, or sale of assets, user information may be transferred as part of that deal.

We do not sell your personal information.

6) Cookies, local storage, and offline data

TaskSense uses local storage / IndexedDB (and similar browser/app storage) to:

• keep you signed in,
• cache data for performance,
• support offline-friendly behavior.

If you want to clear this, you can:

• sign out,
• clear your browser storage,
• or uninstall the mobile app.

7) Data retention

We keep your information only as long as needed to provide TaskSense.

Typical retention patterns in the product:

• Your tasks/lists/workspaces remain until you delete them or delete your account.
• Notifications may be automatically cleaned up over time (for example, older archived/read notifications can be deleted as part of maintenance routines).

We may retain limited technical logs for security and debugging for a reasonable period.

8) Your choices and controls

A) Access, update, export

You can:

• update your profile information in the app,
• export your data (TaskSense provides a JSON export of your user profile + lists + tasks + activity + notifications).

B) Delete data or delete your account

TaskSense provides options to:

• delete all your TaskSense content (tasks/lists/activities/notifications) while keeping your account, or
• delete your account (which deletes associated data and then deletes your auth account).

Security note: Account deletion may require a "recent login" depending on Firebase security rules (you might need to sign in again before deleting).

C) Notifications

• On iOS/Android, you can enable/disable push notifications via system settings.
• In-app notification preferences can be adjusted inside TaskSense.

D) Email communications

If you use email/password:

• we may send verification emails and password reset emails (via Firebase).

9) Security

We use industry-standard protections provided by Firebase and our app architecture, including:

• encrypted transport (HTTPS),
• access control via Firebase Auth + Firestore security rules,
• separation between users/workspaces.

No system can be 100% secure, but we work to protect your data and minimize access.

10) International users

TaskSense may process data in countries other than where you live (for example, where Google's infrastructure operates). If you are in a region with data protection laws (like the EEA/UK), you may have additional rights.

11) Children's privacy

TaskSense is not intended for children under 13 (or the minimum legal age in your country). We do not knowingly collect personal information from children.

12) Changes to this policy

If we update this policy, we'll change the "Last updated" date and may provide an in-app notice for significant changes.

13) Contact us

If you have questions, requests, or privacy concerns:

• Email: hello@tasksense.me
• Support: support@tasksense.me
• Website: https://tasksense.me

Home · Privacy · Terms