Local-First & Data Minimization
CRASGO is an iOS application designed to keep personal financial management as local, private, and under the user's control as reasonably possible. CRASGO does not operate a centralized user financial database for the purpose of collecting your financial records, creating advertising profiles, or tracking your financial behavior.
This Privacy Policy explains how information is processed when you use the CRASGO mobile application and related CRASGO web services, where such information may be stored, when it may leave your device, and what controls are available to you.
1. About CRASGO
Application: CRASGO
Developer / Data Controller: MUKHAMMAD AZIMOV
Contact: muhammed.azimov@hotmail.com
In this Policy, "CRASGO," "we," "us," or "the Application" refers to the CRASGO application and related services operated by the Developer.
2. Information Processed by CRASGO
The information processed by CRASGO depends on how you use the Application and which features are available or enabled.
2.1 Financial Records
Financial information that you voluntarily enter into CRASGO may be stored locally on your device. This may include:
- income records;
- expense records;
- transaction dates;
- amounts;
- currencies;
- categories;
- payment status;
- collection status;
- budget information;
- installment information;
- recurring payment information;
- credit card names or nicknames;
- statement dates;
- payment due dates; and
- card limits and similar user-entered financial management information.
CRASGO is not designed to require or collect your online banking password, banking login credentials, card PIN, CVV/CVC code, or full payment card number.
Information that you voluntarily enter into CRASGO may nevertheless constitute personal or financial information. CRASGO is therefore designed to handle such information with appropriate care.
3. Are Financial Records Sent to CRASGO's Central Servers?
CRASGO is designed around a local-first architecture.
Financial records within the Application are primarily stored in local storage on your device. CRASGO does not operate its own centralized backend or financial user database for the purpose of collecting these records.
Where Apple's iCloud/CloudKit infrastructure is available and used by the Application, application data may be synchronized with the Private Database associated with your iCloud account.
This synchronization is not designed as a manual "upload to CRASGO server" feature. Where iCloud/CloudKit is available, synchronization may occur through Apple's infrastructure and CRASGO's CloudKit integration. Where iCloud is unavailable, the Application may continue to operate using local storage.
The Developer does not operate a system designed to retrieve users' Private CloudKit financial records into a CRASGO-controlled centralized financial database.
4. Local Storage and Security
CRASGO stores financial records locally using SwiftData-based persistent storage.
CRASGO's local persistent data files are configured to use Apple's iOS Data Protection mechanisms, including the .completeUnlessOpen file protection class where supported by the relevant storage implementation.
CRASGO may also obscure sensitive screens when the Application enters the background or appears in the application switcher.
This visual protection is not encryption. It is a user-interface security measure intended to reduce the risk of sensitive information being visible to people around you.
CRASGO uses security mechanisms provided by the operating system together with application-level safeguards. However, no method of digital storage or transmission can provide an absolute guarantee of security.
5. Face ID and Touch ID
CRASGO may use Apple's LocalAuthentication framework for application locking and security features.
CRASGO does not:
- read Face ID or Touch ID biometric templates;
- transmit biometric templates to CRASGO servers; or
- store biometric templates in a CRASGO database.
Biometric authentication is performed by Apple's operating system. CRASGO receives the result necessary to determine whether authentication succeeded.
6. Receipt and Document Scanning
CRASGO may use Apple's Vision/OCR technologies on supported devices to recognize information contained in receipts or documents.
Under CRASGO's current architecture, OCR processing is performed on-device.
Receipt images and information derived from OCR may be stored on your device when you use the relevant feature.
CRASGO does not currently use an external artificial intelligence, OCR, or image-analysis service to process your receipt images.
Where application data is synchronized through iCloud/CloudKit, receipt-related data stored by the Application may also be synchronized through Apple's CloudKit infrastructure.
7. iCloud and CloudKit
CRASGO supports Apple's CloudKit infrastructure for application data synchronization.
Where iCloud is available, application data may be synchronized within the Private CloudKit Database associated with your Apple/iCloud environment. Accordingly:
- application data may be stored in a Private CloudKit Database;
- CRASGO does not create its own centralized financial database for this purpose;
- availability depends on your Apple account, iCloud configuration, device, network connectivity, and Apple's services.
Where iCloud/CloudKit is unavailable, CRASGO may continue operating with local storage.
Apple's iCloud and CloudKit services are subject to Apple's own terms and privacy practices.
8. Exchange Rates
CRASGO may retrieve current exchange-rate information from external exchange-rate services for currency conversion features. The current application architecture may use services such as:
open.er-api.comapi.frankfurter.dev
These requests are designed to retrieve exchange-rate data.
CRASGO is not designed to send your transaction history, income, expenses, card-management information, budgets, or other user-created financial records to these exchange-rate providers.
Exchange-rate data may be cached to reduce unnecessary network requests.
Third-party exchange-rate providers may have their own terms and privacy practices.
9. Widgets and App Intents
CRASGO may use iOS WidgetKit and App Intents. As a result, certain financial information may be displayed or made actionable through Apple system surfaces, including:
- Home Screen widgets;
- Lock Screen widgets; and
- supported system actions or App Intents.
For example, an upcoming payment or payment amount may appear in a widget.
You should consider that another person with physical access to your device may be able to see information displayed on such system surfaces. Visibility depends on your device and iOS privacy settings.
10. Notifications
CRASGO may use local notifications to remind you about payments and other financial events.
Depending on the feature, notifications may contain information such as:
- a payment title;
- an amount;
- a card name or nickname;
- a statement date; or
- a payment due date.
CRASGO's current architecture uses local notifications rather than a CRASGO-operated remote push-notification server for these reminders.
Whether notifications appear on your Lock Screen depends on your iOS notification settings.
11. Advertising, Tracking and Profiling
CRASGO does not currently use third-party advertising or behavioral analytics SDKs.
The current application architecture does not include SDKs such as Firebase Analytics, Google Analytics, Meta SDK, AppsFlyer, Adjust, Mixpanel, Amplitude, RevenueCat, Superwall, or similar third-party tracking and analytics SDKs.
CRASGO does not use your financial records to create advertising profiles and does not sell or rent your financial records to advertisers or data brokers.
12. User Accounts
The current version of CRASGO does not operate a traditional centralized CRASGO account system based on a CRASGO username and password.
You do not need to create a separate CRASGO account to use the Application.
Where iCloud synchronization is used, Apple's account and iCloud infrastructure may be involved.
13. Data Export
CRASGO may allow you to export certain financial records in formats such as CSV or PDF.
Exports may be shared using the iOS Share Sheet.
CRASGO does not automatically upload these generated files to a CRASGO server or automatically send them to a third-party service.
You decide which application or service receives an exported file. Once you choose to share information with a third-party application or service, that third party's privacy practices apply.
14. Data Deletion
CRASGO allows supported user-created records to be deleted individually or through available bulk operations.
The current version may not contain a dedicated universal "Delete All Data" or "Reset Application" control.
Deleting local application data and deleting data synchronized through iCloud/CloudKit may involve different processes.
Apple's iCloud and device-management mechanisms may therefore also be relevant to the lifecycle of synchronized data.
15. CRASGO Website
The CRASGO mobile application and CRASGO website are separate services.
Where the CRASGO website provides beta/TestFlight registration, feedback, or contact forms, information you voluntarily submit may include:
- your name;
- email address;
- device model;
- feedback; and
- information related to beta testing.
Website-submitted information is separate from the locally stored financial records within the CRASGO mobile application.
16. Support Requests
If you contact CRASGO at muhammed.azimov@hotmail.com, your email address and the contents of your message will be received and may be processed for the purpose of responding to your request.
Please do not include banking passwords, full payment card numbers, CVV/CVC codes, PINs, or other unnecessary confidential financial credentials in support communications.
Where CRASGO generates a support email draft, technical information such as the application version/build, iOS version, device model, or locale may be included in that draft for troubleshooting purposes.
17. Third-Party Services
CRASGO may interact with platform or network services required for particular features.
These may include Apple technologies such as iOS, LocalAuthentication, Vision, SwiftData, iCloud/CloudKit, WidgetKit, App Intents, and system sharing features, as well as external exchange-rate providers.
Such providers may process information under their own terms and privacy policies.
18. Sale of Personal Data
CRASGO does not sell or rent users' financial records, use them to build advertising profiles, or intentionally provide them to data brokers.
Data processing independently performed by Apple, a service provider, or a third-party application that you choose to use is subject to the applicable provider's own practices and terms.
19. Children's Privacy
CRASGO is not designed for the purpose of knowingly collecting personal information from children.
Users must comply with applicable age requirements and relevant Apple account rules.
20. International Users
CRASGO is intended for users in multiple countries and jurisdictions.
Different privacy and data protection laws may therefore apply depending on where you live.
Users in Türkiye may have rights under Turkish Personal Data Protection Law No. 6698 ("KVKK").
Users in the European Economic Area, the United Kingdom, and other jurisdictions may have additional rights under applicable data protection laws.
Nothing in this Privacy Policy is intended to waive mandatory rights granted to you by applicable law.
21. Changes to This Privacy Policy
CRASGO's features, technical architecture, and legal obligations may change. We may update this Privacy Policy accordingly.
Where appropriate or legally required, material changes may be communicated through the Application or website.
The "Last Updated" date at the beginning of this Policy indicates the latest revision.
22. Contact
For privacy, data protection, or personal-data questions:
Developer / Data Controller: MUKHAMMAD AZIMOV
Email: muhammed.azimov@hotmail.com
Users in Türkiye may also exercise applicable rights as described in the KVKK Information Notice.
23. Effective Date
This Privacy Policy is effective as of September 27, 2026.
Where applicable law requires separate consent for a particular processing activity, presentation or acceptance of this Privacy Policy does not replace such consent.

