Delete your account

1. Open SmartCommute SG-MY.
2. Go to More, then your Profile.
3. Choose Delete Account and confirm.

In version 2.1.0 and later, the app first asks our server to run the broader cleanup, which can reach data the app cannot. If the server does not confirm that it finished, the app stops before removing your sign-in and lists what was not deleted, so you can try again.

The app sends several deletion requests in sequence. If one fails, requests that already succeeded are not rolled back, so deletion can be partial. The app keeps your sign-in account when an earlier step reports a failure, but records removed before that failure may already be gone. In 2.1.0 and later that can include your profile, because the server step runs first.

The Firebase sign-in account is attempted last. If Firebase requires a recent sign-in, the app-accessible data may already have been removed while the sign-in account still exists. Sign in again and retry, or contact support for a manual review.

Email causewaysmartcommute@gmail.com from the address you signed in with when possible, and include the nickname shown on your profile. Ask us to check both the app-side result and the broader server-side cleanup, including detaching your reports and replies from your account by hand.

An email starts a verification and manual review; it is not a promise that a record with no account identifier can be found or that data subject to a retention need can be erased immediately. Support can tell you what was completed and what, if anything, remains.

Every version removes these with your own access. In 2.1.0 and later they follow the server-side cleanup below; in 2.0.6 and earlier they are the whole in-app deletion. A successful step is permanent, but seeing a final error does not mean every earlier step failed.

Queue watches

Any saved watch, so it should not keep notifying you afterwards.

Flight price alerts

Alerts stored under your account.

Firestore notification preferences

The server record of which community notifications you requested. Device settings are listed separately below.

Legacy trip rows

Older per-user trip records that the app can find.

Your profile document

Nickname, avatar, notification token and platform. Deleting this parent document does not itself delete nested records.

Your Firebase sign-in account

Attempted last, after the app-accessible data steps succeed. Firebase may require you to sign in again before this final step.

These categories need privileged server-side queries. Version 2.1.0 and later run them automatically when you delete your account in the app. Version 2.0.6 and earlier do not: if you deleted with one of them, ask support to run them. Do not treat an in-app success message from 2.0.6 or earlier as confirmation that these server-only steps ran.

Nested account data

Notification history, stats, avatar unlocks, block lists, posting safeguards and sensing-session cursors sit below the profile path. Deleting the profile document in the app does not delete those subcollections.

References held elsewhere

Notifications and block-list entries in other accounts, notification cooldowns, stage votes and other cross-account references need privileged server-side queries.

Community and journey records

The broader process is designed to remove or replace account references on posts, replies, moderation records, sensing data and older journey rows. Some underlying content or measurements are retained as described below.

Version 2.1.0 and later run the broader cleanup when you delete your account in the app; for older versions it runs after a verified email request. Either way, it deliberately retains some useful or integrity-sensitive records while removing or replacing direct account references where described below.

Community reports, comments and replies

The text stays so conversations and traffic reports still make sense. Until broader cleanup runs, a post can still show the name and avatar saved with it; with 2.0.6 and earlier, that is until a support request has it run. That cleanup clears the author uid and avatar and changes the displayed author to “Deleted user” where it can match the post.

Moderation reports

A report stays counted so deleting an account does not withdraw a safety report. The broader cleanup replaces the reporter reference with an unrelated identifier.

Journey, sensing and crowd measurements

Measurements used for aggregate traffic analysis may stay. The broader cleanup clears direct uid fields it can find; session-scoped hashes can remain pseudonymous rather than fully anonymous.

Subscription and entitlement record

This may be retained for refunds or chargebacks. The broader process stamps a 180-day retention date, but automated expiry is not currently enabled, so the record may remain until a later cleanup.

Aggregate and service data

Road, camera, queue and system aggregates are not removed simply because one account is deleted.

These categories cannot be covered by an unconditional automatic deletion promise. Include any relevant details in your support email so they can be reviewed without assuming they were found.

Older fuel-check report hashes

Some reports carry a repeatable hash derived from the account uid. It is pseudonymous and is not cleared automatically today.

Votes on individual comments

The voter exists only in the document name, so cleanup uses a bounded scan rather than a direct account query. A large or interrupted scan can leave votes for manual review.

Website build enquiries

A build enquiry can include a name, company and contact address but no app uid. It cannot be found automatically from an app-account deletion request.

Legacy or externally populated collections

The source cannot establish whether per-user records exist in user_locations, api_keys, api_key_usage or legacy fuel_check_reports, so this page does not promise their automatic removal.

Settings and subscriptions on your device

The current deletion flow leaves local traffic-alert switches, advertising prompt state, approach reminders and the journey-study preference on the phone. It also does not unsubscribe the phone from device-level FCM traffic topics. Turn traffic alerts off before deletion when possible; afterwards, use the device notification controls and mention continued alerts in a support request.

In 2.1.0 and later the app runs the server-side cleanup and its own steps when you confirm. With older versions the app runs only its own steps, and the server-side cleanup waits for a verified manual review, which can take longer. The current code inventory does not define a public backup roll-off date, so this page does not promise that every copy disappears immediately. Keep the app's result message and any support reply as the record of what completed.