Literature does not require account registration and does not sell your personal data.
We use Google Firebase for crash reporting and basic, anonymous usage analytics to keep
the app stable and improve it — details are below.
1. Overview
This Privacy Policy describes how Literature ("the app", "we") handles information
when you use the app on your Android device. By using Literature, you agree to
the practices described below. We process data based on legitimate interest to
ensure app stability and functionality, and to understand how the app is used.
2. Information We Collect
We collect only the minimum information necessary to provide the app's features:
Player name — the name you enter before starting a game.
This is used solely to identify you to other players during an online session
and is never stored on our servers beyond the duration of the game session.
Gameplay data — moves made during a game (card asks, claims)
are transmitted to our server only in online multiplayer mode to keep all
players in sync. This data is held in memory for the duration of the session
and discarded when the session ends.
Crash reports — if the app crashes, anonymised diagnostic
information (stack trace, device model, Android version, app version) is
automatically sent to Firebase Crashlytics. This data does not include your
name, location, or any personally identifiable information.
Usage & analytics data — the app uses Google Firebase
Analytics to collect anonymous, aggregated information about how the app is
used (for example app opens, screens viewed, session length, and basic
device/OS details), together with a Firebase-generated app-instance
identifier. This helps us see which features are used and improve the game.
It is not linked to your name, and the advertising identifier is disabled.
3. Information We Do Not Collect
We do not collect your location.
We do not collect your contacts or any data from other apps.
We do not require account creation or email registration.
We do not store payment information of any kind.
We do not use advertising SDKs or track you across other apps.
4. Offline Mode
When you play in offline mode, all game data stays entirely on your device.
Nothing is transmitted to any server.
5. Online Multiplayer
Online multiplayer requires a connection to our game server. The following
applies to online sessions:
Your chosen player name is visible to other players in the same room.
Game events are relayed through our server in real time to keep all players synchronised.
Sessions are identified by a temporary room code. No account or login is required.
All session data is deleted from our server when the game ends or the room is closed.
6. App Permissions
Literature requests the following device permissions:
Internet access — required for online multiplayer to connect
to the game server and for Firebase Crashlytics to send crash reports.
This permission is not used in offline mode beyond crash reporting.
Network state access — used to detect when your device loses
or regains connectivity so the app can automatically attempt to reconnect
during an online game session.
Vibration — used for haptic feedback during gameplay
(for example on your turn or when a deck is claimed), when haptics are enabled.
Notifications — used to show local notifications on your
device, such as when it becomes your turn or when a game starts or ends.
These are generated on your device; no data is sent anywhere to deliver them.
No other device permissions (camera, microphone, contacts, storage, location) are requested or used.
7. Security
All data transmitted between the app and our game server is encrypted in transit
using TLS (WSS protocol). Diagnostic and usage data sent to Google Firebase
(Crashlytics and Analytics) is also transmitted over HTTPS. We do not store any
personal data on our servers beyond the active game session.
8. Third-Party Services
The app uses the following third-party services, both provided by Google Firebase:
Firebase Crashlytics (Google) — used for automated crash
reporting to help us identify and fix bugs. Firebase Crashlytics may collect
device information such as device model, OS version, and crash logs.
This information does not directly identify you.
Firebase Analytics (Google) — used to collect anonymous,
aggregated usage statistics (such as app opens, screen views, session length,
device/OS information, and a Firebase app-instance identifier) so we can
understand how the app is used and improve it. The advertising identifier is
disabled, and this information does not directly identify you.
We do not sell or rent your information. The only data shared with a third party
is the limited diagnostic and usage data sent to Google Firebase (Crashlytics and
Analytics) described in Section 8, used solely to keep the app stable and improve it.
10. Data Retention
Player name & gameplay data — retained only for the duration of the active game session, then permanently deleted.
Crash reports — retained by Firebase Crashlytics for up to 90 days per their standard policy.
On-device data — your chosen player name, gameplay statistics, match history (most recent games), achievements, daily streak, and app settings/onboarding state are stored only on your device. This data contains no personally identifying information and is removed when you uninstall the app.
Usage analytics — retained by Google Firebase Analytics in accordance with Google's standard data-retention settings.
11. Children's Privacy
Literature does not knowingly collect personal information from children under
the age of 13. The app does not require any personal information beyond an
optional display name chosen by the user.
12. Your Rights
Because we do not maintain user accounts or persistent personal data, there is
nothing to access, correct, or delete beyond what is stored locally on your
device (which you can clear by uninstalling the app). If you have any questions
or concerns, please contact us at the address below.
13. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be
reflected on this page with an updated date at the top. Continued use of the
app after changes are posted constitutes acceptance of the revised policy.
14. Data Controller
The data controller responsible for your information is the individual developer
of Literature. For any privacy-related enquiries, you may contact: