Account & security

Sign-in, sessions, data handling, and what stays on your device.

How sign-in works

Two paths: email + password, or Google OAuth. Email accounts use bcrypt for password hashing (cost factor 10). Google accounts use Google Identity Services; we verify the id_token against Google's tokeninfo endpoint before issuing a Taskin session.

Sessions & devices

A successful sign-in returns a bearer token stored in localStorage for 30 days. You can sign out from any device at any time, which revokes the token server-side. We don't yet show "active sessions across devices" — it's a planned feature.

What data we store

  • Your email and (for OAuth) display name.
  • Hashed password (for email accounts only).
  • Your purchase history and license keys.
  • Session tokens and their IPs / user agents for audit.

That's it. We don't store uploads, generated images, QR codes, passwords, or stock queries against your account.

Client-side tools

The Password Generator runs entirely in your browser — passwords never touch a server. Most other tools (Image Compressor, Image Resizer, File Converter, Background Remover) process server-side because they need heavyweight image libraries, but files are processed and discarded; nothing is persisted beyond the response.

Rate limits

To keep the service stable, we enforce per-IP rate limits on the API. Auth endpoints are particularly tight (5 attempts per 15 minutes per email or IP). IPv6 callers are bucketed by their /64 prefix so an attacker can't cycle host bits to escape the limit. If you legitimately hit a 429, wait a few minutes and retry.