Privacy Policy

1. Information stored on your device

Kapunka may store the following locally:

• Trip plans, dates, countries, expenses, amounts, currencies, categories, notes, locations, bookings, deposits, extensions, and other details you enter
• Card labels, colors, billing currencies, and optional last four digits; Kapunka is not designed to store full card numbers, CVV codes, or banking passwords
• Checklists, reminders, preferences, and app settings
• If you use the trip map's Photos layer: a list of the photos you have chosen to hide from that map, and temporary reduced-size copies of the pictures it has drawn. The list is only identifiers, meaningful on that device alone; the copies live in the app's cache, which the operating system may clear at any time. Neither is included in a backup, and neither is the photo itself — the originals never leave your photo library
• Pending-charge details and local notification history
• Legacy backup files only while you choose, import, export, or share them through the operating system
• A random installation identifier and local state used for rate limiting, review prompts, migrations, and app operation

2. No Kapunka account required

Current versions of Kapunka do not require or offer a Kapunka account. You do not need to give us a name, email address, phone number, or bank login to use the app. An App Store or Play Store account may be used by the platform for purchases.

Kapunka creates a random installation identifier. It is not an advertising identifier and is not used for cross-app tracking. It may be sent to our backend when you use Android place search or send in-app feedback so we can apply fair-use and abuse limits.

Older Kapunka or Voya versions offered sign-in. If you used one of those versions, you can ask us to delete any remaining legacy account record through our data controls.

3. Permissions

Kapunka may ask for these permissions:

• Foreground location: used to suggest where an expense happened, detect the local country, currency, and time zone, center maps, and find nearby places. Kapunka does not request background location.
• Photo library: used for one thing. If you switch on the trip map's Photos layer, Kapunka reads the photos and videos taken on your device between that trip's start and end dates, and shows the ones carrying a location at the spot they were taken. Only that date range is read; anything outside it, and anything with no location recorded on it, is skipped. The layer is off until you turn it on, and turning it off stops the reading. Photos are never copied out of your library, never sent anywhere, and never seen by us. Current builds do not request camera or microphone access.
• Notifications: used for local reminders and alerts you enable, including trip, checklist, visa, booking, and subscription alerts.
• Files: used only when you choose a compatible legacy backup to import, or when you export and share a file.

You can decline or later change operating-system permissions. Some related features may then be unavailable, but you can still enter information manually.

4. Places, maps, exchange rates, and app configuration

On iOS, place search uses Apple's mapping services. On Android, a place query can send the search text, current map or device coordinates, language, a short search-session token, and the random installation identifier through our Supabase function to Google Places. Map tiles and map views may be provided by Apple or Google, depending on the device. The offline city database and local reverse geocoding do not send coordinates to us.

Exchange-rate requests may be sent to open.er-api.com and Frankfurter with the requested currency or date. Your expense list is not included. Kapunka also reads a small public configuration record from Supabase to determine whether an app update is available. These providers may receive ordinary request information such as IP address, time, and device or network headers.

5. Feedback and support

If you send in-app feedback, we receive the message, optional rating, random installation identifier, app version, platform, and language. If you do not choose “Send anonymously,” the app may also include the device model to help diagnose problems. Anonymous feedback omits the device model and any legacy account details.

If you contact us through Telegram or email, we receive what you choose to send and the identifiers that service provides. The in-app Telegram link may include an app-generated support identifier, app version, platform, language, and support entry point. Do not send passwords, full card numbers, or banking credentials.

6. Purchases

Apple or Google processes in-app purchases and subscriptions. Kapunka reads the store's product, price, transaction, and active-entitlement information through the platform's billing APIs so it can unlock or restore paid features. Kapunka does not receive or store your full payment-card details, and current entitlement checks are performed on the device rather than in a Kapunka account.

7. App analytics and diagnostics

Kapunka includes Expo Insights, which reports basic app-usage and diagnostic events — such as an app launch — together with technical details like app version, build, platform, operating-system version, device model, and country or region. It is used to understand how many people use which version and to spot crashes and regressions.

These events do not include your trips, expenses, amounts, notes, photos, places, or any other content you enter. This reporting is part of the app framework and is not something you can switch off inside Kapunka; you can prevent it by not using the app. Expo processes this information as our service provider under its own privacy policy. We do not use it for advertising, and it is not linked to an advertising identifier.

Your operating system and app store separately provide us with aggregated statistics — such as downloads, crash reports, and store-listing performance — under Apple's and Google's own terms and your device settings for sharing analytics with them.

8. Website data

The Kapunka website does not use advertising pixels or cross-site behavioral tracking. Our hosting provider may process standard request information such as IP address, browser type, requested page, time, and security signals to deliver and protect the site.

If you apply to test Kapunka through the website, we collect your name, email address, the kind of traveller that best describes you, the month and year of your next trip, your age range, and your confirmations that you are at least 18 and have access to an eligible iPhone. We store the application in Supabase and use it to assess your fit for a testing round, contact you about testing, and manage the tester programme. Applying does not guarantee selection.

Before a tester application is accepted, Cloudflare Turnstile checks whether the submission appears to come from a person rather than an automated bot. Cloudflare may process browser and device signals, IP address, and the resulting verification token to provide that protection. We use the result only to protect this form from abuse.

9. Service providers

Depending on the features you choose, Kapunka may interact with:

• Google for Google Maps, Google Places, and Play Store services
• Apple for maps, App Store, StoreKit, and operating-system services
• Supabase for public app configuration, Android place-search routing, feedback, and tester applications
• Expo for app-usage and diagnostic reporting
• open.er-api.com and Frankfurter for exchange-rate data
• Telegram, email, and their infrastructure providers for support
• Cloudflare for website hosting, security, and Turnstile bot protection

These providers process information under their own policies. We do not sell personal information, use advertising networks, or share app data for cross-context behavioral advertising.

We may add, change, or replace a service provider as Kapunka develops. Where that materially changes how information is handled, we will update this policy.

10. How we may use information

We use the limited information described above to provide and operate the features you choose, respond to support and feedback, diagnose faults, prevent abuse and fraud, apply fair-use limits, maintain security, improve and develop Kapunka, and meet our legal obligations.

We may also create and use aggregated, statistical, and de-identified information that does not identify you or any individual — for example, how many people use a feature, or how many trips a typical user plans. We may keep and use that information for any lawful business purpose, including improving, analysing, and promoting our products, and it is not subject to the retention limits below.

11. Legal disclosure and safety

We may access, preserve, and disclose information we hold where we reasonably believe it is necessary to comply with a law, regulation, legal process, or enforceable government request; to enforce our Terms of Service, including investigating a potential breach; to detect, prevent, or address fraud, abuse, security, or technical issues; or to protect the rights, property, or safety of our users, the public, or us, as required or permitted by law.

12. Where information is processed

We operate from Israel, and our service providers operate in a range of countries, including the United States and the European Union. Information handled through a connected feature may therefore be transferred to, stored in, and processed in a country other than the one you live in, where data-protection law may differ. Where the law requires it, we rely on an appropriate transfer mechanism, such as an adequacy decision or standard contractual clauses.

13. Retention, deletion, and recovery

Local data stays on a device until you delete it in Kapunka, clear app data, or uninstall the app.

We cannot recover your data. Because your trips and expenses are stored on your device rather than with us, we have no copy of them, no ability to view or restore them, and no obligation to retain, back up, or reconstruct them. If your device is lost, reset, or replaced, or the app or its data is deleted, that information is gone unless you made your own backup. Making, testing, and safeguarding backups is your responsibility.

Feedback, support records, and tester applications are kept only as long as reasonably needed to respond, run or plan testing, diagnose issues, prevent abuse, maintain security, meet legal obligations, or resolve disputes. See the data controls page for deletion steps and requests concerning records we control.

14. Your choices and rights

You can use Kapunka without a Kapunka account, deny permissions, delete local data, and choose whether feedback is anonymous. Depending on where you live, you may also have rights to access, correct, delete, restrict, or object to certain processing. Contact us to exercise a right; we may need enough information to verify the request.

15. Security

We use reasonable technical and organizational safeguards for the services we operate, but no device, network, storage provider, or transmission is completely secure, and we cannot guarantee absolute security. Protect your device, Google account, store account, support accounts, and any files you export or share.

Because your records are held on your own device, their security depends largely on you — your device passcode, your operating-system updates, who has physical access to the device, and where you send an exported file. To the extent permitted by law, we are not responsible for unauthorised access that results from your device, accounts, or shared files rather than from the services we operate.

16. Children

Kapunka is not directed to children under 13 or below the applicable age of digital consent. We do not knowingly collect personal information from children. Contact us if you believe a child has provided information to a service we control.

17. Change of control

If Blueframe or Kapunka is involved in a merger, acquisition, financing, restructuring, insolvency, or sale of all or part of its assets, information we hold may be transferred or disclosed as part of that transaction or its evaluation, subject to the receiving party honouring this policy for information transferred to it. We will note any resulting change in how information is handled on this page.

18. Changes to this policy

We may update this policy as Kapunka changes, as features are added or removed, or as our service providers change. We will revise the date above, and where a change is material and the law requires it, we will give notice in the app, on this website, or by another reasonable means. Otherwise the revised policy takes effect when published.

Continued use of Kapunka after an updated policy takes effect means you accept it. Please check this page from time to time.

19. Contact

Questions, privacy requests, and deletion requests can be sent to privacy@kapunka.app.