Privacy Policy

Last updated: 17 October 2026

Flanio is a travel/discovery app provided by SİSİFOS YAZILIM VE TEKNOLOJİ ANONİM ŞİRKETİ. In this policy, "we" means this company, which is the data controller for your personal data. This policy explains what data we process, why, who we share it with, and your rights. The company's address and how to contact us are in section 13.

1. Data we collect

Account and identity. For guest use we create an anonymous user ID (UID). If you create a permanent account, your email and password (your password is held by our authentication provider; we do not separately store it), and a display name if provided. If you sign in with your Google account, Google sends us your name, your email address, whether your email address is verified, your Google account ID and the link to your profile photo; these are stored in your account record. If your display name is empty and the name from Google has at least two words, we save a shortened form of it (the first two letters of your first name and of your last name) as your display name; you can change it later. If you turn your guest account into a permanent account with Google, your data stays in the same account. If you already have a Flanio account with that Google account or with the same email address, your guest account is not linked to it and you are signed in to that existing account; the same happens when, as a guest, you sign in to your existing account with your email address and password. In this case, the data kept on our servers in connection with your guest account (for example your Flân Puan) is not transferred to the existing account, and the guest account is closed under the guest account rule in section 7; the data on your phone stays on your phone. If you create a permanent account with your email and password, or make your guest account permanent by email, the language the app is using at that moment (Turkish, English, Russian or Arabic) is also saved to your account; this is so that we can send account-related emails (for example, email verification) in that language. If you change the app's language later, the saved language stays the same. For session security, two kinds of record are kept: a record of each open session (IP address, device/browser information, and the times the session was opened and refreshed) in our own database; and authentication audit logs in our hosting provider's log storage.

Travel data. Trips you create; information such as destination, date preference, traveller/interest/pace notes, route, transport type and approximate budget preference; the visit verification record for the trip completion points (see "Location").

Content. AI Travel Cards you generate; messages you write to Flanio Assistant; comments you write about places and the ratings you give, the information notes you send about places (contributions), the comment and contribution reports you send and your block list (details in section 6).

Usage/analytics (product_events). We measure in-app events (e.g. the card-generation flow). These records are not fully anonymous — they can be technically linked to your account (pseudonymous). You can turn analytics off in settings.

Location. With your permission we use your location to show nearby places; this is not stored in our app database and is used momentarily for the request. If you ask for a walking or driving route inside the app, your start and destination coordinates are sent to our routing provider openrouteservice (HeiGIT gGmbH, Germany); we ask you separately before that happens, and you can withdraw your consent in Privacy and security settings. We do not store these coordinates; retention on the provider's side is governed by its own policy.

For the trip completion points, when you open the app within your trip dates, your phone uses your location to check, on the device itself, whether you are in the city you added to your trip. This check is done only with a permanent account and only if you have already given location permission; no separate permission is requested for it. If you are in that city, only a visit signal for that trip goes to our server; your location and the time of day are not sent, and the day the signal arrives is recorded. Only one signal is kept per trip. This record is deleted when your account is deleted; if ownership of a trip you share passes to another member, this record does not pass to them. If you do not give location permission, this signal is not sent; the rest of the app works the same, only the trip completion points are not awarded.

Microphone and dictation. If you press the microphone button in Flanio Assistant, your speech is turned into text by your device's speech recognition service. The microphone is turned on only when you press the button; it listens for at most 60 seconds and turns off after 3 seconds of silence. The voice recording does not reach Flanio: Flanio neither sends it to its servers nor stores it; only the recognized text comes back to the app. Recognition is requested on the device first, but if that is not possible on your device, your device's operating system may send your voice to its default speech recognition service (e.g. Google) for recognition; that transfer is governed by that service's own terms. The recognized text is processed as a message you send to the assistant (sections 5 and 7).

Device/technical. For service operation, security and diagnostics we process IP address, request/session metadata and server logs.

Notification key. If you have given notification permission, a notification key for your phone is obtained from Google's notification service (Firebase Cloud Messaging) so that we can send you notifications while the app is closed. We store this key together with your account (including a guest account), your phone's operating system and the app's language; the language is so that we can send the notification in that language. For this service Google also processes an identifier for each installation and the app version. If you have not given notification permission, no key is obtained. If you turn the permission off later, the key is not renewed and is deleted after the period given in the retention section.

Crash and error reports. If the app crashes or hits an unexpected error, a technical report is sent to Sentry so we can diagnose it. The report contains: the error type and where in the code it occurred (stack trace), device model and manufacturer, operating-system version, app version, and the name of the screen you were on. When the app crashes, or freezes and stops responding, the report also includes an installation ID — a random identifier generated when you first install the app. It is not your name, your email or your user ID, and we do not link it to your account. It is used only to see which crashes come from the same device. The report does not include your email, user ID or display name, no screenshot is taken, and no text you typed is sent — including text entered in the translation screen and messages written to Flanio Assistant. The app does not add your IP address to the report. Sentry sees the connection's IP address when it receives the report; from that address it infers an approximate location (country, sometimes city) and adds it to the report, but does not store the IP address itself. You can turn this off in settings; when off, no report is sent at all.

Permissions. Camera and photo access (photos/translation), location, notifications, microphone (writing to the assistant by speaking), storage (saving to gallery).

Waitlist (website). If you sign up to the waitlist form on flanio.com.tr, we process your email address and the segment you choose ("I live here" / "I am visiting Istanbul"). We use this data only to send Flanio announcements and first invitations; we do not share it with third parties for marketing. We keep it until the purpose of the list ends or you ask to be removed; you can unsubscribe at any time via the link in each email or by writing to info@flanio.com.tr.

Website visit measurement. To measure how many times our website is visited, which pages are opened and how fast pages load, we use Cloudflare Web Analytics. When you open a page, your browser sends Cloudflare the following: the address of the page you open, which site you came from, the type of your browser, operating system and device, and how long the page took to load. Cloudflare sees the connection's IP address; the measurement results also show which country visits come from. This measurement does not use cookies and does not leave an identifier for you in your browser. According to Cloudflare, no attempt is made in this measurement to recognise visitors from their IP addresses or browser information. We see the results only as totals; we cannot see who a visit belongs to.

2. Data that stays on your device — and the exceptions

The following data is stored on your device and is not sent to our servers: your Travel DNA answers, your memory timeline and the memory photos you add. Your phone's iCloud or Google backup may include this data too — that backup is your own cloud. Photo translation runs on your device: text recognition (OCR) and translation happen on your device; your image/text is not sent anywhere. A translation language pack is downloaded on first use. Google ML Kit, which provides the translation feature, does send Google technical information about the device and how the feature is used; details are in section 4.

Your preference profile. The preference profile we derive from your Travel DNA answers is kept on your device; no persistent preference profile is created on our servers. The one exception is Flanio Assistant. When you ask the assistant a question in the trip planning flow or on a trip's screen, three things are sent to our server along with your question: the preference weights calculated from that profile (a number between 0 and 100 for each axis), a confidence score showing how settled those weights are, and the profile's version number. These are what let the answer fit the way you travel. The assistant you open from a place page does not carry any of this. Of those three fields our server passes only the weights and the confidence score on to the assistant provider, Anthropic; the version number goes no further than our server. The request that goes to Anthropic contains no name, no email address and no user ID. The weights accompany that one question only and are not kept as a preference profile on our servers. The record of your conversation with the assistant, however, is kept linked to your account; its retention period is given in section 7. If your preferences change, the next question carries the updated weights. The raw answers you give in Travel DNA are never sent.

Important: Trips you create without signing in (as a guest) are saved to the cloud (under your anonymous ID) — they do not stay only on your device.

3. How we use data

To provide and personalize the service; to generate AI Travel Cards and voice/text content; to run Flanio Assistant; to operate the Flân Puan economy; for security, fraud prevention and diagnostics; for product measurement (analytics); to send you notifications while the app is closed; and to show comments and approved contributions, review contributions, apply the rules for comments and contributions and review reports of AI-generated content (section 6).

4. Third parties

We do not sell your data. To provide the service we use:

• Supabase — hosting, authentication, storage, database (processor/infrastructure).
• Brevo (Sendinblue SAS, France) — sending emails about your account, for example the email that verifies your email address. To deliver an email, your email address and the content of the email go to Brevo.
• OpenAI — AI Travel Card image generation; only cleaned route (origin/destination) and season are sent, not your identity.
• Anthropic — Flanio Assistant (AI assistant); the messages you write to the assistant, your trip context and your preference weights are processed. Your identity is not sent to this provider.
• openrouteservice — walking and driving routes; operated by HeiGIT gGmbH (Germany). When you request a route, your start and destination coordinates are sent to this provider. We ask for separate consent first; you can withdraw it in settings.
• OpenFreeMap — map display; operated by Hyperknot Software Kft. (based in Hungary). When map tiles are loaded, your IP address and technical request data reach OpenFreeMap. Under its own policy OpenFreeMap does not keep IP addresses in its regular server logs; it may temporarily enable IP logging for up to 30 days only during a security incident.
• Google ML Kit — translation (from a photo or from text you type). Text recognition and translation happen on your device; your photo and text are not sent to Google. A language model is downloaded on first use. According to Google's own disclosure, ML Kit sends Google technical information for diagnostics and usage measurement; this includes device information (e.g. manufacturer, model, operating-system version), the app's name and version, a per-installation identifier, the feature's version and settings (e.g. image format and resolution), events from your use of the feature (e.g. initialization, model download, recognition), the size of the input and output, performance and error information, the languages you select and the language detected in the text.
• Sentry — crash/error diagnostics; technical error reports only. Your email, user ID and the text you type are not sent; a crash or freeze sends a random installation ID; Sentry infers an approximate location (country, sometimes city) from the connection's IP address and does not store the IP address (see above). Data is processed in the Germany (EU) region. Can be turned off in settings.
• Firebase Cloud Messaging (Google; global infrastructure) — delivering notifications while the app is closed. Your notification key, your installation identifier and the text of the notification pass through Google's servers.
• Cloudflare (Cloudflare, Inc., United States) — measuring visits to our website (Cloudflare Web Analytics). This measurement runs only when you visit flanio.com.tr and does not measure how the app is used. What is sent is described in section 1.
• Actions such as "Open in Google Maps" and getting directions are transfers you initiate; the coordinates of the place you want to go to are carried to Google inside a google.com/maps address. That address usually opens in an in-app browser tab; if your device has no browser that supports it, the system resolves the address itself and an installed Google Maps app may open.
• Continue with Google — if you choose to sign in with your Google account, Google verifies your identity. In this process Google is a separate data controller under its own privacy policy, and it knows that you signed in to Flanio.
• Your device's speech recognition service (e.g. Google) — writing to the assistant by speaking; when you use dictation and recognition cannot be done on the device, your voice may go to this service. That transfer is governed by that service's own terms.

5. AI features

For AI Travel Cards, limited route/season information is sent to OpenAI (without identity). For Flanio Assistant, your messages and trip context are sent to Anthropic. These providers have their own retention periods (typically time-limited). If you do not use AI features, these transfers do not occur. When you use Flanio Assistant, your preference weights and their confidence score are sent to Anthropic alongside your messages and trip context; that request contains no name, no email address and no user ID (see section 2 above).

6. Comments, ratings, contributions and community safety

When you write a comment about a place, give it a rating or send an information note about a place (a contribution), report a comment or a contribution, or block a user, some of your data is processed. This section explains what data is processed, who sees it, how long it is kept and what you can do. The rules for comments are set out in the "Comments and ratings" section of the Terms of Use, and the rules for contributions in the "Content you submit" section.

Data we process

• Your comment and rating: the text you write, the rating from 1 to 5 that you give, which place the comment is for, and when it was written and last edited. Writing a comment requires a permanent account; the text is optional, the rating is required.
• Your display name: shown next to your comment and your approved contribution; if it has more than one word, its first word and the initial of its last word are shown, and if it is a single word, it is shown unchanged.
• Your contribution: the note you write, which place it is for, when it was sent, the outcome of the review (approved or rejected), the reason if it was rejected, when the decision was made, and whether the contribution earned you Flân Puan. Sending a contribution requires a permanent account. The contribution record does not contain your location or device information. When you send your contribution, you can also answer one short question about the place if you want: you say how much time to set aside there by choosing one of the ready-made options. Your answer is stored as part of the contribution; the rules in this section on reviewing, keeping and deleting contributions apply to it as well.
• Your reports: when you report a comment or a contribution, the reason you choose, a short note if you choose to add one, which comment or contribution you reported and when.
• Your reports of AI-generated content: when you report a Flanio Assistant reply or an AI Travel Card image, the reason you choose, a short note if you choose to add one, the text of the reply you reported and, if there is one, the message you wrote immediately before it in the same conversation; for an image, a record showing which image it is and how it was produced; and the time of the report and, if it has been closed, the time it was closed.
• Your block list: whom you have blocked and when you blocked them.
• Moderation log: when a comment is reported, edited, deleted, hidden or made visible again; when a contribution is sent, approved, rejected, taken down or deleted; and when commenting is turned off or turned back on for an account, we keep a record of it. The record contains the type of action, its time, the comment or contribution and the place concerned, the account that performed the action and the account affected by it, and the reason, if any. The text of comments and contributions is not written to this log. Entries are only added; they are not changed afterwards.
• If commenting is turned off for your account: the date it was turned off, the reason and, if it is turned back on, the date it was turned back on. While it is off, you cannot send contributions either.

Do not write special categories of information about yourself or anyone else in a comment, such as health, religion or political opinions. We do not ask for this kind of information; if we see it in a comment, we may hide the comment.

Why we process it and our legal basis

• Showing your comment, rating, display name and approved contributions to other users, giving you Flân Puan for your approved contributions, and running the reporting and blocking tools: this is necessary to perform our contract with you, that is, the Terms of Use (KVKK Art. 5/2-c; GDPR Art. 6(1)(b)).
• Passing comments and contributions through the banned-phrase filter, reviewing contributions before they are published, reviewing reports of comments, contributions and AI-generated content, hiding or taking down content that breaks the rules, turning off commenting and keeping a record of all this: this is our legitimate interest in providing a safe environment for everyone who uses the app and in being able to show what we did if a dispute arises (KVKK Art. 5/2-e and 5/2-f; GDPR Art. 6(1)(f)).
• Continuing to show your approved contributions on the place's page after you delete your account, with your name removed and their link to your account cut: preserving the knowledge built up about places is our legitimate interest (KVKK Art. 5/2-f; GDPR Art. 6(1)(f)).

Comments and contributions are not used for advertising and do not affect how places are ranked. They are not sent to AI providers.

Who sees it

• Your comment, your rating, the shortened form of your display name and the date of the comment are visible to everyone who uses the app, including people using it as a guest. Your email address and user ID are not shown.
• Your approved contribution, the shortened form of your display name and the date the contribution was approved are visible on the place's page to everyone who uses the app, including people using it as a guest. Your email address and user ID are not shown. Only you and we can see your contributions that are under review or have been rejected.
• The answer you add to your contribution is not shown next to the contribution or together with your name. Until answers have built up for a place from the approved contributions of at least five different users, they are not shown at all; once they have, they appear on the place's page only in combined form (for example, how many users the answer is based on and the most frequently chosen answer).
• A person you have blocked does not see your comments, and you do not see theirs. No notification is sent to the person you block. A place's average rating is not affected by blocks.
• Only we see your reports, the moderation log and the records about commenting being turned off. We do not tell the author of a comment or contribution that you reported it.
• Only we see your reports of AI-generated content and the copy of the content you reported.
• Like your other data, this data is kept with our hosting provider Supabase (section 4). We carry out moderation ourselves; we do not give data to any other company for it.

Automated processing

• Before a comment you send is published, it is automatically checked against the banned-phrase list. A comment that is caught is neither published nor saved; we do not tell you which phrase it was caught on.
• When a comment is reported by three different permanent accounts, it is automatically hidden and put under review. We review the decision to hide it; we may keep the comment hidden or make it visible again.
• A contribution you send is also automatically checked against the same list; a contribution that is caught is not saved. A contribution that passes the list is reviewed by us before it is published. Contributions are not hidden automatically because of reports; we review the reports ourselves and, if necessary, take the contribution down.
• No AI is used in these processes. If you want to object to the outcome of an automated process, you can write to the address below.

How long we keep it

• Your comments and ratings: until your account is deleted. When you delete a comment, its text is deleted; your rating and the fact that the comment existed stay until your account is deleted.
• Your contributions under review: until you withdraw them or your account is deleted.
• Your rejected contributions: deleted 30 days after the rejection decision. A contribution that has been taken down also counts as rejected and is deleted at the end of the same period.
• Your approved contributions: for as long as they stay published. When you delete your account they remain on the place's page, but your name is removed and their link to your account is cut.
• Your reports about contributions: until your account or the contribution you reported is deleted.
• Your reports: until your account, or the account of the author of the comment you reported, is deleted. If the author deletes the comment you reported, the short note you added to your report is also deleted; the reason you chose, which comment you reported and when you reported it are kept.
• Your reports of AI-generated content: in section 7.
• Your block list: until you remove the block or one of the two accounts is deleted.
• Records about commenting being turned off: until your account is deleted; the record stays even if commenting is turned back on.
• Moderation log: when your account is deleted, the log is not deleted, but its link to your account is removed and it is kept in that form.

When you ask for your account to be deleted, your comments and ratings, and your contributions that are under review or have been rejected, are deleted together with your other account data once the deletion window ends (section 8). The same happens when your guest account is closed automatically (section 7).

What you can do

• You can edit your comment and rating at any time, and you can delete your comment. The rating of a comment you delete is no longer visible in the app and is not counted in the place's average rating. You cannot edit or delete a comment that has been hidden by moderation; write to us about it.
• From within the app, you can withdraw a contribution of yours that is under review or has been rejected; a contribution you withdraw is deleted. From within the app, you cannot delete an approved contribution of yours; to ask for it to be removed, write to us. After you delete your account we can no longer match the contribution to you, so in your request you need to say which contribution it is and at which place.
• From within the app, you can report a comment or a contribution that you think breaks the rules; you can do this as a guest too.
• You can block a user through their comment, and remove the block from the "Blocked users" list in the "Privacy and security" screen.
• You can object to your comment being hidden, to your contribution being rejected or taken down, or to commenting being turned off for your account, and you can ask to access these records kept about you, or to have them corrected or deleted. To do so, you can write to info@flanio.com.tr. Your other rights are set out in section 8.

7. Retention

• Analytics events (product_events): 90 days, then physically deleted.
• AI job route texts: redacted after 90 days.
• AI Travel Card images: on the server until your account is deleted; on deletion they are placed in a secure deletion queue.
• Account data: until your account is deleted (see below).
• Comments, ratings, contributions, comment and contribution reports, block list, records about commenting being turned off and moderation log: set out in section 6.
• Flanio Assistant conversation records: 90 days. The copy taken when you report a reply is outside this period; see the "Your reports of AI-generated content" item below.
• Your reports of AI-generated content: when you report a Flanio Assistant reply or an AI Travel Card image, we keep your report (the reason you choose and a note if you add one) and a copy of the content you reported. For a reply, the copy is the text of the reply and, if there is one, the message you wrote immediately before it in the same conversation. For an image, the copy is not the image itself but a record showing which image it is and how it was produced. A report that has not been reviewed is deleted at most 180 days after it was created; a report that has been reviewed and closed is deleted 90 days after it was closed. If your account is deleted, these records are deleted too. This period is separate from the 90-day period for conversation records above.
• Notification key: if 60 days pass since you last opened the app while notification permission was on, the key is deleted in the next daily clean-up. When you sign out on a device, that device's key is deleted; however, if you are not connected to the internet when you sign out, if you turned notification permission off earlier, or if you delete the app without signing out, the key remains and is deleted under the 60-day rule. When your account is deleted, or your guest account is closed, the key is deleted together with it.
• Crash/error reports (Sentry): up to 90 days — automatically deleted by Sentry when the period ends.
• Session records (IP address and device/browser information): kept in our own database. When you sign out on a device, that device's record is deleted; however, if you are not connected to the internet when you sign out, or if you delete the app without signing out, the record remains. Remaining records are deleted when your account is deleted, or when your guest account is closed as set out in the guest account item below.
• Data download request record: we record the time your copy was prepared and its size; we do not keep the downloaded data itself. The record is deleted after 12 months, or together with your account if your account is deleted earlier. Its purpose is to be able to show that we answered your request and to apply the limit of one copy a day.
• Server and Edge processing logs, as well as authentication audit logs: these are not kept in our own database but in our hosting provider's log storage. The retention period the provider publishes for our plan is 7 days, but records have also been observed to remain longer; when they are physically deleted is governed by the provider's policy.
• Guest (anonymous) account data: if 30 days pass since your last sign-in — or since the account was created, if you never signed in — a daily clean-up job closes the account and deletes the data attached to it; there is no waiting or cancellation period (the 30-day cancellation window in section 8 applies when you yourself ask for your account to be deleted; it does not apply to this automatic clean-up). Deletion does not destroy every record: some records — such as the accounting record below — are kept de-identified; and if you share a trip with others, its ownership passes to another member. A guest account you have linked to a permanent account is not covered.
• Accounting record (Flân Puan ledger): retained permanently, de-identified.
• Waitlist record: until the purpose of the list ends or you ask to be removed.
• Website visit measurement (Cloudflare): according to Cloudflare, detailed measurement data is kept for 7 days, after which only a sampled portion of it is retained; measurement results can be viewed going back six months.
• Provider-side retention (OpenAI, Anthropic, OpenFreeMap, openrouteservice, Cloudflare, Google, Brevo) is governed by each provider's own policy.

8. Your rights and controls

• You can get a copy of the data we keep with your account on our server straight away and free of charge by tapping Account › Privacy and security › Download my data in the app; this also works for a guest account. A copy can be prepared once a day. Data that stays on your phone (such as your travel documents, your memories and your Travel preferences) is not included, because we do not have it — it is already with you; your waitlist record on the website is not included either, because it is not linked to your account. The package contains no one else's identity: for example, you do not see who reported your content, only the decision made about it. If you want to have your data corrected or deleted, to request your waitlist record, or to get your copy by email because you cannot reach the app, you can write to info@flanio.com.tr from the email address registered to your account; we will reply to your request free of charge within 30 days at the latest.
• Account deletion: initiated from within the app. Deletion runs over a 30-day window (you can cancel during this period). When the window ends your account is removed; your AI images on the server are placed in a secure deletion queue and physically removed during operational cleanup. Copies you downloaded to your device are not included. Your comments and ratings, and your contributions that are under review or have been rejected, are also deleted together with your account; your approved contributions remain on the place's page, but your name is removed and their link to your account is cut; the moderation log's link to your account is also removed. Trips you share with others are not deleted: if you own the trip, ownership passes to another member; the trip's content (destination, dates and the notes you wrote in it) stays with the other members; your name and the link to your account do not stay in the trip. To request deletion without installing the app: https://flanio.com.tr/delete-account.html.
• Turn analytics off: you can disable analytics in settings (stops future event collection).
• Turn crash reports off: you can switch off "Send error reports" in settings; when off, nothing is sent to Sentry.
• Permissions: you can revoke camera/location/notification permissions from your device settings at any time.
• Signing in with Google: if you signed in with Google, you can also remove Flanio's access to your Google account in your Google account settings.
• Location sharing for routes: in Privacy and security settings you can turn off the consent that lets your coordinates be sent to the routing provider for in-app routes. When it is off, your coordinates are not sent to openrouteservice, but directions do not stop there: the coordinates of the place you want to go to are carried to Google inside a google.com/maps address. That address usually opens in an in-app browser tab; if your device has no browser that supports it, the system resolves the address itself and an installed Google Maps app may open. Flanio never adds your own location; the page or app that opens may ask you for it itself.

9. Security

Your session keys are held in your device's secure store (iOS Keychain / Android Keystore). Data is encrypted in transit (HTTPS). Database access is restricted with row-level security (RLS). No method is 100% secure.

10. Children

Flanio is not suitable for people under 16; we do not knowingly collect data from anyone under 16.

11. International transfers

Some of our providers (OpenAI, Anthropic, Cloudflare, Google, Brevo) may process your data outside your country (e.g. the US). The Supabase infrastructure that stores your data — hosting, authentication, storage and database — is located in Germany as of the date this page was last updated. Germany is in the European Union; under EU law, this is not a transfer to a third country for users in the EU. For transfers from Türkiye, it changes nothing. Some server-side operations run in the Supabase region closest to where you make the request, so the destination country depends on where you are. The country where your data is stored is published on this page; if it changes, this page is updated. Supabase itself publishes the current list of regions where server-side operations may run (https://supabase.com/docs/guides/functions/regional-invocation). Hyperknot Software Kft., which operates the map tile provider OpenFreeMap, is based in Hungary, and HeiGIT gGmbH, which operates our routing provider openrouteservice, is based in Germany. The country a company is based in does not by itself determine where data is processed: in its own privacy policy HeiGIT states that data is also transferred to countries outside the European Union. Sentry processes crash reports in the Germany (European Union) region. Transfers to providers processing data in the US or outside the EU are carried out under the data processing agreements concluded with the relevant providers.

12. Changes

We may update this policy; we will notify you of material changes appropriately.

13. Data controller and contact

• Data controller: SİSİFOS YAZILIM VE TEKNOLOJİ ANONİM ŞİRKETİ
• Address: Caferağa Mah. Şifa Sk. No:19 Kadıköy/İstanbul
• MERSİS no: 0771073654600001 · Istanbul Trade Registry no: 1164979
• Email: info@flanio.com.tr

To exercise your rights, you can apply to us in writing at this address, or write to info@flanio.com.tr from an email address you have given us before. You can also get a copy of your data in the app (section 8). We reply to your requests within 30 days at the latest.

14. Language

This policy is prepared in Turkish and may also be provided in other languages. Non-Turkish versions are for information only; in case of any conflict or difference in interpretation, the Turkish version prevails.