ourden

Ourden Privacy Notice under Türkiye’s Personal Data Protection Law

Effective date:

Who is responsible for your data?

Ahmet Kılıç, who publishes Ourden in Türkiye under the name Kylindravia, is the data controller. You can send privacy questions and requests about your personal data to kylindravia@gmail.com. This notice is provided under Article 10 of Türkiye’s Personal Data Protection Law No. 6698 (KVKK). Version 1.0 is effective from 19 November 2026.

This notice covers the Ourden iOS and Android apps, our website and support correspondence. You can exercise the rights described here if someone invites you to a home or creates a profile for you, even if you never open an account. AI suggestions are optional. You make a separate choice before your first request. We used AI to help prepare this notice.

If someone added you to a home without an account, you can find out what other members see. You can also go directly to how to request correction or deletion.

Data we collect

We receive data when you enter it in the app, when a home member shares a record, and from the sign-in and purchase services you choose. The app, your device and our servers also automatically generate electronic records of connections, sync activity, security events and use of the service. We receive support messages and privacy requests by email or in writing.

To create your account and sign you in, we process your email address, display name, language, time zone and session details. If you set a password, we store a one-way hash. When you sign in with Apple or Google, we use the account identifier and email address provided by that service. Device information can include an app-generated identifier, a public key, the platform, app version, device integrity check result and push notification token.

A home profile contains a name or nickname, an avatar chosen from the app, a profile type, a role and, for a child, an age range. Depending on the features you use, we record home settings, rooms, appliances, chores and their completion, availability, weekly plans, saved dishes, recipe notes, menu objections and comments, ingredients to avoid, shopping lists and household notices. We also process your notification preferences, personal reminders, AI sharing preference and the dishes or chores you have asked us not to suggest again.

For subscriptions, we process store transaction and product identifiers, the link between the paying account and the home, subscription status and the end of the current period. You give your payment card details to the store where you make the purchase. Ourden does not receive your card number or security code. The app does not request access to your location, contacts, photos, microphone or calendar.

Why we use your data and our legal grounds

To create your account, keep you signed in, process an invitation or a request to join a home, sync your home across devices, deliver the notifications you choose, verify a store purchase or generate an export you request, we use the data needed for that task. The legal ground is entering into and performing our service agreement with you as the account holder (Article 5(2)(c) of the KVKK).

We use device checks, attempt counters, technical transaction identifiers and error logs to protect your account from unauthorized access, identify repeat requests and resolve technical problems. We record the relevant previous and new values so members can see who changed a shared record and when. We rely on our legitimate interest in providing a secure and reliable service (Article 5(2)(f)). The Metrics section explains how we measure use of that service.

When you ask for help, we use your contact details and your message to resolve the problem. For members, we do this to perform the service agreement (Article 5(2)(c)). If you do not have an account, we rely on our legitimate interest in answering your question (Article 5(2)(f)). We rely on our legal obligations to respond to privacy requests and binding official demands (Article 5(2)(ç)). Where a specific dispute arises, we keep the documents necessary to establish, exercise or protect a legal right (Article 5(2)(e)). Optional AI use and profiles for people without an account rely on the explicit consent described below (Article 5(1)).

Who can see what in a home?

Members can see names and avatars in the homes they have access to, shared chores and dishes, availability, chore and ingredient preferences, and the history of changes to shared records. They can also see the subscription status and a summary identifying the paying member. Other members do not see your account email, personal reminders, notification settings, AI requests or personal list of suggestions to exclude. They can see a suggestion you choose to add to a shared list.

Before joining, someone who opens a valid invitation can see the home’s name and the inviter’s display name and avatar. If you share an invitation or a list using your device’s share feature, the content goes to the recipient and the app you choose. The disclosures described here to recipients in Türkiye, and disclosures to competent authorities where necessary, take place under Article 8 of the KVKK on the legal ground stated for the relevant purpose.

Adults and children without an account

A home member may create a profile for you. Authorized home members can see your name or a nickname they recognize, your chosen avatar, whether you take part in meal plans and any household preferences recorded about you. Only an age range is used for a child. Children do not have sign-in accounts, but their profiles can be included in meal plans. A home can also be planned without creating a profile for someone else.

Before creating a profile, give this notice to the adult concerned or, for a child, to their legal representative. Explain what you want to add and who will see it. Get the adult’s explicit consent or the explicit consent of the legal representative authorized to act for the child. Add the profile only after receiving a clear yes to this specific use. Explain it to the child in words appropriate to their age and understanding. The same rule applies to a nickname that people in the home can recognize. Consent to a profile does not include consent to use that person’s information for AI suggestions.

If you think a record about you exists, you can contact us without opening an account. You can withdraw your consent or ask us to find, correct or delete the record. Ahmet Kılıç is responsible for this processing. When we obtain your data from someone else, we must inform you within a reasonable time, by our first contact with you if we use it to contact you, or by the first disclosure if we share it. For a profile visible to the home, that means providing the notice before adding the profile.

For an ingredient preference, enter only the ingredient name, such as “hazelnuts.” Keep allergies, diagnoses, treatment, medication and religious beliefs out of dish names, notes and AI requests. Ourden does not ask for this information. If a preference or free-text entry reveals sensitive information, you can ask us to remove it.

AI

When you choose to request suggestions in a home with AI access, we ask separately for your explicit consent to process the data needed for that suggestion and send it to OpenAI (Article 5(1)). Consent is per account. If you decline, you can still use chores, meal plans and shopping lists. You can withdraw consent in Settings › AI suggestions. We stop requests that have not started. A call already sent to OpenAI cannot be recalled. Each new request requires current consent.

What we send depends on the task. A meal suggestion may use the number of people eating, a combined list of ingredients to avoid without linking them to specific people, dish names and when dishes were last eaten. For an alternative menu, OpenAI may receive the menu that members objected to and their comments. For suggestions to add to the dish archive, it may receive your feedback and names you have asked us not to suggest again. An ingredient draft needs the dish name and type.

For chores and routines, OpenAI may receive your description, relevant room and appliance types, and the names of chores and routines. Depending on the weekly planning task, it may receive a planning note or participants’ unavailable days and daily chore counts under temporary labels. To help check for abuse, we also send a pseudonymous safety identifier that stays the same for your home. Ourden can link it back to that home.

In specific note fields, we replace known personal and home names with placeholders. A name in a dish or chore title, or an email or street address typed into a text field, can reach OpenAI as written. We do not include the account email, raw account ID, profile type or a child’s age range as standard data fields. If the request contains information that identifies another person, your consent does not cover them. Only request that suggestion if the person, or their legal representative if they are a child, has separately agreed to this AI use. You can still use the shared record for the home’s ordinary activities.

“Skip for now” temporarily hides a suggestion in the open meal draft. “Do not suggest again” saves a preference for your account in that home. Relevant future suggestions may use the dish or chore names you have excluded. You can reverse this choice.

We ask OpenAI not to keep the request for later use (store: false). OpenAI’s default abuse monitoring logs can contain request and response content and can be retained for up to 30 days. A legal requirement or the need to protect its services or others from harm may extend that period. OpenAI’s API data policy.

Metrics

We use a limited set of events to see where people run into difficulties setting up or joining a home, which features are used and how the service works. Each event contains its type, attributes drawn from fixed options, the platform, version, language and a time rounded to the minute. Metrics exclude names, email addresses, personal notes, dish details and chore content. On the server, a secret key produces a separate code for each account and each home so we can count successive events from the same account or home. Because we can link these codes back to the account or home, we treat them as personal data.

We rely on our legitimate interest in finding problems and measuring which features work, while protecting your fundamental rights and freedoms (Article 5(2)(f)). We suppress report rows based on fewer than ten homes or accounts. We do not use advertising, cross-app tracking or third-party analytics or crash-reporting tools.

You can object to these metrics by emailing us from your registered address with the subject “Ourden ölçüm itirazı” (Ourden metrics objection). There is no separate switch in the app. Once we verify and accept your objection, the server stops recording new events for your account. At the next account sync, your device clears pending events. You can make a separate request to delete past records. Your objection applies to your account only.

Providers and transfers

Railway hosts account and shared home data, as well as sync, security and subscription records. The region selected for the server and database is EU West in Amsterdam, the Netherlands. Railway may process your IP address, the request path and browser or app information when you connect. Our app logs record the route, status, response time, error type and, where needed, a transaction identifier. Passwords, names, email addresses and text entered in your home are excluded from these logs.

GitHub Pages hosts the publisher’s Ourden pages and PDFs at ahmet12.github.io/ourden/. When you open a page or file at that address, your browser connects to GitHub. GitHub logs and stores your IP address for security even if you have not signed in. This data may be processed in the United States and other countries where GitHub operates. We rely on our legitimate interest in keeping these pages accessible and secure (Article 5(2)(f)). GitHub Pages’ explanation of visitor data.

Cloudflare provides Ourden’s domain services. If you visit a page served by Cloudflare on getourden.com, it processes your IP address, the address of the page requested and technical information sent by your browser to deliver the page and protect the service. We rely on the same legitimate interest for this use. When email forwarding is used, Cloudflare also processes the addresses and contents of the forwarded message. When we make backups, we use Cloudflare R2 buckets restricted to the European Union to store encrypted database copies and a ledger used to exclude deleted records during restoration. The setting applies to these buckets. Cloudflare also operates global network services.

Brevo delivers transactional emails such as sign-in codes and security messages. It processes the recipient address, language and message content. Open and click tracking are disabled for these messages. Brevo lists France, Germany and Belgium as locations for its own databases. Google processes the email addresses, message and any attachments you send to the Gmail mailbox we use for support and privacy requests. You can also submit a written request by post.

Apple and Google process account tokens when you use their respective sign-in services, integrity evidence for device security and transaction identifiers to match App Store or Google Play purchases with subscriptions. The Apple Push Notification service or Google Firebase Cloud Messaging receives the device token and, when included, the notification title and text already visible to the intended recipient. Personal reminder text is never sent through this channel. OpenAI prepares optional AI suggestions.

These services involve transfers of personal data outside Türkiye. Apple, Google and OpenAI use global infrastructure and processing may take place beyond the European countries listed above. Article 9 of the KVKK applies separately to transfers to recipients abroad. Your AI consent covers your choice to use that feature. You can ask us which recipient received your data, in which country and under what transfer conditions. When a competent court or administrative authority makes a binding request, we disclose only the records within its scope.

What stays on your device

To let you work offline, Ourden keeps copies of account and home data, unsent changes and reminders on your device. Session tokens and the device key are kept in the operating system’s secure storage. The local copy of your home data is excluded from system backups. Widgets and lock-screen notifications can display the home name, a chore, a dish or the name of the person cooking. You can manage their visibility on your device.

Signing out, switching accounts or deleting your account clears the local copies for that account. Leaving a home clears that home’s copy. If only your session expires, the last email address you used may remain for sign-in. The device key and appearance preferences follow their own retention periods. A pending invitation entry is kept for up to 24 hours.

Information on this website

You can read the privacy, help and account deletion pages without an account. Ourden does not add analytics or advertising cookies, tracking pixels or usage metrics to these pages. The Turkish and English pages have separate addresses. Selecting an email link opens your email app. We receive your address and message when you choose to send the email.

Export and account deletion

Adult home members can export chore lists and history, the dish archive, meal history and shopping lists as a JSON file. The file may include home details, profile names, avatars and any child age ranges. Check it before sharing. The copy on our server is deleted after 24 hours. You control any copies you download or send to someone else. You can request access to other personal data separately.

To delete your account in the app, go to Settings › Account and sign-in › Delete account. If you cannot access the app, use the email link on the account deletion page to send your request. We verify that the account is yours and that you requested deletion, then let you know the outcome by email. If other accounts share a home where you are the last administrator, first transfer that role or close the home. If a recent change to your email address can still be reversed, deletion can finish once that period ends. Account deletion help.

Once we accept deletion, we disable sign-in methods and end your sessions. Your account and personal records are normally scheduled for permanent deletion at the end of a 30-day period during which they cannot be used. A home where yours was the only account closes. In a home still used by others, shared chores, dishes and history remain. We remove your profile name, reset your avatar and show your contribution as “Former member.” Information someone typed about you in a shared note may remain in the text. You can tell us which record needs attention. To end a store subscription, cancel it separately in the App Store or Google Play.

Your rights under the KVKK

Under Article 11, you can ask whether we process your personal data and request information about it if we do. You can ask why we process it, whether we use it for that purpose and which third parties in Türkiye or abroad received it.

You can ask us to correct incomplete or inaccurate data, erase or destroy it when the conditions in Article 7 apply, and notify recipients of those corrections, erasures or destructions. You can object to a result against you that arose solely from automated analysis, and seek compensation for damage caused by unlawful processing. You can withdraw your explicit consent at any time for future processing. Rights available to you under other applicable laws also continue to apply.

How to make a request

Under Article 13, you can write in Turkish from your registered email address to kylindravia@gmail.com. Use “Ourden KVKK başvurusu” (Ourden privacy request) as the subject line. If you do not have an account, cannot access your registered email or prefer to apply in writing, contact us at the same address for our postal address and instructions. We answer initial inquiries from other email addresses too. You may send a request bearing a secure electronic signature or a mobile signature to the same mailbox.

For a formal request, give your full name, your Turkish national ID number if you are a Turkish citizen or, if you are a foreign national, your nationality and passport number or other ID number if available. Include your home or work address for service, your email address for notices, telephone and fax numbers if you have them, and what you want us to do. Sign a request sent by post. If you act for someone else, we may ask for enough information to verify your authority. Keep copies of ID documents, passwords, one-time codes, invitation links and records for an entire home out of your first support message. We do not routinely ask you for an ID photo when you apply from your registered address.

We will send a reasoned response in writing or electronically as soon as the nature of your request allows, within 30 days of receipt. Requests are normally free. If a request incurs an additional cost, only the fee set by the Turkish Personal Data Protection Board may apply. We refund any charge if our error caused the request. If we refuse your request, our response is insufficient or we miss the response deadline, you can complain to the Board after first applying to us. The complaint deadline is 30 days from learning of our response and, in all cases, 60 days from your application to us. The Authority’s guidance on requests and complaints.

Retention periods

Account and home content is kept while the service continues and the purpose for keeping the data still applies. A deleted account or a closed home is kept inaccessible for 30 days. The maximum period for a database backup is 30 days. The technical ledger used to remove deleted records after restoring a backup is kept for 90 days. Turkish regulations require records documenting erasure, destruction and anonymization operations to be kept for at least three years. This evidence does not need to contain a copy of the deleted content.

AI input is processed temporarily while the task is pending and running. We keep draft content for 24 hours, the draft record for 7 days and the request record without its contents for 90 days. We keep the time and version of your current AI consent in your personal settings. Withdrawing consent clears those details. Permanent account deletion also removes your personal AI preferences.

Metrics stay in the device buffer for 7 days, raw events are kept for 180 days, and aggregates without account or home codes for 25 months. We keep subscription event records for 395 days. Railway’s 7-day technical log period is the search window on the selected plan. It does not specify when the provider erases every copy.

We delete ordinary support correspondence from our mailbox within 90 days of closing the issue. We keep a separate, minimal record for only as long as necessary to answer a privacy request, protect a right in a specific dispute or meet a legal requirement. When a reason for processing no longer applies, we erase, destroy or anonymize the data. The table below sets out Ourden’s other technical retention periods.

Retention periods
Data classPeriod
Change feed60 days
Sync receipt30 days
Published events7 days
Operations counters30 days
Service heartbeat1 days
Resolved operations alarm90 days
Backup run record400 days
Operations command record730 days
Deletion record id in an operations command90 days
Deleted account30 days
Closed home30 days
Deleted personal reminder30 days
Export job30 days
Purge ledger90 days
Raw metrics180 days
Client metrics buffer7 days
Server logs7 days
Database backup (maximum)30 days
Deletion notice email (maximum)7 days
Sign-in challenges and attempt records1 days
Closed session (after closure)30 days
Device without sessions (after last seen)90 days
Encrypted record for revoking Apple sign-in authorization30 days
Apple sign-in event receipt and pending encrypted content30 days
Resolved email change (after resolution)30 days
Notification identity and delivery records30 days
Store notification receipt30 days
Purchase intent7 days
Store subscription event record395 days
Store subscription in no home (after it ends)30 days
AI request (without content)90 days
AI draft record7 days
AI access block record30 days
Export file24 hours
AI draft content24 hours
Aggregate metrics25 months
Home audit trailUntil the home is purged
Deleted home recordsUntil the home is purged
Feed sequenceUntil the owner is purged
Device feed progressUntil the device is deleted
Command receiptUntil the principal is purged
Task reminder receiptUntil the task is purged
AI preference and OpenAI sharing permissionUntil the account is purged