Privacy Policy for Japka

Last updated: 15 November 2026 · Effective: 6 October 2026

This Privacy Policy explains how the Japka mobile application (“Japka”, “the app”, “we”, “us”) collects, uses, stores and shares information when you use it. Japka is published on Google Play (package com.eli.japka) and on the Apple App Store.

Japka is a personal finance tracker: you record deposits and withdrawals, categorise them, and optionally share your feed with people you invite. By using the app you agree to this policy and to the Terms of Use.

The short version. We collect the account details you sign in with, the financial entries you create, your app settings, and a device token used to deliver notifications. We do not sell your data, do not show ads, and do not use advertising SDKs or the advertising ID. The app uses Google Analytics for Firebase to measure anonymous usage, such as app opens and sessions. Your data is stored in Google Firebase and is only visible to you and to people you explicitly invite to share your feed.

1. Who is responsible for your data

Japka (“Japka”, “we”, “us”) is the data controller for the purposes of this policy. You can reach us at xplay.appx@gmail.com for any privacy question or request.

2. Information we collect

2.1 Account information

To use Japka you create an account through Firebase Authentication. Depending on the method you choose, we receive:

Every account is identified by a Firebase user ID (UID), which is the key all your other data is stored under.

2.2 Financial entries you create

The content you enter in the app is stored so it can be synchronised across your devices. For each entry this includes: the title, the amount, whether it is a deposit or a withdrawal, the category, the date and time, whether it is an actual or future payment, any instalment details, an optional free-text note, and an optional free-text “by” field. We also store your selected currency.

These entries are treated as personal financial information. We never analyse them for advertising or profiling, and we do not share them with third parties other than the infrastructure providers listed in section 5.

2.3 Sharing information

If you invite someone to view or edit your feed, we store an invitation record containing your email address and user ID, the invited person’s email address and user ID, the status of the invitation, and when it was created. Once an invitation is accepted, the invited person can see and add entries in the shared feed. Only you decide who is invited, and either side can cancel or leave a share at any time from the app’s settings.

You can also invite someone with an invite link. A link invitation has no recipient until it is used: the first signed-in person who opens the link and accepts it joins your feed and can see and add entries in it. Treat an invite link like a key and send it only to the person you mean to invite. Japka cannot tell who forwarded or opened a link, and is not responsible for access gained through a link you shared. You can cancel a pending link, or remove a member, at any time from the app.

2.4 Push notification tokens

When you sign in on a device, the app registers a Firebase Cloud Messaging (FCM) token for that device so we can notify you when a shared feed is updated or when you receive or accept a sharing invitation. The token identifies the app installation on the device, not you personally. Tokens that stop working are automatically deleted from our records.

2.5 Subscription information

Japka offers an optional premium subscription purchased through Google Play Billing or the Apple App Store. All payments are processed by Google or Apple — the app never receives or stores your payment card, bank or billing address details. We store only your entitlement state: whether the subscription is active, when the current billing period ends, whether the store reports it as suspended, and the store’s purchase identifier used to verify the purchase.

2.6 Settings and data stored only on your device

Your theme and language preferences, the last tab you had open and the downloaded AI model are stored locally on your device. Entries you create while offline are held in a local database on the device until they can be synchronised, then removed. This local data never leaves the device except as part of normal synchronisation, and is deleted when you uninstall the app.

2.7 What we do not collect

Japka does not collect your contacts, calendar, photos or camera data, does not collect your location unless you turn on Tag location (section 2.13), and does not store or upload voice recordings. It reads a file on your device only when you pick a CSV file to import, and reads notifications only as described in section 2.12. The app contains no advertising SDK and does not collect the advertising identifier. The only usage measurement is described in section 2.9.

2.8 AI assistants you connect

You can choose to connect Japka to an AI assistant such as ChatGPT or Claude, so you can ask it questions about your money. Nothing is connected unless you sign in to Japka from that assistant and press Allow. Once connected, the assistant can read your entries (including feeds shared with you) and totals by category and period, and only when you ask it something that needs them. It cannot add, change or delete anything.

To make this work we store the assistant’s registration details (its name and return address), short-lived sign-in codes, and access tokens linked to your user ID. Tokens are stored only in hashed form. We also count how many requests each account makes so we can apply fair-use limits.

The data an assistant reads is sent to that assistant’s provider (for example OpenAI or Anthropic) and is then handled under their privacy policy, not ours. You can disconnect Japka at any time in the assistant’s settings; deleting your Japka account also revokes every connection.

2.9 App usage analytics

The app uses Google Analytics for Firebase to understand how Japka is used, so we can improve it. It records events such as the app being opened, session length, app version, device model, operating system, approximate country (derived from the IP address, which is not stored) and subscription purchases, linked to a random app-instance ID. It does not record your financial entries, amounts, merchants, email or name, and does not use the advertising ID. Analytics data is not used for advertising and is kept for up to 14 months.

2.10 On-device AI assistant

Japka Premium includes an AI assistant that runs entirely on your device, using an open-source language model made by a third party (such as Google’s Gemma). The model file is downloaded once and stored on your device. The download comes from a third-party file-hosting service (such as Hugging Face), which receives your IP address and standard request details as part of serving the file, under its own privacy policy. Japka tells your device which model to download using a setting stored in Firebase.

Your questions, the assistant’s answers and the financial entries it reads are processed only on your device and are never sent to us or to anyone else. Chats are not saved: starting a new chat or closing the app clears the conversation. You can delete the model at any time in Settings.

The assistant generates its answers automatically. They may be incomplete, out of date or wrong, and they are not financial, tax, legal or investment advice. See the Terms of Use.

2.11 Adding entries by voice

If you add an entry by voice from the Japka widget, on iPhone the app asks for microphone and speech recognition permission at that moment; on Android, Japka has no microphone permission and opens your device’s voice input screen instead. Your speech is turned into text by your device’s speech recognition service (Apple on iPhone, Google or your device maker on Android). That service may process the audio on the device or on its own servers, under that provider’s privacy policy; Japka does not control this. Japka receives only the resulting text, uses it to create the entry, and does not store or upload the audio. Check the entry before you save it, as speech recognition can mishear amounts or words.

2.12 Payment detection

Payment detection is optional and off until you turn it on.

Detection depends on what other apps put in their notifications, so it may miss payments or read them wrongly. Check every detected payment before you confirm it. You can turn detection off at any time: on Android in Japka’s Settings or your device’s notification-access settings, and on iPhone by turning off the automation in the Shortcuts app.

2.13 Location tag

Tagging a transaction with its location is optional and off until you turn it on, either on a single entry or as a default in Settings. The app then asks for location permission (approximate location on Android, “While Using the App” on iPhone). When you add an entry with the tag on, Japka reads your device’s approximate location once and sends the coordinates to your device’s geocoding service (Apple on iPhone, Google or your device maker on Android) to turn them into a place name, under that provider’s privacy policy. Japka saves only the place name, such as a street and city, as text on that entry; the coordinates are not stored or uploaded to us. The place name is saved with the entry in your feed, so people you share the feed with, and an AI assistant you connect, can see it. Japka does not read your location in the background or at any other time. You can remove the place name from any entry, and turn the tag off in Settings or in your device’s location settings.

3. Why we use your information

PurposeData used
Creating and securing your account, signing you inAccount information
Providing the core app function — storing, displaying and synchronising your entries and summariesFinancial entries, settings
Letting you share a feed with people you inviteSharing information, account email
Sending you notifications about shared feed activity and invitationsPush notification token, sharing information
Unlocking and maintaining premium featuresSubscription information
Answering your questions in an AI assistant you connectedFinancial entries, currency, AI connection tokens, request counts
Offering to add payments you make (only if you turn it on)Payment notification content, processed on your device only
Keeping the service reliable and diagnosing faultsServer-side operational logs

Where the GDPR applies, our legal bases are: performance of a contract (providing the app you asked for), your consent (notifications, optional sharing), and our legitimate interest in keeping the service secure and working and in improving it through anonymous usage analytics.

4. Notifications

Notifications are optional. On iOS, and on Android 13 and later, the app asks for permission before sending any, and you can withdraw that permission at any time in your device settings. Turning notifications off does not affect any other part of the app.

5. Who your data is shared with

We do not sell your personal data and we do not share it for advertising. Your data is processed by the following providers strictly to operate the app:

Our website (japka-app.com) uses Google Analytics only if you accept analytics cookies in the cookie banner. It records anonymous usage such as pages viewed, referring site and device type, and sets Google Analytics cookies. You can change your choice at any time from “Cookie settings” in the site footer. See Google’s Privacy Policy. App usage analytics are described in section 2.9.

If you connect an AI assistant (section 2.8), the entries it reads on your request are sent to that assistant’s provider, such as OpenAI (ChatGPT) or Anthropic (Claude), under their own privacy policy.

Your data is also shared with people you personally invite to a shared feed — they can see the entries in that feed and your email address on the invitation. Nobody else can see your feed.

We may disclose information if legally required to do so, or where necessary to protect our rights or the safety of users.

6. International transfers

Firebase stores and processes data on Google servers, which may be located outside your country of residence, including in the United States. Google provides appropriate safeguards for these transfers, including Standard Contractual Clauses where applicable.

7. How long we keep your data

Your account details, entries and sharing records are kept for as long as your account exists, so the app can show you your history. Device notification tokens are removed as soon as they stop being valid. AI access tokens expire after one hour and refresh tokens after 180 days unless used; unused sign-in codes expire within minutes. When you request account deletion, the data described in section 2 is deleted from our systems, other than records we are legally required to retain. Subscription and payment records held by Google Play or the App Store are retained by Google or Apple under their own policies.

8. Your rights and choices

You may request access to the personal data we hold about you, correction of inaccurate data, deletion of your account and data, a copy of your data in a portable form, or restriction of certain processing. Depending on where you live, you may also have the right to object to processing or to lodge a complaint with your local data protection authority.

Deleting your account and data

You can delete your account at any time inside the app: open Account and tap Delete account. Your account and data are erased right away, and for Sign in with Apple accounts we also revoke Japka’s Apple sign-in token. Full instructions are on our Delete your account page. Alternatively, to delete your Japka account and the data associated with it, email xplay.appx@gmail.com from the email address registered to the account, with the subject “Japka account deletion request”. We will delete your account, your entries and your sharing records within 30 days and confirm once it is done. Entries you added to someone else’s shared feed may remain visible to that feed’s owner.

Cancelling a premium subscription is done through the store you bought it in: Subscriptions in the Play Store app, or Settings → your name → Subscriptions on iPhone; cancelling a subscription does not by itself delete your account.

9. Security

Traffic between the app and our servers is encrypted in transit with TLS. Data is stored on Google Firebase infrastructure and protected by Firebase Authentication together with server-side security rules that scope access to signed-in users. No method of transmission or storage is completely secure, so we cannot guarantee absolute security, but we take reasonable measures to protect your information. You are responsible for keeping your device, your sign-in details and any invite links you create secure. To the extent the law allows, Japka is not liable for unauthorised access that results from a lost or shared device, shared sign-in details, a forwarded invite link, or a security failure at a third-party provider listed in section 5.

10. Children

Japka is not directed at children under the age of 16 and we do not knowingly collect personal data from them. If you believe a child has provided us with personal data, contact us and we will delete it.

11. Changes to this policy

We may update this policy from time to time. The revised version will be posted at this address with an updated “Last updated” date. Significant changes will be communicated in the app or by email where appropriate. Continued use of Japka after a change means you accept the revised policy.

12. Contact

Questions, requests or complaints about this policy or your data:
Japka — xplay.appx@gmail.com