
Account deletion · tested, app not ready
Delete your Home Cadence account
Scope of Home Cadence account deletion: process checked in a test environment, app not ready for distribution.
Process checked in testing, app not yet ready
Home Cadence has a prepared path to request and execute deletion of an individual account. Tests with synthetic data in a test environment confirmed receipt of the request, retention periods, retry after failed operations, the correct order of data deletion and a minimal record confirming deletion. The 18-and-over rule is approved, but the public website and its legal review do not confirm that the app is ready. We still lack confirmation on a real device running the app version intended for distribution that notifications and installation-identifier deletion work correctly, completion of the Data safety declaration and Play Console approval.
Request path
In the app, open Settings, Privacy and data, Delete account. The server issues a receipt containing an identifier, state and dates. Acceptance that starts household separation is not presented as completed deletion.
Deletion scope
- the individual Home Cadence account and its tokens;
- household membership without overriding the other person's rights;
- shared content and the rules for data belonging to two people;
- devices, app identifiers and the Firebase installation identifier (FID);
- encrypted data and metadata stored in cloud services, task queues, logs, backups and the minimal deletion record;
- support correspondence;
- research data if analytics is separately activated.
Household and Google account
Deleting Home Cadence does not delete the user's Google Account. For an active household, the existing separation starts: both people receive the same seven-day export deadline, writes stop, and shared encrypted content is deleted only after archive and retention. The other person's app account is not deleted.
Separation can be cancelled only after both roles agree. The requester records a decision through the protected receipt and the other person through their session. Cancellation does not revive old sessions or FCM; the requester must sign in again.
Retention and deletion confirmation
Tests in a test environment confirmed safe resumption after interruption, the correct order of data deletion and final removal of the account, sessions, household membership, devices and the server-side installation-identifier record. Retention periods for logs, backups and support data still require approval, and the Firebase operations have not been confirmed on a real device running the app version intended for distribution.
Contact
Questions about the path may be sent to hello@brillnet-app.com. Do not send a Google password, tokens, recovery codes or private keys.