Start free, upgrade when you need more notes, tasks or highlights. Limits below are live values from your account configuration — admin can tune them per plan.
For trying things out
No credit card required
Get startedFor power users syncing every day
Cancel anytime
Get Early AccessFor teams & organisations
Volume discounts available
Contact sales| Feature | Free | Pro | Enterprise |
|---|---|---|---|
| Note tabs | 3 | 10 | 20 |
| Characters per note | 5,000 | 10,000 | 20,000 |
| Tasks | 20 | 100 | 500 |
| Task title length | 50 | 50 | 50 |
| Task description length | 160 | 160 | 160 |
| Highlights per page | 10 | 40 | 100 |
Yes. Upgrades take effect immediately on the next API call. Downgrades apply at the end of your current billing period — your existing notes and tasks remain accessible even if they exceed the lower plan's limits.
The server returns a 429 with a clear error message. The extension shows a toast and stops syncing the offending field until you delete enough items to fit the limit, or upgrade.
Your existing tasks, tab notes, and highlights are never deleted or hidden. After a downgrade you can keep viewing, editing, and deleting them as before — even if your current count is above the new plan's limit. The only restriction is that you can't create new items until you trim under the limit (or upgrade again). For example, if you had 50 tasks on Pro and switch to Free (20 tasks), all 50 stay accessible; you'll see a "50/20 tasks used" badge and an over-limit banner explaining how to add new ones again.
Yes. Every limit on this page is enforced at the API layer. The extension also pre-validates against /api/v1/me/limits for instant feedback, but the server is authoritative.
Yes. Email support@quickask.ai with your team size and we'll get back within one business day. SSO, SCIM, and custom data residency options are available on request.
All sync traffic is over HTTPS. Sessions are revocable from the admin panel and via session-bound JWTs. Highlight notes / task descriptions are sanitised on the server before storage to prevent stored XSS — see our security spec for details.