1. Overview
GlowMark turns your device into a canvas of light — draw it, hold it up as an LED sign, share it. Your messages and display settings are stored on your device. The core features do not require an account; publishing a Glow works with or without one (see “Sharing Glows”). The App may send usage data associated with a random app-instance identifier so we can understand how GlowMark is used and improve it. Share Analytics is on by default. You can turn it off in Settings.
2. Information we collect
When Share Analytics is on, the App uses Google Analytics for Firebase to measure usage. This typically includes:
- App events such as first open, session start, work creation, Full Screen use, successful saves and exports, Pack reception and use, and upgrade screen views
- Purchase outcomes and plan categories (monthly, yearly, or lifetime) for analytics, associated with the app-instance identifier; not your payment details or Apple Account
- Device and app information such as device model, operating system version, app version, language, and country
- A random app-instance identifier used to distinguish installs, not your name or Apple ID
The App also uses Firebase Crashlytics so crashes can be found and fixed. A crash report contains the crash location (stack trace), device model, OS version, app version, and diagnostic information about the App at the time. The App does not intentionally attach work contents to crash reports. Turning off Share Analytics stops new analytics events and requests deletion of currently unsent reports. Automatic crash reporting is disabled from the next app launch; the SDK may still store crash diagnostics locally while reporting is disabled. Enabling reporting again can send locally stored reports, so turning OFF is not a promise that no local crash information exists or will ever be sent later. It does not remove reports already received or stop network requests for Pack reception, fonts, authentication, or sharing. Turning analytics back on starts a new measurement identity.
Analytics does not receive your message text, Pack contents or archive hash, local filenames or paths, font files, or Interact touch traces. These analytics events do not contain work contents, selected photos, your name, payment details, precise location, or an advertising identifier (IDFA). If you publish a Glow, see “Sharing Glows” for what that upload involves.
3. Information stored on your device
- Your saved LED message and display settings remain on your device
- Core creation and playback features do not require an account. Publishing and profile features use the authentication described below
- The App does not use cross-app tracking or advertising
4. Camera
If you open LED Camera, the App asks iOS for camera permission and shows a live LED mosaic of the front or rear camera on this device. Camera frames stay on this device. The App does not upload them, and it does not use the camera for tracking or advertising. You can decline camera access and continue using the rest of the App.
5. Motion
Maze uses on-device tilt only while that screen is open and does not store or upload it. Interact Fluid also uses on-device tilt. If you choose to record a Fluid performance, normalized tilt samples are saved in the board on your device. They are included in the project file only if you explicitly share that board.
6. Photos access
If you choose to save an exported video, GIF, image, or an LED Camera PNG, the App asks iOS for permission to add that file to your photo library. Saving an export does not itself upload it. You can also select individual photos using the system picker to add to a work or upload as a profile image; the App does not request access to your entire photo library. Content is sent when you choose sharing, publishing, or profile upload.
7. Downloaded fonts
Additional fonts are requested from Google Fonts when you choose Download for a specific font or open a Pack that requires an author font. That request contains no message text or Pack contents. If the author font cannot be loaded, Pack playback asks for your consent before using a system substitute; text shapes and layout may change. Downloaded fonts are stored on your device, and the built-in System Heavy font continues to work while offline.
8. Notifications and Live Activities
If you export a long video, GIF, or image, the App may show a local notification and/or a Live Activity when the export finishes. The App may also show a local notification when device heat changes the live LED refresh rate. These alerts are created on your device only. The App does not use remote push notifications (APNs) for export or thermal status and does not collect notification content.
9. Sharing Glows
If you share a board from the App, it is published as a Glow: three files are uploaded to our servers — a project file describing the board (.glmk), a preview video, and a thumbnail image. They are stored on Cloudflare and reachable by anyone who has the link https://glowmark.app/g/… — treat that link as public. Another person can open it to watch your Glow and remix their own copy; remixing never changes your original.
Sharing works with or without an account. Sign in with Apple (handled by Firebase Authentication) is recommended and keeps your shared pages manageable from any install; “Continue without an account” uses an anonymous Firebase credential held only on that install — deleting the App removes the ability to edit, hide, or delete that Glow. Your account is identified inside our service by an internal GlowMark user id. Our sharing service does not store your Apple Account name. Firebase Authentication may receive the email address, including an Apple private relay address, provided during Sign in with Apple; it is used for authentication, not app analytics.
You stay in control: hide, rename, or delete a Glow at any time from More → My Glows, which removes the files and the public page, or delete your account to remove your account and all of its Glows. Deleted files are purged from storage within 365 days.
We screen Glows for clearly inappropriate content before they go live, and anyone can report a shared page — web reports are bot-verified by Cloudflare Turnstile, and in-app reports work without an account. Our Content Policy applies to every Glow.
Public share pages themselves measure page views and button taps with Google Analytics (IP anonymized), so we can understand how Glows spread.
10. How we use analytics
We use usage data to understand which features people open, whether the App is stable, and how to improve GlowMark. We do not use this data to show ads, build advertising profiles, or track you across other companies’ apps or websites. Analytics and crash reporting are on by default. Turn off Share Analytics in More → Settings to stop new analytics events. Automatic crash reporting is disabled from the next app launch, and local diagnostics may remain; see “Information we collect” above.
The GlowMark websites — glowmark.app, play.glowmark.app, and shared Glow pages — use Google Analytics 4 to count page visits and see which links lead people to the App. IP addresses are anonymized. Website analytics are not combined with your App usage data and are not used for advertising.
11. Sharing
Analytics data is processed by Google on our behalf as Google Analytics for Firebase, and crash reports as Firebase Crashlytics. Sign-in and account tokens for shared Glows are handled by Firebase Authentication. Shared Glow files are stored and served by Cloudflare on our behalf. We do not sell App data. We do not share App data with advertisers. Google handles this data under its terms for Firebase / Google Analytics; Cloudflare handles it under its terms as our hosting provider.
Learn more: Firebase Privacy and Security and Google Privacy Policy.
12. Retention
Saved messages and settings remain on your device until you replace them, clear App data, or delete the App. A Glow stays online until you delete it or delete your account; the stored files are then purged within 365 days. Turning off Share Analytics stops new analytics events from this installation. Events already sent are retained according to the configured Google Analytics retention period. Turning collection off does not recall data already received.
13. Children’s privacy
The App is rated for general audiences and is not directed at children under 13. We do not knowingly collect personal information from children under 13.
14. Your choices
You can turn off Share Analytics in More → Settings. New analytics events stop; automatic crash reporting is disabled from the next app launch. Local diagnostics may remain, and data already received is not deleted. You can decline camera access and photo-library add access and continue using the rest of the App. Maze tilt is read only while Maze is open. You can manage Camera, Photos, Notifications, and Live Activities permissions in iOS Settings. Sharing is always optional; in More → My Glows you can delete any Glow, and in More → About you can delete your GlowMark account entirely. Deleting the App also stops new analytics events from this installation. Questions or requests about this policy: support@minipro.co.
15. Changes
We may update this policy. The “Last updated” date will change when we do. Continued use of the App after changes means you accept the updated policy.
16. Contact
Questions about this policy: support@minipro.co
MiniPro