Shipaton 2025 - Day 20 - Account Deletion Page

What I Built Today

Today was about making account deletion simple, discoverable, and compliant.

✔️ Created a minimal “Delete Account” web page with a contact form that explains how to request deletion.
✔️ Published the page to a public URL.
✔️ Added that URL to the “Account deletion” field in Google Play Console to meet the requirement.
✔️ Kept scope intentionally small to ship compliance fast.

🎯 Result: The deletion-request page is live and the “Account deletion” step in the Play release flow is unblocked - one step closer to launch.

Why an Account Deletion Page Matters

Account deletion isn’t just a checkbox, it’s user respect, clarity, and smoother reviews.

✅ Unblocks the release pipeline. Google Play expects an easy-to-find deletion method. Having it now reduces back-and-forth during review.
✅ Builds user trust. A clear path to delete data shows the product respects user control from day one.
✅ Cuts support overhead. A single page that explains what gets deleted, how to request it, and how long it takes reduces email ping-pong.
✅ Prepares the foundation. Starting with a simple web flow makes it easy to add self-serve in-app deletion, status emails, and automation later.
✅ Improves data hygiene. Making deletion explicit encourages minimal retention and better lifecycle practices across the stack.

Conclusion

As a result of today’s work, the deletion-request page is live! This milestone means the ‘account deletion’ step in the Play release flow is now unblocked, bringing me closer to the anticipated launch. It’s quite exciting to see the tangible results of my efforts!

I hope you found this update inspiring and useful as you work on your projects. Sometimes, keeping it simple truly pays off!