Privacy Policy
1. Who we are
The Lokaly app is operated by BAMU Teknoloji (the "controller" under the GDPR). For any question about this policy: barkin@flukerapp.com.
2. What we process
- Device ID: a random ID created on first launch, used to count free daily videos and identify your app installation. If you sign in, your requests also include your account identifier.
- Traveler account (optional): to follow others or show your profile you can sign in with Apple, Google or email. Sign-in runs on Google Firebase; we never see your password. We keep: account ID, sign-in method, the name and short bio on your profile, who you follow and who follows you, people you block and reports you send. Your name and bio are public. The rest of the app works without an account.
- Video links and what you share: links you paste or send from the Share menu, videos you pick from your library, lists you send from Notes or a spreadsheet.
- Data files: files you download from Instagram, TikTok or Google yourself and choose. We only read the video links in them; we don't keep the file.
- Your choices in the app: saved cities, places, lists, notes, hearts and plans.
- Location (if you allow it): for "Near me" and "Where do you live" your device location is attached to that request; we use it to sort your saved places by distance and to find your city. We do not create a location history. Since 6 November 2026, automatic request-log entries containing latitude or longitude queries are excluded from storage. Older technical logs may contain those queries until their retention period of at most 30 days expires. The city you pick stays on your phone.
- Language: the language you choose in the app (English or Turkish), so replies and notifications arrive in it.
- Technical logs: request logs for debugging and security (time, URL or route, status and duration), kept at most 30 days. URLs can include searches or content identifiers. Optional product measurement is separate and requires Usage analytics permission.
We do not access your phone address book, your whole photo library or your advertising ID. We receive only the media you select. Your in-app follows are a separate social graph.
3. Why we use it (and the legal basis)
- Finding the places in a video: transcribing its audio, reading its caption and frames, matching places on the map (performance of our contract with you).
- Running the app: your library, lists and search; counting free usage (contract).
- Location features, notifications and optional account features: only with your permission (consent, which you can withdraw in iOS Settings or in the app at any time). Push notifications (e.g. someone followed your list) are sent with Google Firebase Cloud Messaging; for this we store your device's notification token and app language.
- Security and debugging logs (legitimate interest).
4. Who we share it with (service providers)
- Google Cloud (servers and storage, European Union region).
- OpenAI (transcription, place extraction, search, place summaries and translation). Content we send is not used to train models.
- Apple Maps (map location of places and of your city).
- Google Maps Platform (place matching, ratings, reviews, photos and place research you initiate). Place research shares your search criteria and, for nearby searches if you allow it, your location with Google. Google's privacy policy applies: policies.google.com/privacy.
- A video retrieval service (to fetch the file and caption of a public video).
- Apple (subscriptions and payment; we never see your payment details; identity for Sign in with Apple).
- Google Firebase Authentication (sign-in if you create an account; your email is kept there).
Some of these providers process data outside the EU (for example in the United States) under the European Commission's Standard Contractual Clauses or the EU-US Data Privacy Framework. We don't share your data with anyone else and we don't sell it.
Subscription management and optional diagnostics
RevenueCat manages subscription status with Apple using a pseudonymous app user identifier and purchase history. We do not receive your card details. If you enable Usage analytics in Profile, Google Analytics receives selected app events and a Firebase installation identifier; RevenueCat can use that identifier to attribute subscription events. Notes, saved addresses and video links are not included in these analytics events. If you enable Crash reports, Firebase Crashlytics receives technical crash information, app and device versions and stack traces. Both options start disabled and can be turned off in Profile. Disabling collection stops future optional collection; contact us to request deletion of previously collected data.
Google Maps also processes device identifiers, map interactions, performance and diagnostic information under Google's privacy policy. Google Sign-In, when used, processes sign-in/account information, device identifiers and network information that can indicate an approximate location. The optional Usage analytics and Crash reports switches control our Firebase measurement; they do not disable data processing required by these separate Google services. With Usage analytics enabled, our server also receives selected product events with a hashed installation identifier. This is pseudonymous data, not anonymous data.
Optional advertising measurement
Ad measurement in Profile starts disabled and is separate from Usage analytics. If you turn it on and authorize tracking in the iOS prompt, the Meta SDK can send app activation events with an installation identifier and technical network/device information. RevenueCat can send subscription conversion and renewal events, product, currency and revenue information to Meta using that matching identifier. Meta can combine this information with information from other apps or services to measure and attribute ads, under its privacy policy. We do not supply your notes, saved places, email, phone number or advertising ID as matching attributes. Permission is not required to use Lokaly or buy Pro. Turning it off stops new app measurement and clears the RevenueCat matching attributes when connected. If offline, reopen the app online to complete the server update; previously supplied identifiers can remain usable for server events until that update completes. Turning off iOS tracking permission also disables this measurement when Lokaly next checks the permission. This does not recall previously sent events.
Processing with OpenAI
When you use an AI feature your content is processed as described below; the app does not show a separate permission prompt. Video links or selected videos first go to our server; audio, captions and selected frames can then be sent to OpenAI to identify places. Search text, list names, place details you add and trip preferences can also be sent when using those features. An optional profile photo is sent to OpenAI for a content safety check, and the accepted photo is shown on your public profile. Personal place notes and the original notes in your trip preferences are not sent for automatic translation. You can browse existing places and lists without using these features. Contact us about deletion of previously submitted data.
Place verdicts and invitations
For a place you visited you can choose one of four verdicts (from “I’d go out of my way” to “Never again”) and add an optional note of up to 80 characters. If you have a traveller account, a shared verdict and note are shown with your name on your public traveller profile and on place pages of people who follow you; you can turn sharing off for any single verdict. Without an account your verdicts are only used to make suggestions for you. Across Lokaly, verdicts are shown only as anonymous counts and only once at least five have been given. No day, time or location is shown; timing is shown only as “this week”, “this month” and similar. Your verdicts are used to build your taste profile (Your taste) and personal estimates; you can delete anything in Your taste that you think is wrong. Removing a Been there mark deletes that verdict. After you delete your account, your verdicts are no longer shown to others.
The username you enter for “Who told you about Lokaly?” when you first open the app is stored to calculate the inviter’s reward. To check whether an invitation is valid and to prevent abuse, we use your device identifier, the days you open the app and an irreversible hash of your IP address; the IP address itself is not stored.
5. How long we keep it
Your library is kept while you use the app. A video and its frame are kept to play them on the place page. Ratings, reviews and photos from Google are not stored; they are fetched live each time. When you delete your account in the app (Profile → Delete account) your profile, follows and sign-in record are deleted immediately.
6. Your rights
EU, EEA and UK (GDPR): you can access, correct, delete or export your data, restrict or object to processing, and withdraw consent at any time. You can also complain to your local data protection authority.
California (CCPA/CPRA) and other US states: you can know what we collect, ask us to delete or correct it, and you won't be treated differently for using these rights. We do not sell personal information. Sharing for optional advertising measurement occurs only after the separate app permission and iOS tracking authorization described above.
To use any of these rights, email barkin@flukerapp.com with the device ID shown on your Profile page. We reply within 30 days.
7. Children
Lokaly is not designed for children under 13 (under 16 in the EU), and we don't knowingly process their data.
8. Changes
If we change this policy we update the date above and announce important changes in the app.