Table of Contents
Account Closure & Revoke – Backend Process #
Ledgerely ensures a structured and automated process for handling account closure requests while optimizing cloud infrastructure costs. This process includes storing closure data, running daily batch jobs, and allowing users to revoke their request within 365 days before permanent deletion.
Account Closure Request Processing: #
Receiving & Storing Closure Data #
When a user submits a Close Account request, the backend captures:
User’s selected reason(s) for closure (one or multiple options).
Comments (user-provided feedback).
Date field (timestamp of request submission, stored in DB).
Saving Data in the Database #
- The closure request is saved in the database with a timestamp.
- The user remains inactive, but their data is retained for 365 days.
Automated Account Deletion (Batch Job) #
Daily Verification (Batch/Cron Job) #
- A cron job runs daily to check for accounts with closure requests older than 365 days.
- If an account meets the 365-day limit, the system:
Deletes all application-linked data to reduce cloud infrastructure costs. - Sends an email notification to both:
- The user (confirmation of permanent deletion).
- Ledgerely Admins (for internal tracking).
Account Revoke Process #
User Revoke Action #
- Within 365 days, users can log in and click the “Revoke Account” button.
- Once clicked, the closure request is removed from the database.
Cron Job Handling #
- Since the closure request is deleted, the batch job ignores the user in future runs.
- The user regains full access to their account and services.
Final Notes #
- The account is permanently deleted after 365 days if not revoked.
- Ledgerely ensures automated cleanup, reducing cloud infra costs while offering users a chance to recover their data before deletion.
