Yankı V1 · Draft
Privacy Policy
This policy explains Yankı’s current technical behavior in clear language. Legal review and completion of address/effective-date details are still required.
About Yankı
Yankı is a study application that helps users create KONU and SORU study records, add images, and plan reviews. The controller/publisher is Yavuz Alp Demirci.
Information we collect
- Account and identity
- Email address, the user identifier created by Supabase Auth, and session information. Yankı does not store passwords in plain text; authentication is handled at the Supabase Auth boundary.
- Profile
- Date of birth, education type (LGS, YKS, or university), school grade/status, and YKS track; university, department, and year/class for university profiles.
- Subjects
- Controlled subjects for LGS/YKS or custom university courses entered by the user.
- Study content
- KONU/SORU type, title, question topic, mistake reason, note, confidence, favorite and active status, and the subject relationship.
- Images and text
- Saved study images, image technical metadata, and OCR text extracted on-device on Android.
- Review history
- Review result, review dates, next scheduled date, and scheduler version fields.
Photos and text extraction
On Android, text recognition runs on the device using ML Kit; the image is not sent to an external OCR API. When a user saves an image, however, the image and related metadata are uploaded to Yankı’s private Supabase Storage for persistence and synchronization. It would therefore be inaccurate to say that images never leave the device.
Why we use information
- Create and manage accounts and sessions.
- Store profile and subject choices.
- Display KONU/SORU records, images, OCR text, and review history.
- Run the review scheduler.
- Process a user-initiated account deletion request.
- Display Android banner ads and manage user choices.
Cloud services
Yankı uses Supabase for Auth, Postgres database, private Storage, and Edge Functions. Application data is separated by user ownership controls; the image bucket is private and signed URLs are used for viewing. The documented Supabase project region is Frankfurt. Provider-specific retention and logging policies must be reviewed separately.
Advertising and Google AdMob
Yankı uses banner advertising only on Root/Home, Library, and Calendar.
There are no interstitial, rewarded, or app-open ads. The Android
integration is @capacitor-community/admob 8.0.0. Yankı does
not put a user ID, email, date of birth, education, subjects, study
text, images, Library data, review history, or scheduler state into
AdMob options.
Depending on configuration and consent/choice signals, the Google Mobile Ads SDK may process categories such as IP address, product/app interactions, diagnostics, and device/account identifiers for advertising, analytics, and fraud prevention. This third-party flow and the final Play declaration must be verified before release.
Advertising choices / UMP
Yankı requests a banner only after Google UMP consent processing and
when canRequestAds is true. Consent, SDK, network, and ad
failures are noncritical. The Profile UI does not currently expose a
publisher-rendered privacy-options entry point. Track this as a provider
requirement check. Profile itself remains ad-free.
Sharing
Yankı’s private study and profile content is not supplied to AdMob as a targeting payload. Supabase and Google services are third parties operating under their own terms and policies; their legal classification is not determined by this product text and requires legal review.
Security
The app is configured to connect to Supabase and provider endpoints over HTTPS/TLS. Account and data access is limited through authentication and ownership controls. Yankı makes no claim of independent security certification or end-to-end encryption.
Retention and deletion
Active account data is technically retained while the account exists and the service needs it. Users can start deletion in the app through Profile → Hesabımı sil. The flow deletes the Auth account, profile/subject/study records, review history, image metadata, and private saved study images. A fixed period for independent provider logs or legally required security records cannot be derived from this code: LEGAL RETENTION POLICY REQUIRED.
Account deletion
Use the Account Deletion page for the external request pathway. Do not send your password by email.
User rights and contact
For access, correction, deletion, objection, or privacy questions, use the channel listed on Support. Until contact details are finalized: alpyavuz5561@gmail.com. Identity verification may be needed to process a request securely.
Children / 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 sent to AdMob as an ad-targeting option. Play Console target-audience declaration and any child-directed treatment remain PENDING PLAY CONSOLE.
International transfers
Supabase and Google global infrastructure may be used. The documented Supabase project region is Frankfurt; no single country should be assumed for Google advertising infrastructure. The KVKK legal basis for cross-border transfers is LEGAL REVIEW REQUIRED.
Changes
If this policy changes, the current version and effective date should be shown on this page.
Contact
Controller: Yavuz Alp Demirci
Address: Çankaya /
Ankara / Türkiye
Privacy:
alpyavuz5561@gmail.com