Skip to content
Eldgard alxnsv.io

Leave no ember unattended

Data & Deletion

Disconnect Eldgard, remove its local records, and understand what must be deleted separately.

Effective and last updated

What deletion means in Eldgard

Eldgard does not create an alxnsv.io app account and does not keep a server-side copy of your Firestore database. Most deletion therefore happens on your device, in your Google Account, or in the Firestore project and files you control.

Removing a connection tells Eldgard to forget that connection. It does not delete a Google Cloud project, revoke an IAM role, erase Firestore documents, stop an emulator, remove a service-account key from Google Cloud, or delete an exported file.

Disconnect Google access

  1. Desktop: remove each project associated with the Google account from Eldgard. The saved secure session is removed when no selected projects remain for that account.
  2. Mobile: open Account and choose Sign out.
  3. For an account-level revocation, open Google Account connections (opens in a new tab), choose Eldgard, and remove its access. Revocation invalidates the authorization at Google even if a local app record remains.

Your organization’s administrator may separately need to remove IAM roles, OAuth grants, or managed-device data. Eldgard cannot do that on the organization’s behalf.

Delete desktop app data

Before closing Eldgard, clear its secure local records in the app:

  • Open Workspace recovery and choose Clear saved workspace. This clears both secure recovery snapshots and pauses capture for this session. Merely turning off document-draft retention removes drafts, not all workspace metadata.
  • Open Project actions → Local mutation history for each recorded scope. Turn off Record reviewed document changes to delete that history and stop recording. Clear history removes existing records but leaves recording enabled. Both secure copies are scrubbed when removal succeeds.
  • Resolve any storage error before treating a clearing action as complete, and disconnect Google separately as described above.

Then close Eldgard so it cannot rewrite settings while you remove them. Saved queries, query history, and Autoflow records currently use a legacy internal directory named .fireground in your home folder:

  • delete ~/.fireground/queries.json to remove desktop saved queries and recent query history; and
  • delete ~/.fireground/flows.json to remove Autoflow definitions, seed-file paths, and stored run status.
  • delete ~/.fireground/read_only.json to remove saved project and collection protection settings. This resets those local locks if you use the app again; it does not change IAM.

The activity log exists only in memory and is cleared when the app closes. Uninstalling the desktop app may not remove files in your home directory or credentials retained by the operating system, so remove the items above and disconnect Google separately when you need a full cleanup.

Delete mobile app data

You can remove individual local-emulator profiles from the Local connections screen and delete individual saved queries from the Saved queries sheet. These actions do not change data at the endpoint.

Remove pins, clear or remove recent places, and forget remembered cloud destinations from Home independently. These are navigation records, not Firestore documents. In-memory document-change observations are not retained after the app process ends.

To remove all Eldgard mobile storage:

  • On Android, clear Eldgard’s storage in system settings or uninstall the app.
  • On iPhone or iPad, choose Delete App. Offload App can preserve application data.

Mobile operating systems, Google’s sign-in SDK, device backups, and enterprise management can retain authentication or app data under their own settings. Sign out and revoke the Google connection before deleting the app when you want to end Google access as well.

Service-account keys

Removing a service-account connection from Eldgard closes the live client and releases the in-memory key data. Eldgard does not delete the original JSON file. Delete that file from its storage location and backups if you no longer need it.

To invalidate the credential, disable or delete the corresponding key in Google Cloud IAM and rotate any credential that may have been exposed. Removing the local JSON file alone does not revoke the key at Google.

Firestore data, exports, imports, and clipboard

Delete or restore Firestore documents using the controls and backups for the project that owns them. An Eldgard import writes to that target; uninstalling Eldgard cannot undo it. Likewise, you must delete exported JSON or CSV and source import files from the locations and backups you control.

On mobile, copied paths, values, or links may remain in clipboard history or device synchronization. Replace or clear the clipboard and review device clipboard settings separately.

Website and support data

The website has no Eldgard user account to delete. Hosting and security providers may retain limited request logs according to their operational settings.

To leave the early-access list and request deletion of your signup, email hello@alxnsv.io from the address you submitted. We will remove accessible copies from Formspree and our inbox unless retention is required for legal or security reasons. Provider backups and operational logs follow their retention settings.

To request deletion of a support conversation, email hello@alxnsv.io from the address used for the conversation and identify the message thread. We will delete the accessible support copy unless retention is required for legal, fraud-prevention, dispute, or security reasons. Residual backup copies may remain until the email provider’s backup cycle completes.