PRIVACY POLICY
What we collect, why we collect it, and what remains under your control.
oesnada is built around data minimization. We collect only what is needed to keep the service functional, understand product quality, and improve the experience. We do not sell your personal information, share it for advertising, or use it for third-party tracking.
We do not use advertising cookies, third-party trackers, or cross-site identifiers. Our self-hosted Umami analytics does not set any cookies; it groups visits using an anonymous hash derived from your IP address and browser user agent that rotates every 24 hours. The analytics script is restricted to oesnada.com domains and does not load on mirrored or third-party sites.
The only first-party cookie we use is an essential session cookie set when you log into the Lineup writer panel. It is httpOnly, scoped to oesnada.com, and removed when you log out. Local storage on your device stores product preferences only — color palette, dismissed prompts, and similar UI state.
For privacy or data questions, contact us at oktay.dak@icloud.com.
The website uses self-hosted Umami analytics at ‘umami.oesnada.com’. The analytics script loads when the website opens and is restricted to oesnada.com domains.
System data collected through Umami: page views, browser type, operating system, device type, country/region (derived from IP, then the IP is discarded), screen resolution, referrer, and visit time.
Interaction events are recorded across surfaces with minimal context:
Each event carries contextual fields such as story id, category, source, language, and the surface where it occurred. No personal identifiers are attached to analytics events.
The iOS app records product events to operate the service and understand product quality. These events do not include personal identifiers in the analytics payload.
App events: app open, feed loaded, story open, story swipe, undo swipe, settings open, and notification open.
Context fields: story_id, category, source, type, has_audio, has_video. Swipe events may include direction and index. Feed events may include article_count, new_story_count, and source.
System fields: app_version, build, platform, language, and screen.
app_open: Recorded when the app enters the foreground. It contains opening time and system context.
feed_loaded: Recorded when the main signal stack loads. It may include how many stories loaded and which source supplied them.
story_open: Recorded when a story detail is opened. It includes story id, category, and content type.
story_swipe: Recorded when a card is swiped. It includes swipe direction and the story position in the stack.
story_undo_swipe: Recorded when a swipe is undone. It includes the original swipe direction and position.
settings_open: Recorded when the settings area opens. It may include which settings surface was opened.
notification_open: Recorded when the app opens from a push notification. It may include the related story context.
If you subscribe to email updates, we store your email address, your cadence preferences (daily, weekly, monthly), the source of the subscription, and your selected language. We rate-limit signup attempts by hashed IP and hashed email to prevent abuse. An internal operational alert is sent through Telegram with a masked version of the email (for example, ‘a***@***.com’); the actual email is never sent to Telegram. Newsletter emails are delivered through our own SMTP. You can unsubscribe at any time using the link in any newsletter, or by emailing oktay.dak@icloud.com.
If you allow notifications, your browser registers a push subscription with the push service operated by your browser vendor — Apple Push Notification Service for Safari, Google Firebase Cloud Messaging for Chrome and Android, Mozilla AutoPush for Firefox. We store this push subscription together with your topic preferences, delivery mode, summary hours, and time zone so we can deliver the notifications you requested. You can revoke notifications at any time from your browser settings; doing so removes the subscription.
If you submit an application to the Oesnada Lineup writer panel or are admitted as a writer, we collect additional data tied to that role.
Application data: name, email, social handles, short bio, your responses to the application questions, and your KVKK / consent record. To prevent abuse we compute a risk score from signals including time spent on the form, paste ratio, presence of a honeypot fill, IP rate, whether the email is on a disposable-email list, and DNS resolution of submitted URLs. Honeypot triggers result in a silent drop with no application stored.
Authoring data (admitted writers only): hashed authentication credentials, session records, article drafts and final article bodies, your profile (display name, slug, bio), and metadata such as word count and reading time. AI assist actions (rewrite, title alternatives) send the relevant excerpt of your article body to Wiro, a third-party AI service. Cover images and audio narrations for published articles are generated on demand and stored in Cloudflare R2; they are served from a public CDN URL.
You can request access to or deletion of your Lineup data at any time at the contact email above.
We do not share your data with Google Analytics, Facebook Pixel, or similar third-party advertising trackers. Umami analytics is self-hosted by oesnada.
Third-party services we use in limited ways:
External links inside stories lead to third-party websites; their privacy practices are not controlled by oesnada.
Depending on your location, you may have rights to access, correct, delete, object to, or request portability of your data. To make a request, contact oktay.dak@icloud.com.
Analytics data is stored in aggregated form and cleaned periodically. Individual visitor analytics are anonymized or removed after a reasonable retention period, generally no longer than 90 days where technically practical.
oesnada is not designed for children under 13, and we do not knowingly collect personal information from children.
We may update this policy as the product changes. The latest version will always be available on this page.
Last updated: May 2026