GraphMaker — Privacy Policy
Effective October 11, 2026 · Last updated October 15, 2026 ·
App: com.klinck.graphmaker
GraphMaker ("the app") is published by Klinck Software LLC ("we", "us"). This policy explains what the app does and does not collect, who processes it, and your choices. We do not sell your personal information.
1. Information we collect
We keep collection to the minimum needed to run the app and to show ads (unless you purchase Pro Unlock).
You provide / stays on your device
- Your projects and chart data — stored locally on your device only. Cloud sync is not available in the current version (see §3).
- App settings — preferences stored locally.
- Photos for data scanning — if you use the scan feature, the photo you take or the image you select is processed on your device by Google ML Kit text recognition to extract table data into your project. We do not receive the image or the recognized text.
Collected automatically (by third-party SDKs)
- Crash & diagnostics (Firebase Crashlytics): crash stack traces, device model, OS version, app version.
- Usage analytics (Firebase Analytics): app events (e.g. screens opened), device information, the Firebase app-instance ID (a random per-install identifier), and a general country/region derived from your IP address. Firebase Analytics is configured not to collect the Android advertising ID.
- Advertising (Google AdMob — unless Pro Unlock purchased): advertising ID, App Set ID, your IP address (from which an approximate location is derived), and device/usage signals used to serve and measure ads. Where consent is required, only after you consent (see §4).
- Scan-feature diagnostics (Google ML Kit — only when you use the scan feature): device and app information, a per-installation identifier, performance metrics, and error codes, sent to Google over HTTPS for diagnostics and usage analytics, as described in Google's ML Kit data disclosure.
Device permissions
- Camera — only to take a photo for the scan feature, when you choose to.
- Photos / files (storage) — only to import data files or images you select.
- Internet and network state — to send crash reports, analytics and scan-feature diagnostics, process the Pro Unlock purchase through Google Play, and (unless Pro Unlock is purchased) load ads.
- Vibration — haptic feedback.
- Notifications — the app declares the notifications permission but does not post notifications in the current version.
The advertising and Firebase libraries add standard permissions of their own: the advertising ID
permission (AD_ID) and the Android Ad Services permissions, used by AdMob only for users without
Pro Unlock, and background-work permissions (WAKE_LOCK, FOREGROUND_SERVICE) used to send
crash reports and analytics. The app itself requests no other permissions. No location permission is
requested, and the app does not request access to your microphone, contacts, or calendar.
Purchasing the one-time “Pro Unlock” in-app purchase removes ads and stops the app from using your advertising ID. The Firebase app-instance ID (used for analytics and crash reporting) is still used for every install, including Pro.
Purchases. The one-time “Pro Unlock” purchase is processed entirely by Google Play’s billing system. We never receive or store your payment details (card numbers, billing address, etc.); Google Play provides the app only with confirmation of the purchase, and the app stores only the resulting entitlement state (whether Pro Unlock is owned) on your device. Purchase events may be logged by Firebase Analytics (see Third-party services). Google’s handling of your payment data is described in the Google Play Terms of Service and Google Privacy Policy.
2. How we use information
- Operate and maintain the app and your charts.
- Diagnose crashes and improve stability and features.
- Serve and measure advertising (with consent, unless Pro Unlock purchased).
Legal bases (EEA/UK). Where GDPR applies, analytics, crash, and scan-feature diagnostics processing rely on our legitimate interest in app stability, security, and improvement (Art. 6(1)(f)); advertising relies on the consent you give through the Google-certified consent prompt in the EEA/UK/Switzerland (Art. 6(1)(a)); and purchase processing relies on performance of our contract with you (Art. 6(1)(b)).
3. Cloud sync — your own Google Drive / OneDrive
Availability note: cloud sync is not enabled in the initial (v1) release — no cloud connection can be made and no data leaves your device for cloud storage in v1. This section applies from the version in which the feature ships.
Cloud sync is optional and off by default. When you enable it and sign in with Google or Microsoft, the app stores your project files in your own Drive or OneDrive account. We do not operate servers that host your files, and we do not retain copies. Sign-in tokens are stored encrypted on your device and are excluded from device backups. You can revoke the app's access at any time from your Google Account or Microsoft Account permissions.
4. Advertising & consent
We use Google AdMob. In the EEA, UK, and Switzerland we show a Google-certified consent (UMP) prompt before any ad processing, and the ad SDK initializes only if you allow it. You can reset ad personalization via your device's Ads settings (advertising ID). In the EEA, UK, and Switzerland you can review or change your consent choice at any time via the app's privacy options in Settings.
Approximate location, IP address and App Set ID. While ads are active, Google AdMob and Firebase derive an approximate (IP-based) location — a general region only — from your device's IP address. It is used for ad serving, fraud prevention and regional analytics, and is shared with Google for advertising. Google does not store the raw IP address after this derivation. AdMob also reads the App Set ID, a Google-provided identifier shared by apps from the same developer on your device, to measure ad campaigns. The advertising ID is used only by AdMob and only for users without Pro Unlock. The app never collects precise location and requests no location permission.
5. Third-party services
- Google AdMob — policy (ads)
- Google Firebase (Analytics, Crashlytics) — policy
- Google ML Kit (on-device text recognition for the scan feature) — terms
- Google Drive / Microsoft OneDrive — not used in the current version (cloud sync is not available)
6. Data retention
Local data persists until you delete it or uninstall. Firebase Analytics event data is retained for up to 14 months by default; Crashlytics crash reports are retained for a shorter, Google-defined period. See Google's Firebase privacy & security page for details. Cloud sync is not available in the current version, so the app stores no data in any cloud account.
7. Security
We use platform security features and HTTPS for network calls. No method of transmission or storage is 100% secure.
8. Children's privacy
GraphMaker is not directed to children under 13 (or the equivalent minimum age in your region) and we do not knowingly collect their data. If you believe a child provided personal data, contact us and we will delete it.
9. Your rights
EEA/UK (GDPR): access, rectification, erasure, restriction, portability, and objection. You also have the right to lodge a complaint with your local data protection supervisory authority — find yours via the European Data Protection Board. California (CCPA/CPRA): know, delete, correct, and opt out. We do not sell personal information for money. AdMob's use of the advertising ID for personalized ads may qualify as "sharing" under the CPRA; you can opt out by withholding or withdrawing ad consent, enabling non-personalized ads, or purchasing Pro Unlock, which stops ads and the use of your advertising ID for advertising. You can turn off Usage Analytics and Crash Reporting at any time in Settings, and erase your projects and settings with Settings → “Delete my data”. To exercise any right, email support@klincksoftware.com. For more on deleting your data, see our account & data deletion page.
10. International transfers
Google/Firebase may process data in the United States and elsewhere. These transfers are covered by the EU-U.S. Data Privacy Framework and/or Standard Contractual Clauses; see Google's ads data processing terms for details.
11. Changes
We may update this policy; the effective date above will change and material updates will be surfaced in-app or here. Material changes affecting advertising or data collection will be flagged in-app before they take effect.
12. Contact
Klinck Software LLC
c/o Northwest Registered Agent Service, Inc.
306 W Redwood St Ste 201
Baltimore, MD 21201
support@klincksoftware.com