Documented-Policy tier only. This score rates how clearly Context.dev's public cancellation page is published (cited, dated) — opinion grounded in disclosed facts, not a finding about the real cancel experience, and not legal advice. The behavioural Verified-Flow grade is pending.

60/ 100 · C

AI tools · US

How hard is it to cancel Context.dev?

Context.dev scores 60/100 (grade C) for how clearly it documents cancellation in the US — a partially documented cancellation policy with notable gaps. Cancellation is available via online (self-serve), email.

Last reviewed 2026-06-11 · Documented-Policy tier · grade C

Context.dev (formerly Brand.dev) allows self-serve cancellation by logging into your account at any time. Cancellation takes effect at the end of the current paid term (monthly billing cycle). All purchases are non-refundable. The pricing page states 'No enterprise contracts. No lock-in. Cancel anytime.' Support is available via [email protected] for billing questions.

How to cancel Context.dev

  • Channels: online (self-serve), email
  • Official cancellation page: https://brand.dev/term
  • Pause/freeze: not offered. No pause or freeze option found in official terms or FAQ.
  • Account/data deletion: Privacy policy exists at context.dev/privacy. No specific account deletion flow was documented in public-facing pages; contact [email protected] to request data deletion. https://www.context.dev/privacy

Evidence

Scope & fairness

This is the Documented-Policy tier: it measures how clearly the cancellation policy is published (cited, dated facts), not the behavioural experience of cancelling (Verified-Flow audit pending). Every company is scored on the same five dimensions with the same published weights — scores cannot be bought or removed. It is opinion grounded in disclosed facts, and not legal advice.

Is this wrong? Companies can request a correction ->

Cite this. Cancel Atlas (2026). “Context.dev — Cancellation Friction Index (US).” CES-1.1. https://www.cancelatlas.com/c/context-dev (CC BY-SA 4.0).

See Context.dev in the full index -> · How we score · Open data