Design

Deleting Your Account

Feb 15, 2015

This weekend, I wrapped up a “feature” that’s been at the top of my list for a while—deleting your account. It’s not an exciting feature, but certainly a necessity and one that’s very important to me. We owe it to our users to put them in complete control of their data. If they no longer want any of their data in your database, they should be able to easily delete it—not just abandon it.

2015-02-14-tweet

I recently tweeted about a few prerequisites I believe each app developer should build into their app before launching. I knew others felt the same, but I didn’t realize it would become my most favorited and most retweeted tweet. It’s a sign that people really care about these aspects of an app, even if they’re not the killer features one would spotlight on the product page.

The ability to delete your account is especially important to me because I’ve come across so many web services that simply don’t allow it—even ones with millions of users and thousands of employees. There’s absolutely no excuse not to build support for it. In my eyes, it should be a legal requirement for anyone putting an app into the world. We’re so quick to build apps, scale them, and strive to reach exponential growth that we act like it’s a complete waste of time to spend two or three days building these features.

In Cushion, I built the initial phase of a two-part plan for deleting your account. With the first beta accounts expiring soon, I needed the bare minimum in place, in case anyone wanted to call it quits. For beta users, this means simply deleting their data upon request.

2015-02-14-modal

Within the app, the user would click a link to delete their account. This opens a modal with an explanation of what deletion entails, emphasizing the seriousness of the request—in case users simply want to cancel their subscription. The modal also suggests downloading a backup beforehand.

2015-02-14-github

I followed Github’s model for confirmation by requiring users to type their email address to enable the delete button. With the past several apps I’ve built, I can’t tell you how many users “accidentally” deleted their account or deleted it assuming they could return a month later and just restore it. This also clarifies which account is being deleted, in case the user has more than one. I want the user to be fully aware that they are about to delete their account.

Upon clicking the delete button, the user’s subscription is cancelled, if one exists, and their data is deleted. That’s phase one.

The plan for phase two is to provide the most thorough experience for deleting an account, covering all angles of what may potentially happen next. In case the user forgets to download a backup, the user’s data will automatically be emailed to them upon deleting their account. If they ever attempt to log into their account again, they will find a list of downloadable receipts from Cushion charges. And, for the inevitable user wanting to restore their account shortly after deleting it, accounts will be put it in a queue to be deleted 30 days later after the request. Within those 30 days, a user can restore the account and be back to using it in no time.

So far, I’m happy with the first step, but look forward to building the full package. It does feel strange investing this much time in the experience of someone leaving, but I refuse to skimp on any aspect of Cushion.

The beta is still going strong, so if you’re interested in participating, even just to test out deleting your account, be sure to request an invite.

Share this on Twitter or Facebook

Archive

  1. Visualizing Daylight Saving Time
    Dev
  2. Recording Screencast GIFs
    Dev
  3. Writing a Job Listing
    Story
  4. Using Feature Flags to Run Betas
    Dev
  5. Our First Company Lunch
    Story
  6. How to embed Vue.js & Vuex inside an AngularJS app... wait what?
    Dev
  7. Funding Cushion
    Story
  8. Hiring a Team of Freelancers
    Story
  9. Taking a Real Break From Work
    Story
  10. Slack as a Notification Center
    Dev
  11. Document Your Features
    Story
  12. 300
    Story
  13. Vacations
    Design
  14. Offering Discounts
    Design
  15. Waves of Traffic
    Story
  16. Less Blogging, More Journaling
    Story
  17. Retention Through Useful Features
    Design
  18. The Onboarding Checklist
    Design
  19. Spreading the Word
    Story
  20. From Beta to Launch - The Subdomain
    Dev
  21. From Beta to Launch - Sign up
    Design
  22. From Beta to Launch - Messaging
    Design
  23. Launch
    Story
  24. Authenticating with 3rd Party Services
    Dev
  25. Intro to Integrations
    Design
  26. Inspiration vs Imitation
    Story
  27. The Emotional Rollercoaster
    Story
  28. Designing Project Blocks
    Design
  29. Everything in Increments
    Story
  30. Deleting Your Account
    Design
  31. Designing the Subscription Page
    Design
  32. Rewriting the Timeline
    Dev
  33. Restructuring the Individual Project Page
    Design
  34. Project Blocks
    Story
  35. Redesigning the Homepage
    Design
  36. Multiple Timelines
    Design
  37. Archiving and Estimate Differences
    Design
  38. Multiple Financial Goals
    Design
  39. Zooming in on the Timeline
    Design
  40. Currency
    Dev
  41. Preferences, Accounts, and a Typeface Change
    Design
  42. Sending Out the First Email
    Story
  43. Currency Inputs, Notifications, and Invoice Nets
    Design
  44. Dots and Lines
    Design
  45. Calculating in the Database and Revealing Tendencies
    Dev
  46. Improved Form UX
    Design
  47. Cushion is Online
    Story
  48. Schedule Timeline Patterns
    Design
  49. A Slimmer Schedule Timeline
    Design
  50. The Schedule Timeline
    Design
  51. Plugging in Real Data for the First Time
    Design
  52. Transitions and Project Lists
    Design
  53. Death to Modals
    Design
  54. The Individual Project Page
    Design
  55. Estimated Incomes and Talks with Other Freelancers
    Story
  56. Statuses to Lists and the Paid Beta
    Story
  57. The Timeline
    Story
  58. Invoice Terminology
    Dev
  59. Modal Forms
    Dev
  60. Wiring the Backend to the Frontend
    Dev
  61. Balancing Design and Dev
    Story
  62. Timecop, Monocle, and Vagrant
    Dev
  63. Going with Ruby and Sinatra
    Dev
  64. Ditching local-first and trying out Node.js
    Dev
  65. Switching to AngularJS
    Dev
  66. Building the Table with Vue.js
    Dev
  67. Clients, Projects, and Invoices
    Dev
  68. Introduction
    Story

Ask a Freelancer

A podcast series where experienced freelancers answer questions about freelancing.

Listen to the Podcast

Talking Shop

An interview series where we talk to freelancers about important topics in the freelance world.

Read the Interviews

Running Costs

Take a close look at the costs that go into running a web app and why we use specific services.

View the Costs

How It’s Made

Follow along with the journal for insight into the overall experience of building an app.

Read the Journal