Contact support
Email hello@alxnsv.io. Eldgard is still in development, so support is best-effort and no response-time guarantee currently applies.
Please include:
- desktop or mobile, operating system, and OS version;
- Eldgard version or build identifier;
- whether the target is Google Cloud or a local emulator;
- the action you tried and the complete error message; and
- steps that reproduce the problem.
Screenshots are useful after you crop or cover account email, project identifiers, document data, and private paths. Never send a password, OAuth token, service-account JSON, private key, exported database, secret environment file, or unredacted production record.
Google sign-in and IAM
Signing in identifies your Google account but does not grant that account a new role. If a project or database is missing, confirm that the chosen account can see the Firebase project and that its Google Cloud IAM role authorizes the operation you are attempting.
A permission error from a production database is normally an IAM issue. Firebase client Security Rules do not authorize Google OAuth or service-account REST requests. For the mobile reader, assign a read-only IAM role even though the interface itself contains no write controls.
If a saved sign-in stops working, remove the affected cloud project, reconnect the Google account, and approve the scopes again. You can also review or revoke Eldgard from your Google Account connections (opens in a new tab).
Local emulator connections
On the same desktop, start with 127.0.0.1 and the Firestore emulator port, commonly 8080. Confirm the project ID matches the emulator configuration and that the emulator is already running.
A physical phone cannot use its own 127.0.0.1 to reach an emulator running on your computer. Use the computer’s reachable LAN address, allow the port through the firewall, keep both devices on a trusted network, and avoid exposing the emulator to the public internet. Network and emulator behavior vary by development setup.
Before imports, deletes, and bulk changes
Confirm the selected project, database, and collection and make a backup before a desktop import or destructive action. Test the same workflow in an emulator when possible. CSV imports validate every row and only create new documents; existing IDs are rejected. Other import formats have different behavior, and Firefoo imports can overwrite fields on existing documents. Check the chosen import policy. A successful operation changes the connected database, not merely the local view. Interrupted or failed bulk work can leave partial changes; inspect the reported outcome before retrying.
Exports are written to the path you select. If an export is missing, check that location and your operating system’s file permissions. An Autoflow records the seed-file path, so moving or deleting that file will prevent a later run from reading it.
Safeguards and recovery
Read-only mode
Use a project’s menu or a collection’s lock control to prevent new writes from Eldgard while keeping reads and exports available. Inherited collection locks must be removed at the parent that enabled them. Requests already sent can finish. These app settings do not change Google IAM or Firebase Security Rules.
Single-document review
Review the exact environment, document path, typed diff, and loaded server version. If another client changed the document, reload the latest version, rebase the draft, and review again. An unknown write outcome also requires a reload; it is not proof that nothing changed. Bulk imports, collection operations, and multi-document saves have their own behavior and are not an atomic transaction.
Returning after a restart
Workspace recovery restores your working context. Document-draft retention is optional and off by default. Reconnect to the exact target, revalidate access, and review a recovered change before applying it. Clearing recovery does not delete Firestore data.
Optional local mutation history
Enable Record reviewed document changes from Project actions → Local mutation history if retaining sensitive document contents locally is appropriate. Eligible confirmed single-document operations can be reviewed for restore, subject to current server-version or existence checks. This is not a complete audit trail, database backup, point-in-time recovery service, or bulk undo. It does not cover external writers, imports, or collection operations.
Google OAuth and service-account access still follows Google’s Firestore REST authorization rules (opens in a new tab). Use appropriately limited IAM permissions for production work.
Mobile reader
The Android and iOS app is a read-only companion and is also in development. It can browse and query Firestore but does not provide document mutation methods. If a cloud connection works on desktop but not mobile, check the selected Google account, mobile OAuth setup, required scopes, Firestore Native mode, and IAM permissions.
Removing a saved local connection removes only its profile from the device. It does not stop the emulator or change any Firestore data.
Search covers loaded documents, not unseen collection pages. Query Count is an explicit server request and can count all matches or respect the query’s limit; it is not the number of loaded rows. Document Changes compares successful observations from your own refreshes, not every intervening write. Neither feature is a live monitoring service.
Take a saved query to mobile
- On desktop, choose Export for mobile on a saved query. Review the payload and copy it using Copy handoff.
- Transfer the text using a channel you trust. On mobile, open Import saved query, paste it, and choose Review import.
- Choose or set up your own matching connection, then confirm the environment, project, database, and collection or collection-group scope.
- Load the query draft. Review or edit it, then choose Run or Save separately. Importing does not execute the query.
Credentials, emulator addresses, and result documents are excluded, but query values can still contain sensitive data. There is no automatic sync. Mobile can export this format too; desktop currently exports it but does not import it. A phone needs its own reachable emulator address, not the desktop’s localhost address.
Security reports
Report a suspected vulnerability privately to hello@alxnsv.io with the subject “Eldgard security report.” Include the affected version, impact, and safe reproduction steps. Do not access other people’s data, disrupt a service, or include live credentials in the report. No public bug-bounty program is currently offered.