Privacy policy

1. Information handled by Limina

Accounts and sign-in

Limina uses Firebase Authentication for Google, Apple, and anonymous sign-in. This creates a unique account identifier. Google or Apple may provide a display name, email address (including an Apple private relay address), and provider account information, depending on your sign-in choice and what the provider supplies. Limina stores profile information such as your display name, anonymous-account status, and update timestamps.

Anonymous mode also creates an account identifier and syncs reading data. It does not mean that all use is offline or that no information leaves your device. An unlinked anonymous identity may become inaccessible after sign-out or loss of the app's sign-in state.

Authentication credentials and tokens are handled by Firebase and the sign-in providers. Limina does not ask for your Google or Apple password and does not include authentication tokens in exported reading-data backups.

Reading data and preferences

Limina stores bookmarks, collection names and membership, reading history and progress, open or closed reading sections, queue entries and order, reader preferences, and an optional reader handle. Account identifiers, source language editions, entry titles and identifiers, source links, status values, and timestamps connect these records to your account. The app stores this information locally using Drift and synchronizes it to Cloud Firestore.

Your language selection and first-use completion are stored only on this device using Drift. The selection changes the interface and the source language edition. Reading records and downloaded copies are separated by edition; articles and user comments retain their original text. Available-language metadata may be refreshed from the public source.

Article discussions

Before posting or editing, we record the version and acceptance time of the discussion terms privately in Firestore, linked to your account. That record is deleted by in-app account deletion. Automatic text filtering runs in the app and Firestore security rules; comments and drafts are not sent to a separate moderation provider.

Discussions are Limina community conversations, separate from the article source. Comments and replies are public, including their text, chosen reader name, account identifier, source language edition, article identifier, parent/reply relationships, and posting or editing timestamps. Anonymous visitors can read; a registered account is required to post. Do not include information you do not want other readers to see.

Unsent drafts and recently viewed discussion pages are stored locally using Drift. Drafts are not uploaded as comments or synchronized to Firestore. Blocked-reader preferences are private account data stored locally and synchronized to your Firestore records. Reports are private to the reporting account and authorized moderation staff. A report identifies the comment, article, reason, reporter, and submission time.

You can edit or delete your own comments and block or report other authors. Deletion removes public text, the author name, and the author identifier, while a minimal placeholder retains the thread relationships and timestamps so other readers’ replies remain available. Account deletion performs the same cleanup for your comments and removes your reports and this device’s discussion drafts/cache. Copies cached by other readers can remain until refreshed, and other people’s quotations or screenshots cannot be remotely erased. A small private posting-rate/security record can remain for abuse prevention after account deletion.

Local downloads, searches, and backups

Downloaded article text, revision information, images, and download status are stored on your device. Limina does not upload downloaded article bodies or images to your Firestore account. Offline search and find-in-article searches run locally. Online archive searches and article or media requests are sent to their source hosts, as explained below. Editions use backrooms.fandom.com, with backrooms-eesti.fandom.com used for Estonian.

Exported JSON backups contain your selected account's reading records for the current language edition and shared display preferences, including queue and progress information. They exclude authentication credentials, account identifiers, downloaded article bodies and images, public comments, discussion drafts/cache, and blocked-reader preferences. Exported files are not encrypted by Limina. Their storage and any sharing depend on the destination you choose.

Technical and support information

Firebase, sign-in providers, source hosts, and website hosting infrastructure receive information needed to handle network requests, such as IP addresses, requested URLs, browser or device/platform information, and service or SDK versions. Firebase Authentication also processes technical information for account security and abuse prevention. If you email support, we receive your email address and the contents and attachments you choose to send.

Limina does not request access to your contacts, precise location, microphone, or camera. It includes the Google Mobile Ads and User Messaging Platform SDKs. It does not separately integrate Firebase Analytics or Firebase Crashlytics; advertising measurement and diagnostics performed by AdMob are described below.

2. Why information is used

• Establish your identity and manage sign-in, account linking, and deletion.
• Keep your library, queue, preferences, and reading position available to your account.
• Retrieve source articles and images and make downloaded content available offline.
• Respond to support, privacy, and deletion requests and verify ownership before account changes.
• Protect accounts and services from misuse and meet applicable legal obligations.

Inline banners help fund the app. Limina requests non-personalized ads and does not send its account identifier, reader handle, searches, or reading history as advertising targeting data. Non-personalized ads can still involve identifiers, advertising measurement, and fraud-prevention data; they do not mean that no information is collected.

3. Services that receive information

Google Firebase

Firebase Authentication handles identity, Cloud Firestore stores synced account data, and Firebase Hosting serves these public pages. Google processes service and security information as described in its Firebase privacy information and privacy policy.

Google and Apple sign-in

The provider you choose handles its own sign-in experience and account information under its policies. See Google's privacy policy and Apple's privacy policy.

Google AdMob

When ads are enabled, the Google Mobile Ads SDK may process IP-derived approximate location, app- or device-related identifiers, ad impressions and interactions, and diagnostic/performance information for ad delivery, measurement, analytics, and fraud prevention. Limina removes Android advertising-ID permission and does not request Apple's tracking authorization. Other SDK identifiers may still be processed. See Google's advertising information and the SDK disclosures for Android and iOS.

Fandom and article image hosts

Online searches, article loads, and media loads contact Fandom and the image hosts used by source contributors. They receive the search or resource request and network information such as your IP address. Limina does not attach your Firebase identity or synced library records to these source requests. Supported Fandom image requests include a public source referrer so images load. See Fandom's privacy policy.

Email and files you choose

Support messages are received through the published Gmail address. Your email provider and any file or cloud-storage service you choose for exported backups process that information under their own policies.

Article, source, support, and policy links in Limina ask for confirmation before opening another app. Ads use Google's own click-through behavior and may open an advertiser's website, an in-app browser, or an app store when you tap them. The destination's policies apply. These policy pages use locally hosted assets and contain no analytics scripts, advertising scripts, sign-in widgets, or tracking cookies.

Limina checks privacy requirements through Google's User Messaging Platform before loading ads. Any required message is shown before ads can be requested. When Google requires an ongoing privacy entry point, Settings → Ad privacy choices lets you review or change those choices. If privacy settings cannot be established, ads remain unavailable; access to reading is not dependent on agreeing to advertising. Device settings can provide additional advertising controls.

Account data may also be disclosed where required by law or necessary to respond to a valid legal process.

4. Storage, processing, and security

The configured Firestore database is in Singapore (asia-southeast1). Firebase Authentication operates from US data centers, and hosting, support, source, and other provider infrastructure may process information internationally. The Firestore location does not mean that every service processes information only in Singapore.

Firebase connections use encrypted transport, and Firestore rules restrict account records to the authenticated account owner. Local records are separated by account in the app database. Exported JSON files are readable by anyone you give access to them; protect the locations where you save them. No storage or transmission method can guarantee absolute security.

5. Retention and deletion

Account and synced reading data remain while your account exists, unless you remove supported records or delete the account. Downloads and other local copies remain until removed from the relevant device or the app's data is cleared. Signing out and uninstalling the app do not delete your cloud account.

Successful in-app account deletion removes the account's Firestore records, deletes its Firebase identity, and clears that account's local records and downloads on the device performing deletion. Deleting an account from another device or through a support request cannot remotely erase local files on every device. Remove those copies and any exported backups separately.

Provider backups and security logs can follow separate retention schedules. Firebase states that Authentication IP logs are kept for a few weeks and that other authentication information is removed from its live and backup systems within 180 days after customer-initiated account deletion. See Firebase's retention information.

Deleting a Limina account does not automatically erase independently held advertising or source-host information. Google and other service providers apply their own retention and privacy-request processes to that information. Use the advertising privacy controls above and the linked provider policies for those records.

Support correspondence is retained as needed to resolve and document your request. You can also ask us to delete that correspondence. If a legal obligation requires specific information to be retained, we will explain the relevant exception rather than treat account deactivation as deletion.

6. Your choices and requests

• Change your reader handle and display preferences in Settings.
• Remove bookmarks, collections, queued entries, history, and downloads using the app's controls.
• Export reading data through Settings → Export & import data.
• Delete your account through Settings → Delete account and data, or use the account and data deletion page.
• Email us to request access, correction, deletion, or information about other privacy rights available where you live. We may verify account ownership before making changes.

Limina is intended for readers aged 16 and older and contains horror fiction and mature themes. Its store age rating separately describes content suitability. Parents or guardians with a concern about a child's information can contact us. Limina does not request a date of birth.

7. Changes to this policy

Updates will be published here with a revised effective date. Material changes to data handling will also be communicated through an appropriate app or account notice when needed.

8. Privacy contact

Publisher: keinetic
Privacy and support: akfdev22@gmail.com

Use the subject “Limina privacy request” and describe what you need. Do not send passwords, sign-in codes, access tokens, or payment information.