Privacy Policy

This Privacy Policy explains what data Glossnote (“the App,” “we,” “us”) collects, how it is used, and who it is shared with. Glossnote is developed and maintained by an independent developer, contactable at valeriachub.dev@gmail.com.

Glossnote does not require an account and does not operate its own servers. Almost everything you create in the App — notebooks, notes, translations you write yourself — stays on your device. The sections below describe the few cases where data leaves your device, and why.

1. Data you create

Notebooks, saved text, and any translations you write by hand are stored locally on your device using on-device storage (Hive). This content is never uploaded to us, and we have no way to see it. If you delete the App or its data, this content is permanently deleted with it — we cannot recover it for you.

2. Translation lookups (third-party service)

When you look up a word or a sentence, the App does one of two things:

• Offline dictionary lookups (English → Ukrainian) are answered from a dictionary file bundled inside the App. Nothing is sent anywhere for these.
• When the bundled dictionary can’t answer, or when you look up a sentence for context, the App sends the word or sentence text to Lingva Translate, a free, open-source translation API (by default hosted at lingva.dialectapp.org), in order to fetch a translation and display it to you.

This means the specific words and sentences you look up are transmitted to Lingva’s servers to be translated. Lingva is an independent, third-party service — it is not operated by us, and its handling of that traffic is governed by its own operator, not by us. We do not control what Lingva logs or retains. We do not send your notebook titles, your saved notes, or any other content — only the specific word or sentence you actively look up.

3. Analytics (Firebase Analytics)

We use Firebase Analytics (a Google service) to understand how the App is used — for example, how many notebooks people create, which features get used, and whether the App crashes. Analytics events are limited to things like counts, buckets, and fixed category labels (e.g. “notebook created,” “word tapped — result: looked up successfully”). We deliberately never log the words you look up, your notebook text, dictionary entries shown to you, or any translation you write — this is enforced in the code that sends analytics events, not just a policy promise.

Firebase Analytics automatically collects some standard technical data as part of how it works, such as an app-instance identifier, device model, operating system version, general (city-level) location derived from IP address, and app usage timestamps. This data is processed by Google. See Google’s Firebase privacy documentation and Google’s Privacy Policy for details on how Google handles this data: firebase.google.com/support/privacy and policies.google.com/privacy.

4. Crash reporting (Firebase Crashlytics)

We use Firebase Crashlytics to receive crash and error reports so we can fix bugs. These reports can include technical diagnostic information such as device model, OS version, app version, and the state of the App at the time of the crash (e.g. a stack trace). Crash reports are processed by Google under the same Firebase privacy terms linked above.

5. Remote configuration (Firebase Remote Config)

We use Firebase Remote Config to remotely adjust certain app settings (for example, feature availability) without requiring an app update. This does not involve any of your personal content and does not identify you individually beyond the same technical identifiers described in Section 3.

6. What we don’t collect

We do not require or ask for your name, email address, phone number, or any account credentials. The App does not request access to your camera, microphone, photos, contacts, or location. The only device permission the Android version requests is internet access, which is required for translation lookups and the services described above.

7. Data sharing

We do not sell your data. The only recipients of any data described above are:

• Lingva Translate — receives the specific text you look up, as described in Section 2.
• Google / Firebase — receives analytics events, crash reports, and remote-config requests, as described in Sections 3–5.

We do not share data with anyone else.

8. Data retention

• Content you create (notebooks, notes) stays on your device until you delete it or uninstall the App.
• We have no server-side copy of your content, so there is nothing for us to retain or delete on your behalf.
• Analytics and crash data are retained by Google/Firebase according to Google’s own retention schedules; see Google’s Firebase privacy documentation for current retention periods.
• We do not control how long Lingva retains lookup requests, as it is an independent third party.

9. International data transfers

Because the App uses Google’s Firebase services and a third-party translation API, the limited data described above may be processed on servers located outside your country, including in the United States or other jurisdictions where those providers operate.

10. Children’s privacy

Glossnote is not directed at children under 13, and we do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us at valeriachub.dev@gmail.com so we can address it.

11. Your rights and choices

Because your notebook content lives only on your device, you already have direct control over it: you can edit or delete any notebook, note, or translation at any time within the App, and uninstalling the App removes all locally stored content.

Depending on where you live (for example, under the GDPR in the EU/EEA, or similar laws elsewhere), you may have additional rights regarding the technical data processed by Google/Firebase as described above, including the right to request access to or deletion of that data. Because that data is processed by Google as described in its own privacy documentation, you can also manage certain analytics and advertising identifiers directly through your device’s OS-level privacy settings (e.g. resetting your advertising identifier). For requests specifically about data we hold, contact us at valeriachub.dev@gmail.com and we will assist to the extent we are able, given that we hold no server-side account or content data.

12. Security

We take reasonable measures appropriate to a local-first app: your content is stored using standard on-device storage mechanisms, and network requests to Lingva and Firebase use standard encrypted (HTTPS) connections. No method of storage or transmission is 100% secure, and we cannot guarantee absolute security.

13. Changes to this policy

We may update this Privacy Policy from time to time, for example when we add a new feature that changes what data is processed. We will update the “Effective date” above when we do. Continued use of the App after a change means you accept the updated policy.

14. Contact us

Questions about this Privacy Policy or how Glossnote handles data can be sent to valeriachub.dev@gmail.com.