Giglow
Privacy Policy
Summary
Giglow is a local-first app. Your concerts, festivals, notes, tags, and photos are stored on your device.
If analytics and/or ads are enabled in your build, limited device identifiers and event data may be collected by third-party SDKs.
Backups you export are files you choose to share; they may contain your photos and notes.
Who we are
This build of Giglow is published by Datanisha (“we”, “us”).
Contact: data.nisha.io@gmail.com
Data we store on your device
Giglow stores the content you enter (event names, dates, locations, ratings, notes, tags) and the photos you attach. This information is saved locally in the app database and the app media directory on your device.
Giglow may also store app preferences such as feature toggles.
Photos and storage
When you attach photos, Giglow copies them into its private app storage so they remain available even if the original is removed from your gallery.
To reduce device storage usage, Giglow may downscale and re-encode photos (for example, to a smaller resolution and a compressed format) before saving them in app storage.
Backups (export/import)
When you export a backup, Giglow creates a zip archive that may include your database content and photo files. The backup file is stored temporarily on your device. You can share it using your operating system share sheet, or save a copy through a system save flow (for example, to Files on iOS or a folder you choose on Android).
If you share a backup file with another app or person, that recipient may be able to access your notes and photos. Only export and share backups with parties you trust.
When you import a backup zip, Giglow reads the archive contents and writes the data and photos back into app storage.
Analytics
Depending on your build configuration, Giglow may use analytics (for example, Firebase Analytics) to understand usage, improve reliability, and prioritize features.
Analytics may collect events (such as screen views and button taps) and may use device identifiers or advertising identifiers as provided by the platform/SDK.
If you distribute Giglow publicly, you must provide any consent flows and disclosures required by law and platform policies.
Diagnostics (crash reports and performance)
To improve app reliability, Giglow may collect diagnostic data such as crash reports and coarse performance metrics (for example, app start time and network request timing).
Diagnostic data is intended to help identify crashes, freezes, and regressions. It may include device and OS information and an anonymized session or installation identifier provided by the SDK.
Giglow enables diagnostic collection only when the release build configuration and consent state allow Firebase-backed collection.
Giglow does not intentionally collect the content of your notes or photos as part of diagnostics, and you should not include sensitive information in feedback you choose to send.
Advertising
Depending on your build configuration, Giglow may show ads (for example, via Google Mobile Ads). Ad providers may process device identifiers (including advertising identifiers) to deliver, measure, and limit ads.
Giglow uses Google Mobile Ads consent APIs where supported. Depending on your region, consent choices, and platform privacy settings, Google may serve personalized ads, non-personalized ads, limited ads, or no ads.
If a production build uses cross-app/site tracking or IDFA access, the app and store disclosures must be updated and any required platform permission prompts must be shown before release.
Your choices (analytics and ads)
Where required by law (for example, in parts of the EU/EEA/UK), Giglow may present a consent prompt for analytics and/or advertising.
Outside of regions where consent is legally required, Giglow does not provide an in-app setting to turn ads on or off after the fact. The presence of ads and analytics depends on the build configuration and applicable legal requirements.
Third-party services and policies
Giglow may use third-party SDKs for analytics and ads. Their processing is governed by their own policies:
Data sharing
Giglow does not provide a built-in cloud sync service. Outside of analytics/ads SDKs (if enabled) and backup export actions you initiate (such as sharing a backup or saving a copy through your device’s file UI), Giglow does not intentionally transmit your archive content off-device.
Data retention and deletion
Your archive remains on your device until you delete it (for example, by removing entries or uninstalling the app).
Analytics/ads data retention is controlled by the third-party providers and your configuration with them.
Changes
We may update this Privacy Policy from time to time. The effective date at the top indicates the latest revision.