Skip to content
Eldgard alxnsv.io

A considered boundary

Privacy Policy

What Eldgard accesses, why it needs that access, and how you stay in control of your data.

Effective and last updated

The short version

Eldgard is a Firestore client, not a data host. The apps send requests directly from your device to Google APIs or to the Firestore emulator endpoint you choose. There is no Eldgard-operated proxy receiving your Firestore documents, and the current apps have no advertising or behavioral analytics. We do not sell personal information or Google user data.

Desktop Google refresh tokens are stored in your operating system’s credential vault. On Android and iOS, Google’s native sign-in software manages authentication persistence. App preferences, connection details, saved queries, and workflow metadata are stored locally as described below.

Scope

This policy covers the Eldgard desktop app for macOS, Windows, and Linux; the read-only Eldgard mobile app for Android and iOS; the Eldgard pages on this website; early-access requests; and support messages sent to alxnsv.io. Eldgard is developed by Aleksandr Nosov under the alxnsv.io name.

Google, Firebase, your organization, your device platform, and any emulator host you connect to handle information under their own policies and agreements. If an employer or another organization manages your Google Cloud account or Firestore project, that organization may also control and audit your access.

Google user data Eldgard accesses

When you choose Google sign-in, Eldgard may access the following data for the account you select:

  • Account identity: your Google account identifier and email address, plus your display name on mobile, to show which account is connected and keep accounts separate.
  • Firebase and Cloud metadata: projects visible to your account and their Firestore database metadata, so you can pick a project and database.
  • Firestore data: collection paths, document IDs, document fields and values, query results, and related Firestore responses needed to browse and work with the database you select.
  • Authorization data: short-lived access tokens and, on desktop, a refresh token used to keep you signed in. Eldgard does not receive your Google password.

Permissions requested

Depending on platform and the step you choose, Eldgard requests:

  • openid and Google’s email/profile access for the account identifier and display information;
  • https://www.googleapis.com/auth/firebase.readonly to discover available Firebase projects; and
  • https://www.googleapis.com/auth/datastore to call the Firestore API.

The desktop app can read and modify Firestore data. The mobile app is designed as a read-only client, but Google does not provide a read-only Firestore OAuth scope; the Datastore scope itself can authorize broader access. Your Google Cloud IAM roles remain the controlling boundary, and Google sign-in does not grant a new project role.

Use an account and IAM role limited to the access you intend. For the mobile reader, use a read-only IAM role when connecting to production data. Requests authenticated with Google OAuth or a service account are governed by Google Cloud IAM, not Firebase client Security Rules.

Data stored or handled on your device

Desktop

  • The secure session record contains your Google account identifier, email address, selected project IDs, refresh token, and an authorization-version marker. It is stored through the operating system credential vault.
  • Saved query definitions and the 15 most recent query definitions are stored in ~/.fireground/queries.json. Query values may themselves contain personal or confidential information.
  • Autoflow definitions are stored in ~/.fireground/flows.json. They can include project and database identifiers, collection names, a local seed-file path, and last-run status. The source file is not copied into that record.
  • The activity log is a bounded, in-memory view of recent actions and errors. It is not an analytics feed or a persistent log file.
  • Workspace recovery keeps tab references, query editor state, and view settings in operating-system secure storage, with a backup snapshot. Optional document-draft retention is off by default. When enabled, it can retain document contents, unfinished edits, and original server versions. Recovery has size limits and a seven-day tab retention window; it does not persist fetched pages as an offline database.
  • The optional local mutation journal is separate from the activity log. Recording is off by default. When enabled for a project scope, it stores reviewed single-document operations, typed before/after contents, resource paths, times, server versions, and outcomes in secure storage. Its default retention is 30 days, subject to entry and size limits. Pending operations and active restore records may be retained until settled. It keeps one additional secure backup snapshot and has no plaintext fallback.
  • Read-only protection settings are stored locally in ~/.fireground/read_only.json. Secure credential, recovery, and journal storage does not make every local app file encrypted.
  • A service-account JSON key you select is read into app memory to create that connection. Eldgard does not copy the key into its settings or session files. The original key file remains wherever you stored it.

Mobile

  • Saved local-emulator profiles can include a name, host, port, project ID, database ID, and the last selected profile. They are stored in the app’s application-support directory.
  • Saved query definitions are stored locally per database and query scope, including collection groups, and can contain field names and query values.
  • Home stores up to 20 pins, 30 recent places, and 20 remembered cloud destinations in a bounded local file. These records contain endpoint, account, project, database, path, and saved-query identifiers—not document bodies, query results, or tokens. Document-change comparisons and frozen baselines stay in memory and are not persisted.
  • Google’s native sign-in SDK manages the authorized account and token persistence. Eldgard does not write access tokens into mobile connection profiles.

Firestore content and files

Firestore content is held in memory while you view or edit it and can be retained by the optional desktop recovery and journal features described above. Desktop JSON and CSV imports may use temporary local staging files; exports create files at the location you choose. Copy actions and saved-query handoff put selected content on the system clipboard. Handoff includes query names, scope, field paths, and operand values, but not credentials or result documents. You choose how to transfer that text; the transfer channel, exported files, and clipboard history are outside Eldgard’s control.

How data is used and shared

Eldgard uses Google user data only to authenticate you, discover the projects and databases available to your account, display and query Firestore data, and perform the user-directed desktop operation you choose. We do not use it for advertising, credit decisions, data brokerage, or training general-purpose AI models.

The app transmits data to Google when calling Google and Firebase APIs and to a local or network emulator host when you choose that endpoint. We do not transfer Google user data to third parties except when you direct the app to an endpoint, file, or clipboard destination, or when disclosure is required by law. If you send logs, screenshots, or data to support, that material is shared with the email providers used to deliver and store the conversation.

If you request early access, we use the email address you submit to manage your request and contact you about Eldgard invitations and launch availability. Formspree processes and stores the submission and forwards it to our email inbox. Our email providers process and store the forwarded notification. Formspree also processes request and security information under its Privacy Policy (opens in a new tab).

Eldgard’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.

Retention and deletion

Local settings remain until you remove them or clear the app’s data. A desktop Google session remains in secure storage until its projects are removed from Eldgard, the session becomes invalid, or the secure record is otherwise deleted. Google’s mobile SDK may retain the authorized account until you sign out, revoke access, or clear the app’s data.

Secure workspace recovery and local mutation history have the retention limits described above and separate in-app clearing controls. Disconnecting Google does not itself clear those records, saved queries, or files you exported. Complete the applicable steps on the Data & Deletion page for a full local cleanup.

Support correspondence is kept only as long as reasonably needed to answer the request, maintain support records, resolve disputes, or meet legal and security obligations. Website infrastructure may keep limited request and security logs according to the hosting provider’s operational retention settings.

Our current Formspree plan provides 30 days of submission history in its dashboard. We retain forwarded requests in our email inbox while managing early-access invitations and launch communication, unless you ask us to delete them sooner. The dashboard history limit does not delete inbox copies. You can withdraw your request by emailing hello@alxnsv.io from the address you submitted.

See Data & Deletion for step-by-step removal instructions. Removing a connection or deleting Eldgard does not delete documents from Firestore, delete a Google Cloud project, remove an IAM role, erase an exported file, or revoke a service-account key.

Security and your choices

Eldgard uses Google’s installed-app sign-in flow on desktop, native Google sign-in on mobile, TLS for production Google API requests, and the operating system credential store for desktop refresh tokens. No method of storage or transmission is completely secure, so protect your device, local files, emulator network, and credentials.

You can use a local emulator without Google sign-in, decline Google access, remove saved connections, sign out on mobile, revoke Eldgard in your Google Account, or stop using the app. Restrict emulator access to trusted networks: an emulator exposed on a LAN may be reachable by other devices and should not be treated as a production security boundary.

Optional website analytics

This notice covers the alxnsv.io website, including its product pages. If you choose Allow analytics, the website uses Google Analytics to measure page visits and clicks on app-store, early-access, and contact links. Google may process cookie identifiers, browser and device information, and approximate location derived from your IP address. These measurements help us understand which pages are useful.

Analytics loads only after you opt in. We store your choice in your browser. You can decline or change your choice using Analytics preferences. We disable advertising features and do not send email addresses, email contents, spool inventory, or Firestore documents as analytics events. A contact-link click does not tell us whether you actually sent an email.

Withdrawing consent stops future collection in this browser and removes the website’s Analytics cookies; it does not erase information already processed by Google. See Google’s Privacy Policy for information about Google’s processing. Hosting and security services may still process ordinary request data such as IP address, user agent, requested page, and access time to deliver and protect the site.

Privacy rights

Depending on where you live, you may have rights to ask about, access, correct, delete, restrict, or object to certain processing of your personal information, or to receive a portable copy. Eldgard cannot retrieve app data that never leaves your device or Google project; use the app, device, Google Account, and project controls described in Data & Deletionfor that material. Contact us about support correspondence or another record held by alxnsv.io. We may need to verify the request and may retain information where the law permits or requires it.

Eldgard is a professional developer tool and is not directed to children under 13 or the higher minimum age required where they live. We do not knowingly solicit children’s personal information. If you believe a child sent personal information to support, contact us so we can review and delete it where required.

Changes and contact

We may update this policy as Eldgard changes. The effective date above identifies the current version. Material changes will be reflected on this page before or when they take effect. Paid checkout, license activation, and public trials are not currently active; this policy will be updated before a launch introduces additional purchase or activation data handling.

For a privacy question or a request involving early-access or support data, email hello@alxnsv.io. Include no Google password, OAuth token, service-account private key, or unnecessary Firestore content.