1. Scope
This notice describes personal-data processing in the Paymoria iPhone/iOS and Mac/macOS apps. Providing a privacy notice does not, by itself, obtain explicit consent.
2. Categories of data
Depending on the features you use, Paymoria may process:
• Personal financial records you create, including assets, debts, income, expenses, transactions, credit cards/overdrafts, budgets, rent, plans and goals.
• Names, descriptions, categories and notes you assign to those records.
• Settings such as app language, notification preferences and primary currency.
• Current App Store storefront region and currency read through Apple StoreKit and evaluated in memory for service availability and suitable initial setup suggestions. This current storefront information is not persistently stored on the device for that purpose or used to build a lasting customer profile or track advertising/marketing activity. Separately chosen app preferences include number format and response language.
• Date ranges, income types, excluded record identifiers, amount basis, rates, credits and additional-tax definitions for optional tax estimates, together with card-visibility and liability-display preferences.
• StoreKit-verified product/subscription access, purchase transaction identifiers, product identifiers, expiry and any grace-period information, and test/production environment.
• Technical identity and subscription-matching information, including an Apple CloudKit web authentication token, CloudKit user-record identifier, and Paymoria-issued account identifier/appAccountToken.
• The province identifier used to request districts when you select a Turkish province in a property form.
• CloudKit workspace, share, member and shared financial records if you use Paymoria Family.
• Limited technical information and error conditions needed for safe, correct operation.
• For optional receipt scanning, the image you select or capture with the camera and the text, description, amount, currency and date candidates temporarily extracted on your device. On-device processing of the image and raw text is separate from storing the expense record you confirm; section 6.2 explains the scope.
Paymoria's core purpose is not to create advertising profiles.
3. Purposes
Data may be processed to provide the financial tracking and calculations you request; show assets and debts; manage payment and income plans, budgets and goals; provide optional reminders; determine regional service availability and initial setup suggestions; verify subscription access; operate Family sharing; maintain data integrity and security; and resolve technical problems.
4. Sources and collection
Data is obtained electronically, mainly from information you enter; records and preferences you create in the app; current storefront region/currency and verified subscription information from Apple StoreKit; Apple iCloud/CloudKit when personal synchronization or Family sharing is used; technical connections to Paymoria's proxy/backend and third-party market-data services when market data is used; Apple CloudKit and Paymoria's subscription server for necessary identity/access checks; and TürkiyeAPI when province/district selection is used.
When receipt scanning is selected, the image comes from Photos or an image file you choose, or from the supported iPhone/iPad camera flow only after camera permission and your capture action. Scanning is optional; expenses can also be entered manually.
5. Legal grounds
The applicable grounds under Türkiye's Personal Data Protection Law No. 6698 (KVKK) depend on the processing activity. These may include necessity directly related to entering into or performing a contract, compliance with a legal obligation, the controller's legitimate interests where those interests do not harm fundamental rights and freedoms, and explicit consent for optional activities where the law requires it.
Where explicit consent is required, it is obtained through a separate user action, apart from this notice.
Where the GDPR or UK GDPR applies to a processing activity, its lawful basis is also assessed under that law: performance of a contract for the core financial tracking and subscription operations you request; legal obligation where an applicable law requires processing; legitimate interests balanced against your rights and freedoms for purposes such as security and preventing misuse; and consent for optional sharing that requires separate permission. The applicable basis depends on the purpose and whether the necessary conditions are met.
A sharing permission or acceptance of this notice does not automatically replace any separate conditions or safeguards required for an international transfer.
6. Personal financial data and iCloud synchronization
Core personal financial records may be stored on the device in a SwiftData-based database. If you enable “Sync with iCloud,” personal transactions, assets, debts, payment/income plans, budgets, goals, savings preferences and investment history are sent to a private CloudKit space for the same iCloud account. This personal sync space is not shared with Family members. iPhone and Mac apps using the same iCloud account and CloudKit environment can access it. Synchronization requires connectivity. Offline changes or simultaneous changes on two devices may be delayed or produce a conflict you need to resolve. Financial datasets are not automatically appended together. Market-price caches, window layout, notification permissions and device test options are not part of personal synchronization.
Up to four local recovery copies may be retained during synchronization; these are excluded from device backup. Account deletion removes the personal financial content in iCloud, records on this device and sync recovery copies. A technical deletion marker containing no financial content remains in the private iCloud space to prevent an old offline device from uploading deleted records again. Other devices learn of the deletion when they reconnect and show a step to clear their old local records, including app-created recovery copies. Independently exported copies must be removed separately. Paymoria applies iOS file-protection mechanisms to local financial files.
Before an app database migration, technical backups may be created in the device's Application Support directory. They are marked as excluded from iCloud device backup. Verified update backups are retained for at most the last three builds. Incomplete or unverified copies may be excluded from automatic cleanup for recovery purposes. These backups are not used for advertising or marketing.
6.1. Device-specific calculation and display preferences
The Income and Tax Plan scenario's date range, selected income types, excluded record identifiers, rates, credits and additional-tax definitions are stored in device preferences in this version. These settings, card visibility and liability-display choices are not part of Paymoria's personal CloudKit financial synchronization and may differ between the same person's iPhone and Mac. This statement does not describe the operating system's separate device-backup behavior.
Tax estimates are calculated on the device from existing financial records; income amounts, rates and results are not sent to a separate tax-calculation server for that calculation. Processing of the underlying financial records through personal iCloud sync or Family sharing follows the other sections of this notice. Hiding the card does not delete records or scenario settings. Account deletion clears app preferences; independently exported copies require separate management.
Theme and light, dark or system appearance preferences are also stored in this device's app settings. Classic is the default; other themes are optional choices. These appearance preferences are not included in Paymoria's personal financial synchronization and are not sent to Paymoria's server, OpenAI or RevenueCat. Choosing a theme does not change amounts, currencies, bank terms or tax rules. The operating system's separate device-backup behavior still applies.
6.2. Optional receipt scanning
The receipt image is read on your device using Apple Vision. A temporary working copy may be resized for text recognition; the original image file you selected is not changed. This scanning flow does not send the image or raw OCR text to Paymoria's server, OpenAI, RevenueCat or analytics services, and does not create a separate permanent receipt-image or raw-text archive. The camera flow does not automatically save the captured photo to your library. Storage of your source photo in Photos, iCloud Photos or the file provider you selected remains subject to that service's own terms.
You can check and edit the description, amount, currency and date. You are asked to select uncertain details. If the receipt currency differs from your record currency, you enter the amount actually charged in your record currency; this flow does not apply an automatic exchange-rate or bank-rate estimate. Scanning or confirming the extracted details alone does not create a financial record or change a balance.
Only when you press Save in the normal expense form are the description, amount, date, note and other expense fields you confirm stored as an ordinary financial record. Use of that record in personal iCloud synchronization, Family sharing you separately choose, or financial-summary processing you permit follows the relevant sections of this notice. You can change camera permission in system settings. On Mac, this feature uses a photo or image file you select; camera capture is not provided.
7. Paymoria Family and CloudKit
Family sharing is optional and requires an Apple iCloud account. Family data may be stored in Apple's private/shared CloudKit databases. Sharing is not configured as public.
Sharing covers records created in, or explicitly added to, the Family workspace. Enabling personal iCloud sync does not open your personal ledger to another member. This version does not send new personal-data sharing or personal-record contribution requests through the retired “Finance Together” feature.
For personal-record copies shared through older versions of that feature, the current app runs a cleanup when connectivity and verified Family access are available. It clears personal document content, previous document copies and edit/share-request content from the relevant shared CloudKit records. Network or permission errors mean cleanup is incomplete and may be retried. Original personal records and shared Family workspace records are not deleted by this cleanup. Transaction and recovery records necessary to maintain the consistency of financial operations already started may be retained.
Both devices should use the current version. Older-app behavior, copies already stored on other devices and exported documents cannot be fully removed remotely by this update. Retiring the feature does not itself remove Family membership or access to shared workspace records.
A local cache may support offline viewing of Family records. It is scoped to the account and workspace and cleared on account/workspace sign-out or verified removal of access. A local recovery journal for financial creations with an uncertain outcome may be kept longer to reconcile that outcome within the same account/workspace. Do not assume that this removes all data on another member's device or in their exported copies.
Invited people who accept the CloudKit share can access and change shared records within the permissions granted. Consider the consequences of granting access.
If the Family subscription is inactive, the current version restricts creation and editing of shared records while preserving viewing for verified CloudKit members. This does not itself delete the workspace or Family data. Deletion, removal of sharing, iCloud-account changes and CloudKit lifecycle rules apply separately.
8. Market-data infrastructure
The app may request foreign-exchange, gold and other supported prices through Paymoria's HTTPS proxy/backend. Financial ledger records are not intended to form part of a market-price query.
The proxy/backend may process connection and server logs needed for secure operation and troubleshooting. Data minimization should apply; unnecessary financial content should not be collected in these logs.
9. Turkish province and district lists
When you select a province in a property form, the app may retrieve districts directly from TürkiyeAPI (api.turkiyeapi.dev). The request contains the selected province's identifier; this feature neither requests nor sends the device's GPS location. District lists are cached on the device. The provider may see connection information such as an IP address.
10. Identity and subscription verification
When creating a Family workspace or changing shared records, the server checks CloudKit access and the owner's current subscription. The workspace record/zone identifiers and owner's CloudKit identifier are sent for this purpose. The server requests technical system information and schema version from CloudKit; it does not request income, expense, balance, title or note fields in that query. The database stores the workspace-to-owner account mapping, test/production subscription environment and last verification time. This version has no automatic age-based cleanup for these mappings. The web authentication token sent in this flow is not stored in the database.
The current app enforces access checks within its operations; it does not automatically revoke CloudKit sharing permissions. To remove access through an older app or another client, the CloudKit share must also be revoked.
After the current Terms and this notice have been acknowledged in the app, identity matching may occur during purchase, purchase restoration, Family workspace creation/editing or an AI request separately authorized by you. Launch alone does not create a server account. When iCloud is available, the app communicates with Paymoria's HTTPS subscription service on Cloudflare Workers. Authentication sends Apple's CloudKit webAuthToken and test/production environment; subscription verification also includes the StoreKit transaction identifier and environment. Acknowledging this notice does not replace separate explicit consent where required.
The service may return a Paymoria account identifier, appAccountToken, CloudKit user-record identifier, product/subscription status and duration. These technical values match identity to entitlement. The appAccountToken may be derived using a server secret from verified iCloud identity and environment. It can be derived again if you explicitly recreate an account using the same identity; no user-specific recovery record for the deleted account is retained on the server for this. The token is sent to Apple purchase records and may remain there. Identity and access-check request bodies do not contain ledger records. Optional AI requests follow the separate flow below. CloudKit webAuthToken is an authentication credential and should not be included in support requests or user-visible logs.
StoreKit determines subscription and any trial eligibility. For an eligible account, Apple's purchase sheet shows the active offer's duration, post-trial price and renewal terms. Neither the device nor Paymoria's server creates trial rights independently of Apple. Paymoria does not collect payment-card numbers or security codes; Apple manages payment methods.
RevenueCat subscription processing
After you acknowledge this policy version in the app, your Apple-verified subscription transaction may be sent through Paymoria's server to RevenueCat, Inc. The request contains only a pseudonymous customer identifier derived from a random Paymoria account identifier, Apple's signed purchase/renewal record, product identifier and iOS/Mac platform. The Apple record may include price, currency, storefront, transaction dates and subscription status. These data support verification, restoration, renewal/cancellation tracking and assessment of subscription-transaction reliability. A pseudonymous identifier is not anonymous data.
Income, expenses, assets, debts, Family budgets, descriptions and documents from your ledger are not included, nor are email, phone number or the CloudKit authentication token. This version does not use RevenueCat's device SDK; the connection originates from Paymoria's server rather than the device's IP address. Older app versions do not initiate this new transfer. A RevenueCat error does not remove Apple-verified access or require another purchase.
RevenueCat may use infrastructure in the United States and other countries. Subscription records are processed for the subscription lifecycle and applicable retention obligations. Privacy requests and account deletion include this provider. Server-side account deletion is not considered complete until deletion of the RevenueCat customer record is verified. Apple's own purchase records and legally required retention are considered separately. Provider information: https://www.revenuecat.com/privacy/ and https://www.revenuecat.com/dpa/
10.1. Report history and optional backups
Report history is stored in protected files on the device, separated by iCloud identity; reports are not automatically synchronized to the cloud. You can delete reports from history or export a JSON backup to a Files location you choose. The backup includes report content and a hashed account identifier and is not separately encrypted by the app. It can be restored only under the same iCloud account. Deleting your app account does not delete exported PDF or JSON files; manage them where you saved them. If you choose a cloud provider in Files, that provider's terms also apply.
10.2. Optional OpenAI suggestions
With separate sharing permission, period income, spending, remaining planned expenses and days remaining; coded budget/spending-reduction scenarios; total recorded personal assets, debts and cash; expected receipts and remaining planned payments; and counts of missing values or uncertain payment matches are sent through Cloudflare to OpenAI. Data also includes the current and next three budget periods' start/end dates, planned income/payments, remaining receipts/payments, potential income, ending-installment totals and budget limit/spent/planned allocations. Codes and numerical amounts of on-device decisions are added for prioritization; individual event dates and personal names are not included in that decision catalog. Balance and monthly-rate details for up to 12 personal debts with the highest recorded rates may be included for comparison; total debt is not limited to those 12. The chosen focus—balanced, spending or debt—is included. You are not asked to complete a cash form or choose a card. These summaries are personal financial data; removing names does not make them anonymous.
A report request may also send limited regional service scope derived from the current App Store storefront, response language, number format, calculation currency, and technical context indicating that tax and bank terms depend on the relevant records or information you provide to Paymoria's server. The raw App Store storefront identifier is not added to this report context. The calculation currency sent is your independently chosen record currency, not the storefront currency. Service scope is not interpreted as tax residency or bank contract terms and is not used to build a lasting customer profile. An unverified storefront region is not treated as verified. The server restricts AI features according to the supported service scope. When a neutral informational report is available outside Türkiye or for an unverified storefront, the server processes the financial summary without sending it to OpenAI or using the AI allowance.
This App Store-derived service-scope metadata is used for the request's availability check and is not added to AI-provider content or cache matching. Financial summaries and reports remain subject to the processing, retention and provider practices described below.
Category/debt names, transaction descriptions, notes, bank/card numbers, documents and Family workspace records are not added to the OpenAI request. iCloud identity is verified on Paymoria's server; neither the identity token nor Paymoria account identifier is sent to OpenAI. This explicit action may create a server account through the existing identity infrastructure if necessary. Launch does not trigger an AI request.
OpenAI processes these summaries to produce suggestions. Verified Family membership and the owner's active subscription may be checked on the server; workspace identifiers are not sent to OpenAI. Completed reports are stored with application-level encryption in Cloudflare D1 and may be reopened for 24 hours with the same account and inputs. Expired content is cleared by scheduled cleanup or a later report request. If cleanup fails, the content may remain encrypted until cleanup succeeds, but expiry prevents renewed access. Usage control retains a pseudonymous account hash derived with a server secret from iCloud identity/environment, an input hash, period, timestamps and processing status. Records older than 62 days are deleted by scheduled cleanup or a later report request; cleanup may be delayed if the task is disabled or fails. Account deletion also removes that account's server report and usage records. Financial request/response text and identity tokens are not written to server logs; technical error codes and model token counts may be logged. Cloudflare and OpenAI may process connection/security data under their service terms.
OpenAI requests use store:false; this does not eliminate all security logging. According to OpenAI's API documentation, API data is not used for model training by default, and abuse-monitoring logs may be retained for up to 30 days, subject to legal requirements. Provider information: https://developers.openai.com/api/docs/guides/your-data
Processing may take place outside Türkiye. Before first use, the data categories and recipient are explained. Report and coach permissions are separate and remembered for this device and iCloud account. Data is sent only when you initiate an action such as Create Report or Send. Coach permission also covers your messages and limited conversation history; messages may contain personal information. Turn off permission in Settings > AI and Data Sharing. Permission is requested again if the account or scope changes. On-device suggestions remain available without permission. Canceling a request in the UI cannot retrieve data already delivered to a provider. Withdrawing permission stops future sharing; it does not itself delete previously shared data or report history. Send rights requests to the privacy contact.
11. Apple services and other recipients
App Store/StoreKit subscription operations use Apple infrastructure. Personal sync and Family sharing also use Apple iCloud/CloudKit. Apple and its infrastructure providers may process the data necessary to operate those services.
Market-price queries may be shared with Paymoria's proxy/backend and the relevant market-data provider. TürkiyeAPI receives technical district-list requests; Paymoria's Cloudflare Workers subscription infrastructure receives technical identity/access-check data. Connection and server-log processing by these services is also relevant to the data-processing assessment.
12. International transfers
Because Apple iCloud/CloudKit, App Store/StoreKit and other infrastructure services operate globally, personal data may be processed outside Türkiye or transferred abroad. International transfers must satisfy Article 9 of Law No. 6698 and the conditions and safeguards in applicable implementing rules.
Changes to a service or data flow require a corresponding update to the transfer assessment and this notice.
13. Notifications
Notification permission is optional. Permission for visible notifications is requested when you want to use a notification feature and can be disabled in system settings.
The option to show sensitive financial details in notification text may be off by default. Enabling it may expose more detailed financial information on the lock screen; consider the privacy of your device.
Technical remote-notification registration used for CloudKit changes is not permission to send marketing messages.
14. Subscription data
Paymoria checks StoreKit-verified subscription/product entitlements to determine paid access. Its own application logic is not designed to collect payment-card numbers or App Store payment credentials. Apple processes payments.
15. Advertising, profiling and data sales
Google app-usage analytics is disabled in this version, and app-usage measurement data is not sent. If enabled later, its provider, data scope and retention will be disclosed; measurement will not begin without separate permission.
Paymoria is not designed to sell personal financial records for advertising or create behavioral advertising profiles. Before adding advertising, profiling, a new analytics/attribution SDK or another use of data, the relevant flow, App Store privacy disclosures and this notice must be updated.
16. Retention, deletion and subscription expiry
Local personal financial records may remain on the device until you delete them, remove app data or the relevant technical lifecycle removes them.
Verified migration backups are limited to the last three builds. Incomplete/unverified copies are not automatically deleted; they require separate cleanup when no longer needed for recovery.
Apple's CloudKit sharing/retention lifecycle applies to Family data. Subscription expiry does not by itself delete Family records, but it restricts creation and editing of new shared financial records.
Completed Family plans may remain marked complete to allow reversal consistent with the payment record. When a Family transaction or plan is deleted, CloudKit may retain workspace, record and creator identifiers, technical creation/modification timestamps and a deletion marker to prevent reprocessing and concurrent balance errors. App fields such as amount, title and note are cleared. These technical deletion markers currently have no automatic age-based cleanup. CloudKit system fields and provider-side retention also apply.
Start account deletion in Settings > Delete My Account. iCloud identity is verified again. Financial records, app-created migration backups and caches on this device are cleared; server account, subscription-verification records and Family-owner mappings are removed. A network or permission failure means deletion is not complete; a protected local deletion journal supports retry. The server's deletion-job record is removed once the job finishes.
Deleting a Family workspace you own removes all members' access. If you belong to another person's workspace, your records' titles, names, notes and location descriptions, and copied titles/notes traceable to you through record links, are cleared. In-app member identifiers are replaced with a generic value and you leave the share. Shared amounts, transaction dates, record links, category/subcategory classifications and valid investment-valuation history remain. Classifications include custom category names you entered. This process does not delete or anonymize all shared financial records.
The app cannot clear CloudKit system fields such as creator and last-modifier identifiers. It cannot fully remove information another member wrote independently or copied to unrelated records, their earlier downloads or exported documents. Deletion does not physically destroy every provider backup.
Account deletion does not cancel your Apple subscription. The app directs you to Apple subscription management. Verified older purchases may be migrated during deletion to a reproducible subscription-matching token. If you explicitly recreate an account with the same iCloud identity, Apple-verified purchases can be linked again on another device. This does not restore deleted financial records or the Family workspace or erase Apple's purchase history.
If you choose, an encrypted recovery credential for older purchases can be kept only in this device's Keychain. It contains no financial records, does not itself grant a subscription and is not transferred to another device. Turning off the option removes it. A credential may be needed for a purchase deleted in an earlier version that had not been migrated to reproducible matching. The server does not retain a deleted user's recovery credential.
Data that must be retained by law may be kept for the relevant statutory period. When retention is no longer necessary, applicable deletion, destruction or anonymization procedures apply.
17. Security
Paymoria uses data minimization, HTTPS, iOS file protection, local migration backups, Apple platform security, private/shared CloudKit spaces and an approach that keeps production market-provider keys out of the client app.
Critical shared financial operations may use atomic CloudKit saves and concurrent-change checks to maintain integrity.
No electronic system can guarantee absolute security.
18. Your rights and requests
You can exercise the rights under Article 11 of the KVKK by contacting the data controller. A request may need enough information to securely verify that it comes from the person concerned.
Privacy/data-protection requests: yusuf@paymoria.app
Other request methods allowed by law remain available. Necessary, proportionate additional identity-verification information may be requested depending on the request.
18.1. Rights that may apply in the EEA and United Kingdom
Applicable privacy rights are not determined solely by your App Store storefront. To the extent the GDPR or UK GDPR applies, you may have rights to be informed; access your personal data and obtain a copy; correct inaccurate information; request erasure or restrict processing in certain circumstances; obtain a portable copy of data you provided where automated processing is based on consent or contract; and object to certain processing based on legitimate interests. You can withdraw consent for future consent-based processing without affecting the lawfulness of processing before withdrawal. Rights and statutory exceptions apply according to the processing involved.
The controller's identity and address in Türkiye are in section 21. You can send requests to yusuf@paymoria.app; other request methods available under applicable law remain available. Explaining the scope of your request and relevant country helps us assess it; necessary and proportionate identity verification may be requested. Requests are handled under the applicable legal conditions and deadlines. GDPR and UK GDPR rights requests generally receive a response within one month, with extensions or exceptions only where the law allows.
You may also complain to a competent data-protection supervisory authority. In the EEA, this may in particular be the authority where you habitually live, work or where the alleged infringement occurred; in the UK, you can contact the Information Commissioner's Office (ICO). The authority’s complaint procedures and jurisdiction rules also apply.
Paymoria does not initiate payments from your bank account or decide credit or investment eligibility. Calculations and optional reports provide information and scenarios based on your records; they do not automatically execute a bank transaction or financial decision.
18.2. Rights that may apply under US state laws
If the relevant state law applies to Paymoria and the processing concerned, you may have rights to access, correct or delete personal data; obtain a portable copy; and opt out of sale, sharing, targeted advertising or certain profiling uses specified by that law. Some laws also provide rights to appeal a request decision and not be discriminated against for exercising privacy rights. Scope, applicability thresholds and exceptions vary by state. You can send your request and relevant state to yusuf@paymoria.app; other statutory request and appeal routes remain available. This explanation does not mean every state law automatically applies to every user or processing activity, or that this version carries out sale, targeted advertising or profiling.
19. Notice and explicit consent
This document is a privacy notice under the KVKK. Reading it or accepting the Terms does not automatically give consent to a separate activity that requires explicit consent.
An optional future feature requiring explicit consent will use a separate explanation and user action.
20. Changes
Material changes to data flows, providers or legal requirements may result in a new policy version and update date. An updated notice is shown where necessary, and App Store privacy disclosures are updated.
21. Controller and contact
Data controller: Yusuf Orhan Yerebasmaz
Business: Yerebasmaz Gayrimenkul
Address: Fenerbahçe Mah. Fener Kalamış Cad. Ünver Apt. A Blok No: 21 İç Kapı No: 1, Kadıköy / İstanbul, Türkiye
Privacy/data-protection inquiries: yusuf@paymoria.app
Support: support@paymoria.app
Website analytics and browser storage
This section applies to paymoria.app, separately from the app. The site uses Cloudflare for delivery; technical connection information may be processed to deliver and secure pages. Any Cloudflare infrastructure measurement is separate from Google consent. See Cloudflare’s Privacy Policy. Optional Google Analytics measurement begins only after you select Allow in Analytics preferences. Rejecting or closing that panel does not grant permission, and the Google measurement library is not requested before permission. You can withdraw permission from the footer at any time.
When permitted, measurement uses an allowlisted page path and fixed page title. Query strings, fragments and the referring page are removed from the page data sent by our script. The script does not send your app account ID, financial records or form contents. Google still receives technical connection and browser information when its service is contacted; this is not anonymous simply because direct identifiers are omitted. Google signals, advertising personalization and advertising storage are disabled by our configuration.
The site configures analytics cookies to expire after 30 days without refreshing that expiry on each visit; browser restrictions may shorten this period. Your permission choice and its timestamp are kept in this browser’s local storage for up to 180 days. Withdrawing permission removes the site’s analytics cookies and stops subsequent measurement. It does not retroactively delete measurements already processed by the provider. Website measurement and app account deletion are separate; contact yusuf@paymoria.app for a privacy request.
Google services may process data outside Türkiye. Enabling optional analytics is not a statement that data stays in Türkiye or that every international-transfer requirement is satisfied. See Google’s Privacy Policy and Google Analytics cookie information for provider practices. The site’s settings above override the default cookie duration.