Privacy Policy — Light Sword
Last updated: 25 August 2026
Thank you for using Light Sword (the “App”). This policy explains what data the App does and does not handle, and what choices you have.
Summary
- The App shows ads served by Google AdMob. The ads SDK collects a limited set of data (such as your device’s advertising ID) to serve and measure ads.
- The App also sends anonymous usage and crash reports (Google Analytics for Firebase and Firebase Crashlytics), so that problems can be found and fixed. There are no accounts, and these reports are not tied to your name or e-mail address.
- Everything you do in the App — colors, hilt builds, scores, achievements — is stored locally on your device and is never uploaded.
- The camera, motion sensors, flashlight and two-phone duel all work on-device or device-to-device, with no servers involved. Video clips you choose to record are saved only to your device's gallery.
Advertising (Google AdMob)
The App displays banner ads and optional rewarded ads served by Google AdMob (Google Mobile Ads SDK). To serve and measure ads, Google may collect:
- your device’s advertising ID,
- coarse, IP-derived information (such as approximate location at the country/region level),
- basic device and diagnostic information used for ad delivery and fraud prevention.
Google acts as an independent controller of this data. You can read how
Google uses information from apps that use its services here:
https://policies.google.com/technologies/partner-sites
Rewarded ads are always optional. Watching one to unlock a blade color, a hilt part or a training continue is your choice; every unlock also has a play-to-earn path.
Your consent choices (EEA / UK)
If you are in the European Economic Area or the UK, the App shows a consent form (Google’s User Messaging Platform) on first launch. You can change or withdraw your choices at any time in the App: saber selection screen → ⓘ (Credits) → Privacy options. You can also reset your advertising ID or opt out of ads personalization in your device’s Google settings.
Analytics and crash reports
The App uses Google Analytics for Firebase and Firebase Crashlytics. Together they collect:
- an app instance identifier generated on your device (not your name, e-mail address or Google account),
- which screens you open and which features you use — for example that a training run started, or that a blade colour was unlocked,
- approximate location derived from your IP address at the country/region level, after the address itself has been masked,
- crash reports and performance data: the type of device, the operating system version, and the state of the App at the moment it stopped working.
None of this identifies you personally, and none of it contains anything you typed. It exists so that a crash on a device we do not own can still be diagnosed and fixed.
Your consent governs this collection, not just the ads. If you decline in the consent form described above, analytics and crash reporting stay switched off — the App does not start collecting them and then discard the results.
You can reset your app instance identifier at any time by deleting and reinstalling the App.
Data stored on your device only
The App keeps your preferences and progress (chosen blade color, hilt configuration, blade voice, scene, play statistics, achievements, unlocks, training scores) in local storage on your device. This data:
- never leaves your device,
- is not linked to any account or identity,
- is deleted when you uninstall the App.
Device features the App uses
- Motion sensors (accelerometer, gravity): detect swings, clashes and tilt so the App can play matching sounds and drive the training game. Readings are processed in real time, on device, and are never stored or transmitted.
- Camera (optional): the saber screen has a camera mode that uses a live preview as the backdrop, with the saber drawn over it. Nothing is recorded until you tap the record button; a recorded clip is saved only to your device's gallery (Movies/Light Sword) and is never uploaded or transmitted by the App. Sharing a clip is entirely your action, through the Android share menu. The App works fully without camera permission.
- Microphone (optional): when you record a clip, you can allow the microphone so the clip has sound. Audio is captured only while you are recording, stays inside the clip file in your gallery, and is never transmitted. If you decline, clips simply record without sound.
- Flashlight: brief LED pulses accompany ignition and clashes (can be turned off in the Hilt Workshop). This uses the flash hardware only.
- Vibration: haptic feedback on clashes and hits.
Two-phone duel (Nearby Connections)
The optional Duel mode connects two phones directly over Bluetooth / Wi-Fi Direct using Google’s Nearby Connections — no internet, no servers. During a duel, your device shares with the other phone only: your device’s model name (shown as your player name) and real-time game events (swing timing, scores). Nothing is stored or sent anywhere else. Bluetooth and (on older Android versions) location permissions are requested solely because Android requires them for local device discovery — the App never reads or derives your location.
Permissions
| Permission | Why |
|---|---|
INTERNET, ACCESS_NETWORK_STATE |
fetching ads (Google AdMob) |
AD_ID |
the advertising ID used by AdMob (added by the ads SDK) |
CAMERA (optional) |
live backdrop in camera mode + clips you choose to record (saved locally) |
RECORD_AUDIO (optional) |
sound for clips you record — captured only while recording, stored locally |
VIBRATE |
haptic feedback |
| Bluetooth / Nearby / legacy location (optional) | discovering and connecting the second phone in Duel mode; no location is read |
Children’s privacy
The App is a general-audience toy and does not knowingly collect personal information from anyone, including children. The only third-party processing is ad serving by Google AdMob, subject to the consent controls described above. If you believe a child has provided personal data through the App, contact us and we will help.
Data sharing and selling
We do not sell personal data. We share nothing with third parties beyond the ad-serving data handled by Google AdMob described above.
Changes to this policy
If this policy changes, the updated version will be published at the same URL with a new “Last updated” date.
Questions about this policy? Contact: matt.olczyk@gmail.com