Galgi ERP

Privacy Policy

Last updated:

This policy explains how Galgi ERP collects, uses, stores and shares information when you use its Android and desktop applications and associated services to manage finances and collaborate in workspaces.

Galgi ERP is operated by Sergej Drusch. For privacy questions, contact druschsergej@gmail.com.

Request account deletion

1. Data we collect

Account and authentication information
Your email address, display name if provided, account identifier, currency preferences and account timestamps. We process passwords and verification codes to authenticate you. The server stores password hashes and session information rather than plain-text passwords.
Financial and workspace information
Information you or other workspace members enter, including financial accounts, balances, transactions, assets, debts, counterparty names, payments, recurring expenses, notes, ownership and participation shares, workspace membership, join requests and activity history. Notes and attachments may also contain personal information you choose to enter about yourself or other people.
Files you choose to attach
Documents, photos and other files you upload, together with their names, types, sizes and links to workspace records. The Android app uses system file and photo selection, or an external camera app, when you choose to attach a file.
Usage and diagnostic information on Android
Firebase Analytics collects app usage events, screen views, session information, installation identifiers, device and app information, and approximate location derived from network information. Firebase Crashlytics collects crash and application-not-responding reports, stack traces, exception messages, device metadata and installation identifiers. Exception messages may contain information from the operation that failed.
Connection and support information
Technical information needed to handle requests and protect the service, such as IP addresses, request metadata and error information. Server request logs include a request identifier, method, path, response status, duration and result code; paths can contain workspace or record identifiers. We also process information you provide when contacting us by email.

2. How we use data

  • Create and secure accounts, maintain sessions and recover account access.
  • Store and display your financial records, attachments and workspace activity.
  • Enable collaboration with members of your workspaces.
  • Send verification codes and account security emails.
  • Schedule recurring expense reminders on your Android device when you enable them.
  • Understand app usage, investigate failures and improve reliability.
  • Respond to support, privacy and deletion requests, and prevent abuse.

We do not sell your personal data. The Android app disables advertising ID collection and advertising personalization. Usage and crash reporting are enabled in the released Android app. It does not explicitly set an ERP user ID, email address or custom business events in Firebase Analytics or Crashlytics; Firebase still uses its own installation identifiers. Reported screen names do not include navigation arguments such as email addresses or record IDs. The desktop app and backend use local logging rather than Firebase telemetry.

3. Sharing and service providers

Records and attachments in a shared workspace are available to its authorized members according to their access. Members can see display names, roles and activity authorship. Workspace owners and administrators can also see member email addresses and the names and email addresses in join requests. We also use these providers to operate Galgi ERP:

  • IONOS: hosts our server infrastructure in the European Union, where the main Galgi ERP service stores and processes account and workspace data. IONOS Privacy Policy.
  • Resend: processes recipient email addresses and service email content to deliver verification and account security messages. Resend Privacy Policy.
  • Google: Firebase Analytics and Crashlytics process Android usage and diagnostic information to provide analytics and crash reporting. Gmail processes privacy and support emails sent to our contact address. Firebase Privacy and Security and Google Privacy Policy.

When you choose to open or share an attachment with another application, that application receives a copy and handles it under its own privacy practices.

Resend and Google may process information outside the European Union under their applicable terms and data protection arrangements. Hosting our main infrastructure in the EU does not mean that all service providers process data only in the EU.

We may also disclose information when required by applicable law or a valid legal request.

4. Storage and security

The application communicates with the Galgi ERP API over HTTPS. Passwords are stored as hashes. Access to account and workspace data requires authorization, and attachments are kept in private storage and served through authorized requests.

The app keeps preferences and local application state on your device. Session access tokens are held in memory; refresh credentials use protected platform storage. On Android, the refresh credential is encrypted using Android Keystore and stored in a directory excluded from Android backup. On desktop, it uses the system keyring.

If you enable Android recurring expense reminders, the app stores a local snapshot of the recurring item, its amount, dates and your reminder settings, associated with your user, workspace and this installation. Reminder settings are stored on the device rather than on our server. Notifications can show the item's name, due date and amount according to your device's notification settings. Delivery is cancelled on sign-out, but saved reminder settings remain for a later sign-in by the same user.

Viewed attachments can be cached in the app's private temporary storage. Cached copies expire after 24 hours and are removed when the cache is next accessed; older files may be removed earlier to keep the cache within its size limit. Ending the session clears this document cache. Copies you save or share outside the app are managed by you and the receiving application.

Android backup is enabled for eligible local app data, including preferences and the local database, depending on your device's backup settings and backup provider. The protected refresh credential, reminder installation identifier and temporary document cache are excluded from Android Auto Backup. Device backups are separate from our server backups and follow your device and backup provider's rules. See Android backup information. Protect access to your device and do not share passwords or verification codes.

5. How long we keep data

We keep account and workspace data while it is needed to provide your account and the service. After your deletion request has been verified and manually processed, we apply no additional retention period to your deleted account and personal data in the active Galgi ERP systems.

Our server backup copies may remain for up to 30 days before they are deleted or overwritten. Shared workspace history is handled as explained in the deletion section below.

In-app record removal is separate from an account deletion request. Deleting a workspace archives it and allows it to be restored. Deleting a financial operation can leave activity history and earlier record snapshots. Detaching an attachment removes its link to that record and does not itself physically delete the stored file; other links and historical records may remain. Use the account and data deletion process below to request removal of your personal data.

Android analytics and diagnostic data have separate retention rules managed by Google. Crashlytics retains reports and associated identifiers for 90 days before beginning their removal from live and backup systems. Analytics retention depends on the Google Analytics property settings and the type of data. These periods are separate from the Galgi ERP account and backup periods above. See Firebase retention information and Google Analytics data retention.

6. Account and data deletion

You can request deletion of your Galgi ERP account and associated personal data by email. You do not need to reinstall the app or sign in to submit a request.

  1. Send an email from the address registered to your Galgi ERP account to druschsergej@gmail.com.
  2. Use the subject Galgi ERP account deletion and state that you want your account and personal data deleted.
  3. We process requests manually and verify that you own the account. If you no longer have access to its email address, contact us to discuss verification. Never send your password or verification codes.

After verification and manual processing, we delete the account, authentication records and associated personal data from active systems without an additional waiting period. This is permanent deletion, rather than account suspension. Sending an email does not automatically or instantly delete the account.

In shared workspaces, we remove your personal data and anonymize your authorship in retained shared history. Other members' data and shared records remain available to them. Our server backup copies may remain for up to 30 days.

A server-side deletion request does not remotely erase remaining settings or reminder snapshots on your devices, device backups, or copies you shared with other applications. You can remove remaining local app data using your device's application settings and manage device backups through your backup provider.

Firebase uses installation identifiers rather than an ERP account ID, so deleting an ERP account does not automatically identify or erase all related Firebase records. Contact us about analytics or diagnostic data deletion; we will assess what can be identified and request deletion from providers where applicable.

Email an account deletion request

7. Your choices and contact

You choose which financial information and files to add and which workspaces to join. To ask about your data, request access, correction or deletion, or raise a privacy concern, contact Sergej Drusch at druschsergej@gmail.com.

This policy page does not load analytics, advertising tools or external fonts. Your browser still sends the connection information needed to load the website. If you contact us by email, your email provider and ours also process that message.

8. Policy updates

We will update this page when our data practices change. The date at the top identifies the latest version.