Yankı V1 · Draft

Privacy Information Notice

This informational counterpart summarizes Yankı’s data flows for international users. The Turkish KVKK notice is intended to be the local statutory notice if that legal structure is adopted; this wording requires legal review.

Review status: Address, legal-basis, and effective-date details are not finalized.

Controller and contact

Controller: Yavuz Alp Demirci
Address: Çankaya / Ankara / Türkiye
Privacy contact: alpyavuz5561@gmail.com

Data categories and purposes

Yankı handles email and Supabase Auth identifiers for account management; date of birth and education details for the profile; subjects/courses; KONU/SORU titles, notes, metadata and scheduler state; saved image files and metadata; on-device OCR text that may be persisted with an image; and review events. These data support authentication, profile and study functionality, persistence, review scheduling, support, and deletion requests.

Device processing and cloud persistence

On Android, OCR is performed on-device with ML Kit and no image is sent to an external OCR API. Saved images are uploaded to private Supabase Storage for persistence and synchronization. Supabase also provides Auth, Postgres database and Edge Functions. The documented Supabase project region is Frankfurt.

Advertising and consent

Yankı uses Google AdMob banner ads only on Root/Home, Library, and Calendar. UMP consent gates ad requests. Yankı does not send private study/profile content, images, email, user IDs, education data, subjects, review history, or scheduler state as AdMob targeting options. The Google Mobile Ads SDK may automatically process IP address, product interactions, diagnostics, and device/account identifiers for advertising, analytics, and fraud prevention; final declarations require current SDK/provider review. A publisher-rendered privacy-options entry point is not currently exposed in Profile; track this as a provider requirement check. Profile itself remains ad-free.

Sharing and international processing

Supabase and Google are external service providers/third parties used for the purposes above. Their legal roles, global infrastructure, transfer mechanisms, and retention practices are not concluded by this product text. Cross-border transfer review is required.

Retention and deletion

Active application data is retained while the account exists and the service needs it. The in-app Profile → Hesabımı sil flow deletes the Auth account, application records, review history, image metadata, and private saved images. External requests can be started through Account Deletion. Provider or legally required records may follow separate retention rules: LEGAL RETENTION POLICY REQUIRED.

Rights and requests

For access, correction, deletion, or privacy questions, contact alpyavuz5561@gmail.com. Identity verification may be required. Do not send passwords.

Age policy

Yankı V1 is a general-audience study application with no app-level 18+ gate. Date of birth is an ordinary Profile field; onboarding, Profile editing, and persisted profiles are not blocked solely because of age. Date of birth is not an AdMob targeting option. Play Console target-audience declaration and any child-directed treatment remain PENDING PLAY CONSOLE.