Korani Solutions AS

Last updated: July 11, 2026

Turklar Privacy Policy

Turklar is a local-first outdoor trip planning and packing app operated by Korani Solutions AS. This policy explains what the closed Android beta stores on the device, what leaves the device when an online feature is used, and what is shared through optional Turklar team sync.

Local-first Most trip, Gear, Pack, meal, note, profile, achievement, and settings data stays on the device.
Optional Turklar team sync Team data is sent to the Turklar sync service only when a user creates, joins, or uses a shared team.
No ads or behavioral analytics The current closed beta has no advertising, behavioral analytics, or third-party crash-reporting SDK.
No required account Turklar does not require a user account. Store purchases and team invite codes are handled separately.

Controller And Contact

Korani Solutions AS, Norway, is the controller for personal data processed by the Turklar service. For privacy, support, access, or deletion requests, contact jonas@korani.no. To help locate optional team-sync data, include the relevant team ID or invite code if available. Do not send a team access key by email.

Data Stored On The Device

Turklar stores app content locally. Depending on the features used, this can include trip plans and dates, coordinates and routes, Gear inventory, Pack selections and assignments, backpack layouts, meals and ingredients, notes and checklists, fishing plans, readiness state, achievements, post-trip learning, profile name and optional home area, settings, weather cache, subscription entitlement status cached from the store, and backup/import state.

Local photos are copied into app-controlled storage. Clearing app data or uninstalling can remove local data. Android Auto Backup is disabled for Turklar; make a local export before uninstalling if you want to keep supported text and planning data.

Optional Turklar Team Sync And Invites

Team sync is optional and does not require an account. Creating an invite, redeeming an invite, or continuing to use a shared team sends a team-scoped snapshot to the Turklar sync service. It can include team and trip identifiers, trip title/dates/type, route and stop coordinates, fishing-plan fields, participant display names and roles, shared packing and carry/ownership progress, team change events, and notes explicitly marked Team.

Team sync excludes private notes, the user profile outside the team member name, the full Gear inventory, photos and media attachments, local checklist history, Plus templates and systems, post-trip learning, weather cache, and local backup files. Access secrets are used to authorize a team; the service stores a one-way hash rather than the raw team access key.

Invite codes expire after 72 hours and are intended for a trusted recipient. The join page exposes only limited invite-preview information before redemption. Anyone who can use a valid code may receive the shared team snapshot, so codes should not be posted publicly. Closed beta teammates are trusted editors of the shared team data.

Location, Maps, Weather, Routes, And Fishing Providers

Turklar requests foreground location permission only when a location-based map flow needs it. Approximate location is accepted. There is no background-location tracking. A user can deny the permission and search or tap the map instead.

When an online map, place search, reverse geocoding, route, weather, offline-map, fishing water, or species-evidence feature is used, the required coordinate, bounding area, route points, or search query is sent to the relevant provider. The provider also receives normal network information such as the IP address and request headers.

Current providers can include OpenStreetMap tile services and Overpass, OpenTopoMap, OpenFreeMap, OpenStreetMap Nominatim, routing.openstreetmap.de, MET Norway, NVE, Artsdatabanken/Artskart, GBIF, and iNaturalist. Links opened for permits, fishing rules, or other references are handled by the user's browser and the destination's own privacy terms. Provider availability may change as the beta develops.

Camera, Photos, And Media

If a user chooses a profile, trip, Gear, meal, or note photo, Turklar requests the relevant camera or media-picker permission through Android. Only media the user captures or selects is adopted into Turklar's app-controlled local storage. Photos and media files are not uploaded through Turklar team sync and are stripped from portable backup and invite data.

Local Backup, Export, And User-Directed Sharing

A local inventory backup can contain supported profile/settings data, trips, routes, Gear records, packing state, meals, notes, and Plus planning templates. Media files are excluded. Turklar does not automatically upload a local backup; it leaves the device only when the user copies, shares, or stores it using another app or service.

Pack lists, notes, invite codes, and other exports are sent only to the Android share target selected by the user. Recipients and third-party storage apps process that copy under their own terms. Review the preview and share only with people you trust.

Turklar Plus, RevenueCat, And Google Play

Turklar uses Google Play Billing and RevenueCat to offer and verify Turklar Plus. These services can process an anonymous app-user identifier, app/store/device information, product and offering identifiers, purchase status, transaction and subscription dates, price/locale information, and diagnostic billing errors. Korani Solutions AS does not receive the user's full payment-card details. Google Play and RevenueCat process data under their own privacy terms.

Developer test access shown in a development build is local test state and is not a Google Play purchase.

Service Logs, Hosting, And Security

The website and optional Turklar team sync are hosted using service providers acting on our behalf. Web-server and security logs can contain IP address, date/time, requested path, response status, and browser or app request information. We use this information to operate, secure, troubleshoot, and prevent abuse of the beta. We do not use it for advertising profiles.

Network traffic uses HTTPS. Team invite codes are randomly generated, team access keys are not included in public invite links, and stored authorization secrets are hashed. No system is risk-free; protect the device, backup text, and invite codes, and revoke an invite if it was shared with the wrong person.

Purposes And Legal Bases

Optional Android permissions can be denied or changed in device settings. Turklar does not use location, photos, or team data for targeted advertising. Korani Solutions AS does not sell or rent Turklar personal data and does not use it for automated decisions with legal or similarly significant effects.

Retention And Deletion

Local data remains until the user edits it, resets Turklar, clears app storage, or uninstalls. Weather and other response caches are refreshed or replaced as the app operates. Invite codes expire after 72 hours and can be revoked earlier.

Shared team snapshots and events are retained while needed to provide beta team sync, resolve conflicts, secure the service, and handle support. Deleting local app data, leaving a screen, or uninstalling does not automatically delete copies already shared with teammates or stored by the sync service. Contact us to request deletion of identifiable beta service data. The current closed beta does not yet provide an in-app server-side team deletion control. Limited security logs, expired/revoked invite records, legal records, and backups may remain for a reasonable period where necessary.

International Processing

Some external providers, including store, billing, mapping, and biodiversity services, may process requests outside Norway or the EEA. Their own privacy notices describe their locations and transfer safeguards. We limit requests to the data needed for the selected feature where practical.

Other People And Children

A trip can contain names or planning information about other participants, including family members. Enter and share another person's information only when you are allowed to do so. Turklar is not directed at children creating their own accounts, and the app has no child account system. Do not place sensitive personal information in trip titles, Team notes, or invite previews.

Your Privacy Rights

Subject to applicable law, users may request access, correction, deletion, restriction, portability, or object to certain processing. Most local data can be viewed, edited, exported, or deleted directly in Turklar. For service-side data, contact us using the email above. Users may also complain to the Norwegian Data Protection Authority, Datatilsynet.

Policy Updates

This policy may change as Turklar, its providers, or legal requirements change. Material changes will be published here with a new update date before they apply where required.