Personal Data Protection Notice
1. Controller
Controller: Millennium Production · Tax ID: 5000955901 · Address: Elmasbahçeler Mah. 3. Kumru Sokak No: 54/5, Osmangazi/Bursa, Türkiye · Email: destek@eniyisi.app. This is information under Article 10 of Turkish Law No. 6698. Membership acceptance, acknowledgement of this notice and optional consent are distinct. Reading this notice is not consent to advertising, tracking, sensitive-data processing or unlimited transfers.
2. Collection and data categories
Messages, reviews and transaction information about you may also be obtained from other users in the service relationship. Data are collected through registration/verification, profiles, requests, quotations, messages, uploads, reviews, payment/notification systems, support correspondence and app/web technical records by automated means or partly automated means within a filing system. Categories include time-limited registration/email-verification applications and choice/acknowledgement records; identity/contact, account security, professional/profile, address/coordinates, service transactions, messages/images, blocking/reporting and related review information, billing/payment results, IP/device/notification tokens, activity/presence and measurement events. Avoid unnecessary health data, identity documents or third-party information.
Optional biometric quick login on supported devices uses the OS for face/fingerprint verification. Face or fingerprint templates are not sent to Platform servers; necessary device information and login-authorisation credentials are processed to verify the device and its access.
3.1. Membership and service interactions
Necessary identity, contact, profile and transaction data for account verification, profiles, requests, quotations, messaging and contact between service parties rely on Article 5(2)(c), necessity for forming or performing the contract. Location supports matching/maps. If particular processing or disclosure is not contractually necessary, that ground does not apply automatically: another applicable condition or separate consent where required must be established.
3.2. Payments and statutory duties
Credit/sponsorship sales, payment and delivery rely on Article 5(2)(c). Required invoicing and statutory records rely on Articles 5(2)(a) and/or (ç), as required by the specific legal duty. Records necessary for legal claims may rely on Article 5(2)(e).
3.3. Security, support and legitimate interests
Necessary security, fraud-prevention, troubleshooting and support records may rely on Article 5(2)(f) where no specific contractual/statutory ground applies, subject to a documented balance and protection of fundamental rights. This is not a general basis for unlimited tracking or all advertising.
3.4. Advertising and usage measurement
The app may measure app launches, screen usage and transaction events through Firebase Analytics, serve advertisements through Google AdMob, and measure events such as registration, search, contact, quotations and purchases through Meta App Events. Depending on the integration, device and advertising information, account or transaction identifiers, search terms and event parameters may be transmitted to the relevant service provider. Firebase Analytics and Meta measurement are enabled only with the user's separate, optional consent, which can be changed at any time in the app settings. Disabling these choices does not prevent AdMob advertisements from being shown. Advertising personalisation is managed through Google UMP, while iOS tracking permission is managed in device settings. Refusing personalised advertising does not provide an ad-free service; the types of ads shown are determined by Google UMP and operating-system choices. Permissions and transfer safeguards required by applicable law are applied separately. Email campaign permission does not authorise advertising or usage-measurement activities.
4.1. Visibility between users
Provider promotional profiles, ratings/reviews and regional information are shown in discovery. Authorised signed-in users see the stored provider coordinates on the service map, without approximation; the point may reveal a home or business location. Ordinary profile/listing and public-share responses exclude street addresses and precise coordinates; public-share pages also exclude the registered telephone. Signed-in customers can obtain the provider telephone through the call function. Depending on the quotation endpoint and access rights, registered provider email and telephone fields may also be returned. Customer-entered service addresses and coordinates are visible to providers with request access; a provider that has quoted can obtain the registered customer telephone through the contact function. Messages and attachments reach their recipients. Details users add to descriptions/images are visible to the content audience. Recipients may not use these data for unrelated marketing, scraping or republication without a lawful basis.
Anonymous review display hides the name and profile image in the review view. The related account and service/quotation relationship remain in Platform records; this choice is not irreversible anonymisation. Account and service notifications may include message, quotation or review previews. Their visibility on the device and lock screen depends on the device’s notification/preview settings.
4.2. Suppliers and other recipients
Supabase supports the database and storage of service images/provider verification documents; Cloudinary stores profile/message images and files; Google/Firebase supports notification tokens and measurement described in section 3.4; AdMob supports advertising and related device/advertising data; Meta supports app/conversion events described in section 3.4; PayTR processes necessary payment/contact/IP/order information. Maps and address resolution may use Google Maps and device mapping/geocoding services, processing coordinates, searches and connection data. The configured SMTP supplier (currently a Brevo integration) processes necessary email addresses and message content. Google Vision, when enabled and legally supported, processes relevant images for safety review. Staff access is role-limited; authorities and advisers receive information only as authorised or necessary for duties/claims. Supplier roles vary by activity. Not every recipient receives every data category. The measurement flow is described in section 3.4.
PayTR payment flow: Credit-package and sponsored-visibility payments use PayTR Ödeme ve Elektronik Para Kuruluşu A.Ş. Necessary name, email, telephone, payment/billing address, IP, order reference, basket, amount and currency are sent to PayTR. Payment results and necessary refund/chargeback information are processed by the Platform for payment performance, transaction security and disputes. Necessary contract processing is assessed under Turkish Article 5(2)(c), the Platform's specific statutory duties under Article 5(2)(ç), and legal claims under Article 5(2)(e). This flow does not depend on advertising permission. Card entry takes place in PayTR's payment form; Platform servers do not store card numbers or security codes. PayTR may act as processor for activities performed on the merchant's behalf and as a separate controller for its own payment-law purposes and duties. Its own records and rights-request procedures are described in its official notice. Deleting a Platform account does not automatically erase records PayTR must retain. The Platform remains responsible for its own processing and necessary recipient notifications.
5. International transfers
Transfers to service providers whose infrastructure or access is located abroad are governed by Article 9 of Turkish Law No. 6698. In addition to the relevant Article 5 or 6 processing condition, an adequacy decision or one of the appropriate safeguards prescribed by law is applied. Where standard contracts are used, execution and regulatory-notification requirements are fulfilled. Statutory exceptions are considered only for incidental transfers where their conditions are met. Information about recipients, destination countries and applicable safeguards may be requested from destek@eniyisi.app.
6. Retention and disposal
There is no single retention period for all data. Fiscal documents within Turkish Tax Procedure Law Article 253 are kept for 5 years starting with the following calendar year. Documents within Turkish Commercial Code Article 82 follow the applicable 10-year period and statutory start rule. Sole-proprietor status alone does not make every record subject to 10 years. Applicable distance-contract information/performance and transaction evidence follows the 3-year duty; disposal logs follow the minimum 3-year Turkish rule. These periods do not apply to every profile, coordinate or message. Account deletion keeps a separate minimal administrative history including name, email, account type, former account identifier and creation/deletion times; deleting the account does not automatically anonymise that history. Account, service-request, message, verification and security records are assessed by purpose, the account/service relationship, concrete claims and applicable duties; when grounds end, erasure, destruction or anonymisation must be performed. Account deletion does not mean instant physical erasure at every supplier or backup. Statutory preservation, recipient notifications and reapplying erasure decisions after recovery require separate handling.
The Supabase project infrastructure is hosted in the Frankfurt (eu-central-1) region. Google Analytics is configured to retain event data for 2 months and user data for 14 months; Brevo transactional email records are configured for 1-month retention. Aggregated reports and service providers' mandatory technical and security records may be subject to different retention periods. Retention settings are reviewed regularly, and erasure requests are coordinated with the relevant service providers.
7. Rights under Turkish law
Under Article 11 you may learn whether your data are processed, request information, learn the purpose and whether use complies with it, learn domestic/foreign recipients, request correction of incomplete/inaccurate data, request erasure/destruction under statutory conditions and notification of corrections/disposal to recipients, object to an adverse outcome based exclusively on automated analysis and seek compensation for unlawful processing.
8. Requests and complaints
Apply in writing to the postal address in section 1, from your registered email to destek@eniyisi.app, or by another valid Turkish application method. An active account is not required; identity checks must be necessary and proportionate. Requests are answered without undue delay and within 30 days under Turkish law. Where GDPR applies, the one-calendar-month rule and, when its conditions are met, reasoned extension and notification rules also apply. Requests are normally free; lawful exceptions must be justified. Under Turkish Article 14, complaints may be made within 30 days of learning the response and in any case within 60 days of application. GDPR supervisory complaints and judicial remedies remain available.
9. GDPR and updates
The GDPR applies where its territorial and material requirements are met for the relevant processing activity. In that context, the rights of access, rectification, erasure, restriction, portability, objection and complaint may be exercised subject to their applicable conditions. This notice is updated when processing activities change materially; additional information and consent are obtained where legally required.
10. Provider verification documents
Uploaded tax, professional qualification or activity documents, applicant name, profile/business information, document type and review result are assessed by authorised reviewers. Files are not published on public profiles; the verification status may be displayed. Purposes include accurate provider information and prevention of misleading profiles/fraud. Processing is assessed activity by activity under necessary contractual steps, a specific legal obligation or balanced legitimate interests. Avoid unnecessary identity numbers, sensitive data and third-party information.
11. GDPR legal bases and provision of information, where applicable
Processing genuinely necessary for membership, requests/quotations and purchases is assessed under Article 6(1)(b); optional analytics, advertising and Meta measurement rely on Article 6(1)(a) to the extent based on separate consent. Necessary limited security, fraud-prevention, genuine transaction evidence/claims and Turkish commercial/fiscal record activities are assessed under Article 6(1)(f), with a fundamental-rights balancing assessment. A Turkish statutory duty is not automatically an Article 6(1)(c) basis: applicable EU/Member State law and Article 6(3) conditions are required. Article 21 objections to legitimate-interest processing and direct-marketing objections remain available. Required fields are identified for the relevant transaction; missing necessary information may prevent the relevant membership/order/service transaction, while refusal of optional ads/analytics does not prevent core services. Category/region matching and suggestions may be automated; objections and human review may be requested where applicable. GDPR third-country transfers additionally require the applicable Chapter V adequacy/safeguard conditions; blanket KVKK consent does not replace these. Ask destek@eniyisi.app about the mechanism and an accessible copy. This notice does not assert that an unverified transfer arrangement has been established.
12. Short-link, badge and category-suggestion records
Profile short-link and opening-count data are processed to operate the link, provide security and produce technical statistics. Existing account data such as ratings, review counts, completed jobs and account age may be used to calculate profile badges and achievement indicators. Category suggestions and review outcomes are processed to improve the service catalogue and decide the suggestion. These activities are assessed individually under contractual necessity or balanced legitimate interests, as applicable.