Feature Deprecation Notice

Write a deprecation notice for a feature people use. Dates, replacements, and no euphemism. FEATURE Name: [FEATURE] Who uses it, as far as we know: [WHO] Why it is going away: [REASON I CAN PUBLISH] Replacement: [FEATURE OR "none"] Stop selling it: [DATE] Stop working: [DATE] What happens to existing data: [MIGRATED | EXPORTED | DELETED ON DATE] Action they must take: [STEPS] WRITE 1) In-app banner, under 240 characters, with the end date. 2) Email to people who used it in the last [N] months. The date in the first sentence. What breaks. What to do. What happens if they do nothing. 3) Help article outline: timeline, replacement mapping, export steps. 4) The word I should not use ("sunset" without a date, "improved experience" for a removal). Use "we are removing this on [DATE]." If there is no replacement and data will be deleted, the email says that in the subject, not the footnote.