Skip to policy content
CommitDiaryWork journal for developers
PricingContactSign in

Cookie policy

Small files. Clear reasons.

CommitDiary keeps cookies limited to the work of signing in, securing sessions, and recovering access.

Version 2026-08-28Effective 28 August 2026

On this page

  1. Necessary cookies only
  2. Current cookie groups
  3. Providers and checkout
  4. Managing cookies
Published byCommitDiaryLagos, Nigeriaprivacy@commitdiary.dev

1. Necessary cookies only

The website currently uses cookies that are necessary for the service to function. They help maintain an authenticated session, protect requests against cross-site forgery, remember recovery state, and understand when a session expires.

These cookies are not used to create an advertising profile or to sell personal information. Because they are necessary, blocking them can prevent sign-in and protected features from working.

2. Current cookie groups

  • Authentication and session: keeps an authenticated browser session active.
  • Expiry: helps the application know when a session should be refreshed.
  • Recovery: supports password-recovery and sign-in handoff flows for a limited time.
  • Security: supports CSRF protection for browser requests.

3. Providers and checkout

Paddle's hosted checkout and customer portal may set or read cookies under Paddle's own policies when you open those experiences. Review the notices shown by Paddle there.

If we add optional analytics, advertising, or preference cookies, we will list them here and provide a consent control before using them where required.

4. Managing cookies

You can delete or block cookies through your browser settings. Necessary cookies may be recreated when you return to sign in. Contact us if you need help with a privacy or cookie request.

Contact the CommitDiary team
© 2026 CommitDiary
TermsPrivacyRefundsCookiesContact