Privacy Policy
TasQuest is designed to stay lightweight and privacy-conscious during the MVP phase. We currently use only the cookies and account data required to authenticate users, secure sessions, and keep the application running reliably.
What TasQuest Collects
We collect the information necessary to create and maintain your account, such as your name, email address, authentication identifiers, profile settings, guild context, quests, focus sessions, and other in-app productivity data that you create while using TasQuest.
Current Cookie Approach
During the MVP phase, TasQuest uses essential cookies only. These cookies are required for sign-in, account security, session continuity, and core application behavior. We do not currently require a consent banner for analytics or marketing cookies because they are not active at this stage.
- ✓Laravel session cookies
- ✓Authentication cookies
- ✓Privacy Policy
- ✓Cookie Policy
- ✕Cookie banner during MVP
If Analytics Or Marketing Tools Are Added Later
If TasQuest later adds tools such as Google Analytics, PostHog, Microsoft Clarity, or Meta Pixel, the consent model should become more granular and user-controlled.
- Google Analytics
- PostHog
- Clarity
- Meta Pixel
What Large SaaS Apps Commonly Do
- GitHub uses a cookie banner only when analytics or marketing cookies are active.
- Linear takes a very minimalist approach.
- Basecamp generally follows an essential-first model.
- Figma offers granular cookie settings.
Recommendation For TasQuest
For the first product phases, the smoothest and most GDPR-friendly approach is to keep TasQuest essential-only. This avoids unnecessary friction during registration while still documenting how account and session data are handled.
In later phases, TasQuest should add a consent banner, analytics preferences, marketing preferences, and a way for users to update those settings at any time.
- ✓Consent banner in phase 3+
- ✓Analytics preferences
- ✓Marketing preferences
- ✓Ability to change consent later