Privacy Policy
This policy explains how your personal data is processed when you use the Splitloo mobile app and splitloo.com, as required by Türkiye's Personal Data Protection Law No. 6698 ("KVKK"), article 10. It is a notice, not a consent form. Where we need your explicit consent we ask for it separately and clearly.
In short
- Your votes are private to strangers. By default only your followers can see which option you chose ("My votes are visible to followers", can be turned off under Settings > KVKK and Consent). Votes on sensitive, confession and 18+ questions are never shown to anyone. Percentages are anonymous totals.
- We do not sell your data, share it for advertising or use ad networks.
- Some questions touch on sensitive areas such as politics, belief, health or private life. They are shown to you only if you give separate permission, which you can withdraw at any time.
- You can download your data and delete your account inside the app.
- Your data is processed on Google's servers in the EU and the US; see section 8.
1. Data controller
Loo Teknoloji Sanayi ve Ticaret Limited Şirketi
Sağlık Mah. Ataç 1 Sk. Ömerbey No: 3 İç Kapı No: 8, 06430 Çankaya, Ankara, Türkiye
MERSİS: 0609139314700001 · Tax ID (Mithatpaşa): 6091393147 · Ankara Trade Registry No. 523969
Email: destek@splitloo.com (use the subject "KVKK" for data protection requests)
2. Who this covers
People who create an account in the app, people who vote on splitloo.com without an account, people who open and play a friend link, visitors to the website, and people who email us.
3. Account types and sign-in data
- Email and password: your email address and password. The password is stored by Firebase Authentication as an irreversible hash; we cannot see it. Password-reset emails are sent through Firebase.
- Sign in with Google: the email address, name and account ID of your Google account.
- Sign in with Apple: your Apple account ID and email address. If you choose "Hide My Email" we receive Apple's relay address, not your real one.
At sign-up we also ask for a username (public), your name (never shown to other users) and a city. You may add a profile photo and a short bio; photo, city and bio are visible on your profile.
4. What we process, why, and on which legal basis
The table lists, for each data group, where it comes from, the purpose and the KVKK legal basis. "Contract" means art. 5/2-c (performance of a contract), "legal obligation" art. 5/2-ç, "establishing or protecting a right" art. 5/2-e, "legitimate interest" art. 5/2-f, "explicit consent" art. 5/1 and art. 6/3-a.
| Data | Source | Purpose | Legal basis |
|---|---|---|---|
| Account and profile: email, name, username, city, photo, bio, account type, sign-up date | You; Google or Apple | Running your account, showing you to others under your username, contacting you | Contract |
| Votes: which option you chose on which question, and when | You | Computing results, your Opinion DNA and streak, listing answered questions on your profile and (if your setting is on) showing them to your followers | Contract; explicit consent for questions touching sensitive areas (section 5) |
| Opinion DNA: a five-axis summary derived from your votes | Computed from your votes | Showing you your own opinion summary and your match with friends | Contract |
| Comments: your text, your side, time written; like and "persuaded me" counts | You | Publishing your comment publicly; checking it against community rules | Contract; legitimate interest and protection of rights for moderation |
| Questions you submit: text, options, category, review status | You | Reviewing and, if approved, publishing the question | Contract |
| Interactions: likes, "persuaded me", saves, who you follow and who follows you, who you block | You | Running these features, keeping blocked users away from you | Contract |
| Reports: reporting and reported account, comment text, report category, outcome | You, or another user if you are reported | Enforcing community rules, meeting obligations under Law No. 5651, keeping records for disputes | Legal obligation; protection of rights; legitimate interest |
| Moderation records: comment text rejected by the automated check and the rejection category; sanctions applied | Generated by the system | Preventing abuse, handling appeals | Legitimate interest; protection of rights |
| Friend links: the 10 questions in a link you create and your answers; the answers and match score of the person who opens it | You; the person opening the link | Computing and showing the match to both sides | Contract (you); legitimate interest and the player's own request |
| Optional gender (Woman / Man / Prefer not to say) | You, asked separately | Aggregate women / men breakdown on question results | Explicit consent |
| Notifications: push token (FCM), your notification preferences, a record of notifications sent to you | Your device; the system | Sending the notifications you chose and listing them in the app | Contract; operating-system permission |
| Usage analytics: which screens and features are used (Google Analytics for Firebase) | Your device, only if you consented | Improving the product | Explicit consent |
| Crash reports: device model, OS, app version and your account ID at the time of a crash (Firebase Crashlytics) | Your device | Finding and fixing bugs | Legitimate interest |
| Security and access logs: IP address, request time, App Check attestation result, Firebase installation ID, rate-limit counters | Your device; the system | Preventing fake accounts, bots and attacks; keeping the traffic records required of hosting providers by Law No. 5651 | Legitimate interest; legal obligation |
| Premium: subscription status, purchase receipt ID, RevenueCat app user ID | Apple / Google and RevenueCat | Unlocking Premium features, verifying subscription status | Contract; legal obligation for financial records |
| Support correspondence: emails you send us and their attachments | You | Answering your request, handling data protection requests | Contract; legal obligation |
| Consent and acceptance records: which version of which text you accepted and when; when you gave or withdrew consent | Generated by the system | Our burden of proof under KVKK and contract law | Legal obligation; protection of rights |
5. Questions touching sensitive areas and explicit consent
Most Splitloo questions are about everyday preferences. Some may touch on political opinion, religious or philosophical belief, health or sexual life, which KVKK article 6 classifies as "special categories". Your vote on such a question counts as special-category personal data while it is linked to your account. So:
- These questions are flagged by our editors and shown to you only if you give separate permission, requested on its own screen the first time such a question would appear, stating clearly what is asked (KVKK art. 6/3-a).
- If you decline, the app works exactly the same; these questions simply do not enter your feed. Declining disables no feature.
- You can withdraw permission at any time under Profil > KVKK ve Rıza. On withdrawal your votes in these areas are removed from your account and remain only in anonymous totals.
- If you write a comment on such a question, the comment and your side become public; that is data you have made public by your own choice (art. 6/3-ç). You can delete the comment at any time.
- We never transfer these votes to third parties in identifiable form, never use them for advertising or profiling, and do not build a separate "political" or "religious" axis in Opinion DNA. Results are published only as anonymous percentages.
- We apply the additional safeguards the Personal Data Protection Board requires for special categories (restricted access, encryption in transit and at rest, access logging).
6. Automated processing and profiling
- Opinion DNA is computed automatically from your votes and shown only to you; nobody sees it unless you share it. It has no legal or similarly significant effect on you.
- Friend match compares the two sides' answers to the same 10 questions.
- Comment pre-check: before publication your comment passes a word filter and an AI model (Google Gemini). Only the comment text and the question text are sent; not your username or email. If it is rejected you see why and can appeal; a human reviews the appeal (KVKK art. 11/g).
7. Who we share data with
We do not sell, rent or share personal data for advertising. Data goes only to the following providers acting on our behalf (data processors) and, where legally required, to competent authorities:
| Recipient | Purpose | Server location |
|---|---|---|
| Google Cloud / Firebase (Google Ireland Ltd., Google LLC) | Database and server code, authentication, file storage (profile photos), notifications, app attestation, remote configuration, crash reports; usage analytics if you consented | Database and server code: Belgium and the Netherlands (EU). Photo storage, authentication, notifications, crash reporting and analytics services: US |
| Google Gemini API (Google LLC) | Comment pre-check (comment and question text only). Used under the paid service terms; Google does not use this content to train its models | US |
| Google reCAPTCHA (Google LLC) | Bot protection for voting on splitloo.com | US |
| Apple (Apple Distribution International Ltd., Apple Inc.) | Sign in with Apple; App Store purchases and subscription management | Ireland, US |
| Google Play (Google Commerce Ltd.) | Google Play purchases and subscription management | Ireland, US |
| RevenueCat, Inc. | Verifying subscription status | US |
| Google (Gmail) and AI-assisted correspondence tools (Anthropic PBC) | Receiving, summarising and answering support emails; only the correspondence itself is sent to these tools | US |
| Courts, prosecutors, the Information and Communication Technologies Authority (BTK), the Personal Data Protection Board and other competent public bodies | Only where and to the extent the law requires | Türkiye |
We have data processing agreements with Google, Apple and RevenueCat; they process your data only on our instructions and under their own privacy commitments.
8. International transfers
The providers above host data outside Türkiye, so your personal data is transferred to the European Union and the United States. Transfers are made under KVKK article 9: data processing agreements are in place with the providers, and the process of putting the Board's standard contract in place with them and notifying the Board is under way. You can ask us about the basis and the possible risks of these transfers. We cannot offer Splitloo without them; if you do not accept them, please do not use the app and delete your account.
9. Retention
| Data | Period |
|---|---|
| Account, profile, votes, interactions, DNA | While your account is open. When you delete it, deletion starts immediately and completes, including backups, within 30 days. |
| Votes after account deletion | Unlinked from you; kept only as anonymous counts in the percentages. |
| Comments | Until you delete them. If you delete your account they stay anonymised as "deleted user"; delete them first if you do not want that. |
| Questions you submitted | Pending submissions are deleted with your account; published questions stay, anonymised. |
| Friend-link plays and web-to-app continue codes | 30 days |
| Notification records | 90 days |
| Rate-limit counters (IP hash) | 2 hours |
| Report and moderation records | 2 years after closure |
| Security and access logs (including Law 5651 traffic data) | As required by law; at most 2 years |
| Crash reports | 90 days (at Google) |
| Usage analytics (if consented) | User-level data at most 14 months; aggregate reports are anonymous |
| Purchase records | 10 years under tax and commercial law |
| Consent and acceptance records, support correspondence | For the limitation period after the account closes or the correspondence ends: at most 10 years |
10. Security
Data is encrypted in transit and at rest. Database access is limited by per-user security rules (Firestore rules) and app attestation (App Check). Only the founding team members who need it have access to personal data. In the event of a data breach we notify the Personal Data Protection Board within 72 hours and affected users as soon as possible.
11. Your rights and how to use them
Under KVKK article 11 you may: learn whether your data is processed; request information if it is; learn the purpose and whether it is used accordingly; know the third parties it is transferred to in Türkiye or abroad; request correction of incomplete or inaccurate data; request deletion or destruction under article 7; request that corrections and deletions be notified to recipients; object to a result produced solely by automated analysis that is against your interests; and claim compensation for damage caused by unlawful processing.
In the app: Profil > Verilerim ve Hesabı Sil (download your data, delete your account) · Profil > Kişisel Bilgilerim (correction) · Profil > KVKK ve Rıza (give or withdraw consent for analytics, gender and sensitive questions). The app interface is in Turkish.
By request: email destek@splitloo.com from the address registered to your account with the subject "KVKK", or write to the address in section 1 with proof of identity. We reply within 30 days, free of charge as a rule, under the Communiqué on Applications to Data Controllers. If you find the reply insufficient or receive none in time, you may complain to the Personal Data Protection Board.
12. Age
Splitloo is for people aged 18 and over; you confirm this at sign-up. We do not knowingly process data of anyone under 18 and delete such accounts when we find them or are told about them. Parents can write to destek@splitloo.com.
13. Website, cookies and similar technologies
- splitloo.com uses no advertising or tracking cookies and no ad networks.
- Voting on the website (/bugun and /soru pages) requires no account. Your browser generates a random device identifier and keeps it only in its own local storage; the server stores an irreversible hash of it together with your choice. This record is not linked to your identity; it prevents a second vote from the same device and feeds the percentages. If you continue in the app with the button on the result page or the continue code, your web votes from this device move to your account and the web record is deleted.
- The friend-link page keeps your answers only in your own browser so you can resume.
- Google reCAPTCHA protects the voting pages against bots. It sends browser and device signals to Google and may set a Google cookie; this is necessary for the security of the service. The Google Privacy Policy and Terms of Service apply on those pages.
- Access logs: on voting pages your IP address is kept for 2 hours as an irreversible hash for hourly rate limiting. The hosting infrastructure (Firebase Hosting) keeps its own access logs at Google for a limited time for security.
14. Notifications and marketing messages
App notifications (question of the day, a friend played your link, follow requests, reactions to your comment, question review status, weekly summary) are part of the service; each can be turned off under Profil > Bildirimler. We send promotional emails or notifications only with your separate consent under Law No. 6563; we currently send none.
15. Changes
We may update this policy. Changes to what data is processed, why, or with whom it is shared are announced in the app at least 15 days before they take effect, and any new processing that needs explicit consent is asked for separately. The current version is always on this page.
16. Version history
- 2.1 correction (22 October 2026): the term "reason" was renamed "comment"; comments are deleted or reported by long-pressing them instead of the "…" menu. Meaning and rights are unchanged.
- 2.1 (draft, 20 October 2026): vote visibility: private to strangers, visible to followers by default ("My votes are visible to followers", can be turned off); votes on sensitive, confession and 18+ questions are never shown; votes moved to a record only the owner can read. City optional at sign-up. Consent records (10 years) and Law 5651 traffic records (2 years) added to the retention table. Sensitive-question list narrowed.
- 2.0 (draft): email/password accounts; per-data-group table with source and legal basis; separate explicit-consent mechanism for sensitive questions; recipients' server locations; retention table; reCAPTCHA, support correspondence and consent records added; international transfer section updated.
- 1.0 (7 October 2026): first version.